the new sc2 editor feature of obfuscating the script prevents me from using the TriggerDestroy() native.
i have created a new action with a trigger as param (triggerParam). it calls the custom script ("TriggerDestroy(lp_triggerParam)"), BUT
this doesn't work anymore due to the fact that the params are renamed too. i think it's not possible since nothing is replaced inside the custom script but i ask anyway, so any ideas?
TriggerDestroy() is not available in GUI. Creating an custom action with same name "TriggerDestroy" didn't work either (thought it might override the native not available in GUI).
BTW what does the option enable custom script do? it screws the function call, at least no more params can be passed to a action/function with this option selected. (i think it will run the code inside the inbuild custom script field which isn't used)
ok found it here. you missed the part with the param and trigger reference, but still no success! the trigger can still be executed after calling my custom action!!
native void TriggerDestroy (trigger t);
-update- ok got it working, the param seems to need the use refernce for type flag
This part of that tutorial seems to be false (or outdated):
"You can call the parameters whatever you want but you will need to change the script identifier to the name given in the natives.galaxy file."
Because I tested it with other script identifiers for the parameter and it still worked fine. Only the type and number of parameters needed to be the same (Otherwise a compile error occurs).
It's strange yours only works with that "use reference" flag checked because in mine it worked fine without it.
i cannot run the map, i have no HotS. well just looked into your triggers. strange that it didn't work for me then. anyway now it does, thx for the help
Hello there,
the new sc2 editor feature of obfuscating the script prevents me from using the TriggerDestroy() native.
i have created a new action with a trigger as param (triggerParam). it calls the custom script ("TriggerDestroy(lp_triggerParam)"), BUT
this doesn't work anymore due to the fact that the params are renamed too. i think it's not possible since nothing is replaced inside the custom script but i ask anyway, so any ideas?
1. create an action definition/function with the exact name (to be exact: same identifier) and enable the "native" option.
2. use that function in GUI instead of custom script.
-> no custom script => obfuscation should work
@Ahli634: Go
TriggerDestroy() is not available in GUI.
Creating an custom action with same name "TriggerDestroy" didn't work either (thought it might override the native not available in GUI).
BTW what does the option enable custom script do? it screws the function call, at least no more params can be passed to a action/function with this option selected. (i think it will run the code inside the inbuild custom script field which isn't used)
@FunkyUserName: Go
Make sure to add a parameter of type trigger to the "TriggerDestroy" custom action you created. And tick the "Native" option. It works.
@DeltaV: Go
ok found it here. you missed the part with the param and trigger reference, but still no success! the trigger can still be executed after calling my custom action!!
native void TriggerDestroy (trigger t);
-update- ok got it working, the param seems to need the use refernce for type flag
Glad you got it working. :)
This part of that tutorial seems to be false (or outdated): "You can call the parameters whatever you want but you will need to change the script identifier to the name given in the natives.galaxy file."
Because I tested it with other script identifiers for the parameter and it still worked fine. Only the type and number of parameters needed to be the same (Otherwise a compile error occurs).
It's strange yours only works with that "use reference" flag checked because in mine it worked fine without it.
Example map:
@DeltaV: Go
i cannot run the map, i have no HotS. well just looked into your triggers. strange that it didn't work for me then. anyway now it does, thx for the help
Oh. Hmm yes strange indeed. Maybe I'd have a clue if I knew what that flag actually did.
WoL: