fix: Align lockstep player IDs with command player IDs in multiplayer#1175
Merged
Merged
Conversation
Fixes two critical multiplayer issues: 1. Lockstep barrier used network peer IDs (pubkeys) but commands used slot IDs (player1, player2), causing lockstep to wait indefinitely. 2. Command validation only checked against the first remotePeerId, rejecting valid commands from other peers in 3+ player games. Changes: - Add peer-to-slot ID mapping (peerToSlotId) to multiplayerStore - Set up mapping when peers connect (host: guest.pubkey -> guest.slotId, guest: hostPeerId -> host's slot) - Update getExpectedPlayerIds() to return slot IDs via getAllRemoteSlotIds() - Update command validation to accept commands from any mapped remote slot https://claude.ai/code/session_01PqaegjhvDFuLUVK3bDmsgr
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes two critical multiplayer issues:
Lockstep barrier used network peer IDs (pubkeys) but commands used slot IDs (player1, player2), causing lockstep to wait indefinitely.
Command validation only checked against the first remotePeerId, rejecting valid commands from other peers in 3+ player games.
Changes:
https://claude.ai/code/session_01PqaegjhvDFuLUVK3bDmsgr