GAMENIGHT / DOCUMENTATION
Bring your game to the couch
GameNight puts local multiplayer games in one lobby. Players pick a game, keep their controller and profile, and return to the lobby with Back. Your game keeps its engine and runs in its own process.
Pick your engine
| Engine | Starting point | What is included |
|---|---|---|
| LÖVE / Lua | Shared party runner | Lifecycle, controller mapping, window handling and faces |
| Rust / Bevy | Rust SDK | Typed protocol events; your engine handles input consumption and rendering |
| Godot 4 | Godot addon | Lifecycle, controllers per seat, window handling, settings, faces and phone screens |
| C / C++ | Single-header adapter | TCP transport and lifecycle; no controller stream or face decoder yet |
| Unity, Unreal and others | Wire protocol | Implement the connection and engine adapter yourself |
These are implementation starting points, not certifications. Engine support compares every engine feature by feature and lists the open work.
What a good integration does
Prepare a playable frame while hidden and silent. Show it when the host says Start. Pause simulation and audio when players return to the lobby, then resume the same state. Keep processing host messages throughout.
Controllers follow player seats. Faces, names and colours follow player IDs. Your game owns the rounds and score screens; finishing a round does not end the GameNight session.
Read Game lifecycle, then Controllers & players. Add faces and colours once play is reliable.
Have a game already?
Announce it in the developer portal. Sign in with your email; a title, a short pitch and a player count are enough to start. We can help with integration, or you can work through these guides yourself.
How these docs stay current
These pages are built from Markdown in the public repository. Code excerpts are read from source, not pasted copies. CI checks generated pages, internal links and watched implementation files. The Rust example compiles against the SDK; the C example compiles against the header.
An implementation change makes the docs check fail until someone reviews and regenerates the affected pages. This catches drift; it cannot prove every explanation is correct. Godot snippets are source-checked, not runtime-certified. Physical controller and window tests still matter.