|
Hello all,
I've scripted out some scripts. All are done by myself by looking at the opcodes within each script binary file so some may not be fully correct but I wanted to make them as readable as possible. I know there are a few tools released but I decided to go my own route and do it fully. There is about 707 scripts in the zip file.
When I read the opcodes as to where it can return a default value or a value made within the script I use a colon to differentiate them. For some of the callbacks, I realized later on that the callbacks were just another script and the parameters where being passed. Therefore some are as follows:
new Callback([#,#,#], [#])
and now callbacks are:
new Callback(script)<params>)
Some opcodes are unknown to me so they are just labeled as OP_#.
For sample:
Spoiler for Sample:
Here is the zip file: https://mega.nz/file/aE9WHJxb#BEdVRH...9hG-6s4CmLYEVU
That's a nice learning project, but since there's already a release CS2 (de)compiler that supports all 3 revision types (osrs, rs2, rs3) this is probably more aligned towards people who don't know how to set it up and get the scripts themselves. Any reason you decided to work on your own tool though?
Anyway, cool contribution!
Well I wanted to do it to where whenever there was a varc, varp, varpbit or a varcstr present in a script I could document in a single file that can tell me what type of "config" and what ID I should use for a certain task. Other than that, I just decided to do it without a CS2 project, although it would be so much easier. I'm not anywhere close to being able to create a program for making a binary file go into a sort of flow type text file to where it is readable. So I guess by me doing this myself, its just helping me get into how they decided to write their scripts. lol.
« Previous Thread | Next Thread » |
Thread Information |
Users Browsing this ThreadThere are currently 1 users browsing this thread. (0 members and 1 guests) |