The "native" output is almost 1 on 1 with the original script.
When using the UOSL mode than some code is modified. The reason I programmed it that way was to make the scripts more intuitive to read for those who know the C language. Inside the trigger you see variables being used without a definition. That was very non-intuitive for me.
This resulted in "on speech("*")(object speaker, string arg)"
Two times () on the same line I didn't like. So I decided to replace the () by <>, as the parameter following is not really used by the code, but is more of a parameter to the engine as to tell when to trigger the speech event.
Resulting in "on speech<"*">(object speaker, string arg)"
You can also add a optional chance to the trigger (yes even to the speech trigger):
Originally this looks like: "on 500 speech", which was again non-intuitive for me.
Therefor the Mass M Decompiler will output this as: "on<500>speech("*")(object speaker, string arg)"
Because the 500 chance is again ment as input for the trigger engine inside the EXE, so I used the same <>.
The same is true for the "case" and "default" keywords, in UOSL mode I decided to an extra ":". In native mode this character is not added.
I put those <> and : there for a reason, mainly because I believed, and I still believe that, it improves readability (it's important to know where variables comes from and what parameters are ment for the engine instead of the script itself).
Also note that the latest Mass M Decompiler corrects many bugs found in the scripts : Statistics: Posted by Batlin — Wed Jun 29, 2011 7:13 pm
]]>