PokéSurvivorIndependent guides · Megabonk.org
Menu
JPTER78 browser game · Independent guide

Read the rift window before waiting

Rifts need an eligible map state before their random opening checks run. Enter an opened portal before it expires, then finish the timed arena for its reward and Bond. If no rift appears, inspect the run stage and boss state before assuming a fixed timer failed.[1]

By Megabonk.org editors · Checked October 26, 2026 · Source-based; no comparative gameplay test

Eligible map window → Random check → Enter timed arena → Return and inspect group
Eligible attempts are not a wall-clock promise that a portal must appear.

Why a rift may not have opened yet

The checked code begins eligible checks only after the early-run threshold and stops new openings two minutes before the 30-minute Judgment phase. Existing arenas, host authority in co-op and a living scheduled boss also affect when an attempt can occur.[1][2]

Source conditionWhat to do with it
Before the early thresholdContinue the run; a rift is not promised immediately at spawn.
A scheduled boss is aliveResolve that state before counting missed eligible checks.
Already in an arena / existing portalDo not expect another independent opening simultaneously.
At or beyond 28:00New rifts stop opening before the Judgment boundary.
Co-op guestThe authoritative opening decision belongs to the host.

Constants in the source include a 75-second early boundary, 30-second eligible checks and a base 20% chance that increases after misses. Because checks pause or skip under conditions, “a maximum of five checks” is not an unconditional two-and-a-half-minute wall-clock guarantee. Do not infer a kill-count trigger from that timer alone.

Portal time and arena time are different

An opened portal has a 45-second lifetime in the checked code. The legendary arena has its own 120-second limit after entry. Spending time fighting a scheduled boss before an opening is a different wait from these two countdowns.[1]

  1. Notice the portal and read the current field situation.
  2. Enter before its portal lifetime expires if you choose that fight.
  3. In the arena, track its own fight timer and attack warnings.
  4. After the result, inspect your active group and return position instead of assuming a safe pause on the original map.

These are source-defined timers, not observed average spawn times or a promise that a particular legendary will appear.

A Bond changes your grouping options

A won rift increments a Bond and offers the grouping step. Linking moves lets them share one active slot; owning four unlinked moves is a different setup. Read the group you return with before the next wave.[1]

The creator documents tickets/coins as arena rewards, while the source distinguishes ordinary rifts from Judgment legendaries. Do not use the latter as an assumed source of the same rewards. A win does not establish that you now own the legendary species as a selectable partner.[3][2]

Returning is a risk check, not a guaranteed safe spot

bmorman reported being hit immediately after returning from a rift on October 23 (#312). That is one original-project report, not a reproduction by this site or proof that every return is unavoidable.[4]

The checked return path restores the map state and player position, clears several temporary effects and can offer the Bond step. It does not justify a universal promise of a safe empty radius. On return, read the field, your health and the selected group; if the same symptom recurs, include the return location and version in the report.[1]

At the end of the rift window

If your next goal is a Bond, waiting for a new portal after 28:00 is the wrong plan for the checked version. If the run reaches 30:00 while you are inside an arena or choosing a card, the Judgment transition waits for that state to finish. Read the Judgment timeline before applying an older infinite-run strategy.[2]

Rules below refer to JPTER78’s source snapshot 680c3e12c670, reviewed October 26, 2026. Other hosted editions and native ports can differ. We have not completed a comparative run or verified a universal fix.

Sources & verification

  1. JPTER78 GitHub — rift checks and return ↗ (external website, opens in a new tab) — Eligibility, random checks, arena timing, Bonds and return behavior at 680c3e12c670. No spawn-frequency experiment.
  2. JPTER78 GitHub — Judgment of Arceus ↗ (external website, opens in a new tab) — 28/30/35-minute boundaries, damage scoring and scaling at 680c3e12c670. Source-based explanation, not a successful endgame run.
  3. pokesurvivor.com — creator’s guide ↗ (external website, opens in a new tab) — Controls, devices and core progression, reviewed October 26, 2026. Single author source; some prose can lag the source code.
  4. JPTER78 GitHub issue #312 — bmorman ↗ (external website, opens in a new tab) — October 23, 2026 (UTC issue date). Reported taking an unavoidable hit after leaving a rift; one report, not reproduced here.
Back to guide ↑