Never heard of this packet...Quote:
TQ has a packet for the lag. Just nobody use it.
What about coding an efficient socket system?
08/10/2010 12:38
Korvacs#16
08/10/2010 13:08
KraHen#17
He means the ping packet I guess
08/10/2010 15:50
~Falcon#18
He's maybe talking about the 0x3F4, which isn't really a 'lag' packet.
08/10/2010 16:46
Korvacs#19
Thats a bot check packet if i remember correctly, nothing to do with lag as far as i know, except that if you lag the server might think your botting due to the large amount of packets that it receives when your connection drops in again...
08/10/2010 17:42
CptSky#20
Yes, I know, in theory it's a bot check, but nobody is sure. I have checked the server-side part and it's all about the timestamp. If it's ridiculous, your connection will drop. With a big lag, my connection can be drop. Tested on my implementation and on a binary server. Maybe it's not related. Hard to be sure.Quote:
08/10/2010 18:17
~Falcon#21
The 0x3F4, is generally named as the "Keep-Alive" Packet, tq issue the packet to the client, if it does not respond within a certain period and with the correct hash (generated based on current character credentials), then the connection is dropped.
Therefore in theory, it is a botcheck, as the response needs to be correct.
Therefore in theory, it is a botcheck, as the response needs to be correct.
08/10/2010 18:19
CptSky#22
The real name is MsgTick. The server check also the timestamp.Quote:
Therefore in theory, it is a botcheck, as the response needs to be correct.
08/10/2010 18:35
~Falcon#23
Yeah. The EO source is a more valuable resource than people realize.Quote:
Thanks to that source, I was able to get my standalone running perfectly :D
Anyway I'm going to stop with the digression, I'm taking this thread further off-topic with every post :o