Game update · Article updated
Changes at a glance
- In the original game from October 14, open Settings → Controls → Place the buttons. Drag the attack bar with its held-item icon and the pause button, choose Floating or Fixed for the joystick, then save. Fixed movement starts near the saved joystick; Floating starts where you touch.
- Since October 14, coins, single-pull tickets and ×10 tickets use a per-device ledger of earnings and spending. Synchronization merges each recorded change once, so an old open tab no longer simply replaces the other device’s newer balance. Owned and shiny collections still merge by union; permanent upgrade levels use the maximum. This does not add two displayed total balances or combine unrelated accounts.
- Username/password cloud accounts can link Gmail after sign-in for future Google-based recovery of the same account.
- Co-op selection waits, overlapping item/cards, missing enemy bodies after a rift and false offline friend status from a bad device clock are listed as fixed. Large in-run announcements are centered.
- Weekly and monthly leaderboards also reset after the earlier all-time reset. The author identifies pokesurvivor.com as the free official site and records a source-license change to PolyForm Noncommercial 1.0.0.
Set up movable buttons and a fixed joystick
- Open the original game in landscape and check that the October 14 controls are present. In Settings → Controls, choose Place the buttons. Older bundled APKs may need their maintainer’s update first.
- Drag the attack bar as one group, including the held-item icon, and move Pause to a reachable position. This changes screen placement, not which move belongs to each slot.
- Choose Floating to create the joystick where your finger lands. Choose Fixed to keep it visible in one place; with Fixed selected, drag its preview to your preferred thumb position.
- Press Save. Return to a low-stakes run and test movement, switching between two learned attacks with the other finger, and Pause. With Fixed selected, begin the drag near the joystick, not anywhere on the playfield.
- To return to the default arrangement, reopen the editor, choose Reset, then Save. Reset also selects Floating. Cancel exits without applying the draft; clearing site storage is unnecessary.
- The layout is stored in this browser’s settings, separately from cloud progression. Set it up again in another browser/app when needed; signing into the same account does not prove these button positions transferred.
What changed in cross-device saves on October 14
Since October 14, coins, single-pull tickets and ×10 tickets use a per-device ledger of earnings and spending. Synchronization merges each recorded change once, so an old open tab no longer simply replaces the other device’s newer balance. Owned and shiny collections still merge by union; permanent upgrade levels use the maximum. This does not add two displayed total balances or combine unrelated accounts.
A concrete coin and ticket example
Scroll sideways to read every column.
| Starting situation | Merge rule | Result and next step |
|---|---|---|
| Both devices start with the same 100 coins; A earns 20 and B spends 10. | Merge the shared starting amount once, then the distinct +20 and −10 changes. The same rule applies separately to single and ×10 tickets. | The merged result is 110 coins, not 120 + 90 = 210. Sync before spending the same resources on two offline devices. |
Switch between PC and phone without discarding the source copy
- On device A, confirm a cloud account and note the exact account identity, a known Pokémon, an upgrade level and ticket counts. Guest and browser-local modes do not become cloud saves just by using the same nickname.
- Bring A online, keep its site data and wait for the saved indicator. New Pokémon, shinies, pulls and purchases request an early upload, but pending/offline still means the browser copy may be ahead of the cloud.
- On B, sign into that same cloud identity. A Google login reaches the existing username account only if it was linked there first; a different Google account or a local account with the same name is not a match.
- If B was left open in the background for more than 30 minutes, returning can fetch and merge A’s collection without reloading. The source limits pulls to at most one per 30 minutes and waits until the menu if a run or upload is active. A brief tab switch is not an immediate refresh command.
- Compare collection entries, the known upgrade and currency after synchronization. If B remains old, first let A finish its pending upload, then safely finish B’s run and reopen the original with the same account. Keep the more complete browser copy intact while investigating.
Link Gmail before you need account recovery
- Sign into your existing cloud account with its username and password. The October 14 version offers Gmail linking after sign-in for an eligible account; start from the account whose collection you want to keep.
- Accept the link prompt, select your Gmail and wait for confirmation. If the game says that Gmail already has its own account, the source asks for a different Gmail; changing nicknames does not merge those accounts.
- After a successful link, Google sign-in can reopen that same account if you later forget the username-account password. A Gmail that was never linked is not a recovery route for the old account. Guest sessions and unrelated local saves remain separate.
Check the October 14 co-op fixes with your group
- Before the next shared run, let every player return to the menu and load the current original version, then recreate the room if needed. Record whether the affected player is the host or a guest; mixed old tabs can still lack the fix.
- For a card-choice pause, check that each player has actually finished the level card, held-item or Bond selection. The update repairs mutual waiting, overlapping item/card choices and missed selection messages. An unfinished choice or an away host can still pause the group normally.
- If a non-host sees attacks but no enemy bodies after returning from a rift, compare all players’ versions first. This exact guest-visibility issue is listed as fixed; preserve the host/guest role, rift and symptom if it persists.
- Friends showing offline because a device clock or time zone is wrong is also listed as fixed. If invitations still fail, separate friend status, room invitation and connection-to-host checks; keep the host tab active and compare an allowed alternate network. Updating cannot remove every network restriction.
Weekly and monthly boards after the Arceus reset
On October 13, the author announced an all-time board reset for the Judgment of Arceus, while weekly and monthly boards were initially kept. The October 14 entry subsequently resets those weekly and monthly boards too, aligning their entries with the Arceus-era rules. Read the dates in sequence: the earlier statement that they were kept is historical, not the final state after October 14.
A leaderboard reset concerns rankings, not proof that your Pokémon, upgrades or balance were deleted. For an apparently empty collection, follow the account and pending-upload checks instead. The Judgment encounter still begins at 30:00 and new rifts stop at 28:00.
Original website, local copies and community versions
The author identifies pokesurvivor.com as the official free game. This website, poke-survivor.org, is an independent Wiki. These October 14–15 instructions describe the original game, not a claim that every community APK or translated launcher has already integrated the same changes.
The current original cloud configuration restricts account access to its allowed hosts. A copy on another host can show local-only saving instead. Use the original site for its cloud identity and co-op, and check the actual login-mode message rather than assuming any copy shares the same account service.
Continue with the practical guide
Game date, publication date and evidence
Game changelog date: 2026-10-14. 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
- Phone players can place controls around their hands; returning players should check save identity and upload state before interpreting a missing balance or leaderboard history as lost progress.
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/5bbc3b29288d6af4596f21188fb8b54e0e9b739f/js/data/changelog.js
- https://github.com/JPTER78/pokesurvivor/blob/5bbc3b29288d6af4596f21188fb8b54e0e9b739f/js/core/touch.js
- https://github.com/JPTER78/pokesurvivor/blob/5bbc3b29288d6af4596f21188fb8b54e0e9b739f/js/core/settings.js
- https://github.com/JPTER78/pokesurvivor/blob/5bbc3b29288d6af4596f21188fb8b54e0e9b739f/js/ui/layout-ui.js
- https://github.com/JPTER78/pokesurvivor/blob/5bbc3b29288d6af4596f21188fb8b54e0e9b739f/js/core/db.js
- https://github.com/JPTER78/pokesurvivor/blob/5bbc3b29288d6af4596f21188fb8b54e0e9b739f/js/ui/login.js
- https://github.com/JPTER78/pokesurvivor/blob/5bbc3b29288d6af4596f21188fb8b54e0e9b739f/js/net/coop.js
- https://github.com/JPTER78/pokesurvivor/blob/5bbc3b29288d6af4596f21188fb8b54e0e9b739f/js/net/ranking.js