Function can run only one times

[btdonald]

scope Test initializer Init

private function Init takes nothing returns nothing
    // WORKING
    call AddLightning("CLPB", false, 2000,2000, -2000, -2000)
    call GroupEnumUnitsInLine(ENUM_GROUP,2000,2000,-2000,-2000,200,null)
        loop
            set bj_lastCreatedUnit = FirstOfGroup(ENUM_GROUP)
            exitwhen bj_lastCreatedUnit==null
            call SetUnitVertexColor(bj_lastCreatedUnit, 255, 0, 0, 255)
            call GroupRemoveUnit(ENUM_GROUP,bj_lastCreatedUnit)
        endloop
    call TriggerSleepAction(3)
    // NOT WORKING
    call GroupEnumUnitsInLine(ENUM_GROUP,2000,2000,-2000,-2000,200,null)
        loop
            set bj_lastCreatedUnit = FirstOfGroup(ENUM_GROUP)
            exitwhen bj_lastCreatedUnit==null
            call SetUnitVertexColor(bj_lastCreatedUnit, 255, 255, 0, 255)
            call GroupRemoveUnit(ENUM_GROUP,bj_lastCreatedUnit)
        endloop
endfunction

endscope

Idk why func

GroupEnumUnitsInLine

only work one times.

I put that func in General Func. I can't see anything goes wrong so I need your help

This is the test map
View attachment Standard Plugin.w3x

P/s: SOLVED

 

[Wietlol]

The init function is not a trigger.
So the TriggerSleepAction tries to make the trigger thread sleep which is impossible because it is not a trigger.
That is why the script beaks and wont run the second action.

 

[Bribe]

Scopes don't have their own init threads, so you are crashing the main thread with the TSA. Change this to a library or use ExecuteFunc on this from your scope initializer.

 

[btdonald]

Scopes don't have their own init threads, so you are crashing the main thread with the TSA. Change this to a library or use ExecuteFunc on this from your scope initializer.

But that cause same problem with my Wall System (On the bottom of category)

P/s: SOLVED

 

[Bribe]

I can assure you that ExecuteFunc (which is what library initializers use) will fix the function you shared. I have no idea what that other trigger looks like. Care to share?

(Im not at my PC)

 

[Wietlol]

I wont suggest ExecuteFunc() because the map optimizer changes the names of the functions.
I dont know if it also changes the strings in ExecuteFunc() but last time I checked it didnt.

You could make a trigger that starts on map init or make a timer that would call the second GroupEnumUnits action.

 

[Zwiebelchen]

I wont suggest ExecuteFunc() because the map optimizer changes the names of the functions.
I dont know if it also changes the strings in ExecuteFunc() but last time I checked it didnt.

You could make a trigger that starts on map init or make a timer that would call the second GroupEnumUnits action.

Map optimizer won't break ExecuteFunc() unless you use string concatenation (and this only if you have "compress names" ticked).

So as long as you input the function name as a complete string, it will work.

This will work with map optimizer regardless of settings:

library creampie initializer init

function lolpatrol takes nothing returns nothing
endfunction

function init takes nothing returns nothing
     call ExecuteFunc("lolpatrol")
endfunction

endlibrary

This will break when using map optimizer and "compress names" is ticked:

library creampie initializer init

function lolpatrol takes nothing returns nothing
endfunction

function init takes nothing returns nothing
     call ExecuteFunc("lol"+"patrol")
endfunction

endlibrary

However, you can just do this and always be on the safe side:

library creampie initializer init

function lolpatrol takes nothing returns nothing
endfunction

function init takes nothing returns nothing
     local trigger t = CreateTrigger()
     call TriggerAddAction(t, function lolpatrol)
     call TriggerExecute(t)
     set t = null
endfunction

endlibrary

 

[Wietlol]

You cant execute triggers on the main though.

 

[Bribe]

You cant execute triggers on the main though.

How so? Blizzard does that for all Map Initialization triggers.

 

[Wietlol]

Because I tested it running a trigger in the InitTrig function of another.
However, I didn't realize that the trigger that I would run was initialized in another InitTrig function that could have been called after the other.