TriggerCondition > TriggerAction?

[The_Kingpin]

So, one of my maps uses dynamic triggers, and I've heard that using TriggerConditions as the actions instead of TriggerActions can be a lot faster and more convenient, and that destroying TriggerActions can bug your map. Is this really true?

 

[Arkan]

I don't know if it's any significant improvement, but I'm using conditions instead (as long as you don't have waits, they work perfect), and it never failed me.

You don't have to think about cleaning up any actions.

 

[SFilip]

Destroying TriggerActions can be messy as you most likely need to attach them to your trigger.
This is the main advantage of conditions, they don't need to be destroyed.
Both a disadvantage and an advantage is that they run in the same thread, this makes them faster, but you can't use waits inside.
So if you have some Jass experience conditions are usually a better idea.

 

[The_Kingpin]

Great.
I don't need waits anyway.

Thanks!