Add Room/Game Server Protocol documentation to RFC #2807
Merged
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.



Summary
Changes
New section 4.6 includes:
Also updates:
Related Issues
Test plan
🤖 Generated with Claude Code
Note
Integrates detailed Room/Game Server Protocol into the main RFC and updates spec metadata.
4.6 Room/Game Server Protocol: port ranges (9000-9014TCP,9500-9508UDP), client/server opcodes (0x1xx/0x2xx), channel types/flags,RoomChannelData(256B) andUserData(64B) structures, game server state machine, room join and server startup flows, full session diagram, NPS error codes, and string length constantsNPS_SEND_NOT_SINGLE (0x87)in game message routingGame/Room Serversand rename lobby toLobby Server (PLS); adds terms (PLS,Riff,CommId,Channel)docs/MCO_PROTOCOL_RFC.mdto version0.2.0with changelog and dateWritten by Cursor Bugbot for commit b836be0. This will update automatically on new commits. Configure here.