Ragnaroll

The pitch

Ragnarök already happened. The gods lost. You are the Janitor of what’s left — and your job is to flick-throw six dice across a dead god’s felt table, score poker hands from where they land, and fight your way through fifteen realms of Norse beasts.

If Balatro and Hades had a dice-obsessed child, it would look like this.

Why I’m making it

I love score-engine games — the moment in Balatro where your build “turns on” and numbers explode is one of the best feelings in modern game design. But I kept wishing the physical act of playing had weight too. Digital dice are usually fake: a random number with an animation on top.

In Ragnaroll the dice are real rigid bodies. You flick them with your finger, they collide, bounce off the rim, knock each other over. Where they settle is what you score. The randomness isn’t hidden in code — it’s sitting on the table where you can see it, and with the right runes, bend it.

How I’m building it

The table is rendered with Three.js via React Three Fiber, and the dice are simulated by Rapier, a Rust-based physics engine compiled to WebAssembly. Game state — runs, realms, the Forge — lives in Zustand stores, cleanly separated from the render layer. The whole thing is TypeScript, wrapped with Capacitor for iOS, with Firebase handling telemetry from playtest builds and over-the-air updates for rapid iteration.

The hard problem so far: making a flick feel fair. A physics throw must be chaotic enough to be exciting but readable enough that a skilled player can aim. Getting the mass, friction and restitution of six tumbling dice to sit exactly on that line has taken more tuning sessions than I can count — and it’s the make-or-break feel of the whole game.

Follow the build in the devlog.