• 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!

HIVE

AGD
AGD
The reason we use TriggerAddCondition() instead of TriggerAddAction() is because it performs faster than the later (There are benchmarks supporting this I think). And the reason we return FALSE is so that the trigger doesn't attempt to run the triggeractions (which is empty in this case, but still has an overhead - like calling TriggerExecute() on a trigger with no actions) when for example there is only one triggercondition registered and it returns TRUE.
AGD
AGD
The only downside in using TriggerAddCondition is that you can't have TriggerSleepAction() inside the code but well, TSA is prone to errors in some cases and it's safer to just use a timer usually.
Back
Top