Hello. I've been currently cleaning and rewriting the Matrix source since there are so many areas where content could be done better. I just need some explanations on how a few things work because I am not that well versed in general RSPS knowledge.
-How configs work
-How RunScript works (Please explain how they work, what they are, etc.)
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:
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.Code:
588 595 69 483 977 195
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.
|« [Matrix 3] Bad Location errors | I need the Chaos Giant Emote/Gfx Ids »|
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)