Guide updated November 5, 2026

See which enemy tier applies now, upcoming scheduled bosses and conditional weather, event and rift windows. Use the timeline to prepare space and review scaling before a transition.

Rankings now use the original service

The original client now consistently uses its ranking service; earlier advice that Firestore is the default and the service is optional describes older snapshots. Valid signed-run credentials still govern the heartbeat, called every 60 seconds of game time. Seal acquisition retains up to eight attempts, three-second pauses, 15-second request timeouts and an 80-second overall budget; authentication rejection stops retries. This does not prove the private service's internal implementation or uptime.

The 120-second overall and 600-second Pokémon upload gates, all-time damage preservation, friend top-50 scope, 8/6/2-hour caches and the 5c97df2e cumulative damage cap are unchanged. The run timeline therefore keeps its actual scoring calculations and old-share restoration. Transport changes do not increase combat damage or alter event dates; refresh the correct ranking and check upload eligibility before treating a delayed list as lost progress.

Wiki configurations and game progress are separate

This original update changes save/cache handling, not the combat catalog, prices, odds or calculator formulas. All 13 tools retain their inputs, calculations, share links and JSON import/export. A Wiki configuration restores tool inputs; it cannot recover an original account’s cloud/browser progress. After game recovery, use the actual restored balance and collection in the planners and tracker.

Why an original leaderboard summary can look old

Historical original snapshot before 4 November; see the linked 4 November update for current account and room services: Original b742e437 extends the cache lifetime for all-time summary entries (S: keys containing _all4) to 8 hours. The r: entry cache remains 6 hours and other cached entries remain 2 hours. These are client-cache lifetimes, not upload deadlines, run-duration caps or a change to combat damage. A cached summary is not proof that a run was rejected or deleted; compare the same account, board and period before drawing that conclusion. The upload signature/retry rules and the run-timeline damage cap remain the reviewed 5c97df2e rules. The Wiki calculator estimates the cap; it neither sends a score nor refreshes the original leaderboard cache. b742e437 also adds a separate optional ranking-service route. It requires an explicit vps ranking selection and is disabled for the emulator; the published default still uses Firestore, independently of the new room default. In that optional route, authenticated run-start credentials, score submission, own/friends records, reports and account-ranking deletion use the ranking API; public top summaries do not require authentication. During advancing gameplay, a beat is prepared at each 60-second run-time threshold with time, level, kills and Judgment summary damage; sending requires that optional route and valid credentials for the current account. This is not a new save interval or proof of score acceptance. Failed optional calls do not establish successful submission or automatic Firestore fallback. Backend enforcement was not tested.

Current original snapshot and tool model

Original public client eae98df1a1 (version timestamp 4 November 23:19:53 UTC), reviewed 5 November. Comparing complete normalized client modules found 101 unchanged and 13 changed/new modules. Executed catalog comparisons retain 966 Pokémon, 103 moves, 97 evolutions, 4,830 stat checks and 412 move-level transitions; gacha, combat, shop and progression formulas remain unchanged. All thirteen Wiki tools retain calculations, sharing and JSON recovery; use confirmed account balances for planning. Catalog source d567c6da, execution/upload model 5c97df2e, seasonal rules f7fbcfc4 and calendar d667c216 remain separately versioned.

The game embedded here remains the independent survivorpoke.com/play/ release 3667bcad81 with selected f7 seasonal changes; Community calculations retain their own fixed model. The new original account service and online-pull behaviour have not been deployed into that embedded game by this Wiki update. These versions must not be treated as identical.

Calendar and calculator versions

Pokémon, move levels, evolutions and legal learnsets stay at d567c6da; seasonal combat/rewards stay at f7fbcfc4 and damage/buff execution at 5c97df2e. Only the calendar is updated to d667c216. New planners use the extended window; old f7 calendar shares retain the former November 2 midnight end and show a calendar selector. The original public bundle 01d06d8e0c matched immutable d667c216 on October29. The embedded game remains a separate observed3667bcad81 build declaring selective f7 adaptation; this Wiki does not change it or claim that its calendar was extended. Community calculations remain fixed395a0e47/build559ca0a7c8.

