Four buttons, four eligibility checks
| Chosen pull | Ordinary-ticket button | ×10-ticket button |
|---|---|---|
| 10 results | 10 ordinary tickets | 1 ×10 ticket |
| 100 results | 100 ordinary tickets | 10 ×10 tickets |
These costs are read from costOf and the matching interface buttons, not inferred from an icon. The two balances are checked separately: do not add “4 ordinary + 1 ×10” and assume any button accepts that combined total.[2]
Worked checks: 9 ordinary tickets alone do not qualify for the ordinary ten-pull button. One ×10 ticket qualifies for its ten-pull button, not for the hundred-pull button. Ten ×10 tickets meet the latter cost. This arithmetic establishes source-defined eligibility, not that every reported disabled button is user error.
What the guarantees do and do not promise
The checked source has separate pity per regional banner. A ten-pull guarantees at least an Epic-or-better result; the five-star counter governs rarity, not a named species. In the checked pull loop, the counter increments first and requests five-star rarity when it reaches 70. That is the 70th pull since the last five-star if none appeared earlier, not a promise about a particular species. The source comment’s “next pull” wording is less precise than this executable condition.[1]
Switching region does not mean one shared global pity counter. A five-star result is not proof it must be shiny, and a shiny roll is separate from rarity. A hundred-pull is handled as ten ten-pull batches in the reviewed code; it is not a new guarantee of a specific legendary.
When the balance and result seem wrong
FeujKiller reported having tickets but being unable to use gacha on October 25 (#335); erenlim0521-hue reported an apparent ×10 amount mismatch the same day (#334). Neither report alone establishes a root cause. On October 23, EremFP asked about not receiving Sandslash after many pulls (#314); that is a desired-species question, not a controlled drop-rate experiment.[3][4][5]
| Symptom | Useful next check | Evidence boundary |
|---|---|---|
| Button unavailable | Record each ticket balance and which button is disabled | Correct source cost does not rule out a UI or account bug. |
| ×10 reward looks short | Compare the two balances and exact reward message | Do not relabel a real report as mere confusion without the before/after values. |
| Wanted species still missing | Check the banner and distinguish rarity from species selection | Many failed pulls do not create a guarantee of that species. |
Use earned tickets in the right edition
The original creator describes tickets as earned through play, not bought for money. Regular enemies and bosses/rift rewards can contribute tickets; exact reward events are not a guaranteed farming rate. The game’s original guide and itch release both describe this free-play boundary.[6][7]
A similarly named edition offering ticket packs is not established as this original project. Check the address and save system before following its prices, banners or account instructions. This guide offers no ticket sales, codes or purchase buttons.
Before leaving after a pull
Inspect the collection and Save state on the current device before expecting the result on another one. If the new partner is missing elsewhere, follow save and sync checks; repeated pulls do not diagnose an upload problem.
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. No live gacha pull, shiny test or probability simulation was performed.
Sources & verification
- JPTER78 GitHub — gacha costs and guarantees ↗ (external website, opens in a new tab) — Ticket types, banner-specific pity and rarity/shiny rolls at 680c3e12c670. No live pulls or redemption test.
- JPTER78 GitHub — gacha buttons ↗ (external website, opens in a new tab) — Four cost checks and separate ticket balances at 680c3e12c670. A source-defined eligibility check is not diagnosis of every reported failure.
- JPTER78 GitHub issue #335 — FeujKiller ↗ (external website, opens in a new tab) — October 25, 2026 (UTC issue date). Has tickets but cannot use gacha; cause not established.
- JPTER78 GitHub issue #334 — erenlim0521-hue ↗ (external website, opens in a new tab) — October 25, 2026 (UTC issue date). Reported ×10 ticket amount mismatch; root cause not verified.
- JPTER78 GitHub issue #314 — EremFP ↗ (external website, opens in a new tab) — October 23, 2026 (UTC issue date). Asked about failing to obtain Sandslash after many pulls; not a controlled probability sample.
- 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.
- JPTER78 on itch.io — original release ↗ (external website, opens in a new tab) — Published October 11, 2026 at 00:38 UTC. Browser game and offline-HTML instructions; downloadable package not installed in this review.