sgdk-multiplayer
SGDK multiplayer
Keep a controller's logical slot separate from the player it controls. A pad on
JOY_7 can join as Player 1. Joining, leaving, pausing and respawning are game
rules; SGDK supplies controller snapshots and rendering services.
Establish the session rules
Agree on participant count, join/leave controls, pause ownership, shared versus individual progress, body blocking and what happens when everyone is down. Choose a shared camera, separate screens or another framing policy deliberately. Do not silently impose the Lab's four-player cap, theme or tuning on another game.
Pull ewrogers/sgdk:latest and verify its controller headers and implementation.
Read controller routes and SGDK contracts before
configuring adapters. sgdk-input covers low-level input; this skill owns the
participant/session layer. It does not implement network multiplayer.