Initially off triggers consume resources?

[chopinski]

I know that's a realy dumb question, but, if i have a trigger that's initially not enable and that trigger have an event like "A Unit is Attacked" and a condition, will that trigger consume any resources from my computer when i'm in game?

 

[ShadowFlare]

Do you enable in-game? If you leave it disabled then it will be ignored by the compiler.

 

[chopinski]

Do you enable in-game? If you leave it disabled then it will be ignored by the compiler.

I'm editing a map, and it has a lot of triggers (100+ triggers), most of them are for heroes skills and others for items, so i just enable a trigger if this trigger belongs to a unit that is controlled by a player user, otherwise all of non used trigger stay disabled during the game. So disabled ones will not be a problem right?

 

[ShadowFlare]

Nope, they will be ignored completely. 100! Oof sounds like time consuming fun right there haha. GL!

 

[chopinski]

Nope, they will be ignored completely. 100! Oof sounds like time consuming fun right there haha. GL!

Yeah, ahahha, i think i've been editing this map for like 1 year, almost every day!! Thx Man.

Btw, how bad is for gameplay a periodic trigger that's always on?

 

[SAUS]

Yeah, ahahha, i think i've been editing this map for like 1 year, almost every day!! Thx Man.

Btw, how bad is for gameplay a periodic trigger that's always on?

It's not a problem as long as the trigger doesn't do ridiculous amounts of work or doesn't run often.

1) How low is the timer?
2) What happens in the trigger?

You can have tons of triggers and timers without any problems.

I don't know about turned off triggers, but I doubt they will be a problem.

 

[chopinski]

It's not a problem as long as the trigger doesn't do ridiculous amounts of work or doesn't run often.

1) How low is the timer?
2) What happens in the trigger?

You can have tons of triggers and timers without any problems.

I don't know about turned off triggers, but I doubt they will be a problem.

Considering the one's that is always ON, they usually just move units to position.

 

[SAUS]

Considering the one's that is always ON, they usually just move units to position.

As long as you are clearing the memory leaks when when the trigger runs, there should be no problem (and that is only if it's going to be run A LOT during a single game).

 

[Dr Super Good]

Triggers that are disabled are not compiled so have no overhead in game.
Triggers that are off and have evenets should have practically no overhead in game as their actions will not fire. I am unsure if the events are deregister from internal event lists or if the event just does not cause the JASS virtual machine to run but in any case it is a lot faster than having the trigger on.
Triggers that are on and have events will cause the JASS virtual machine to run every time the event fires. Although quite fast, it is not trivial so if it happens hundreds of times at once it can result in performance problems.

 

[IcemanBo]

DSG, I think they he means "disabled" like the trigger is simply turned off.
Though there is an extra option in trigger editor to completly deactivate a trigger (marked with a red cross), then it would not even compile.

---
Normaly disabled triggers, so ones you can turn on later again, won't be unregistered by the used event(s).
But that's probably not so important because onEvent, it won't fire the trigger's evaluation and execution part (so running the trigger), and so it's not really consuming resources.

It's good practice to turn triggers off that are needed only temporary.
And the bigger the code-body is and the more operations are done insde, the more effect it will have obviously.