Well, my users have debugged this a ton and it turns out Blizzard broke their stuff again.
Using a map with custom dependencies defined in the Battle.net Publishing System creates an issue where, in multiplayer, a significant number of players can get a "desync" error message and drop from the game.
For obvious reasons, this bug is fairly critical and I'm requesting that you guys can fix it in a timely manner.
For testing purposes, this bug can be replicated by joining a game of "Cortex Roleplay - Swamp" with multiple people (bug can be finnicky, you may need more than 2 and a few attempts to get desyncs). This map has a dependency on "Cortex Toolkit" a mod I've published.
Well, my users have debugged this a ton and it turns out Blizzard broke their stuff again.
Using a map with custom dependencies defined in the Battle.net Publishing System creates an issue where, in multiplayer, a significant number of players can get a "desync" error message and drop from the game.
For obvious reasons, this bug is fairly critical and I'm requesting that you guys can fix it in a timely manner.
For testing purposes, this bug can be replicated by joining a game of "Cortex Roleplay - Swamp" with multiple people (bug can be finnicky, you may need more than 2 and a few attempts to get desyncs). This map has a dependency on "Cortex Toolkit" a mod I've published.
Thanks!
Cross-posted: http://us.battle.net/sc2/en/forum/topic/801610359
You got a blue response. This will be addressed
That was some impressive response time! :D