Thread: Player update protocol - Could use a little guidance :P

Originally Posted by Graham

I don't quite understand what you're trying to get at. The magic 2047 clause works for any number of players - it makes the client break out of the loop early and switch to the block reading mode.

Remember that the bit-based updates for all players are always prior to the (byte-based) blocks for all players. They aren't interleaved - i.e: the order is like this:

- existing player 1 bits
- existing player 2 bits
- new player 3 bits
- magic 2047 marker
- existing player 1 blocks
- existing player 2 blocks
- new player 3 blocks

If no players have any blocks, then you can omit the magic 2047 marker, because there is no need to distinguish between bits/blocks in that case. The client detects it is at the end of the packet and skips reading the blocks.



The A/C/S suffixes aren't Jagex's naming scheme (I don't think we know what Jagex call them).

But yes, I've long suspected that whoever used those suffixes originally used them to stand for add, complement and subtract respectively.

Basically in that loop it's considering my masks data, which it shouldn't obviously lol cause then its reading the bits in my masks as new players. That's my prob, I've actually got another post explaining my problem in much more detail here:
[Only registered and activated users can see links. ]

Originally Posted by Graham

I don't quite understand what you're trying to get at. The magic 2047 clause works for any number of players - it makes the client break out of the loop early and switch to the block reading mode.

Remember that the bit-based updates for all players are always prior to the (byte-based) blocks for all players. They aren't interleaved - i.e: the order is like this:

- existing player 1 bits
- existing player 2 bits
- new player 3 bits
- magic 2047 marker
- existing player 1 blocks
- existing player 2 blocks
- new player 3 blocks

If no players have any blocks, then you can omit the magic 2047 marker, because there is no need to distinguish between bits/blocks in that case. The client detects it is at the end of the packet and skips reading the blocks.



The A/C/S suffixes aren't Jagex's naming scheme (I don't think we know what Jagex call them).

But yes, I've long suspected that whoever used those suffixes originally used them to stand for add, complement and subtract respectively.

Omg Graham thank you! I just presumed it was for a single-player instance, but manually breaking makes a lot of sense, THANK YOU!