"Last Created" Trigger Question

[tbjl2006]

When a trigger says "last created" like in the "make (last created) unit invulnerable" does it mean the last created unit created by the trigger? Or will it make any last created unit invulnerable? Also it it says Last created quest is enabled, is that the last one created by the trigger? Thx, tbjl2006

 

[Doom-Angel]

well im pretty sure it speaks for trigger action cuz if u train unit in building it's counted as trained unit and if u use a summon skill it would be counted as summoned unit so i guess the only unit which counts as last created unit is the one created by triggers....

 

[SFilip]

Last created using the "Unit - Create ..." action.

 

[tbjl2006]

SFlip What happens if you have two triggers that make a unit at the same time?

 

[Dr4gonL0rd]

Yeah, I think I understand your question; I had the same one once. With 'last created' it is referring to the "last created" whatever within that trigger.

 

[tbjl2006]

Thank you very much it is very helpful Dr4gonL0rd. +Rep

 

[AceHart]

> With 'last created' it is referring to the "last created" whatever within that trigger.

Within whatever trigger last created something.
"Last created ..." is a global variable. It only exists once.

 

[Korolen]

What happens if you have two triggers that make a unit at the same time?

Two triggers can never run at the same time. Even if they both fire on the same event, one will go and then the other. If you put a wait into the trigger, however, then other triggers will then have a chance to go before the first one is finished. Therefore, if the first trigger creates a unit and then waits, the second trigger can see that new unit with Last Created Unit. Also, if the second trigger then creates a unit, the first trigger won't know it's Last Created Unit as the global variable was overridden in the second trigger. This is why you should never attempt to use Last Created Unit after a trigger has waited.

 

[tbjl2006]

Then how would do this: you have this trigger-

Event
Unit-unit enters region

Conditions
((Triggering unit) is a hero) equal to true

Action
Quest- Create required quest title YourQuest with description YourDescription
Quest- mark (last created quest) as discovered

Then you have trigger

Event
Unit- A unit enters region

Action
Mark (Last create quest) as Complete

Then you have another quest trigger.

How would you make it so that if the first quest was started then you start the other one, the second trigger would trigger for the first quest? Or does it already do that? :banghead: :banghead:

 

[Ghan]

Use a Quest Variable?

 

[tbjl2006]

and how do those work

 

[Ghan]

There are plenty of tutorials on variables, so you can look that up on how to create one, but here's the trigger:

Quest
    Events
        Unit - A unit enters a region
    Conditions
    Actions
        Quest - Create a Required quest titled <blah> with the description <blah>, using icon path ReplaceableTextures\CommandButtons\BTNAmbush.blp
        Set MyQuest = (Last created quest)

This will store the quest that is created as the variable MyQuest, so when you need to use it later, just use the variable.

 

[Terrabull]

Two triggers can never run at the same time. Even if they both fire on the same event, one will go and then the other. If you put a wait into the trigger, however, then other triggers will then have a chance to go before the first one is finished. Therefore, if the first trigger creates a unit and then waits, the second trigger can see that new unit with Last Created Unit. Also, if the second trigger then creates a unit, the first trigger won't know it's Last Created Unit as the global variable was overridden in the second trigger. This is why you should never attempt to use Last Created Unit after a trigger has waited.

What if the wait action is at the start of the trigger, and the "Last Created" is after a creation, but there are not waits after the creation?

 

[Doom-Angel]

This is why you should never attempt to use Last Created Unit after a trigger has waited.

u are saying it like it's forbidden u should have mentioned that this cases must require a variable....

 

[Korolen]

What if the wait action is at the start of the trigger, and the "Last Created" is after a creation, but there are not waits after the creation?

That would work fine (forgot about this). Last Created Unit is set and, because there are no waits from then on, no other trigger can change it.