The compression algorithm is completely different. The files start with the following header:
'Z', 'L', 'B', 0x01
followed by the uncompressed length as a 4 byte integer and then a ZLIB stream.
I don't think it'll fit into the Store interface easily, as it's a bit too low level for the changes.
The Js5Index format seems to be unchanged (in a sample of one, which isn't a great sample size).
https://github.com/villermen/runescape-cache-tools/tree/nxt-support is a good reference.
The SQLite files are fairly easy to figure out.
The compression algorithm is completely different. The files start with the following header:
'Z', 'L', 'B', 0x01
followed by the uncompressed length as a 4 byte integer and then a ZLIB stream.
I don't think it'll fit into the `Store` interface easily, as it's a bit too low level for the changes.
The Js5Index format seems to be unchanged (in a sample of one, which isn't a great sample size).
The JS5 container format is still used in the JS5 remote protocol. However, it's impossible to go back from the new ZLB format to the JS5 format without recompressing everything (and thus changing all the checksums). I therefore think implementing it is of limited utility.
I'm not going to implement this.
The JS5 container format is still used in the JS5 remote protocol. However, it's impossible to go back from the new ZLB format to the JS5 format without recompressing everything (and thus changing all the checksums). I therefore think implementing it is of limited utility.
https://github.com/villermen/runescape-cache-tools/tree/nxt-support is a good reference.
The SQLite files are fairly easy to figure out.
The compression algorithm is completely different. The files start with the following header:
'Z', 'L', 'B', 0x01
followed by the uncompressed length as a 4 byte integer and then a ZLIB stream.
I don't think it'll fit into the
Storeinterface easily, as it's a bit too low level for the changes.The Js5Index format seems to be unchanged (in a sample of one, which isn't a great sample size).
I'm not going to implement this.
The JS5 container format is still used in the JS5 remote protocol. However, it's impossible to go back from the new ZLB format to the JS5 format without recompressing everything (and thus changing all the checksums). I therefore think implementing it is of limited utility.