Which version does this use?

Latest original execution rules: 5c97df2e (October 27); reviewed October 28. Pokémon, move, evolution and legal-learning data remain d567c6da; Halloween stays f7fbcfc4. All 13 tools are retained. New original calculations use the independent equipment pool and corrected buff transition. Previously versioned shares without an execution pin retain d567c6da behavior and display that pin; use Recalculate with current rules to migrate deliberately. Community remains its separate fixed snapshot and keeps its own rules. The iframe remains https://survivorpoke.com/play/. Source tests and projections do not establish that both live games behave identically. Public bytes observed October 28 match embedded build 3667bcad81, declared selective upstream f7fbcfc4. The Community calculator is the fixed 395a0e47 snapshot (build marker 559ca0a7c8), not a reproduction of that current embedded build.

Ranking: longer seal retries and All-time damage

The client requests each player’s run seal up to 8 times, with 3-second retry gaps and at most 15 seconds per request. Requests are bounded by an 80-second client window; a new attempt needs at least 2 seconds remaining. 401/403 stops retries. A qualified run lacking a seal now shows a connection warning, including a team missing any member’s seal. This cannot recover an older unsealed run. In All-time, a higher damage record is saved even when time does not improve and both top-50 lists are missed; the prior better time/level/kills are preserved and pending time uploads retain the higher damage. Friends only also fetches friends and yourself outside the All-time top 50, sorts by positive damage and shows at most 50, cached for 2 hours. Other periods and species tables retain their top-50 scope. The global position badge does not become a friends-only rank. Upload damage caps and minimum run times are unchanged.

Very wide windows: enemies can approach

The far-away reset threshold is now max(1400, spawn outer radius+300) for ordinary enemies and max(2500, spawn outer radius+300) for a lost boss. This prevents endless recycling when a very wide, short window spawns enemies beyond the old fixed threshold. The ordinary off-screen/behind delay remains 2.5 seconds; the lost-boss delay remains 4 seconds. Rift exclusions and existing encounter rules remain. This is a viewport-dependent reset fix, not a new spawn-rate or Pokémon-stat increase.

A fresh server seal is required for every run

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.

Which game version does this describe?

Great Gengar at Judgment

An event run replaces the minute-30 Arceus presentation with a giant Witch Gengar. The fight may wait for a Rift or card choice to finish. Gengar is fixed Ghost-type with its own base Defense and Special Defense, not an Arceus Plate selection. It remains an invincible score target: credited hit damage is scaled by 0.05 ÷ (1 + arena seconds ÷ 150), without reducing its HP, and control/status effects are suppressed. Automatic targeting skips Gengar while summoned legendary enemies live, but area attacks and projectiles that actually collide can still score hits. The same damage leaderboard is used. Legendary reinforcements always exclude Arceus #493, even in this Gengar run. Existing contact escalation, player speed cap, five-second reinforcement schedule and 35-minute item break remain; this is not an ordinary capturable Gengar boss.

Night biomes, pumpkins and enemies

Pumpkin Patch, Haunted Graveyard and Gloomy Forest replace the three biome presentations, with themed music and a dark menu. Each enemy tier adds up to two eligible Ghost species not already in its randomly chosen cast; availability and the original tier's candidate rules still apply. These are additional run candidates, not guaranteed fixed spawns or changed species stats. Pumpkins use the seeded map, so group members see the same positions. The menu has denser decorative pumpkins; do not use its density as a combat drop rate.

Halloween: dates, candy, skins and Spooky Night

Source versions used here

Halloween: dates, candy, skins and Spooky Night

Judgment keeps every local player inside the arena

Judgment now clamps the local player after each update, including guests, to a radius of (24−1.4)=22.6 tiles from the arena center. High speed no longer allows survival outside the arena. Enemy and Arceus target selection also skips silent teammates. Plate probabilities, damage-credit scaling, legendary growth, item-break timing and all move/stat formulas are unchanged by these two commits.

