New ping/pong mechanism

[apes0]

New ping/pong messages

The ping and pong messages have been modified, now instead of being 0xB00B and 0xB00C, they are created as follows:

• ping: 0x0B + a blob consisting of the message id of the client (as a uint32)
• pong: 0x0C + a blob consisting of the message id of the server (again as a uint32)

note: the message ids are basically like the ones of the extracted tag message's ids

Other findings about the messages

There seems to be a new "feature" that makes pings rarer. It skips every second ping, by doing this:

...
pingID++;
if (!fasterPingRequirement && (pingID % 2) !== 0) {
	return;
}
...

(pingID just being the number of the ping message and fasterPingRequirement being whether not to skip every second ping, which currently seems to be always set to false)

note: pingID is only used here, and the ids in pings/pongs are the message ids of the party who is sending them :-)

[Sup3rFire]

fasterPingRequirement is only used when in gameplay

[apes0]

Ah, my bad, i thought it was a constant haha. :p