abilities got an "Ignore User" flag at commands. if you add 2 kinds of move to a unit a user might only cast the one without this flag, but i didnt test it.
Tested: when trying to order unit to use "move copy" getting error "too many move abilities" error and unit wont go and btw move ability doesnt have this flag
i just checked, move also has this flag (under commands, not ability flags). you could use 2 dummy abilities with smart cast with higher priority than move which issue order to move to target point.
Random guess: Maybe when you issue an order via triggers you could also change a unit custom value to a non-zero value, wait .0625 seconds, and then change it back to 0. Then you could check the custom value in a condition.
Edit: I would probably make sure the custom value action comes before the issue order action.
Edit2: Or maybe instead of the wait, have the trigger that fires change the custom value back to 0. Anyways, that'll be my last edit, you get the idea I hope.
Check the triggering player. Since Issue Order will have a source player of the game system, it will have the value of 16, instead of a normal player number.
like in topic
there is no way to do so.
Still alive and kicking, just busy.
My guide to the trigger editor (still a work in progress)
abilities got an "Ignore User" flag at commands. if you add 2 kinds of move to a unit a user might only cast the one without this flag, but i didnt test it.
@FunkyUserName: Go
that would be huge! gonna test it right away
Tested: when trying to order unit to use "move copy" getting error "too many move abilities" error and unit wont go and btw move ability doesnt have this flag
i just checked, move also has this flag (under commands, not ability flags). you could use 2 dummy abilities with smart cast with higher priority than move which issue order to move to target point.
Random guess: Maybe when you issue an order via triggers you could also change a unit custom value to a non-zero value, wait .0625 seconds, and then change it back to 0. Then you could check the custom value in a condition.
Edit: I would probably make sure the custom value action comes before the issue order action.
Edit2: Or maybe instead of the wait, have the trigger that fires change the custom value back to 0. Anyways, that'll be my last edit, you get the idea I hope.
Check the triggering player. Since Issue Order will have a source player of the game system, it will have the value of 16, instead of a normal player number.
@ArcaneDurandel: Go
it always returns owner of unit