Wondering if we could have a feature enabled in maps to print logs on what/where caused a desync. This would help immensely, especially with the given new natives and testing what does/doesn’t cause desyncs.
We can of course go through our code and look for the usual suspects, but if the game is already detecting a desync? Why not just allow us to see what triggered it (or when)?
1 Like
Blizzard doesn’t even know how to fix this issue seeing as how they claimed to have fixed it years ago. I believe its a server side issue and not a map issue.
I’m not referencing the desync issues happening for many maps in general - just in terms of map makers and testing out code D:
Would be great. I got issues in my map (Metal Maul Wars) aswell. No clue what causes them. But Blizz gives sh*t about custom games it seems…
There acutally is such a feature but you will have to understand what you are doing. It helped me at least. Just go in the documents folder to the following location:
\Documents\Warcraft III\Errors
There are folders with the exact time stamp and two files. Both can help you but as I said. You have to know what you are doing and what is happening.
Have you tried looking through this list SymphonyX?
Hiveworkshop threads/would-a-tutorial-about-known-desync-causes-be-useful.317486/#post-3363615"
Especially check 3 b)
Also look for very fast periodic triggers (0.1-0.01) . With the state of the servers right now i think Blizzard changed something in the network load that has to do with syncing classic and reforged users graphics This might lead to being less sync calls available /frame for your custom code. Which would cause some spells that prior were fine or a little laggy to outright desync now 100%.
At least it fixed the issue for me.