Twungeon · Development log
The public record of Twungeon from pre-development through MVP delivery and beyond.
Twungeon now enforces four fixed party slots, reforms the party between floors, uses a five-second rolling player-phase timer, and presents consistent player colors in responsive desktop and mobile Extension layouts.
Twungeon gained a private, authenticated operator console and last-socket disconnect handling that sends absent viewers directly into AutoGuard instead of delaying every player phase.
Read entry →Twungeon replaced its component-style viewer popup with a transparent, responsive Twitch video overlay that reuses the authenticated controller while leaving the streamed dungeon visible.
Read entry →Twungeon moved from a local proof of concept to a live Twitch-connected deployment with broadcaster OAuth, Extension identity sharing, Channel Points resurrection, a focused viewer control panel, and an authenticated spawn button.
Twungeon moved beyond its planning baseline with an authoritative local game loop, production-shaped transport and UI boundaries, automated verification, and a deliberate scope correction from Bits to Channel Points resurrection.
Technical specification work began for the Twungeon MVP, translating the approved product boundary into authoritative state, component contracts, deterministic game rules, integration boundaries, and a verification strategy.
Read entry →With the technical specification approved, Twungeon gained a sequenced ten-phase build checklist and 33 traceable acceptance tests that define the evidence required before the MVP can be called complete.
An extensive design conversation between ChatGPT 5.6 Sol High Reasoning and Labyricorn (Christopher Chambers) shaped the Twungeon concept, narrowed its MVP, and produced the current product requirements document.
Read entry →