Game update · Article updated
Changes at a glance
- Original 6b2b3547e5 now keeps the news carousel visible at viewport heights of 520px or less. It sits above the title and partner in the left column, beneath the top bar; the title and partner shrink to make room. At 400px or less, the subtitle is hidden and the partner is smaller again. The previous 7cc83e285f version hid the banner at 520px or less. Its 7-second rotation still requires an open menu, a visible tab and no pointer hovering over it. Arrows, dots and Left/Right select an item; Enter or Space opens the creator’s corrected Discord or regular YouTube video in another tab. This describes the original, not the game embedded here.
- Before an automatic version reload, the original first waits for pending sync for up to 6 seconds and records a same-tab reload marker only if the save status is already OK. On the next startup, a valid cloud cache with a positive stored revision may be reused without an initial server read only while that marker is less than 2 minutes old and no extension-recovery marker is present. The marker is consumed once. Otherwise the normal server/cache merge runs. This reduces redundant reads; it does not prove that another device’s latest progress has been fetched. Keep the original browser/profile, check the actual save status and reconnect with the same original account when troubleshooting. Do not clear or hand-edit storage to force recovery.
- The new original client checks for an altered page/runtime environment, including unexpected Object prototype additions and certain injected extension/page elements. A detected condition stops its cloud-write path and schedules an overlay after roughly 6–20 seconds; the button reloads the page. A warning is a client compatibility/protection result, not proof of a server ban, deleted account or lost progress. If it persists, first preserve your original profile and any available export, then test the original in a clean browser profile without page-changing extensions. Keep the old profile for recovery. No such detector is added to this Wiki, its tools or the embedded game by this documentation update.
- The original adds an administrator-gated Accounts screen, reached through the account settings or moderation panel. Authorized administration can add coins, ordinary tickets, ×10 tickets, Pokémon and optional shiny ownership to an existing cloud save. This is not a public gift-code system, player-to-player trading or a reward every player is promised. The client rejects unknown Pokémon IDs, preserves existing ownership and marks new entries as gifts. Currency inputs are floored and limited to 0–1,000,000,000 per supplied amount. If you are online, the panel says the addition merges on a subsequent save (run end, Save or exit); otherwise check the same original account on the next login. A newly delivered gift can therefore require a cloud merge before appearing. Wiki collection tracking is manual and does not read that account. Enter the balance you actually have into the upgrade/gacha tools; gift delivery does not change their prices or probabilities. Backend authorization and real delivery were not tested here.
- Original 6b2b3547e5 now uses the WebSocket room service by default; an explicit rtdb transport selection retains the older realtime-database path. This supersedes 1c249c541c, where WebSocket rooms required an explicit vps selection. There is no new ordinary Settings switch. The room service handles creation, joining, membership and signalling; WebRTC combat messages and damage formulas remain separate. Requests time out after 8 seconds. Reconnect waits are 1, 2, 4, 8 seconds, then at most 15 seconds, with rejoining and possible host-room recreation. A replaced connection (close code 4002) ends that session without a reconnect loop. Missing, started/closed and full-room errors still apply, with at most 4 players. If an invitation fails, check that everyone uses the same original version and ask the host to recreate the room/invite. This does not claim that the embedded version has changed.
- 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.
Original menu on a landscape phone
Original 6b2b3547e5 now keeps the news carousel visible at viewport heights of 520px or less. It sits above the title and partner in the left column, beneath the top bar; the title and partner shrink to make room. At 400px or less, the subtitle is hidden and the partner is smaller again. The previous 7cc83e285f version hid the banner at 520px or less. Its 7-second rotation still requires an open menu, a visible tab and no pointer hovering over it. Arrows, dots and Left/Right select an item; Enter or Space opens the creator’s corrected Discord or regular YouTube video in another tab. This describes the original, not the game embedded here.
Automatic reload and the cloud cache
Before an automatic version reload, the original first waits for pending sync for up to 6 seconds and records a same-tab reload marker only if the save status is already OK. On the next startup, a valid cloud cache with a positive stored revision may be reused without an initial server read only while that marker is less than 2 minutes old and no extension-recovery marker is present. The marker is consumed once. Otherwise the normal server/cache merge runs. This reduces redundant reads; it does not prove that another device’s latest progress has been fetched. Keep the original browser/profile, check the actual save status and reconnect with the same original account when troubleshooting. Do not clear or hand-edit storage to force recovery.
When the original asks you to reload
The new original client checks for an altered page/runtime environment, including unexpected Object prototype additions and certain injected extension/page elements. A detected condition stops its cloud-write path and schedules an overlay after roughly 6–20 seconds; the button reloads the page. A warning is a client compatibility/protection result, not proof of a server ban, deleted account or lost progress. If it persists, first preserve your original profile and any available export, then test the original in a clean browser profile without page-changing extensions. Keep the old profile for recovery. No such detector is added to this Wiki, its tools or the embedded game by this documentation update.
Receiving an administrator gift
The original adds an administrator-gated Accounts screen, reached through the account settings or moderation panel. Authorized administration can add coins, ordinary tickets, ×10 tickets, Pokémon and optional shiny ownership to an existing cloud save. This is not a public gift-code system, player-to-player trading or a reward every player is promised. The client rejects unknown Pokémon IDs, preserves existing ownership and marks new entries as gifts. Currency inputs are floored and limited to 0–1,000,000,000 per supplied amount. If you are online, the panel says the addition merges on a subsequent save (run end, Save or exit); otherwise check the same original account on the next login. A newly delivered gift can therefore require a cloud merge before appearing. Wiki collection tracking is manual and does not read that account. Enter the balance you actually have into the upgrade/gacha tools; gift delivery does not change their prices or probabilities. Backend authorization and real delivery were not tested here.
Room transport: default and optional paths
Original 6b2b3547e5 now uses the WebSocket room service by default; an explicit rtdb transport selection retains the older realtime-database path. This supersedes 1c249c541c, where WebSocket rooms required an explicit vps selection. There is no new ordinary Settings switch. The room service handles creation, joining, membership and signalling; WebRTC combat messages and damage formulas remain separate. Requests time out after 8 seconds. Reconnect waits are 1, 2, 4, 8 seconds, then at most 15 seconds, with rejoining and possible host-room recreation. A replaced connection (close code 4002) ends that session without a reconnect loop. Missing, started/closed and full-room errors still apply, with at most 4 players. If an invitation fails, check that everyone uses the same original version and ask the host to recreate the room/invite. This does not claim that the embedded version has changed.
Why an original leaderboard summary can look old
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.
Reviewed original, embedded game and tool versions
Reviewed 1 November: original public 6b2b3547e5 corresponds to b742e437, including all three commits after d2bf542d. The combat catalog retains 966 Pokémon, 103 moves, 97 evolutions, all levels, legal learning pools and default-start exceptions. Catalog d567c6da; seasonal combat/rewards f7fbcfc4; calendar d667c216; execution and upload calculations 5c97df2e. New room/cache/gift handling is versioned separately from those formulas. All 13 tools and their historical share/import models remain available. The observed embedded game remains 3667bcad81 with selective f7 integration, and Community calculations remain 395a0e47/559ca0a7c8; these original-client changes are not attributed to them.
Related pages
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
- https://github.com/JPTER78/pokesurvivor/blob/b742e43772e37d077549bf2fad3d615d60f42961/js/app.min.js
- https://github.com/JPTER78/pokesurvivor/blob/b742e43772e37d077549bf2fad3d615d60f42961/css/style.css
- https://github.com/JPTER78/pokesurvivor/blob/b742e43772e37d077549bf2fad3d615d60f42961/en/news/index.html
- https://github.com/JPTER78/pokesurvivor/commit/e5997d563fd271168d4c801fbe46274622f92c13
- https://github.com/JPTER78/pokesurvivor/commit/b742e43772e37d077549bf2fad3d615d60f42961