A way of preventing orders

I remember ordering units in response of orders (at least stop) didn't work and had to pause->stop->unpause or some sort of dirty work. While I was testing a 0-sec timer, I found out that it also works in this case. Ordering stop or whatever orders with a 0-sec timer callback will guarantee that the order is overridden.

Any questions or more ideas?

I heard SetUnitPosition interrupts orders.

ya ...rising dusk should use that method in his SimErrorEx ..much better then pause / unpause

I use 0 second timers and they work nicely and are easy to implement.

I'm aware, but I need to be home and have access to the WE before I can update. :)

thx for imparting. pause-unpause screws up other deliberate pauses.

Huh. Does using a timer of 0 require using locals?

Actually, it requires use of globals (either structs or raw globals, depending how safe you want it to be).

y bother with a timer and all it entails when u can just do a wait.

Because wait suck, they don't provide the control you need, they are random in the time it waits (can actually fuck up replays if played at a faster speed), and cause the unit to still be issued the order (which we are trying to avoid).

They couldn't have even received an order in the first place if they were paused to begin with. That argument is really quite silly. The pause/unpause overhead is not that bad, neither is the timer version. I think giving users the option is the proper approach in my case.

SetUnitPosition will order the unit to "stop", even if it has Amov gone.

set position may and will cause unit to jump around if its near other moving units.

this easy (much more easy then timer 0) but can cause many problems.

It's not easier just more lame, because you must use a 0 timer also xD

timer 0 or not timer 0 units jump around, you can test it self or watch DotA mobs (pathing system uses position for path correcting)