SC2Mapster

Oh my God, you found the source of the bug. I almost can't  believe it :D

THANK YOU!!! If you happen to visit Warsaw or if we meet anywhere else by chance you're getting a vodka (or whatever else you drink) from me xD

How the hell did you figure out that it was the frame? Did you like run the map just in code,  matrix style, or something?

Honestly, I have no idea why I had that frame up. I must have added it while adding other loading screen stuff cause it sounded cool or something :D

"BattleUI? Like Battle.net? Gee, can't go wrong with that, right?" xD Fuuuuuuuu... Those kinds of bugs are the worst.Tiny stuff that you think only adds a little particle there, a semi-colon there. Ends up crashing your stuff.

As for the Allied Commanders. Good thing it wasn't that cause I am actually using some stuff from there :D

Damn, what else can I say. I'll keep testing it out properly now. You saved my life xD Thanks again.

Okay, I've found out the source of it.
It's because you've used special BattleUI frame as custom layout frame for loading screen.. BattleUI is actually root frame for Battle.net UI. Apparently trying to use it for loading screen is pretty disruptive :D And something from SC2 cannot recover without a full game restart.

By curiosity I've tried to use couple of other frames that should not be used for loading screen, but none of it resulted in broken game.
I don't know what made you use custom layout, and why did you actually pick BattleUI. But this together was worst case possible, haha.

Generally editor should report about issues like that, but I haven't been seeing anything in the log. So it took a while to find.
In fact it can be considered as bug, because ideally maps should be sandboxed in SC2. That is nothing you do inside the map should affect the game itself after you quit the map. And destroying Battle.net UI is certainly something that negatively affects user experience ;D

To summarize, to fix it just just go to *Map -> Map Loading Screen*. Unlink *BattleUI* frame. OK.

Nope. There's nothing special you need to do, for your map to work correctly in Battle.net. The behavior you experience is either caused by some obscure bug in SC2 which reason I cannot guess. Or there's *something* in your map that causes this freeze.

It's good that you were able to save the replay. And what's better, it seems like the bug can be reproduced by running the replay.
If you could attach the replay here, or upload it somewhere and post the link, then I'd look into it myself (yes, replay from online game is all I need). If the bug will also occur on my end, I should be able to track down the cause.
Also, what's the length of the replay? Because if the freeze actually happens right after start, I'd expect it to have ~0s.

In the meantime, here's small checklist you could do, to narrow the area. Proceed it until you'll confirm the freeze doesn't happen anymore.
(Of course before doing anything of this, backup your map.)
- Simply republish the map w/o changing anything. To make sure this is not result of some error during publishing process.

- Remove custom dependencies/mods (if you have any). Publish & retry.
- Remove triggers that are running at the start of the game. Publish & retry.
- Remove ALL of the triggers. Publish & retry.
- Remove ALL preplaced units on the map. Publish & retry.
If at this point the freeze will still be occuring, I'll be suprised. But you should keep going and remove remaining things such as: custom imported assets (if you have any), lobby attributes/variants, data entries.. it might sound funny, but I'm serious - when you can't guess the source of your trouble, then removing the possibilities piece by piece is smart way to approach it.
Unless you'll end up with empty map, haha.

Given the fact it works flawless in test mode, it does seem pretty weird.

I could see infinite loop in triggers or infinite recursion in Data causing something like this, where game freezes for a while thus putting you in a state of being not available to Battle.net. Although in such scenario it should unlock after a while - when SC2 detects things went wrong, to put it simple.

But.. if you can't reproduce it offline in test mode, I don't think that's the problem you're running into.

Does the disconnect happen every time? Are you able to quit the game before getting "attempting to reconnect" screen pop up, and have a score screen visible? Does the replay file save after the game?