[Trigger] blink when move-commanded?

[oxxo]

• blinkmove
  • Events
    • Unit - A unit Is issued an order targeting a point
  • Conditions
    • (Issued order) Equal to (Order(move))
    • (Unit-type of (Ordered unit)) Equal to Builder
  • Actions
    • Game - Display to (All players) the text: ORDER ACQUIRED
    • Set Temp_Point = (Target point of issued order)
    • Unit - Order (Ordered unit) to Night Elf Warden - Blink Temp_Point
    • Custom script: call RemoveLocation (udg_Temp_Point)

wanna make the unit blink, to pointX whenever it is issued the order to move to pointX. the text is only to check if the trigger conditions are fullfilled.

the trigger condition seem to be wrong, because the testing-text is not displayed.

but what could be the cause for this?

any help appreciated

 

[xD.Schurke]

i would say because of the (Issued order) Equal to (Order(stop)) line :O

 

[bounty hunter2]

(Issued order) Equal to (Order(stop)) why is the order stop if the unit is ordered to move?

 

[oxxo]

CRAP! sry guys!

that was actually a typo, it says "move" in the trigger, and still it doesnt work.

care to try again? ^^

 

[bounty hunter2]

blinkmove
Events
Unit - A unit Is issued an order targeting a point
Conditions
(Issued order) Equal to (Order(move))
(Unit-type of (Ordered unit)) Equal to Builder
Actions
trigger - run trigger 2 ignoring conditions
Set Temp_Point = (Target point of issued order)
Unit - Order (Ordered unit) to Night Elf Warden - Blink Temp_Point
Custom script: call RemoveLocation (udg_Temp_Point)

trigger 2
Game - Display to (All players) the text: ORDER ACQUIRED

try this spliting the triger might work

 

[oxxo]

well then i get the text message. but the unit doesnt blink.

the problem is that the unit doesnt blink. the text message was merely to verify,

wether the problem is in the conditions or in the actions.

since the text message doesnt fire, the problem is within the conditions.

i suspect the "move" command line to be invalid or smth...

 

[bounty hunter2]

do the units have blink? try move to instantly creating effects on the blink spots

 

[oxxo]

do the units have blink? try move to instantly creating effects on the blink spots

the units have blink.

if i make the same trigger with the "move unit instantly" action, the conditions are still the same. and since the problem is in the conditions, that wont help =/

 

[bounty hunter2]

the conditions seem fine, the string move is even sat as an example in the trigger editor.
I tried the trigger in my editor its not working. Removed the conditions, its working.

I don't know what the problem would be.

 

[Zack1996]

Hmm, try moving the unit to the point instantly instead of Blink. Other than that I don't know what's wrong.

 

[Palaslayer]

what about using

• blink
• Conditions
  • And - multiple conditions are true
    • (Issued order) Equal to (Order(move))
    • (Unit-type of (Ordered unit)) Equal to Builder
• Actions
  • ------<your actions>------

instead of just doing two conditions???? dunno why i say this but the And - Multiple Conditions should be there for sth, right???

 

[reatek]

Why not do it with "Move Instantly" . I think it will be better than blink...

 

[Palaslayer]

3 people said that before lol, keep reading the posts

 

[TheBlooddancer]

add

• (Issued order) Equal to (Order(smart))

 

[oxxo]

thanks for every comment,

but adding (Issued order) Equal to (Order(smart)) doesnt work either

 

[darkrider]

hey oxxo i wanted to make a unit controled by neutrals to blink when i casted something on it... but it never worked... seems that the blink actions doesnt work... at least it didnt for me... so i had to think of something else :/


EDIT: try this for me plz... remove the leak removal line from the trigger and see what happens. I think that you may be removing the point before the unit actually blinks... and that could be your problem... that thing has just came to my mind and i dont have WE to test

and try the conditions like this

• Or - Any (Conditions) are true
  • Conditions
    • (Issued order) Equal to (Order(move))
    • (Issued order) Equal to (Order(smart))

 

[Lord_BoNes]

Just a thought here... Try making the variables local, and adding a 0.5 second wait before removing the location at the end.

 

[Dr Super Good]

Remember that the events fire before the unit actually physically carries the order out. Thus you need to have a small delay between the event firing and you issuing a different order via triggers otherwise your order gets qued up as the event response order overwrites it. To work around this problem, use a timer that expires in 0 seconds to delay the blink order after the event fires. Equally a TriggerSleepAction could be used but it would result in a visable delay before blinking occurs, and thus why I recommend timers.

 

[darkrider]

• Or - Any (Conditions) are true
  • Conditions
    • (Issued order) Equal to (Order(move))
    • (Issued order) Equal to (Order(smart))

ill quote myself here... later i tried this... and it worked this way, any of those orders and removing the leak removal thing... you can use a timer as DSG said to remove the leak

 

[terradont]

Just a small thing, i'm not used to orders.
Try writing (Order(Move))
Big M?
Sometimes big or small letters make a difference.
EDIT: well, i didn't see the second page, damn tired me. Their ideas seem better than mine, so try em first.