Tonight I played my first game on Patch 1.34. My game was a custom game and there was an imported file that became messed up because of the aggressive caching system added in Patch 1.33 (August 17, 2022 recent patch).
This aggressive caching system has been reported countless times in different ways and in different flavors all over the forums. But the problem is that, in the game programming, this new patch has a line of code that essentially says:
When loading a file from a path “X/Y.zzz”, if we have ever loaded a file from this same path before, then return the binary contents from the previous load request instead of looking up the file again.
However, there are tons of features and systems in the Warcraft III game that use file overrides and loading different sub paths and different things. So, for example in my play session tonight, there was a file path that loaded when I played in SD graphics, then I realized that I had intended to play on the HD graphics and I played the game again. But the aggressive caching mechanism cached a file that was loaded while the game was in the SD mode, which corrupted the visual display in the HD mode. As far as I know, the issue is not specific to custom games.
Please turn off the aggressive caching in the game to make it less broken, like how it was for two years until you recently broke it with this new aggressive caching feature, which is itself basically entirely a bug. Thanks.