October 25: cloud saves, rankings and co-op recovery

Co-op choices and guest weather

Guests now repeat their choice-round number and item/Bond hold state in every normal frame. A lost “finished choosing” notice can recover on the next frame instead of freezing everyone; older clients still use their notices. Drought, Drizzle, Sand Stream and Snow Warning can now request weather as a guest. Each local summon ability checks at the start and every 180 active seconds, starts 60 seconds of weather only when none is active, and the host validates the weather ID and accepts a guest request at most once per 60 seconds. These fixes change whether weather starts, not its damage/type multipliers: select the weather actually present in the calculator.

October 25: cloud saves, rankings and co-op recovery

Read the end-of-run damage summary

The original now shows an end-of-run summary for solo and co-op, with a tab for each available teammate snapshot. Each attack lists actual credited damage and displayed DPS = damage ÷ max(5, run seconds − learned-at seconds), rounded for display. Example: 12000 damage at time 900 from a move learned at 300 gives 20/s, not 12000/900. Support moves show a dash; total damage sums damaging moves currently listed. The transmitted snapshot has up to eight moves, rounds time/damage, refreshes about every 5 seconds and is also included at run end, so a disconnected teammate can have an older snapshot. This is observed-run accounting, separate from the Wiki calculator’s conditional output or Arceus team ranking damage.

October 25: cloud saves, rankings and co-op recovery

Which edition and source this covers

The behavior notes cover original source d567c6da..680c3e12 (7 commits), release marker 6b6bde6e28. Entity values, move/evolution rules and numerical calculator formulas remain those extracted at d567c6da; player/game edits add weather activation, input and summary behavior. All 13 tools retain their abilities. The embedded community edition and the Wiki’s local collection/share state are independent; original account, cloud and ranking fixes do not automatically apply to them. Original source tests use isolated mocks, not real player accounts.

680c3e12 · changelog

Arceus Plates and Judgment damage scoring

Original rules at d567c6da: Judgment Arceus is invincible but takes damage credit. Its random Plate is one of 17 non-Normal types (1/17 each). Auto-targeting prefers living legendary bosses; area attacks can still hit Arceus. Credit multiplier = 0.05/(1+arena seconds/150), rounded per hit with a minimum of 1. It loses no HP and is immune to status; Hex receives no status bonus. Playable and ordinary-rift Arceus remain separate encounters.

Legendary damage growth

Judgment legends grow HP ×1.25 and contact/projectile damage ×1.15 per spawn, starting at index 0. Burn ticks every 0.5 s for 3 s; poison every 0.6 s for 4 s. On these legends, either deals round(1.5 × stacks), minimum 1 per nonzero tick, rather than ordinary HP-based poison. They drop XP only, with no orbs. At game 35:00, item destruction waits for the current cast/next action, then warns for 1.6 s before unequipping. Select “already broken” only once that happens; collection ownership is retained.

Current Judgment scenario

Earlier calculator snapshot (d567c6da)

Original-game data: source d567c6da. See the data version for applicable rules and sources.

Data version and sources

What to do

Enter the in-game time rather than time since opening the tab.
Read the next transition and its affected systems.
Follow linked survival or boss guides before resuming.

Numbers & conditions

Ordinary enemy tiers start at 0, 70, 160, 260, 380 and 500 seconds. Scheduled bosses arrive at 3, 6, 9, 12 and 15 minutes. New rifts stop at 28:00; the Judgment begins at 30:00 after any active rift. The old 60-minute overtime formula no longer applies.

Common mistakes

A timeline is not a live game overlay and does not trigger encounters. Random windows must not be interpreted as guaranteed timestamps.

Original and embedded edition

These additions apply to the pinned original release 1a52cc838c. The embedded community game uses its separate published rules snapshot: its Meteor Mash and legacy evolution names are retained by the Community model, and the new original-only Orbs, Plate scoring and item-break assumptions are not applied to it.

Version and source details

Tools

Run Timeline

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 →