Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The text on the King of the Swamp does not say that it can be used instead of a specific monster, it says that it can be substituted for **ANY** fusion material monster. If you know English, you should know what does the word "any" mean:
1.
used to refer to one or some of a thing or number of things, no matter how much or how many.
2.
whichever of a specified class might be chosen.
Knowing how your cards work and cards not working as their text says are different things.
If the card text says ANY but ANY is not accepted - then it is a bug. Unfortunately, I understood Konami doesn't give a **** about this game, so all bugs will remain here forever.
Are you still salty about this after 3 months?
Even if you in particular are "sugary".
Not understanding card rulings has the same effect on people.
There are A LOT of different bug types. Just several examples.
Functional bug - the behavior of part of a program does not match the intended expected behavior (for example, you play a card to destroy 1 monster but it destroys all monsters instead).
Localization bug - the localized text does not match the original text (usually typos or incorrect trasnslation).
Design bug - a mistake that was made on the early development of a product, on a stage when it was only designed "on paper". Usually some design decision that doesn't correspont to the initial demand of a product owner.
UI bug - visual errors in the user interface of the program. For example, a button that is partially shifted outside the visible area. Can be of different severity, from trivial (button slightly moved but is still clickable) to major (button completely unclickable and thus some functionaliy is unavailable).
Compatibility bug. A subtype of functional bugs, where functionality suffers only on some platforms / devices as a result of incorrect code modification.
Text bug. Is a subtype of UI bugs. Since text is part of the UI, it can be missing, misleading, incorrect or irrelevant. Or just contain a typo. Text bugs are usually trivial, but in some cases their severity might be higher. For example, if a button says "save the document", but instead its function is "close without saving" - the result for a user is quite severe - loss of time or even information.
The bug which I am discussing in this particular topic is a text bug. The text on the card says that I can use it as ANY material, while in fact, it can only used as a SPECIFIC material with a very specific requirement: its name must be listed to be valid for substitution. Having false information provided by the card, I was planning the game around this card and its effect, only resulting in a loss because card haven't done what its text said.
Actually, KONAMI fixed this bug in real-life TCG card game. They have changed text on the card in the latest errata to match the intended card's effect:
But they did not fix this bug (irrelevant text) in this game.
I have explained everything as detailed so that even the dumbest person out of those who is mentally able to play TCG would have understood. If you are still unable to understand simple info that even kids can - than its your fault, I've put enough effort to help you.