Understand the October 15 required-update notice, how it differs from ordinary updates, what the quit-style save preserves and which versions support it.

Changes at a glance

  • The author can mark a release as required. A supported client in a run receives a 10-second warning before the run ends and the game reloads.
  • Coins, tickets, records and leaderboard submission follow the same path as quitting the run. The ended battle itself is not resumed after reload.
  • Ordinary updates still wait for an active run to finish; the 10-second interruption is specific to a detected required release.

Normal update or required update?

Scroll sideways to read every column.

SituationWhat the game doesWhat you should do
A normal update appears while you are in a runThe run continues; updating waits for its end and the menu. It is not a 10-second forced stop.Finish normally, then allow the menu update to reload.
An update is ready at a safe menuA normal menu update counts down 5 seconds. Gacha, upgrade/settings screens and active text entry postpone this safe reload.Finish the current menu action and keep the browser open for saving.
A required update is detected during a runThe supported updater shows a 10-second warning, ends the run through the normal Quit path, then reloads. Earned coins, tickets and records use that end-of-run saving path; leaderboard handling follows the run’s ordinary rules.Let the countdown and save finish. The live run ends; this does not create a resumable mid-run checkpoint.

What to do when the warning appears

  1. Read whether the message says required or an ordinary menu update. During a required countdown, keep the page open and allow the normal end-of-run saving process.
  2. After reload, confirm the intended account, save indicator and earned resources. If cloud upload is pending, reconnect the same browser copy before trying another device.
  3. If an old tab never shows this warning, return to the menu and load the current original release. Do not use the absence of a warning to conclude that a local file or community port supports required updates.

Which versions support the warning and what saving means

Required updates are supported by the original published web build containing the October 15 updater. An older open tab must first load that updater. This mechanism does not run for a local file:// launch or the development page, and does not establish the behavior of an independently maintained APK, launcher or offline port.

Before reload, the updater attempts to flush a pending cloud save for up to 6 seconds. If the network does not finish, the source retains the browser copy for a later upload. After reconnecting, open that same account and check the save indicator, coins and tickets before clearing anything. Guest play still does not promise persistent progress.

Continue with the practical guide

Game date, publication date and evidence

Game changelog date: 2026-10-15. This guide was first published and revised on 2026-10-17, using the author’s changelog and the linked files at 5bbc3b29. Source-based instructions are provided here; no device playtest or live-version equivalence is claimed.

What to change in your next run

  • A valuable long run can end for a required fix, while its already earned persistent rewards use the normal quit/save flow. Keep normal updates and required updates separate when diagnosing a reload.

Related pages

Previous and next updates