Labyricorn/Twungeon
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Implement Channel Points Twungeon MVP

Browse Source
This commit is contained in:
Labyricorn
2026-08-17 07:16:13 -07:00
parent 21b845d16e
commit 222cf903f6
33 changed files with 4399 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.labyricorn/project/contents.lr
+16 -13
View File
@@ -18,7 +18,7 @@ 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
tags: Twitch, Twitch Extension, Channel Points, RPGJS, Twurple, TypeScript, game development, proof of concept, MVP, architecture, acceptance testing, documentation
---
body:
@@ -30,20 +30,22 @@ 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.
death, Channel Points 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 runnable proof of concept uses an authoritative TypeScript game core,
deterministic two-room floor generation, HTTP and WebSocket boundaries, and a
shared broadcast/controller interface. Twurple supplies the production Twitch
boundary for chat, follower verification, Channel Points redemptions, and a
Twitch Extension identity flow. The RPGJS boundary remains an authority-free
render adapter rather than a completed engine integration.
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).
@@ -53,7 +55,8 @@ 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.
The repository can run locally with synthetic viewer identities and has passing
lint, type-check, domain, integration, and production-build gates. This is a
proof of concept, not an accepted MVP: live Twitch credentials, independent
setup, first-time-viewer usability, and real-viewer concept validation have not
yet produced acceptance evidence.