• Check out the results of the Techtree Contest #19!
  • Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • Create a void inspired texture for Warcraft 3 and enter Hive's 34th Texturing Contest: Void! Click here to enter!
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!

0.00 wait desynch

Status
Not open for further replies.
Simple question here.
Can a 0.00 second wait cause any problem whatsoever in a multiplayer map?
The obvious answer is of course no since there isn't really a wait period, but on the other hand it does get detected.
It's useful for some item triggers, and if you want a unit to play an animation at the correct time.
Usually I just use it without thinking about it. That was, until I began thinking about it.

I am not even sure if desyncing is the correct term here.
 
The "wait causes desync" is a lie.

Edit:maybe very very extreme case.

Edit2:make it veryx100
 
Last edited:
Well, if you want a waiting period, I strongly recommend a timer. Back in my spell-making days a wait was a sign of newbie coding, but not once did I see people complaining about a wait of 0 seconds. However, I never use it, not even for cinematics, where I don't care for perfect coding. I prefer having a solid effect than taking risks.
 
Status
Not open for further replies.
Back
Top