Running Destroyed Trigger

[BloodDrunk]

will running it cause game to crash?

 

[Almia]

Nope. Because it returns null.

 

[BloodDrunk]

nice

 

[MasterTrainer]

No it won't. Proof:

• Go
  • Events
    • Player - Player 1 (Red) types a chat message containing -go as An exact match
  • Conditions
  • Actions
    • Trigger - Run Untitled Trigger 001 <gen> (ignoring conditions)

Then second trigger:

function Trig_Untitled_Trigger_001_Actions takes nothing returns nothing
    call DisplayTextToForce( GetPlayersAll(), "TRIGSTR_001" )
    call DestroyTrigger(gg_trg_Go)
endfunction

//===========================================================================
function InitTrig_Untitled_Trigger_001 takes nothing returns nothing
    set gg_trg_Untitled_Trigger_001 = CreateTrigger(  )
    call DisableTrigger( gg_trg_Untitled_Trigger_001 )
    call TriggerAddAction( gg_trg_Untitled_Trigger_001, function Trig_Untitled_Trigger_001_Actions )
endfunction

... It won't crash bro.

 

[Almia]

^ I already said it bro. Its like adding 1 to 0. or damaging unit with 0.

 

[MasterTrainer]

^ I already said it bro. Its like adding 1 to 0. or damaging unit with 0.

Oh sorry about that... I was supposedly the first one to reply but whilst copy and pasting my trigger data you already replied... looks like your level of coding intellect is just too high and too fast for me (already knew this fact though)

 

[WaterKnight]

The variable is not reset to null when destroying the object. And using functions with invalid parameters can very well cause a crash if it is not protected from it. Just do not do it.

 

[themerion]

I have to agree with WaterKnight. Running functions with destroyed/removed objects can potentially mess up things, and is never a recommended thing in any programming language I've encouontered.

I'd say try to work around it. Set a boolean or sth.

 

[Dr Super Good]

When destroying the trigger you should null the global (to allow proper resource recycling). A custom function can be made to do this in a single call for neater code (but slower, stupid JASS). If TriggerExecute does not crash for null then there is nothing more that has to be done.

If TriggerExecute does crash with null then you need to do pre-condition testing yourself. A custom function can be used for ease of programming.