Triggers functions are constants, which means you can know the function a trigger has by turning it to custom text, check the functionname, and then "Undo" the conversion. So, you can create your custom function in GUI and call the function with the ExecuteFunc("") or just Execute the trigger, since the trigger itself has the function.
Most system uses "u" and "i" for units, and, as far as I know, globals and locals can't have the same name, or their values could get messed up, so, it's better to avoid "u", "i", "p", "h", "r" globals.
If it is undefined variable, why when I put that code in map header, everything works fine ?
Because the name of the variable the function requires is irrelevant.
JASS:
function takes unit u returns nothing
call KillUnit(u)
endfunction
Now, if you call it from GUI
-
t
-
Actions
-
Set TheUnitIWantToManipulateWithTheCustomFunction = (Triggering Unit)
-
Custom script: call Test(udg_TheUnitIWantToManipulateWithTheCustomFunction)
The system will take "
udg_TheUnitIWantToManipulateWithTheCustomFunction" and do with "
udg_TheUnitIWantToManipulateWithTheCustomFunction" all the things that the function does with "
u", as long as inside the function you manipulate "
u".
Remember that functions uses arguments, not "strings". Doesn't matter the name you give to the variables the execution will work as long as you give the right argument (you can set u = bj_lastCreatedEffect and it won't work, because, tough you're using u, that isn't the right argument for the function). They don't even have to be a variable.
call Test(GetTriggerUnit())
You're not using "endfunction" at the end of the function.
They don't just have to copy the trigger, but they have to copy it in the right place. If the trigger with your function si at #13 on the list, and the Player is using the function of that trigger in Trigger#8 in the list, it won't work, because the trigger #13 hasn't been declared when you're already calling it in the trigger #8. The map header starts before anything, even before "Map Initialization", so, that's the best spot for any custom function. In worst cases, the player would have to create a folder called "Initialization" and add there (in the correct order) all the triggers that are just used for initialization, and that doesn't call another triggers or another functions, other than the functions already written inside them.
