How come the wait bug is not fixed in v1.03???

I've just noticed that patch v1.03 is out. It's good that Blizzard fixed quite a number of bugs, though most of them I hadn't heard of. But how come the famous "wait" bug in multiplayer game is not fixed? Probably every maps use the wait action and many mappers have the experience that their maps got screwed up when went from single player to multiplayer just because of this bug. And I don't think this bug is difficult to fix. It's often so mysterious how those big companies run. :nono:

First make a interger varible called NumPlayers and a player group varible called AllPlayers (or anything you want it to be).
on the map initilazation actions:
-Player group remove all players from AllPlayers
-For Each interger A 1-(number of max players in your map) do If Player Slot Status is = to Is Playing, Then add Player(Interger A) to player group AllPlayers
Set NumPlayers = Count the number of players in AllPlayers
Then you can do this:

For each interger 1 to NumPlayers do (wait X.XX)

that works perfect for me. Also i noticed that if you are going to use multiple wait commands in a trigger, is tends to mess up. Your better off splitting it into seperate triggers. and using the "Trigger run ignoring conditions" to trigger the next

They probably didn't want to screw up the already existing maps... cause then the For each integer thing would make load times become like 1000 seconds which is no fun.

yea thats probly the reason, i never even thouht of that heh

They could've also let multi-player maps be linked together too.

I thought it was possible to link multiplayer maps together. Otherwise why does it say Quit Campaign or Continue in the dialoge box in multiplayer games? Never understood that.

Continue just lets you keep playing even though everyone has left. Map linking isn't possible right now, only the host (at least I think the host at least) goes on.

Wait definitely has some problems, but it's 99% more likely that the problem stems from the "wait bug myth." There ARE wait bugs, but people make it sound like they NEVER work. In reality alot of the time they do, even in multiplayer -- it's just that if someone presses escape during a transmission, the text disappears for all players, so people think the wait was ignored. Also, putting wait inside a unit group (usually done with custom text) causes a TON of wierd problems -- have it run a seperate trigger with the actions you want instead.

Wrong!!! Hitting Escape while a transmissions DOES absolutely shit unless you actually trigger it to do something like that.

God and you call yourself an Overlord? What should I call myself I though master was enough but now all these people have cool names like DKSLAYER and stuff like Jass &AI guru damn King & God sound too obnoxious...

It is easy enough for Blizzard to avoid messing up the old maps after fixing the wait bug. The program just need to check the time of map creation before running. If the map is created before, for example, v1.03, then do the "wait" in the bugged way. Otherwise, do the "wait" in the more logical non-NumOfPlayers sensitive way. So simple and this should work. Maybe someone can write to Blizzard about this?

Anyone going to write the e-mail?

Uhm weaaddar go and actually try it before saying something like that :P It DOES make text disappear for everyone.

I have not been on the Warcraft B.net fo long. I quit long ago and I do single plahyer now. What is this wait bug?

Well, it is probably the most well-known world editor bug among mappers. The action "wait" is fully functional in single player. However, when there are more players in the game, it looks like all "wait"s are ignored. It is probably that the computer somehow divides the actual waiting time by number of players, so the solution to this bug is "for integer A = 1 to NumOfPlayers, do wait xx seconds"!

Damn, you just ensured me quitting B.net!

No, you don't need to quit B.net! The bug only causes problem to (new) mappers. As we all know the fix, you won't notice the bug in the game.