Mission 5 (Red Ridge Mountains)
-locks selection when you select one of 2 buildings that suppose to be destroyed, you can only interact with stuff inside of that buildings[recruiting wolf riders/upgrades in Blacksmith] and F5 with menu button at the bottom (youtu.be/I1d0ilLvhjw)
-crashes when you select barracks (youtu.be/q3fW7JyS_yU)
This bug appears throughout the game from the very first missions and made my playthrough of the game impossible.
Problem: if you select a damaged building, the game either crashes or the selection hangs on that building, preventing you from doing anything else. The problem is reproduced 100% of the time, just start a mission and damage your building and then select it (maybe several times).
The problem seems to be a serious crit and I was wondering why other players aren’t complaining about it. I decided to investigate this and test a few theories. The topikstarter videos gave me a tip: they show a Russian language interface, just like mine. I tried switching the game to English and the bug disappeared, the game became working.
So it’s some internal bug related to localization and game engine. I think Blizzard should do something about it, but I’m not sure if they are aware of it.
1 Like
So, I decided to look into this bug some more. After some experiments I found out that it is related only to strings. The error that crashes when the game crashes indicates memory overrun - it means that some of the strings are too big.
Since the strings are available in the game files, I went through several variations and found the problematic one:
“unit_other_repair_cost”: “Для ремонта потребуется по %d ед. золота и древесины”
While there is no official fix, you can fix the error yourself this way:
Open the Russian localization file (“data/strings/ruRU.json”) and replace this string with a shorter one, for example: “Для ремонта нужно по %d золота и древесины” (the length of this string corresponds to the original), and the problem with the building selection will disappear.
The bug is officially fixed with yesterday’s hotfix, manual fixes are no longer needed. 