PokéSurvivor Updates · 2026-10-22: October 22: Orbs, Shiny Charms, ×100 gacha and co-op recovery

Changes at a glance

• Six run-only Orbs use four independent slots, up to three per type, with one shared 1-second cooldown. Consumed slots stay empty instead of moving other types. A full inventory leaves the drop on the ground. Use keys 5–8/numpad, touch buttons above attacks, or controller X to use/Y to select; use requires being alive in an active run. Effects are not cloud-saved and end with the run. Reapplying a buff refreshes duration without stacking strength. Buffs reach living teammates strictly less than 384 units away; the host validates use and applies enemy control.
• Own every species in the region, including legendaries; a defeat record alone does not count. The charm is derived automatically from ownership, with no separate save flag. Matching-banner shiny odds rise from 1% to 2%. Each ten-pull locks its rate at batch start: completing the region inside a batch affects the next batch. Wild 1/4096 and rift 1/512 stay unchanged.
• The current original-game buttons are ×10 and ×100. ×100 costs 100 normal tickets OR 10 ten-pull tickets, without mixing. It runs ten ten-pull batches; each keeps its ≥4★ guarantee. This planner also retains arbitrary draw counts and unbatched API scenarios. Skip/Esc only shortens animation.
• ×100 shows ten spins, each representing the best result of that ten-pull batch. The final summary counts new species, shinies and refunded PokéCoins; cards are sorted by shiny first, then rarity, then new ownership. The results and ticket cost are committed before animation. Skip or Esc reveals them sooner without rerolling.
• The October 22 original fix addresses guests seeing “The room has been closed” midway through a run, sometimes after a few minutes or at a rift, while everyone else keeps playing. A temporary Firebase Realtime Database disconnect could delete the guest’s membership or the host’s entire room through onDisconnect. A missing room record now does not end an active run; the existing peer data channels remain authoritative.
• A failed peer-channel state during a run starts one 45-second grace timer. The guest pauses while waiting for the host; the host keeps playing and retains that guest in the run and room. A successful reconnection cancels the timer and shows the return message. Repeated failure events do not restart the window. If recovery does not succeed, the guest's run ends and the host removes that guest from the run and room. Deliberate departure or a closed channel is different and does not receive this failed-state grace. A player outside an ongoing run can wait in the room until the others finish, rather than treating a rejected room-membership write as a closed room. The host can show “Name: reconnecting…” and then “Name is back”.

Applicable version

The author’s changelog dates Orbs, Shiny Charms and ×100 gacha to October 22, and Arceus ranking/Plates/balance to October 23. This Wiki completed these source details on October 24 from d567c6da. The earlier co-op recovery notes retain their own source versions and historical dates.

Compare all six Orbs

Scroll sideways to read every column.

• Slumber Orb
• Slow Orb
• Blowback Orb
• Focus Orb
• Luminous Orb
• Quick Orb

Regional Shiny Charms and collection requirements

Own every species in the region, including legendaries; a defeat record alone does not count. The charm is derived automatically from ownership, with no separate save flag. Matching-banner shiny odds rise from 1% to 2%. Each ten-pull locks its rate at batch start: completing the region inside a batch affects the next batch. Wild 1/4096 and rift 1/512 stay unchanged.

Scroll sideways to read every column.

• Kanto Shiny Charm
• Johto Shiny Charm
• Hoenn Shiny Charm
• Sinnoh Shiny Charm
• Unova Shiny Charm
• Kalos Shiny Charm
• Alola Shiny Charm
• Galar Shiny Charm
• Paldea Shiny Charm
• Regional Shiny Charms
• Calculate shiny odds

Plan ×100

The current original-game buttons are ×10 and ×100. ×100 costs 100 normal tickets OR 10 ten-pull tickets, without mixing. It runs ten ten-pull batches; each keeps its ≥4★ guarantee. This planner also retains arbitrary draw counts and unbatched API scenarios. Skip/Esc only shortens animation.

Animation, skip and result order

