In our last update, we were preoccupied with the identity of our heroes—Aric, Mira, and Dawn—and the struggle to ensure the Narrator recognized them correctly. We were teaching the engine how to see them. Now, we are teaching the engine how to respect the consequences of their existence.
The transition to v0.5.0 is less about a “big release” and more about bringing order to the chaos. We have officially moved to a unified engine. Whether you are playing on your desktop or via an Android device, the heart of the game—the logic that drives the world—is now one and the same. We’ve effectively bridged the gap between two different interfaces, ensuring that the adventure doesn’t change just because you switched screens.
But a unified engine is useless if the rules remain a mess. This is why we’ve introduced the Combat Arbiter. While the Narrator continues its improvisational dance, providing the prose and the atmosphere, the Arbiter has taken over the “hard” math. It handles enemy encounters, calculates official hits, and resolves damage. This separation ensures that while the story can be as fluid and unpredictable as a DM’s whims, the mechanical outcomes remain consistent and fair.
To make these mechanical moments feel less like a spreadsheet and more like a tabletop session, we’ve brought the dice into the light. We’ve implemented shared animated 4d4 dice. The logic is synchronized: the numbers are calculated by the Arbiter, but the visual ritual—the slow roll, the staggered stops, and the golden flash of a natural 4—is shared across both platforms. It’s a small touch, but it turns a calculation into a moment.
We’ve also refined the Validator. It’s getting smarter at distinguishing between a player’s intended action and the natural movement of NPCs or companions. We’re trying to prevent those frustrating moments where a simple sentence triggers a cascade of unintended rule checks.
As for the technical side, the numbers are encouraging: 376 pytest cases passed and a successful Android build. It’s a solid foundation, but we aren’t claiming victory just yet. We still have significant manual work ahead of us: we need to verify the APK signature, conduct full manual playtests of the combat loop, and ensure our new save-migration system—designed to protect your progress from the 0.4.1 era—works flawlessly in the real world.
The engine is unified. The rules are being codified. Now, we see if the story can keep up.
