Thread: New JS5 Protocol (634)?

Originally Posted by Method

The server currently sends 27 integers back to the client that have to deal with the loading of some "required" elements (native libraries and files within certain index files that are necessary to run the game). They might be size values for the required data or something of that nature, but I haven't really looked into it.

Also, the data received after requesting (255, 255) isn't just CRCs (nor was it from 500-600). It used to contain just a crc32 and version value for each reference table, now it also contains a Whirlpool digest of the data.

AHH the native libs forgot about them, odd way to do it i suppose..I completely forgot that they moved them into the js5

But this still doesn't explain the new request packets, go check it out..

When you say "also" do you mean it contains both?

Originally Posted by Method

What new request packets are you referring to? There are still just the normal and priority requests (with opcodes 0 and 1, respectively).

When I say also, I mean it contains all three pieces of data for each entry (i.e. crc32, version, and digest).

Do you know the header is for the received data?

[index]
[id]
[size]
[cycle]
[DATA]

?

Originally Posted by Method

Yes, I do. It's eight bytes long, consisting of:

byte index
short file
byte settings
int size

The settings value contains the compression type (used for allocating an appropriately sized buffer) along with the byte 0x80 if it was a normal request (so the client can choose which queue to grab the request from).

My thread about the Update Protocol and the cache downloader I posted should come in handy if you'd like to learn about the protocol.

lol sorry i just reverse engineered it from their source code, lol.

Originally Posted by Method

What new request packets are you referring to? There are still just the normal and priority requests (with opcodes 0 and 1, respectively).

When I say also, I mean it contains all three pieces of data for each entry (i.e. crc32, version, and digest).

Lol ah so index 255 container have digest now too? Btw for ppl who dont know "file 255" is just used verificy which index 255 containers are outdated/corrupted. Its pretty simple how the engine works.

Originally Posted by dragonkk

Lol ah so index 255 container have digest now too? Btw for ppl who dont know "file 255" is just used verificy which index 255 containers are outdated/corrupted. Its pretty simple how the engine works.

Lol and you say you wrote your cache editor without ripping from client

look at the caculation and u will see

.put(Whirlpool.whirlpool(currentData, 5, currentData.length - 5));