×100 shows ten spins, each representing the best result of that ten-pull batch. The final summary counts new species, shinies and refunded PokéCoins; cards are sorted by shiny first, then rarity, then new ownership. The results and ticket cost are committed before animation. Skip or Esc reveals them sooner without rerolling.

Co-op rooms recover after a room-server disconnect

The October 22 original fix addresses guests seeing “The room has been closed” midway through a run, sometimes after a few minutes or at a rift, while everyone else keeps playing. A temporary Firebase Realtime Database disconnect could delete the guest’s membership or the host’s entire room through onDisconnect. A missing room record now does not end an active run; the existing peer data channels remain authoritative.

The host can recreate the same room ID with the previous members, closed to new arrivals during a run. A guest restores its own membership after finding the host. After a 3-second recheck, the host can restore a missing member still retained by the co-op session, including a member reconnecting during its grace period. Database reconnection rearms onDisconnect cleanup. The temporary room list does not remove peers during a run or room recovery; a genuine channel failure follows the separate reconnection rules below.

Failed peer connection: a 45-second recovery window

A failed peer-channel state during a run starts one 45-second grace timer. The guest pauses while waiting for the host; the host keeps playing and retains that guest in the run and room. A successful reconnection cancels the timer and shows the return message. Repeated failure events do not restart the window. If recovery does not succeed, the guest's run ends and the host removes that guest from the run and room. Deliberate departure or a closed channel is different and does not receive this failed-state grace. A player outside an ongoing run can wait in the room until the others finish, rather than treating a rejected room-membership write as a closed room. The host can show “Name: reconnecting…” and then “Name is back”.

Recovery timing and what to do

Failed room recovery during a run now waits 8 seconds between attempts. Outside a run, the third ordinary failed attempt closes the lobby, with 4-second waits; each lookup/write has its own 5-second timeout. A guest membership-write rejection other than timeout instead keeps waiting with 8-second retries and does not consume that three-attempt budget. This lets a guest wait while the host's current run still blocks admission. The announcement's approximate 12 seconds is not a fixed total deadline. Finishing a run resets a lost room's ordinary attempt counter.

If the team is still playing, keep the current tabs and run open while the room recovers; do not refresh or repeatedly accept an old invitation just because the room database briefly disappears. If the lobby really closes outside a run, ask the host to create a current room and send a fresh invitation. A frozen or broken peer connection still needs the connection checks below. Report whether the run continued, host/guest role, exact message and original version.

Version and source boundary

Room and peer recovery use original source 6f0f4409, including the earlier 4bd9283c fix, on 22 October 2026. Numeric data, traits, shop, TMs and all 13 tools remain pinned to ce578531. Initial direct/TURN attempts still allow 9/15 seconds, but cached TURN credentials are now reused only when more than 80 minutes remain before expiry; the former ten-minute margin is historical. Authorization, 403/30-minute and other-failure/one-minute request delays remain conditional. The embedded independent edition has its own history; this is not a real account/network gameplay test or a claim of identical behavior.

The current original cache release f9fe33f52c at 6f0f4409 omits force:true. Compatible updaters therefore do not force an active run to quit for this release. Normal updating waits for a safe menu state, then counts down 5 seconds; starting a run, typing or opening protected menus cancels that countdown. The force=true sequence documented for the October 21 Kecleon release remains a historical rule for that release, not the flag on this October 22 snapshot.

• js/net/social.js · 6f0f4409
• js/ui/social-ui.js · 6f0f4409
• js/data/changelog.js · 6f0f4409
• version.json · 6f0f4409
• js/core/updater.js · 6f0f4409
• js/net/net.js · 6f0f4409
• js/net/coop.js · 6f0f4409

Related pages

• Mystery Dungeon Orbs: effects, drops and controls
• Regional Shiny Charms and collection requirements
• Host and join a room
• Connection troubleshooting

Previous and next updates

• 2026-10-23 · October 23: Arceus damage ranking, Plates and move balance
• 2026-10-21 · Kecleon Shop: natures, abilities & TMs