fix an Issue when more then one RCON-pakets are in data-buffer #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
hi pushrax,
thanks for your work. You helped me so I want to help you ;-)
in socketOnData you handle each buffer as only one RCON-packet.
When you have for example logging enabled you can have multiple packets in the buffer, so the line
cuts the header of the first RCON-Packet but dont touch the headers of the other packets in buffer and emit the packets as one big packet.
This fix read the structure of the RCON-Packets descriped on https://developer.valvesoftware.com/wiki/Source_RCON_Protocol
and splits the buffer in single packets.
lg
fastrde