NoCharge

First-party numbers · built from the catalog

Registry facts

NoCharge currently publishes 26 browser games, 26 guides, 47 articles, 11 collections, 210 setup guides, and 16 tools. 25 of 26 games have a documented complete keyboard path (96%), and 25 are untimed by default or offer an untimed mode. These figures are regenerated at build time from the same source as the Arcade.

Last registry review:

Current counts

Catalog at a glance

MetricValueNote
Games2611 solo + 6 Pass & Play at the time of writing
Pass & Play games9Two players, one device; no network play
Original NoCharge designs5 (19%)Rules are not a named third-party game
Games with a documented complete keyboard path25 (96%)Verified against game code, not prose
Games untimed by default or with an untimed mode25 (96%)Word Tile Rush is timed-only
Median documented session upper bound10 minAcross all games; individual rounds vary
Median upper bound for untimed games10 minUntimed means no countdown, not a fixed length
Guides26One definitive guide per game
Articles47Game notes plus platform/trust explainers
Collections11Each with an explicit inclusion method
Setup guides210Across 7 Quiet Setup topics
Tools16All client-side; no uploads

How these numbers are produced

  1. The Arcade, Discovery Wheel, Game Finder, sitemap, and this page all read the same game catalog and content collections.
  2. Session lengths come from the published session labels; the catalog parses the same label the card shows.
  3. Keyboard completeness is verified against game code (native buttons/focus loop) and is marked per game; it is not inferred from guide prose.
  4. Originality means the rules are not a named third-party game; it is a factual classification, not a quality claim.
  5. The facts regenerated here are exactly the facts published in llms.txt and llms-full.txt.

Monthly update procedure

Runbook (documented in the repo at docs/PHASE0_MAP.md and in IMPLEMENTATION_STATUS.md):

  1. Add the game, tool, or page to its content collection and the game catalog.
  2. Extend the storage allowlist in src/lib/local-game-data.ts and the Privacy storage table.
  3. Run npm run test:unit and npm run build — build-time validation fails on stale catalog entries.
  4. Re-check IMPLEMENTATION_STATUS.md, the sitemap, llms.txt, and this page in preview.
  5. Update REGISTRY_REVIEW_DATE in the catalog when the review happens (dates are data, not page copy).

What these numbers do not say

  • They are not a quality ranking and not a measure of difficulty or fun.
  • “100% keyboard-complete” would be a claim; the honest number is 25 of 26 with Pass the Picture excluded.
  • Session bounds are estimates for typical play, not timers or guarantees.
  • Counts describe the public catalog on the review date; they are not a promise of permanence.

FAQ

How are these counts produced?

The registry-facts page is generated at build time from the same content collections and game catalog that publish the Arcade. The numbers cannot drift from the pages they describe. Review date 2026-08-27 was set when this inventory was completed.

What does “documented complete keyboard path” mean?

The core play loop (start, every move, restart, and completion) works with the keyboard alone, and the game page plus guide document the keys. Drawing-based Pass the Picture is excluded because strokes require pointer or touch.

Does “untimed” mean a game takes no time?

No. Untimed means there is no countdown or pressure timer; a session can still be short or long. Session labels are estimates, not promises.

How often are the facts updated?

Every time the catalog changes. The procedure is: add the game/tool — update IMPLEMENTATION_STATUS.md — run the build (facts regenerate) — update the sitemap and llms.txt endpoints if hubs changed — re-check this page in preview.

Where is the machine-readable list?

Everything is in sitemap.xml, llms.txt and llms-full.txt. The registry facts page is the human-readable version of the same source.

Next action

Read the source