Games platform — current developer reference
Audience: Developers and administrators
Player guides: Games overview · Bramble Harvest
This page documents maintained behavior and technical integration points. Past implementation reports and abandoned character plans are available in Git history, not in active feature documentation.
Presentation and assets
- Games use responsive, game-specific UIs with shared navigation, stage and score indicators where applicable. Normal and fullscreen/immersive display modes do not change the authoritative game state.
- Most arcade and puzzle screens use decorative, original WebP backgrounds such as
inky_admin/static/img/games/background_<game-id>.webp. The playable board and interactive controls are separate from the artwork. - Card games have their own presentation CSS/JS; Pantry Path uses its own compact layout. Bramble Harvest and Flavor Lab have purpose-built interfaces.
- Recipe Memory requires accessible cached recipe photographs to start its board; it does not generate substitutes during play.
Persistence, inspection, and cleanup
The shared game-session layer uses game_shared_progress and game_shared_sessions; Recipe Memory and trivia have dedicated progress records. Bramble Harvest uses garden, membership, event, presence, and reward records. All gameplay mutations must pass through authenticated service endpoints with revision/state validation. The global AI Seed allowance is separate from per-garden rewards.
Database Admin offers read-only inspection of Games resources. Game History retention covers eligible finished/shared sessions, Recipe Memory round history, historical garden events, and stale garden presence. It must not delete active game progress, garden state or membership, deletion approvals, or real AI Seed credits.
Bramble Harvest account settings
Character animation, seasonal visitors, ambience, and effects are preferences of the signed-in Blackcap account, not separate per-garden or per-player character equipment. The game reads them via /admin/games/api/cappy-harvest/settings and synchronizes changes on refresh/focus. Fullscreen presentation remains device/browser-local. The garden's Cappy outfit, difficulty, and stamina are shared garden state instead.
Garden export and import
Gardens export as versioned .bh snapshots. The import endpoint creates a new garden with validated, bounded state (including no more than 80 beds); it does not overwrite the original, copy memberships, or duplicate external AI Seed transactions. The importing user chooses Personal or Community visibility. The format preserves the garden difficulty and stamina.
Imported coins are tracked as a subset of the available balance: ordinary spending draws down the imported reserve, while AI Seed purchasing requires eligible, newly earned coins, adequate reputation, and accumulated daily allowance. A portable file is not a cryptographically secure proof of fresh gameplay; external-credit protection requires stronger provenance if policy changes.
Multiplayer events and UI
Garden mutations and revisioned event deltas drive the shared garden display. Viewers replay visual work and sale receipts in event order when possible; when events are missing, the client adopts authoritative state instead of fabricating intermediate actions. The presence/refresh cycle keeps shared state up to date. Shop, Sell, and Growing Now may stay open through remote updates; editing dialogs are protected from interruption. Every physical action and stamina purchase must be transactionally validated against the current shared revision.
Validation
Developer scripts and tests live under tests/ and tools/. Stamina/order balancing simulation scripts are optional and are not required for production. See Bramble developer tools for console-only visual previews, including the first-time player introduction.