Auto Retreat Problem / Bug

i am using auto retreat a lot, and in almost every match i have some units not following the retreat order properly and instead walking randomly into their death, which is kinda annoying.

i think what is happening here is some sort of "race condition" where the unit receives a move command right after the widget sends the retreat order, but before it unselects the units.

if i am correct, the fix for this could be as simple as making it unselect the unit first and then sending the move to retreat order.

ahh i see, i hope this can get fixed because i often lose important units like aspis or placeholder to this

The easiest fix might actually be to make the autoretreat a widget instead of a gadget.
If it is a widget, the retreat commands will be sent with network latency, but when it is a gadget, it is synced and is run instantly in the simulation when the unit goes below the HP threshold.

I have this so bad and it's driving me crazy.

What if it were a widget and a gadget?