PokéSurvivor Updates · 2026-10-27: October 26 late update: signed runs and leaderboard damage limits

Game update October 27, 2026 · Article updated October 27, 2026

Check the original game’s new per-run server seal, co-op requirements, time gates and score-upload cap.

Changes at a glance

At each run start, including a co-op guest’s start, the original client requests a signed account/time seal from ice.pokesurvivor.com. A run without its seal is not submitted. In co-op, each player obtains their own seal; guests send theirs to the host, who submits the team only when every member has one. The client tries up to three times, waiting 5 seconds between retries, with a 6-second request timeout; 401/403 stops retries. Check sign-in, the public profile and network access before starting another run. Preserve your local save; the calculator cannot issue a seal or retroactively guarantee a missing record. This seal controls leaderboard submission; a missing record alone does not prove that local progress or cloud saving failed.
For the original client’s score field, use t = integer run seconds clamped to 1–86,400. Before t = 1,800, uploaded damage is 0. From t = 1,800, it is max(0, min(floor(cumulative credited damage), (t − 1,799) × 50,000)). Thus the limits are 50,000 at 30:00 and 5,050,000 at 31:40. The cap uses total run time, even if Judgment began late. It also covers Halloween Gengar because that encounter uses the same score field and submission path. This does not cap damage per hit, DPS or the in-run display; enter the cumulative credited score, not raw DPS multiplied by time.
The two fixes were committed on October 26 at 22:17 and 22:37 UTC; this Wiki review is dated October 27. Backend rules, Firebase setup and TURN deployment files were removed from the public repository. Their removal does not prove those live services were disabled or changed. Historical explanations keep their immutable sources and dates. These are reviewed client conditions, not a live audit of the private server.

A fresh server seal is required for every run

At each run start, including a co-op guest’s start, the original client requests a signed account/time seal from ice.pokesurvivor.com. A run without its seal is not submitted. In co-op, each player obtains their own seal; guests send theirs to the host, who submits the team only when every member has one. The client tries up to three times, waiting 5 seconds between retries, with a 6-second request timeout; 401/403 stops retries. Check sign-in, the public profile and network access before starting another run. Preserve your local save; the calculator cannot issue a seal or retroactively guarantee a missing record. This seal controls leaderboard submission; a missing record alone does not prove that local progress or cloud saving failed.

Upload cap, separate from combat damage

For the original client’s score field, use t = integer run seconds clamped to 1–86,400. Before t = 1,800, uploaded damage is 0. From t = 1,800, it is max(0, min(floor(cumulative credited damage), (t − 1,799) × 50,000)). Thus the limits are 50,000 at 30:00 and 5,050,000 at 31:40. The cap uses total run time, even if Judgment began late. It also covers Halloween Gengar because that encounter uses the same score field and submission path. This does not cap damage per hit, DPS or the in-run display; enter the cumulative credited score, not raw DPS multiplied by time.

Time gates and separate run records

A run needs at least 120 seconds for ordinary boards and 600 seconds for its Pokémon-specific board. The uploaded time is an integer bounded to 1–86,400 seconds. The new rt field retains this run’s time when the stored best-time record belongs to an earlier, longer run. Best time and best damage can come from different runs. Daily, weekly and monthly boards still retain their top 50; this update does not reset them.

Public-source and server boundaries

The two fixes were committed on October 26 at 22:17 and 22:37 UTC; this Wiki review is dated October 27. Backend rules, Firebase setup and TURN deployment files were removed from the public repository. Their removal does not prove those live services were disabled or changed. Historical explanations keep their immutable sources and dates. These are reviewed client conditions, not a live audit of the private server.

Which game version does this describe?

This section and the upload preview use original-game client bed34edb. Pokémon/move combat data remains pinned to d567c6da, and Halloween mechanics to f7fbcfc4. The embedded game at survivorpoke.com/play/ is a separately pinned Community edition; this Wiki update does not change it or claim that it uses the original seal service. A preview result is not proof of a submitted or accepted score.

Previous and next updates

Game data & sources

The linked game files show where these stats, costs and rules come from. Updates to the game may change them.

Data version: d567c6da

Data version →