• 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.
  • 💡 We're thrilled to announce that our upcoming texturing contest is in the works, and we're eager to hear your suggestions! Please take this opportunity to share your ideas in this theme discussion thread for the Texturing Contest #34!
  • 🏆 Hive's 7th HD Modeling Contest: Icecrown Creature is now open! The frozen wastes of Icecrown are home to some of Azeroth’s most terrifying and resilient creatures. For this contest, your challenge is to design and model a HD 3D monster that embodies the cold, undead, and sinister essence of Icecrown! 📅 Submissions close on April 13, 2025. Don't miss this opportunity to let your creativity shine! Enter now and show us your frozen masterpiece! 🔗 Click here to enter!

[Solved] call DestroyTrigger vs Turn Off

Status
Not open for further replies.
Level 12
Joined
May 7, 2008
Messages
346
So I've been thinking about this lately a bit too much, and I'm not sure what is the right decision.

Basically I have a lot of triggers in my map that get used only once and therefore I've been using call DestroyTrigger( GetTriggeringTrigger() to get rid of them.

However, I've also had some crashes (could be unrelated to this, but I'm not certain) and I have to rethink about using the call Destroy function in GUI.


My question would be:

Does the call DestroyTrigger( GetTriggeringTrigger() have any benefit over Turn off This trigger, in particular in the clearing / purging RAM?
 
Last edited:
Level 7
Joined
Sep 4, 2016
Messages
116
I can't say for sure either, but I do know it reduces the memory taken by the triggers during the match. This could make a difference if you have a significantly large amount of triggers you are destroying.

I imagine that if it is the cause of any of the crashes, it is because a trigger gets destroyed that another trigger is still dependent on. Someone with more experience with that action hopefully can verify or give additional insight.
 
Level 12
Joined
May 7, 2008
Messages
346
I can't say for sure either, but I do know it reduces the memory taken by the triggers during the match. This could make a difference if you have a significantly large amount of triggers you are destroying.

I imagine that if it is the cause of any of the crashes, it is because a trigger gets destroyed that another trigger is still dependent on. Someone with more experience with that action hopefully can verify or give additional insight.

Thanks.

Truth to be told some of the triggers I'm destroying are very minor so even if they weren't destroyed shouldn't use that much of RAM anyway.

Something like - set point / create unit / create fx / kill unit / remove fx / clear leak / etc.
 
Level 12
Joined
May 7, 2008
Messages
346
Found the solution and i wasn't the call Destroy, lol.

Ordering an artillery unit with an orb ability to attack-ground crashes the game.

I've ordered the Mortar Team to Attack Ground, and after 5 mins or so the game freezes for all players and crashes.

You think stuff like this would simply not work instead of crash things, but oh well.


Thanks for the help!
 
Status
Not open for further replies.
Top