does the 'wait' trigger action has any influence?

Hello,

I create 2 triggers:

trigger 1

event 'scv' enters region 'buy marauder'
condition
action create 1 'marauder' for player 1 at 'units'
action wait 10 game seconds
action move 'last created unit' instantly to 'attack location'


trigger 2

event 'scv' enters region 'buy ghost'
condition
action create 1 'ghost' for player 1 at 'units'
action wait 10 game seconds
action move 'last created unit' instantly to 'attack location'


question

If I buy a marauder and move my scv 2 seconds later in the 'but ghost' region will the trigger of the marauder then send the ghost to the 'attack location'?

(since the ghost in the 'last created unit')

the wait action has influence on when the action is performed, and for example, say you do something to unit variable after a wait, well if that isnt a local variable it may have been changed to another unit beforehand, thus, not performing how it sounds it should

??

"last created unit" can be any unit that was created in that 10 seconds
for instance, 2 scvs enter the "buy marauder" region at the same time, that trigger runs twice at once, however, both of them only move the 2nd one instantly, the first is never moved... to prevent this use a local variable, that is litterally the only way. Under the local variables part add a new variable of type "unit"

then between the create unit and the way put this:
Set [Unit Variable] = Last Created Unit

then change the "move last created unit instantly" part to:
move [Unit variable] instantly

basically:
add the variable
set the variable to the last created unit after you create it
change the last created unit parts after the wait to the variable

omg so complicated with all this variable and global things

I found a simple solution!!

trigger

event any unit enters region 'units'
condition
action wait 10 game seconds
action move 'triggering unit' instantly to region 'attack location'

why does all things works now ??

well, it works because triggering unit refers to the unit that.. well triggers the trigger (causes the event to fire)

But to be fair, by using a local variable it would not be any harder, you just create a local variable of type unit (lets say that this is a box) then you store the unit you just created in the box, and label the box "Unit" after the 10 seconds passed you will be able to go back to your box and take out your unit and do with it what ever you want.

The reason we are using local variables is that (as far as I know) the 'triggering unit' is not fully reliable, and may not work 100%. (Please correct me if I'm wrong)

yes I know about the variable but the part I don't understand:

if you store a unit in a variable and the next unit comes right after, can you get another place for this unit too then?

thats what the local part is for, it creates a new version of that variable every time the trigger runs, allowing it to be used once by you but its actually being used tons of times by the game

there is no variable

if you followed my instructions there would be, im talking about that variable

no need variable for this simple thing

I already solved it by the trigger I showed in 6 post above

i know, but you are going to run into this issue again sometime when that solution wont work, better to learn sooner than later...

aight