About the Project
ChatVerse began with a question: how can viewers feel like part of a streamer’s world without asking the streamer to stop playing? We turned that idea into a persistent fantasy kingdom shaped by Twitch community activity.
Viewers can join through Twitch chat, develop a character, earn rewards, upgrade equipment, invest in their kingdom, and help choose battle tactics. Streamers can run community events and battles from a control room while the Royal Herald turns recorded game events into spoken announcements. Simulation Mode lets us demonstrate the full experience with clearly marked fictional activity, separately from genuine Twitch integration.
We built ChatVerse as a local-first application with a shared game engine for simulation and live environments, persistent game data, a streamer dashboard, and an OBS browser overlay. Battles use deterministic calculations, so outcomes can be reproduced and verified. Narration uses event data and local text-to-speech; an LLM is not required.
One of our biggest challenges was balancing a rich progression system with the pace of a live stream. We designed streamer controls for events and quiet mode, and kept subscription recognition cosmetic so it does not grant gameplay advantages. We also had to distinguish what Twitch can actually provide from what should be confirmed by the streamer: ChatVerse does not assume access to live Valorant or Fortnite match events.
Building the project taught us to treat the viewer and streamer experiences as two sides of the same product. Viewers need reasons to participate and return; streamers need interactions that fit around the game they are already playing.
Built With
- and
- css
- deterministic-game-simulation
- local-text-to-speech
- node.js
- oauth
- obs-browser-sources
- react
- sqlite
- twitch
- twitch-eventsub
- typescript
- websockets
Log in or sign up for Devpost to join the conversation.