Problem with a trigger why doesnt that count!

Problem with a trigger why doesnt that count!

Alright so heres the thing, I have a trigger for my map that I'm working on where a car can run over a unit IF it's moving makes sense right? I found a way to do this except for a glitch, apparently right clicking on terrain as if to make the unit move doesn't count! Doesn't count that! So anyways I'm gonna show you the exact trigger below.

-Moving Car

-Events

Unit-A unit comes within 275.00 of Car 0001 <gen>

-Conditions

(Unit-type of (Triggering unit)) Not equal to Car

-Actions

If ((Current order of Car 0001 <gen>) Equal to (Order(move))) then do (Unit - Kill (Triggering unit)) else do (Do nothing)

Please Help =(

You need (Entering Unit) not (Triggering Unit) i think.

I tried that and it didn't do anything diffrent, it just went past when I right clicked then when I clicked move it worked... it's very odd.

Maybe instead of that trigger, make a 275 aoe permanent immolation that you 'put on' the car when its ordered to move or attack and gets removed when it stops.

Oh I just figured it out because I was messing around and, thought about how it might just be that I got the wrong order string. So I searched google and someone had a trigger to tell you all the order strings and right clicking it turns out is 'smart' not 'move' thanks for all who posted here!

TeifiYou need (Entering Unit) not (Triggering Unit) i think.

sorry to ruin the moment, but Triggering Unit is actually BETTER than Entering Unit

also, if the car was issued a patrol order, the order would be patrol, and if it was issued an order by right clicking, the order would be smart. if it was issued an order by Attack, the order would be attack.

make a trigger that displays order every time unit recieves one, and modify your script accordingly.

low-lifemake a trigger that displays order every time unit recieves one, and modify your script accordingly.

Thats what I ended up doing although I didn't know until I googled it.

PurplePoot

TeifiYou need (Entering Unit) not (Triggering Unit) i think.

sorry to ruin the moment, but Triggering Unit is actually BETTER than Entering Unit

I'm just wondering... Is there actually any positive effect in the end, or is it just because it's the first function for units that you see and it's less work to do it with triggering unit?
--donut3.5--

its simpler, its shorter than most other calls ( saving a bit of map space every time u use it ), and its about a billionth of a second faster

I don't see how it can be fater. Both functions only return varibale that is set when even happens.

PurplePoot

TeifiYou need (Entering Unit) not (Triggering Unit) i think.

sorry to ruin the moment, but Triggering Unit is actually BETTER than Entering Unit

Oh ok... ^.^