[General] Very long triggers and lags ?

[Ardenian]

Hello,

I am worried whether my trigger causes lag.
My trigger is a very long trigger, as it consists of around 30+ If/Then/Else with SetVariable and Condition each If/Then/Else time.

I wonder whether this is will cause lag, as the trigger can run up to 5 times at the same time.

How long can a trigger be without causing lag, considerung its length and runnings at the same time ?

 

[SAUS]

I think the speed performance highly depends on what kinds of things you are checking for / doing. What kind of stuff is happening in the trigger (or what checks)?

 

[Dr Super Good]

How long can a trigger be without causing lag, considerung its length and runnings at the same time ?

If by lag you mean latency then trigger length has nothing to do with it since that is due to network traffic. Certain trigger actions will cause lag due to increase network traffic. Anything that requires synchronization does this.

If you mean "dropped frames" then length does have something to do with it but mostly it comes down to complexity. For example a tiny loop doing expensive unit movement calls will cause a lot of dropped frames compared with a massive long sequential trigger of simple variable sets.

When flow control structures are involved (if/then/else or loops) the actual length of script no longer matters since it comes down to the complexity of the flow control. For example you could have a massive 256 different if/then/else blocks arranged in a binary tree it only takes resolving 8 of them to reach the final code block which is the only code that gets executed (all 255 other blocks are not touched). However if you have a loop with a block in it that you run 256 times then that block will be executed 256 times even though there is only 1 block in the resulting script. This is the power of flow control.

 

[Ardenian]

Thank you for your response!

The event is a casting unit.
Basically, the trigger uses a loop to get an indexed ability, the ability that is casted.
After this, there are many If/Then/Else consisting of Buff checks and counts, check whether the unit has a certain item, checking unit type, hero experience and so on.
The end is a damage function that uses many variables that were set before.

Saying I understand all of your explanation would be a lie, Dr Super Good.
But, as far as I understand, MANY If/Then/Else are no problem because not all are running due to the conditions.
So I do not have to fear that my trigger will have an influence on gameplay ?

 

[RobertMKD]

Consider adding new If/Then/Else's in the Else - Actions of the last If/Then/Else, if the new one is impossible to run when the first one runs.

 

[Ardenian]

Oh, I understand, so I can reduce the amount of running ones, thank you!

 

[PurgeandFire]

It depends on the trigger. If/then/else complexity is handled very quickly by the engine. The performance mostly depends on what is done within the respective blocks. You should focus your attention on loops and things that happen periodically, as well as functions that are particularly heavy performance wise (such as creating a unit or adding a special effect).

But ultimately, the best thing to do is to test the trigger out and see how it runs. You can type /fps in game to measure performance. The higher the value, the better the engine is running. Low values (20 fps or below) tend to look choppy to our eyes and indicate poor performance (we usually call this "lag". Technically "lag" refers to latency, but it is commonly used to describe low frame rates since the English word "lag" refers to falling behind expected performance).

 

[Ardenian]

Ah, alright!
I am going to test it out, thank you! I wasn't aware of this command.

It seems my trigger hardly consists of heavy performance stuff, so I am confident about the issue.

Thank you guys, you helped me a lot!