Warcraft III resources & community, 2003–2006 · archived

Player get randomly disconnected

5 posts
#1

Player get randomly disconnected

i have a problem with my td map and i know that there are a lot threads about this but i couldnt find a solution for my problem.

the problem is that sometimes players get a random disconnect but i cant see a reason for it. its always just 1 player and its always an other point in the game. (and yes they got disconnect, no leave) so its nearly impossible to figure out if it is caused by a trigger.

i heared it´s maybe memory leak but the map doesnt lag and you cant see any signs that someone will be disconnected. so how can this happen and why is it so random? and how can i fix it?
#2
Server Splits

(desyncs)

certain functions in wc3 ( like Pan Camera To Point Over Time, or w/e its called ), and can randomly cause server splits.

this is most likely what is happening :?

try to isolate the problem, detect which trigger it is coming from, then post that trigger here :D
#3
make at every part of your trigger this thing:
Text-Show text to "host" (trigger name)

at the first trigger just add
for 1 to 12
if name of player(integer A) = your name at b.net
then set "host" = player(Integer A)

Then you'll may fredomly watch debug messages
#4
i have just one pan camera trigger at the start of the game but each player has his single pan to his startposition and at this point no one got ever disconnected.


and i must set this
"make at every part of your trigger this thing:
Text-Show text to "host" (trigger name)"
after each action in each trigger or how do you mean it?


and i dont know if this is a serversplit because a serversplit is more like: you have 4 player - split - and then 2 player in one game and the other 2 in another game, but in this case 1 player just gets: "waiting for host" - "connection lost"
#5
Server Splits dont have to be more than one player

anyways, to detect the desync, try disabling a trigger and testing it. if it doesnt desync anymore, post it here, but if it does, then re-enable that trigger and try a differend one.