_model: project --- schema_version: 1 --- project_id: twungeon --- title: Twungeon --- summary: A Twitch-controlled cooperative dungeon game where viewers share a live world, control individual characters, and discover whether the core loop is worth building into a full game. --- status: active --- started: 2026-08-17 --- author: Christopher Chambers --- repository_url: https://git.labyricorn.com/Labyricorn/Twungeon --- default_branch: main --- tags: Twitch, Twitch Extension, RPGJS, Twurple, TypeScript, game design, pre-development, PRD, MVP, planning, architecture, documentation --- body: Twungeon is a Twitch-controlled cooperative dungeon game. Viewers watch a shared dungeon on the stream while controlling their own characters through a Twitch Extension. Followers join intentionally with `!spawn`, take turns using simple action points, fight or evade a Goblin Guard, and cooperate to reach the exit. The MVP is designed to prove the complete interaction loop with real Twitch viewers: eligibility, identity binding, spawning, movement, combat, healing, death, Bits resurrection, floor advancement, and total-party reset. It uses a deliberately small two-room floor with one Goblin Guard so the project can test the social game idea before investing in balance, polish, progression, or production art. The stream-facing experience has three required regions: a compact control/status area, the shared game view, and a running action log. When no players are active, the current floor remains loaded in a dormant state and invites an eligible follower to type `!spawn`. The initial technical direction is RPGJS for the prototype game environment, Twurple for Twitch integration, and a Twitch Extension for player controls. The design keeps Twungeon's game rules separate from RPGJS where practical so the prototype can be replaced without discarding the validated concept. The current source of truth is the [Twungeon MVP Product Requirements Document](https://git.labyricorn.com/Labyricorn/Twungeon/blob/main/Twungeon_MVP_PRD_Current.md). The project is in pre-development: the PRD and MVP definition are complete, and this repository will document the transition through technical planning, implementation, testing, release preparation, and maintenance.