Check the version before trying an old fix

The original game's main menu has a version button beneath the logo. Click it to open What's new. On October 17, our session showed v0.5.5, with earlier hotfixes listed underneath.

When you return to the main menu between runs, reload the original site to obtain its current version, then check that panel again. The official announcements also ask players with an older open session to reload after an update. An older tab may still be running code from before a fix.

The version history distinguishes several problems that players have grouped together: stalled menu choices, movement after closing a menu, item caps, long boss fights, and delayed run submission. Match your symptom to a specific change rather than assuming one fix covers every issue.

Lag, flashes, or too much happening on screen

Open Settings → Graphics on the original game. The panel we inspected offered High, Medium, and Low quality; its own hint says Low performs better. That is the first built-in option to compare if a crowded run is struggling.

  • Show FPS: use the game's counter to observe the effect of a setting change in your own session.
  • Effects opacity: reduce visual clutter if effects obscure enemies or the ground. This is a visibility adjustment, not a measured performance guarantee.
  • Screen shake and Shake intensity: inspect these if repeated hits make the camera difficult to read.
  • Reduce flashes: another available visual-comfort setting.

Change one option at a time so you can tell what helped. We have checked these settings in the desktop interface, but have not benchmarked devices or completed a touch-device performance test.

The version history records fixes for Pokémon remaining as Poké Ball placeholders. A persistent blank map or missing sprites on the current version is still worth reporting with a screenshot; this guide does not establish a universal recovery procedure for it.

Camera movement and attack aiming

In Settings → Controls, Automatic aiming targets the closest enemy, while Manual points toward the camera. Check the selected mode if the attack direction differs from what you expected. Mouse sensitivity and Invert Y axis are separate options on that panel.

For the keyboard legend, pause a run and compare it with our desktop controls reference. The original game's v0.5.2 notes describe fixes to movement after upgrade menus and item interactions; its October 17 community update also covers the camera after pausing.

Controller support appears in the v0.5.1 release history. We have not tested a physical controller, custom bindings, or controller-specific faults, so use the current in-game prompts for your connected device.

A run did not save or the leaderboard looks wrong

Help and bug-report threads included reports of long runs ending around maintenance, missing rewards, and results not appearing where expected. Those reports establish player questions, not a confirmed explanation for every missing result.

The game's v0.5.5 note specifically says that runs continuing through maintenance should no longer enter review merely because they reach the server late. It does not promise to restore every earlier result. Record your version and the time the run ended when asking the project to investigate.

If the issue persists, include the mode, region, starting Pokémon, result screen, and whether maintenance was happening. We cannot inspect the game's private save records from this independent guide. The original project's Report button and its support channels are the appropriate places for an individual run investigation.

Can I play with friends? Is skill fusion available?

The official October 17 announcement describes co-op and skill fusion as features being tested for Season 2. That is a roadmap statement. Our checked menu offered Classic and Survival; we have not verified a released co-op entry or a usable fusion system.

Look for a newer announcement and a corresponding option in the live game before following instructions for those features. Joining a clan does not, by itself, verify that co-op play is available.

Send the original project a useful bug report

The game menu includes Report. Its Discord also has a pinned bug-report guide asking for one issue per post, a descriptive title, and enough detail to reproduce it.

  1. Describe what happened and what you expected.
  2. List the steps that led to the issue.
  3. Include the Pokémon, biome, mode, and approximate run minute.
  4. Name the browser, operating system, and whether you used a PC or phone. Add the game version.
  5. Attach a relevant screenshot or short clip when possible.

Search the existing reports first and add useful details to a matching issue. The pinned instructions ask players to report leaderboard exploits privately to moderation. For general help, visit the original project's Discord; Discord may require you to sign in and join the server.

Sources and verification

Checked on . We checked the original game's version panel and Settings screens, read the official October 17 announcements, and inspected the pinned bug-report instructions in its Discord. Player reports helped select the questions. We did not reproduce every reported bug or verify that an individual lost run can be recovered.