@s3rius: Go
The custom-script way requires more running time - parsing the string and interpreting it (if not even compile it, blizz really suck at writing script language [WOW Lua being an exception]). While most modern processors probably won't have problems with it, on a trigger-intensive map this might become cumbersome.
1) You can store triggers in the data table - store the needed trigger there and get+execute it by string id.
2) You can create triggers on the fly from functions via CreateTrigger, see exact syntax in wiki. Create a trigger from the function and then run it.
You can't run functions per se AFAIK...
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
@s3rius: Go The custom-script way requires more running time - parsing the string and interpreting it (if not even compile it, blizz really suck at writing script language [WOW Lua being an exception]). While most modern processors probably won't have problems with it, on a trigger-intensive map this might become cumbersome.
It's a tradeoff one must consider.
1) You can store triggers in the data table - store the needed trigger there and get+execute it by string id. 2) You can create triggers on the fly from functions via CreateTrigger, see exact syntax in wiki. Create a trigger from the function and then run it.
You can't run functions per se AFAIK...