Development covered 23 Sep 2026 to 23 Sep 2026 (commit dates).
A climax depends on not knowing the outcome until it arrives. Films get this for free, because nothing else is on screen. A game has a whole interface around the moment, and every part of that interface wants to report the new state the instant it changes.
In Myriad Immortal Sect, the heavenly tribulation is the climax. You press a button, a storm gathers, lightning falls, and only then do you learn whether you crossed into the next realm. This window I found that by the time the first bolt landed, the game had already told you the answer half a dozen times.
Six places that knew the result
The result card itself was correctly held back until the storm finished. Everything else was not.
Pressing the button applied the new level immediately, and every system that cared fired at once. A toast saying the tribulation was survived. The achievement for reaching the realm. The unlock toasts for new tabs. A notice that a new volume of the companion novel had opened. The realm name in the top bar. All of it on screen while the map was still loading the first bolt.
Fixing those exposed more. The level number floating over your character's head read the live value, so on a first tribulation it showed level 11 while the panel still said 10. A new tab appeared in the tab bar in the first second, because it unlocks at the new level. The lock on the Soar button dropped. And a random destiny event, "Whisper of the Heart Demon", could roll during the storm and appear beside the tribulation's own title.
One rule: show the state from before the press
The fix is a single idea applied everywhere. While a tribulation reveal is pending, every readout shows the state from before the button was pressed. The top bar, the level over your head, the tab bar and the flight lock all read from that remembered state until the reveal lands, and then all change together.
Events are deferred, not dropped. The destiny roll skips during the storm and the clock keeps running, so whatever was due lands on the first moment after the result. Nothing the player earned is lost. It just waits its turn.
What made this tedious was that each leak was found separately, and each fix revealed the next. The useful habit was a family sweep: after finding one readout that showed the new realm early, list every place on screen that displays anything derived from the level, and check them all. Three of the six leaks above were found that way, not by playing. If the realm ladder itself is unfamiliar, the explanation of minor stages and half steps shows what each level number means.
Quest directions that pointed at nowhere
The other big job in this window was a different kind of broken promise. Readers who had never seen the design went through every quest's "how to complete" line with the map open, and checked whether the place it named actually existed and was labelled.
A large share did not. Across the middle batches, sixteen directions named places the map does not label or that do not exist at all: an "abode", "the arena", a "regional war", a "spirit-pet bonding site". In two later batches, twenty of twenty-one did the same: a teaching hall, an elders' hall, a "tribulation platform" for every quest in the ninth batch. One quest sent players to a famous sword mound while the beast it wanted spawned more than three hundred tiles away.
These were written from the story's point of view, where such places obviously exist. The map is what the player actually has. Every direction now names a place the map labels, or tells you to light a Wayfinding Lamp, which points at the real target. The very first batch was also corrected to happen after you pass the gate rather than "on the road to the sect", because a player reaching it has already met the Sect Master. For a sense of what a real, labelled destination looks like, the entry for the Ancient Sword Mound is an example of a place the map really does label.
The common thread
Both problems are about the gap between what the game knows and what the player should know at that moment. The interface knew the result too early and said it. The quest text knew places the player could not find and named them. In both cases the fix was to write from the player's position, at that second, with only what is on their screen.
If you build a big reveal, list every element that can display the outcome and decide when each one is allowed to change. Your result screen will be fine. It is the top bar that gives it away.
Your first storm is waiting: play free in the browser and find out at the right moment.
Top comments (0)