One JSON file. One PR.

The catalogue is an open, reviewable list of couch multiplayer games β€” one file per game, no build step. A planned entry needs nothing but metadata; climbing the ladder to certified is a follow-up PR whenever you're ready.

The whole entry β€” planned level
{
  "id": "duck-game",
  "title": "Duck Game",
  "tagline": "Ducks. Guns. No mercy.",
  "players": { "min": 1, "max": 4, "best": 4 },
  "price": "paid",
  "emoji": "πŸ¦†",
  "color": "#ffb454",
  "integration": { "level": "planned" }
}

That's a mergeable PR by itself β€” enough for the shelf to show it. Player counts, hardware requirements, and integration level all climb later, in their own PRs.

The ladder
certifiedspeaks the protocol and passes gamenight-certify
integratedspeaks the protocol; not (yet) certified
adapterlaunchable but silent β€” kill-and-relaunch transitions
plannedwishlist metadata β€” no integration yet

Every entry declares honestly where it stands. Climbing the ladder is the point β€” a PR that moves a game to certified pastes the harness output straight in.

The full guide

Everything below is rendered live from catalog/README.md β€” the same file that ships in the repo. One source of truth.

Loading the guide…