22 Mar 11, 04:08AM
This is getting a bit off-topic here. And pretty technical too ;-P
OK, so - UDP doesn't know about order or reliability; ENet compensates for this by providing the reliable-flag (see above post for explanation) and a general mechanism so the receiving end knows what index it's at.
If you read one more sentence after the Features.html-quote from above:
PJ (packet jump) get's it's values from parsed positions, so this is a measure of how bad the route between the client and the server is - those packets don't get resent; if they ever make it to the receiving end, they're simply dropped.
OK, so - UDP doesn't know about order or reliability; ENet compensates for this by providing the reliable-flag (see above post for explanation) and a general mechanism so the receiving end knows what index it's at.
If you read one more sentence after the Features.html-quote from above:
Quote:For unreliable packets, ENet will simply discard the lower sequence number packet if a packet with a higher sequence number has already been delivered.And tempest is right, most messages AC sends are flagged reliable. But SV_POSC, SV_POS and SV_PING (except for once) aren't.
PJ (packet jump) get's it's values from parsed positions, so this is a measure of how bad the route between the client and the server is - those packets don't get resent; if they ever make it to the receiving end, they're simply dropped.