Thread: General Information

This is most likely not the full definition but this is what I know about runscripts.

Basically a runscript is a script inside the cache (index12 I believe) writen in C/C++ (one of the two, I forgot which one). It is used for interface modifications. It is obfuscated into opcodes that each do something different. So a runscript could look like this:

Code:

588
595
69
483
977
195

Each of these numbers mean something, one could be the start of an if statement, a variable call, a variable value, a method that calls something to edit the components, etc... All of the processing for the opcodes is done inside the client. Unfortunately since 718 clients are obfuscated, it is hard to identify an opcode.

I said earlier they were obfuscated, but MGI released a [Only registered and activated users can see links. ] containing all of them because of the NXT client so we now have acess to their unobfuscated version. If you look at the IComponentDefinitionss of any interface component, you'll be able to spot the runscript ids and parameters that are potentially used by the component.