Great Witch Gengar (score target)

Guide updated October 29, 2026

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.

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.

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?

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.

Great Gengar at Judgment

Original source preview · spoilers

Original d667c216 extends Halloween to October 30–November 2 inclusive in Europe/Madrid, ending November 3 at 00:00. In 2026: October 29 at 23:00 through November 2 at 23:00 UTC. The same window covers the map, candy shop and witch skins, Ghost banner and great Gengar. This is the scheduled original-game window, not proof that the event is active now; the source preview below describes its rewards.

Halloween: dates, candy, skins and Spooky Night

Candy: drop budget, collection and shop cost

The shared ambient budget is floor(run seconds ÷ 60 × 1.25). Ghost defeats and broken pumpkins need at least 1 unspent unit; other non-Judgment enemies need a backlog of 3, but each successful drop consumes only 1 and drops 1 candy. Defeating more enemies cannot bypass the time budget. Drops still need collecting. Pumpkins also give 8 XP and a 50% chance of 2 coins. Entering the great Gengar fight grants 60 candy; in co-op the host grants it to everyone. Judgment enemies do not produce ambient candy. At a 30:00 transition, 37 ambient drops + 60 bonus = at most 97, so three such runs give 291, short of a 300-candy skin. A delayed transition can change that budget; the planner asks for its actual start time and whether the fight was reached.

Tools

Gacha Calculator Shiny Probability Run Timeline Upgrade Cost Planner Damage Calculator

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 →