The event "Player selected QUIT button" is not connected to the action "Defeat triggering player." This is causing many bugs on Battle.net. Thanks to this, some players have reported that they lost their melee games even though the other player quit the game.
This is also causing more problems. The game bank is "closed" when the player leaves the game. However, if the player presses the QUIT button, the Bank is not closed. So, during a remake, when the game tries to preload the bank, the game will freeze exactly when the loading bar reaches 50%. (It will freeze for 5 minutes and then drop all players from the game).
Also, all the events "Player has left the game with any" is not being called when the player presses the QUIT button.
This wasn't happening during beta. It seems Blizzard deleted one line from the code and that's the reason for so many bugs. Also, it does not happen during local games (maybe that's why blizzard didn't realize the problem).
Map makers: How to solve it:
Event
Player leaves the game with any;
UI - Player Any Player selected Quit Button on Game Menu Dialog.
Action
End game in defeat for player (triggering player).
(IM NOT SURE IF THIS WILL WORK, I HAVE TO TEST MORE)
PS: This is when the loading screen freezes at 50%. If the loading screen freezes at 75%, it's usually lag problem (one player was dropped).
LOOK THE FILE ATTACHED. It shows an example of a game that crashes in every remake. I made it for 8 players, so you can call your friends to crash with you.
I think this is what I've just been experiencing with my map. Once the game starts and a player leaves, my leave trigger isn't running which means the event player any player leaves game with any isn't working. Actually it might just be because I should be using the Player Any Player selected Quit Button on Game Menu Dialog event.
There seems to be a major issue with the internal "Player () selects Quit Button" event where that event, while successfully disconnecting the player from the game, fails to call/notify the internal "GameOver()" function, which is what the "Player Leaves Game" event seems to fire on.
If anyone can find a proper solution, that's good, but I doubt there's anything we can do without a Blizzard fix or an large ugly .5 second loop.
The event "Player selected QUIT button" is not connected to the action "Defeat triggering player." This is causing many bugs on Battle.net. Thanks to this, some players have reported that they lost their melee games even though the other player quit the game.
This is also causing more problems. The game bank is "closed" when the player leaves the game. However, if the player presses the QUIT button, the Bank is not closed. So, during a remake, when the game tries to preload the bank, the game will freeze exactly when the loading bar reaches 50%. (It will freeze for 5 minutes and then drop all players from the game).
Also, all the events "Player has left the game with any" is not being called when the player presses the QUIT button.
This wasn't happening during beta. It seems Blizzard deleted one line from the code and that's the reason for so many bugs. Also, it does not happen during local games (maybe that's why blizzard didn't realize the problem).
Map makers: How to solve it:
(IM NOT SURE IF THIS WILL WORK, I HAVE TO TEST MORE)
PS: This is when the loading screen freezes at 50%. If the loading screen freezes at 75%, it's usually lag problem (one player was dropped).
LOOK THE FILE ATTACHED. It shows an example of a game that crashes in every remake. I made it for 8 players, so you can call your friends to crash with you.
This is serious.
@RodrigoAlves: Go
Bumping this back to the top. :)
I think this is what I've just been experiencing with my map. Once the game starts and a player leaves, my leave trigger isn't running which means the event player any player leaves game with any isn't working. Actually it might just be because I should be using the Player Any Player selected Quit Button on Game Menu Dialog event.
Okay that's not working either, wtf?
There seems to be a major issue with the internal "Player () selects Quit Button" event where that event, while successfully disconnecting the player from the game, fails to call/notify the internal "GameOver()" function, which is what the "Player Leaves Game" event seems to fire on.
If anyone can find a proper solution, that's good, but I doubt there's anything we can do without a Blizzard fix or an large ugly .5 second loop.
@RodrigoAlves: Go
I know this is a old thread. But i think the problem described by Rodrigo with freezed loading screen very similar with http://www.sc2mapster.com/forums/general/general-chat/54081-game-randomly-drops-a-lot-of-players-freezed-loading/#p9. Thoughts?
http://www.youtube.com/user/RussianMapster