60 lines
2.7 KiB
Markdown
60 lines
2.7 KiB
Markdown
_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, acceptance testing, 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 product source of truth is the
|
|
[Twungeon MVP Product Requirements Document](https://git.labyricorn.com/Labyricorn/Twungeon/blob/main/Twungeon_MVP_PRD_Current.md).
|
|
The approved
|
|
[technical specification](https://git.labyricorn.com/Labyricorn/Twungeon/blob/main/Twungeon_MVP_Technical_Specification.md)
|
|
defines the authoritative architecture and game behavior. The
|
|
[acceptance-test and build checklist](https://git.labyricorn.com/Labyricorn/Twungeon/blob/main/Twungeon_MVP_Acceptance_Test_and_Build_Checklist.md)
|
|
sequences implementation and maps evidence to all 33 MVP success criteria.
|
|
|
|
The project remains in pre-implementation planning. These documents establish
|
|
the build baseline, but they do not claim that runtime behavior, Twitch
|
|
integration, or viewer validation is complete. Future records will document
|
|
implementation, testing, release preparation, and maintenance as they occur.
|