An AI RPG that tracks stats for real, not decoratively
An AI RPG that tracks stats for real stores every number as a record, changes it only through deterministic operations, and requires the narrator to read the record before speaking about it. An AI RPG that tracks stats decoratively shows you a character sheet while the model narrates your health from memory. The two look identical in a screenshot and play completely differently by the second session, because narrated numbers drift: gold inflates, wounds heal off-screen, and the sword you dropped is somehow back on your hip. If the storyteller is allowed to say a number it did not read, the sheet is set dressing.
We build Branching Skies, a mobile AI RPG, and the rule underneath everything in this post is one sentence long: the narrator never announces a change to health, coin, inventory, or experience unless a real operation executed it first. Here is what that rule buys, where it applies, and a five-minute test you can run on any app in the category.
Why do stats drift in AI story games?
Because a language model re-derives numbers instead of reading them. Your health exists as scattered prose mentions across the transcript, and each turn the model reconstructs a figure from whatever mentions it can still see, which is a job it is structurally bad at: arithmetic over a long, partially visible history. The community's workaround says everything, and you can watch players build it in public: hand-rolled trackers and spreadsheets kept open next to the game to hold the numbers the game keeps fumbling. The spreadsheet is the confession. It is the structured state layer, built by the player because the product skipped it.
We made the opposite choice, the same one behind why our worlds remember your story at all: the state layer is the game's job, and the model is never its custodian.
What does it mean for a number to be real?
It means the number has one home and one door. Your health, mana, coin, and experience live as records in your campaign's data. The only way any of them changes is a deterministic operation the game executes: damage applies, payment deducts, a level lands. The narrator is fed the current values every turn and narrates within them. When Algus, our narrator, tells you the fight left you badly hurt, that sentence follows the operation. It never substitutes for it.
The discipline sounds obvious and is quietly radical in this category, because it takes the most convenient tool away from the model. An improvising storyteller loves to round your gold up, wave your wounds closed, and gift you gear the scene made narratively convenient. Ours simply is not allowed: a stat change without an executed operation behind it does not exist, no matter how confidently it was phrased. That is the same authority split that governs whether your choices leave permanent marks.
What about money and inventory?
Money is where decorative tracking dies fastest, so it got the hardest walls. Every shop and tavern in Syrinway carries written prices, authored into the world's files, and a drink costs what that particular place charges rather than whatever the model improvises. Your purse is a stored number that payment operations move. Your pack has a size, so carrying everything is not an option forever. Each item records its history, including whether you bought it or took it off somebody, which matters in a world where people remember what you did.
And there is one wall we are particularly attached to: the story cannot hand you something you did not pay for. A storyteller left to its own devices will cheerfully give you a free sword, so acquisitions that skip payment are blocked at the system level. In our logged test runs that wall holds at zero violations across full play sessions, and we keep measuring it every time the game's prompts change, because a wall you stop testing is a wall you no longer have.
What does the character sheet actually show?
The same numbers the story runs on. The Sheet tab in our development builds shows your health, mana, and level read from your campaign record, which is exactly what the narrator is fed each turn, so the sheet and the story cannot disagree. For a while ours was not this honest, and we will own that: early on, the pools shown were placeholders while the real values ran underneath, and the sheet even leaked an internal class code where your save file said Spellcaster. We fixed both the same week the sheet went live on real data, because a sheet that is wrong in small ways teaches you not to trust it in large ones.
The five-minute test for any AI RPG: ask for your exact health, play two scenes, ask again, and check the answers agree with the events between. Then buy something and watch whether the price matches the menu and your purse moves by exactly that amount. Most products fail on the first purchase. The ones that pass are running on records, which is the first thing our buyer's guide looks for and the same property that decides whether a companion fights with its actual abilities.
Where this is heading
Branching Skies is a curated, mobile-native AI RPG set in Syrinway, a world we ran as a homebrew tabletop campaign for close to a decade before writing a line of code. Everything above, the single-home stats, menu-exact prices, the paid-for-it wall, the pack with a size, and the Sheet tab reading real pools, is working in our development builds today, and the examples come from our own logged sessions and test runs. The early beta list is open now. If you want a campaign where the numbers are load-bearing, the form below is where it starts.