disconnects every 12m 56s

[bytexdigital]

disconnects every 12m 56s

[RyanTT]

Internally the client sends a heartbeat to the server every 3 seconds. The sequence counter will go up to 255, as one byte is reserved for each message's id. 255 * 3 is almost 13 minutes. My assumption is that the sequence counter resetting back to 0 after 255 is making the connection drop. However, the RCon protocol does not seem to indicate that the server will disconnect the client because of that. I'll need to investigate a bit.

[RyanTT]

I believe I have fixed the issue.
The problem was that a code path did not remove messages from the local collection awaiting a response. This caused the very first package with sequence number 0 (and all other packages) to be hold onto, causing there to be two packages with ID 0 eventually. Then the code would accidentally mark the old 0er package as acknowledged instead of the new one.

Please try this version

[PhilPhonic]

Internally the client sends a heartbeat to the server every 3 seconds. The sequence counter will go up to 255, as one byte is reserved for each message's id. 255 * 3 is almost 13 minutes. My assumption is that the sequence counter resetting back to 0 after 255 is making the connection drop. However, the RCon protocol does not seem to indicate that the server will disconnect the client because of that. I'll need to investigate a bit.

I had the same suspicion, but it made no sense to me, cause the sequence counter resetting to 0 after reaching 255 is the way to go, as stated in the BattlEye RCon Protocol Specs.
Thanks for looking into it.

This is no blocker, btw. The application works just fine since the reconnect works like a charm ;-)

[PhilPhonic]

This version works. I'm not seeing those disconnects anymore. Thanks.