So what's the best alternative to "wait" function?

[Matarael]

Since the concencus on wait is that it's bad and causes leaks, what are we to do when we want to postpone something for a certain amount of time?

 

[WaterKnight]

In timers we trust. And no, Waits do not leak.

 

[Vinz]

In timers we trust. And no, Waits do not leak.

Yup, they only cause errors and bugs in your trigger.

 

[Daffa]

but if used properly, waits can turn a plan of using shitload of codes into minor codes, of course, still risky. Waits also needs Triggering Unit or Locals to become MUI for Spells.

 

[Rheiko]

the best alternative and recommended for submitting resource to this site
use periodic timer
use a countdown timer
use a counter
using wait is not recommended even if it's like this

 

[Matarael]

The problem about using timers etc. is that it can't wait for a CONDITION to happen.
For instance: "wait until Unit has xxx buff".

 

[Vinz]

Periodically check the condition.

 

[Rheiko]

use periodic timer and use If then else

 

[Daffa]

Rheiko
I did use Mag's Method with locals and it works well, it's not recommend if your math really sucks to calculate the actual amount of waits [with approx extend time of waits].

Matarael
You can use Periodic Trigger, with 0.03 timer check to see if it reaches certain conditions.

 

[Rheiko]

well, locals are really helpful sometimes
but the reasons why waits are not recommended are:
They are inaccurate
Waits don't 'wait' when the game is paused

actually this things are explained very well at mag's tutorial

 

[Daffa]

They are inaccurate

I don't even bother about inaccuracy much. It's just about time approx [why math is important when using waits].

Waits don't 'wait' when the game is paused

disputable

 

[Rheiko]

well, it's your choice then

 

[FUJI]

Use shadowing globals by locals if you don't want periodic. But it is not recommended anymore. Using waits do not cause leaks and bugs.. it is only brokening the MUI'ness of the trigger or spell ( Multi Unit Instanceability ) Waits are inaccurate and it can only have 0.27 seconds. You can use short waits for the loop but if it is very long waits been used then it will appear the brokening of the MUI. Shadowing globals look like this:

local unit u = GetTriggerUnit ( )
set udg_YOUR_UNIT = u

Writing wait in 0.03 seconds will look like this:

call TriggerSleepAction ( 0.03 )
// --> Will transform to: 
call TriggerSleepAction ( 0.27 )

You can read many tutorials in here about using artificial waits.

 

[Matarael]

Oh yes periodical condition check, I completely forgot about that.
Thanks everyone! Reps frenzy in this thread.

 

[chobibo]

What? locals aren't accurate? You must mean TSAs/sleeps a.k.a. Waits...
Sleeps don't pause with the game timer because it delays the execution of code on the thread using a different timing system (I don't know if it is the system clock or CPU clock).

it is only brokening the MUI'ness of the trigger or spell

No it does not, when a trigger fires and execute code, the local variables in that instance of execution are allocated a seperate and unique space in memory, it's localized for that execution alone.

The reason it breaks instancing is because of the use of a global variable, not the suggested reason...

Waits weren't used because it causes handleId allocation to get messed up, and it only happens when you remove the action on a trigger handle and then destroy it. A testmap is available on wc3c.net, I don't think I remember it correctly.

Short explanation: Waits mess up dynamic triggers.

 

[Rheiko]

ah sorry about that, it's not local, yes
i mean Waits

 

[WaterKnight]

Short explanation: Waits mess up dynamic triggers.

How so often you have to know what you are doing when dealing with wc3.