Mythweave

Mythweave turns Twitch chat into a shared fantasy adventure. Viewers cast ideas, streamers approve choices, and every decision reshapes the world. Chat casts. Worlds change.

Comment

Inspiration

What if the next message in a Twitch stream could become a bridge?

Twitch communities already create stories together through chat, jokes, and shared decisions. I wanted to give those contributions a visible place in the world of a game.

That became Mythweave: a shared fantasy adventure where viewers propose ideas, the streamer approves choices, and the world remembers what happened.

Chat casts. Worlds change.

What it does

Mythweave connects Twitch chat to a cooperative fantasy adventure called The Shattered Observatory. The community starts with ten Aether and eight minutes to cross a broken bridge, survive a storm, and restore the observatory.

Viewers choose one of three roles:

  • Weavers build and restore.
  • Wardens protect the party.
  • Seekers uncover alternative paths.

Using commands such as !join weaver and !weave fallen branches into a bridge, viewers submit ideas through Twitch chat. Mythweave checks the role, supported action, encounter, and resource cost before adding a proposal to the streamer's approval queue.

Equivalent ideas gather support around one proposal. The streamer reviews the choice and has the final say.

Decisions affect later encounters. Building an exposed branch bridge strengthens the next storm. Raising a protective ward captures lightning, reducing the cost of restoring the final lens.

A synchronized read-only overlay displays the world, an authenticated companion page provides another participation route, and the final recap credits accepted contributions with their authors, support, costs, and consequences.

How I built it with Codex

I used Codex throughout development, starting from a written product brief and Canva designs.

Codex helped implement the React and TypeScript interface, Express server, authoritative game rules, Twitch OAuth and EventSub integration, SQLite persistence, and server-sent updates that synchronize the app and overlay.

The work progressed milestone by milestone: establish the adventure, implement proposals and approvals, connect Twitch, match the visual design, test failure cases, and verify a complete live run.

Codex also helped diagnose connectivity problems, improve encounter-specific command guidance, write setup documentation, and prepare the public repository and demo.

Gameplay uses a deterministic action catalogue. An optional OpenAI interpreter can map unfamiliar phrasing to allowed actions, but the server still validates every decision. The recorded live run worked with that interpreter disabled.

Challenges I faced

The hardest part was making chat-driven decisions reliable.

Duplicate events, repeated votes, stale proposals, role changes, and connection failures must not spend resources or advance the world incorrectly. Approvals therefore recheck ownership, current state, support, role, and available Aether before committing a change.

Another challenge was distinguishing an integration problem from a game problem. During live testing, a server network restriction prevented Twitch connectivity. Resolving it allowed real authentication and chat messages to reach the app.

Translating the Canva designs into working screens also required attention to branding, layout, and readable controls.

Accomplishments I'm proud of

Mythweave completes a real Twitch-driven journey from chat command to proposal, approval, world change, and attributed recap.

The recorded run builds the bridge, raises the storm ward, restores the lens, and wins with two Aether remaining.

The public repository includes source code, assets, setup instructions, fourteen automated tests, and a passing GitHub Actions build.

What I learned

A community interaction becomes more meaningful when people can see both its consequences and who contributed.

I also learned that working integrations require testing beyond the happy path. Authentication, reconnection, timing, persistence, and duplicate delivery all affect whether the experience feels trustworthy.

Using Codex effectively meant combining clear milestones with browser inspection, automated checks, and real Twitch testing.

What's next for Mythweave

I want to test with more independent viewers, verify the overlay in a broadcast workflow, expand the authored adventures, and improve animation and audio feedback.

The next goal is to give communities more stories to shape while preserving clear rules, streamer control, and meaningful credit for participation.

Built With

Share this project:

Updates

Submission history