Replacing "Wait" with something more efficient

[WereElf]

Is there any way to avoid using "wait" commands in GUI triggers?
I've heard that they are inacurate and they may cause bugs.
I suppose I could use Countdown Timers instead and seperate 1 trigger into several (depending how many wait commands each has), but then
1) I'd need more global variables, as I wouldn't be able to use local ones to store data until the wait is over and then give the data back to the global variable.
2) I'll end up with too many triggers.

So.. any ideas/suggestions how to do it right (and efficient)?

 

[IcemanBo]

Timers is a good idea, but not much for GUI. (withour custom scripts I mean of course)
But basicly if you want to use timers efficient, then you need some basic JASS knowledge and often hashtable.
Else http://www.hiveworkshop.com/forums/...279/mui-spells-using-artificial-waits-223315/ is the usual way in GUI.

I want to add that yes, the GUI Wait action is not precise but itself does not really bug.
It can cause some unwanted results if used not correctly, yes, but if you know what you do then it doesn't just "bug randomly".

 

[Bribe]

If what you're doing is in relation to a spell, http://www.hiveworkshop.com/forums/spells-569/gui-spell-system-v1-4-0-0-a-273415/ will give you full control over the spell over any period of time while being fully MUI.