Development covered 23 Aug 2026 to 29 Aug 2026 (commit dates).
The novel that shares a world with Myriad Immortal Sect became part of the game this week rather than a thing beside it. There is a reader in the game, chapters arrive through their own channel, and somebody who finds a chapter on the web can be playing a few seconds later.
Writing the chapters was the smaller half of that sentence. The story runs through ten acts, from the first realm to the Ascension finale.
What is written is not what is published
The first rule I had to make explicit is that having the text does not mean the text is available. Those are two different states and they need two different sources of truth: the writing, and a published index that says what a reader may actually open.
Without that split, turning the feature on shows a reader an empty shelf, and the shelf looks like a bug rather than like a book that is still being written. With the split, the feature can be on while the index is honest about carrying three volumes.
I got the inverse wrong once too. The index briefly advertised two volumes that were not there. An index that promises less than exists costs you nothing. An index that promises more produces a reader tapping a title and receiving nothing, which is the single worst outcome in the whole feature.
The states that are not chapters
Most of the reader's real work is in the cases where there is no chapter to show.
You can be offline, in which case previously read chapters should still open and unread ones should say so plainly rather than spin. A volume can be planned and unwritten, which is a real answer and deserves its own presentation, not an error. A chapter can be listed and fail to load, which is different again.
I would guess two thirds of the reader's behaviour is these three states. That ratio is normal for anything that fetches content and always surprises me anyway when I count it.
The screen that could trap you
The interesting bug is worth the whole article.
A visitor arriving from a chapter page should land in the reader, not in character creation. So the reader renders in front of the new player flow. That is deliberate and it is the right call: someone who came to read should read.
Anything you place in front of an onboarding flow needs its own way out, and mine did not have one in every path. The close control lived in the reader's header, and the early return that runs before the chapter index arrives never rendered that header. So a visitor whose index failed to load got a screen with no chapters, no close control, no tabs, and no route into the game. Trapped on arrival, on their first visit, which is the exact moment you can least afford it.
The general rule I wrote down after: any screen that renders ahead of the normal flow needs an exit that does not depend on the thing that might have failed. Put the way out in the branch that runs when nothing loaded, not in the branch that runs when everything worked. A reader arriving at a late chapter such as Mahayana should never be trapped there, whatever loaded.
And the paperwork
The rest of the week went to reading my own design set beside the running game. Working through it in order, the tally came out unpleasant: nine contradicted claims in one file, eleven in another, ten in a third, spread over some fifteen files.
An automatic check now covers the cheapest third of that, refusing any document that cites a name or a file the project does not actually contain. The remaining two thirds still need a human with both open side by side. I have looked for a way around that and no longer expect to find one.
The live build is Idle Cultivation RPG, and the reader is inside it: open a chapter and the game in your browser.
Top comments (0)