How do I learn to understand the client code, make my own interfaces, add higher revision bosses/items into the cache and so forth? To me the client code all looks like obfuscated jibberish.
Printable View
How do I learn to understand the client code, make my own interfaces, add higher revision bosses/items into the cache and so forth? To me the client code all looks like obfuscated jibberish.
That’s because it’s all obfuscated. You’ll be lucky to find someone giving/selling renamed clients for the revision you’re looking for. You’ll be better off learning to rename which takes a LOT of time and determination.
As far as custom interfaces, you’ll need an interface maker and learn cs2 scripts.
Adding higher revision content would require you to convert your client to load the revision data you want. Updating opcodes, input/output data streams, Js5, login.
Compare a regular 718 client to a client loading 718/886 like Valkyr. You’ll see what’s been done.
When did he say we wanted anything apart from a 317 ? this is not the 500+ section ?
The best way is to look at other Clients if you take a look at Elvarg that is very well named here are some Clients to maybe consider downloading and looking at.
You can pack any model from 800+ in a 317 Engine with a bit of work :) and get them working but with interfaces you are probs better of just remaking them since it would be quicker.
https://www.rune-server.ee/runescape...nterfaces.html
https://forum.moparisthebest.com/t/r...actored/552980
If you looking for a higher revision what Selseus said is correct and maybe look at this section of the forums
https://www.rune-server.ee/runescape...client-server/
But the clients are not as well documented so they are harder to learn :)
- u use an already refactored client as reference (can be from different version) as a lot of stuff is just the same (but yeah its not much help if the version difference is huge like having a refactored 317 wont most likely be that much of help if ur trying to refactor rs3 client)
- other option is to do testing. (like if u want to refactor itemDef, take 1 item and first print all the values for it, now u can refactor obvious ones, like possibly name/examine/actions, possibly other values too if u already know them (like if u already know which model the item should use, u can probably find the id in the printed values), after u have refactored all the obvious ones, change 1 of the not yet refactored values to something else and see how it changed - then refactor it to describe what it did)