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
Obviously the bug is still going to cause grief if you don't notice it before it's too late.
But whenever you notice that one of your battles is in this bugged state, the best course of action is to immediately pause, quit the current session and reload. In my experience it's enough to quit to the main menu (i.e. you don't have to close and restart the game altogether)
Supposedly there will be future debugging tools (also made public) that might allow for more info about this to be found.
And until the developers finally figure out what part of code is responsible, or what new piece could stop the bug this 'coping' mechanism will be used.
Which version was that?
If it was the previous wait for the new one. But either way thatks for your input.