Skip to content

Repository files navigation

BoredRoom Games

This repository publishes the official signed game catalog for BoredRoom.

Current release: 1.10.0.0

Catalog

Each directory under games/ contains one independently installable game with its manifest, runtime entrypoint, metadata, and contract tests. The generated catalog.json records artifact URLs, versions, capabilities, SHA-256 digests, Ed25519 signatures, and archive sizes.

Game ID Players
Bible Timeline Rush bible-timeline 1–12
Color Wahala color-wahala 2–8
Connect 4 connect-4 2–4
Endless Tic Tac Toe ettt 2–4
Faith Feud faith-feud 2–12
Half & Half half-half 2–8
Hustle hustle 2–4
Oga Landlord landlord 2–6
Logo Guesser logo 2–8
Ludo ludo 2–4
Market Price market-price 1–12
Pidgin Translator pidgin-translator 1–12
Money Trivia trivia 2–8
Whot whot 2–8
Word Wahala word-wahala 2–8

Runtime contract

Every game runs inside BoredRoom's authoritative HouseSessionRoom. A plugin provides lifecycle methods, legal-intent validation, snapshots, restore, finish/recap data, and separate public, controller, companion, and crowd projections.

Required guarantees:

  • Client actions are untrusted until validated by the runtime.
  • Hidden answers, hands, racks, and transcripts never enter public projections.
  • One controller never receives another controller's private state.
  • Snapshot/restore preserves timers, turns, settings, and deterministic state.
  • AI may suggest content or legal actions but cannot bypass runtime validation.
  • Gameplay remains available when external AI, speech, or content providers fail.

Development

git clone https://github.com/thathman/BoredRoom-Games.git
cd BoredRoom-Games
npm install
npm test

The suite runs shared contract tests and every per-game runtime test.

Signed releases

Production releases are built by GitHub Actions from a four-part version tag. The signing key is a repository secret and must never be committed, logged, placed in a game artifact, or exposed to the browser.

Maintainers with an authorized local signing environment can run:

RELEASE_TAG=vA.B.C.D BOREDROOM_GAMES_SIGNING_KEY="$(cat /secure/path/private.pem)" bash scripts/release.sh

The release process tests all games, builds all artifacts, verifies signatures with the public key, publishes the release assets, and updates catalog.json.

Policies

About

No description, website, or topics provided.

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages