At first everything looked like in the screenshot and I was shocked.. at least a restart fixed most of it.
The issue is being worked on. Please backup your projects/maps and wait for the hotfix to be able to use 1.31.
Until then you could try working on these:
[Need Help] Back to 1.29
Patch 1.30.4 Backup Game Files
Unfortunately not.Thanks, you probably don't have any timeline for the hotfix until it's available, right?
How long does it take usually for Blizzard?
I see, thanks for the insights!Unfortunately not.
It depends on how grave the situation is. Hopefully not more than a week since the patch has also been through a PTR.
I fixed all string corrupt problem. All you need to replace your map folder to documents folder>warcraft III>Maps>replace your map to here and open it from there on world editor.
Strings will not corrupt. They transfered map datas to your documents folder. I hope it will help
My map work well.
I fixed all string corrupt problem. All you need to replace your map folder to documents folder>warcraft III>Maps>replace your map to here and open it from there on world editor.
Strings will not corrupt. They transfered map datas to your documents folder. I hope it will help
My map work well.
We'll have to adapt, no matter what. And it's just the beginning of all the changes. The wisest way would be keeping 2 versions of one's map: one stable for the "classic" WE version, and experiment on the latest one for Reforged/this current version.Why do u touch stuff that is already working if you are going to screw it? The game was fine U.u
The problem is, if i make it work on the stable old version, then i play it on live and is screwed.We'll have to adapt, no matter what. And it's just the beginning of all the changes. The wisest way would be keeping 2 versions of one's map: one stable for the "classic" WE version, and experiment on the latest one for Reforged/this current version.
[Need Help] Back to 1.29 1.29.2The worst thing is that I can't even revert it back to the old patch!! When will Blizzard release the hotfix for this bug?!