- Joined
- Mar 15, 2012
- Messages
- 2,892
Since making one giant trigger can be bad and cause the editor to go extra extra slow and sometimes crash... I was wondering if it's okay to use one global timer for a lot of things?
-
Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
-
Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
-
The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!
-
✅ The POLL for Hive's Texturing Contest #34 is OPEN! Vote for the TOP 3 SKINS! 🔗Click here to cast your vote!
-
✅ The POLL for Hive's Techtree Contest #20 is OPEN! Vote for the TOP 3 FACTIONS! 🔗Click here to cast your vote!
Is multiple timer events to one timer bad?
- Status
sentrywiz
S
sentrywiz
As long as you don't start it while its running, I see no problem.
The obvious problem is using one timer for multiple things makes it
easy to overlap, especially if you start it in multiple triggers.
You should use conditions to check if the remaining time is 0.00 and if yes, start it again.
Though IMO I see no reason to not use multiple loops as long as you turn them off
when you aren't using them. You can easily check when the loop isn't being used, especially
if you use it to pick units.
The obvious problem is using one timer for multiple things makes it
easy to overlap, especially if you start it in multiple triggers.
You should use conditions to check if the remaining time is 0.00 and if yes, start it again.
Though IMO I see no reason to not use multiple loops as long as you turn them off
when you aren't using them. You can easily check when the loop isn't being used, especially
if you use it to pick units.
- Status
