How to know when a worker is idle

Hi guys, I want to display an animation at the head of the worker when he is idle. However to do this I need to know which workers are idle and which workers are not. How does the game finds that out? How can I know when my workers are idle ?

Get its current order? and see if its no order?

you mean, GetUnitCurrentOrder ?? This function returns an integer, what is that integer ? An order conversion? What is the integer for no order?

0

You can know for all hidden workers (all race which is not undead or human), but for these two last races, you can't really know, since you can't know the difference when a builder will build it (receive the order) or is actually building it.
Ok, i've missunderstood the question ...

When worker has an order "stop", game treats it as idle worker so use trigger that fires when player issues "stop" order may be the way to go.

Mmm Ahh thx to all!
+rep for all who helped me.

You're wrong BestZero. It has order of "0" like people said before you, not stop order.

That's true. I have tried it, when unit is in a stop stance it has 0 order not stop order.

Sorry for my misunderstanding.

A unit has stop order for the instance it was ordered stop (caught during the event EVENT_PLAYER_UNIT_ISSUED_ORDER). After that, a 0 order or "" in GUI.

this will work for workers without attack only, cos auto attack without order cannot be detected.

Auto-acquire attacks keep the unit at having no order. (i.e. if you order a unit to stop, then it acquires a target, its registered order will still be "null"). Workers do not usually auto-acquire but I think they engage when they are 'forced' into it. You will not be able to ascertain if the worker is still idle in this case by a simple GetUnitCurrentOrder() method.


edit: zzz the post above

The auto attack can be detected with the event EVENT_UNIT_ACQUIRED_TARGET, then to keep the order track, you can order the triggering unit to attack his target, unfortunately, there is no PLAYER_UNIT_EVENT.

Are workers hard-coded to not acquire a target? Therefore this work-around would not be needed.

i think yes ..units with worker classification wont aquire targets...