Eight TMs refresh by the Europe/Madrid calendar date. The seeded base list is shared. If none can be taught to the selected partner now, slot eight becomes …
Original game ce578531 (21 October 2026). These are original-version rules; the embedded independent game has its own update history. Neutral nature and “ignore ability” are comparison assumptions, not your account’s rolled traits.
Open Shop from the original main menu and buy with coins. Bag shows unused stock; use it through Collection → choose a Pokémon → Mint, Capsule or Teach TM. Pick a different nature/ability, or an eligible TM you own. A successful change consumes one item and saves locally; press Save and wait for cloud confirmation before switching devices.
Eight TMs refresh by the Europe/Madrid calendar date. The seeded base list is shared. If none can be taught to the selected partner now, slot eight becomes a compatible, not-yet-taught TM. Therefore partners or learned lists can change slot eight. Bag and TM stacks cap at 999; buying at cap still spends coins.
25 natures: 20 multiply one of physical attack, special attack, defense, special defense or speed by 1.1 and another by 0.9; five are neutral. HP is unchanged. Attack is recalculated from max(physical, special). A Mint costs 1,500 coins and lets you choose.
Abilities
Each species has its own regular and hidden slots. A hidden slot rolls at 1/20 only where it exists. Traits are fixed from account creation and species; repeated pulls do not reroll them. Regular Capsule: 1,500 coins, other regular slot. Hidden Capsule: 5,000, any other available slot. Both require a valid change.
TM compatibility
Only the listed compatible, off-type TMs can add new moves. Type + Normal natural moves need no TM. Teaching consumes one unused TM permanently; known moves cannot be taught twice. Taught moves join level-up cards and non-buff starting choices. Compatibility alone does not mean already learned.
Second starting choice
Second starting choice costs 400 coins PER POKÉMON and requires Repertoire. Reselecting is free. Choose a different legal non-buff move, including a taught TM or the default-start exception. A valid explicit choice overrides bans; without it Repertoire rolls an unowned, unbanned non-buff from the actual pool.
Open Upgrades and choose the Pokémon. Buy Repertoire first, then Second starting move for400coins. Choose a legal attack different from the first. Choosing again costs0; buying it for another species requires its own unlock.
Original game ce578531 (21 October 2026). These are original-version rules; the embedded independent game has its own update history. Neutral nature and “ignore ability” are comparison assumptions, not your account’s rolled traits.
From the original 4 November update, a signed-in cloud account sends its pull to the original account service. If you are offline or that request fails, the client reports an error and does not silently perform a local pull. Guest pulls still use the local algorithm. The official notice says ordinary gameplay and the shop are unchanged; this connection requirement concerns account pulls, not every offline action.
Check the active banner and enough tickets first. The client locks the pull button while processing, waits for an outstanding save and reuses one operation ID during retries. A revision conflict merges the returned save and retries with a new revision, up to four loop attempts; a transport failure only gets an initial retry, not four guaranteed network retries. Closed banner, insufficient tickets, offline and general failure are separate outcomes. A successful response supplies canonical coins, both ticket balances, ledger, collection, shinies, banner pity and total pulls before the result animation.
After a timeout, reconnect and let the same account sync; inspect its actual tickets, collection and pity before trying again. A missing response does not prove the server never processed the pull or guarantee a refund. Do not clear storage or edit signed copies to repair it. The published local probability, pity, ten/100-pull costs, duplicate refunds and shiny formulas are unchanged in this client snapshot. Wiki calculators remain planning tools: enter the latest confirmed account values; they cannot execute, restore or certify a real server pull.
The current original client retains Firebase sign-in but reads and writes cloud saves through the original account service instead of loading direct Firestore/Realtime Database clients. This describes the public client transport, not undisclosed backend storage. A missing-save response means no save was found for that request; a failed request is not an empty account or a successful sync. Local saves, signed-copy preservation and cross-tab protection remain relevant.
A successful save can return authoritative economy corrections, including coins, both tickets, ledger, removals, permanent upgrades, bag and TMs. On revision conflict the client merges the returned copy and retries a newer revision. A rate-limit response with a gap keeps the save pending and waits the returned seconds (20 by default), plus half a second. A rejected save can explicitly leave the newest changes only in this browser. Keep that browser's data and wait for an actual accepted sync before changing device or clearing storage.
Requests require a current signed-in user. The wrapper refreshes the authentication token once after a 401 response; repeated authentication failure is not successful saving. Its usual timeout is 12 seconds (15 for pulls), and network failures, server errors and unreadable responses are treated as unavailable. Reconnect and confirm the account's sync state; the Wiki cannot repair credentials or infer accepted balances from a spinner.
Original administrator gifts and removals now read/write through the original service, retrying revision conflicts up to three times. The existing non-negative economy, collection revocations and partner fallback rules remain; this Wiki does not grant administrator access or change balances. The original restricted moderation UI adds a server-provided suspect list (coin-based results can be limited to 500; reports may add entries), reasons/reports and economy figures, with dismiss and explicitly confirmed ban actions. A flag is not proof of cheating and does not itself demonstrate an automatic ban.
Original account deletion still requires reauthentication, then requests the original account service before social/ranking cleanup and Firebase user deletion. This client permits continuation after a 403 as well as a 200 response; that is not proof every backend record was erased. Use the original account controls and verify their actual result with that service. Wiki tool JSON, local planning data and the independently embedded game are separate; none of these buttons or explanations transfers deletion authority to this Wiki.
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.
The original administrator Accounts panel now has a separate Remove action alongside Give, with a confirmation. It can subtract coins, single tickets and ×10 tickets from an existing cloud save. Inputs and current balances are floored and normalized to 0–1,000,000,000; the debit is limited to that normalized balance. For example, removing 120 coins from 100 leaves 0. A transaction records the administrator debit, increments the save revision and updates the server timestamp. This is not a player shop purchase, public redemption code or a new fee.
Removing a normal Pokémon removes both its normal and shiny ownership; the shiny-only option keeps the normal Pokémon. The save records a separate revocation timestamp for each form. Loading and merging remove ownership whose acquisition time is at or before that marker, and merging keeps the later marker from either save. A removed partner falls back to an owned starter, otherwise the first owned species; an unavailable shiny partner appearance is cleared. A genuinely later acquisition can survive when the other save has no stale ownership entry; the merge caveat below matters.
The original panel says a Pokémon earned again can be kept. Source execution confirms a narrower condition: DB.merge first chooses the earlier ownership acquisition record, then applies revocation. If another device or backup still contains the old record, merging can remove even a legitimate later capture. Do not repeatedly import that stale backup to restore a removed Pokémon. Keep a backup of the current state, finish cloud synchronization, then check the live account; if the new capture disappears again, report that sequence to the original game's support. This Wiki has documented the reproduced source behavior; it has not changed the original backend or your save.
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.
In original d667c216, receiving the server time after launch or starting/ending Halloween may update the menu background and music, but no longer rebuilds the main menu over an open shop, gacha or another submenu. The main menu is rebuilt when you return to it. Runs still retain the event flag from their start; this fix does not change candy ownership or purchases.
The changelog files these UI improvements under October 24, although they entered source in dc3029a7 on October 25. In Collection, learnable-move icons grow from 16 to 32 pixels; hover or tap an icon for its name, type, physical/special category when applicable, and description. Tap again, elsewhere, or scroll to dismiss it. This reveals the existing legal pool, including compatible taught TMs; it grants no extra move. Kecleon Shop and News now sit below the top bar, including portrait mobile. Menu/settings/news/support windows close only when both press and release occur on the dark backdrop; dragging from inside does not close them. Controller B/Back remains.
Save now compares the actual merged progress with the cloud copy. A newer cloud timestamp alone cannot mark unsent tickets, coins or Pokémon as already uploaded. Tabs of the same browser immediately merge changes through the storage event in cloud-account mode. Different devices still merge when opening the game or resolving a save conflict; this adds no continuous cross-device listener. Keep the same account, press Save before changing devices, and keep the original browser copy while Pending or Offline is shown.
Repeated spending of an old balance on two devices previously created a negative ledger that could inflate later saves or consume later earnings. The new code repairs that debt once through led.fix; merging takes the largest counter, so the same repair is not added twice. Tickets, coins, bag items and TM quantities follow their ledger balances. An unchanged Save skips the cloud write even if the local update timestamp changed. Public-profile writes also skip the nickname-registry lookup when the name is unchanged.
If the first cloud read fails at startup, the game keeps the local copy and schedules up to 10 read retries: 10 seconds initially, exponential backoff, capped at 10 minutes between attempts. A successful read merges the cloud copy; it does not silently upload remaining local progress. Save is still manual. These retries are for the failed initial read. After the retry budget is exhausted, preserve local data and reopen with a working connection. Existing save revision checks, write limits and conflict retry rules remain.
Kecleon sells Witch Gengar, Witch Pikachu and Witch Umbreon for 300 candy each while Halloween is open. Gengar has a hat and cape; Pikachu and Umbreon have a hat only. These are cosmetic sprite sheets, including shiny variants, not new species, moves or stat boosts. A purchase is permanent and cannot be bought twice. You may buy before owning the species; automatic equipping requires ownership. Equip or remove it from that Pokémon's card later. Candy is stored in bag.candy, purchased skins in skins and the most recently selected outfit in pskin. Kecleon's own shop hat is decoration, not a fourth purchasable skin. Candy is earned, not a free coin-shop purchase.
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.
The original's normal successful-upload gap is now 25 seconds, previously 65. A cloud Save already waiting in the timer tries to upload when the page becomes hidden, respecting a 21-second rules gap; merely leaving without a scheduled Save does not create one. This is an attempt, not proof of server receipt: retain the local copy and check the cloud state before changing devices. Purchased skins merge as permanent acquisitions; the latest timestamp chooses the worn outfit, including removal. The unbuilt dev page outside localhost is local-only and disables account/cloud/ranking access. The embedded community game at survivorpoke.com is a separate fixed version: this upstream synchronization updates the Wiki and original-rule scenarios, not that game.
