Mapdata is the information files that load the objects
XTea and Ukeys are what stop us from loading different revisions. They are the locks and you have to have the keys. That's why we have such limited 474 stuff
|
Can someone explain the following terms for me (What is it? What does it do? How can it be obtained?) in relation to RS2Emulators:
- Mapdata
- XTea (I saw it somewhere :\)
- Ukeys
Also, I know that to upgrade the revision of your RS2 Server, you need to change some things (as with any other game emulator) such as the packet structures and opCodes. My question is, what other things must you change or add/remove in order to upgrade your revision support.
Thanks,
Becool
Mapdata is the information files that load the objects
XTea and Ukeys are what stop us from loading different revisions. They are the locks and you have to have the keys. That's why we have such limited 474 stuff
Okay, so, How do you obtain these keys. And once obtained, how do you grant yourself access ? I know thats a tough question to ask, but since rs2 emulation has been going on for a while, I think i can ask without flame.
mapdata is the gay name given for XTEA keys, it's the same thing.
mapdata topics
http://www.rune-server.org/runescape...g-mapdata.html
http://www.rune-server.org/runescape...t-mapdata.html
http://www.rune-server.org/runescape...what-does.html
ukey topics
http://www.rune-server.org/runescape...structure.html
http://www.rune-server.org/runescape...date-keys.html
Mapdata:
Mapdata was the name given to the XTEA keys used in encrypting en decrypting the landscape files in the cache. For example the IDX5 file in the cache folder contains all data related to the maps loaded onto the client. There are several kinds of data blocks in this file, one of them being the data for the floor (i.e. tile types as lava, stone etc) and on of them being the data for the objects loaded on top of the map.
These blocks with object data are encrypted with XTEA encryption and the client needs the keys to be included in the packet that loads maps in the client. The client uses these to decrypt the object data blocks so the correct objects can be loaded. We dump these keys as it's impossible to bruteforce them, the encryption is 128 bits leaving +- 2^128 possible key combinations.
Ukeys:
Ukeys was the name given to a block of data calculated of the reference tables of the cache. There is a file in the cache that contains sizes, pointers etc on how to read all the different cache files. The ukeys exist out of a version number of each of these reference tables and their CRC key. Basically the 'ukeys' are a table of the reference tables crc's and version numbers. The client compares this table to the table on the local machine. If something is outdated it can then request the changed files/containers etc from the servers update server.
Revision updating:
In general you will have to update your packets to match the new clients structures and most of the time you need to dump (unless you know how to calculate or retrieve positions) basic interface information as in child id locations for subinterfaces.
« Previous Thread | Next Thread » |
Thread Information |
Users Browsing this ThreadThere are currently 1 users browsing this thread. (0 members and 1 guests) |