If the homepage player does not respond to keys, click or tap inside the game first. For a blank scene, check JavaScript and WebGL; for a missing result, return with your usual account or Guest identity before changing browser data. The player loads Charcher’s original game directly from pokebonk.com. Its recovery feature saves earned results after an interruption; it is not a promise to resume at the exact point where you stopped.
The embedded player is loaded but keys do nothing
The homepage game runs in a separate frame. Click or tap inside the game area, then use the game’s own menu. A click on this site’s navigation or a player-toolbar button can leave keyboard focus outside the game; click inside again before testing movement.
Desktop defaults are WASD to move, Space to jump, Shift to slide, E to interact, R for the Ultimate, Q for automatic/manual aim and Esc or P to pause. Use Settings → Keys inside the game if you have changed a binding. A website search box or another focused field can consume keystrokes until you return focus to the game.
Use Fullscreen and Exit fullscreen in the player toolbar above the game to expand and return to this page. The game’s own fullscreen icon does not control this embedded view. Reload loads the original game frame again; use it for a stuck loading screen after noting any active-run details. Open original opens pokebonk.com directly and is the fallback if the embedded view is not working in your browser. Compare the two views without assuming that a different Guest identity means your progress was deleted. Keep the context containing your existing progress while investigating.
A blank screen before the game loads
The original loading notice says JavaScript and WebGL are required. If the homepage player remains blank, try Reload, then Open original to compare the same game outside the frame.
- Allow the game’s JavaScript to run. If a content blocker has stopped the page, check its message and permit the original game’s necessary files.
- Check that your browser has graphics acceleration enabled. The original game specifically recommends this for Chrome, Edge and Opera. In Chrome → Settings → System, look for the graphics/hardware acceleration setting, enable it if disabled, restart Chrome and reopen the player. The setting’s wording can vary by browser version.
- If acceleration is already enabled and the game still reports a graphics problem, update the graphics driver through your device or GPU vendor’s normal process.
- Try opening the same original URL in an up-to-date browser. This comparison helps identify a browser-specific problem; it does not establish that your save has been transferred.
If the game opens but performance is poor, use its own graphics options before clearing site data. For a useful Chrome comparison, keep the same map and graphics quality, then compare a similar scene after enabling acceleration and restarting. A smoother menu alone does not establish how a crowded fight will perform. A blocked file, unsupported graphics path and a slow scene require different remedies.
Purple screen over a move list
Beta 0.7.1 fixes a purple overlay covering “See all its moves” and “Still to get.” Check the version below the original game’s logo, then close and reopen the affected list in the current game. This patch concerns those panels; it is different from losing the 3D scene during combat.
If a list is still covered, record which panel you opened, the displayed version, browser and steps. From the menu you can compare Open original with the embedded view. If a run is active, record its details before reloading: a reload is not a promise to resume that battle. Do not delete browser storage or assume that the Pokémon’s learning rules changed because an overlay blocked the list.
Move details no longer open on hover
This is intended in 0.7.1. Level-up cards no longer open the full move sheet when the pointer passes over them. Pause with the default Esc or P, or the on-screen pause button, then inspect Moves. The learned-move rows contain their full numbers and description, and selecting a move opens its sheet. The move guide separates those current-run details from the League’s future learning list.
Use Tab while choosing an upgrade to check your team, then return to the choice. During live play, holding Tab previews the map without pausing; it does not open a move sheet. Missing hover details alone are not a reason to spend Refresh/Banish uses, buy a slot or reinstall the game.
White screen or graphics failure during a run
The game includes a message for a graphics card restart and can wait for the graphics context to return. If it reports that the graphics card did not come back and asks you to reload, follow that on-screen instruction. It may also switch the graphics quality to Low, which you can later change in Settings → Graphics.
In 0.7.0, an active run can also offer Continue without image. This keeps the run going while the 3D scene is missing, using the minimap to help you navigate. Choose it only when that option is shown and you can still follow the game. The new message explains that Reload ends the run and saves what you earned; it does not reopen the battle at the interrupted position.
Before a manual reload, note the version, mode, Pokémon, run time and what happened immediately before the failure. If the game still responds, use its bug-report option. Avoid rapidly opening several copies of the same run while trying to recover it.
Reopening can trigger result recovery, but it does not guarantee the interrupted battle will continue. Check the run history and earned progress separately from whether you can re-enter the map.
Low frame rate or too many attack effects
Open Settings → Graphics and lower the quality. The game also has Hide my attacks, added to reduce the visual workload when effects fill the screen. Attack-opacity, camera and other graphics controls let you trade presentation for readability.
On mobile, inspect the battery-saver option and compare how the game responds with less demanding graphics. The 0.6.0 notes address flickering on the mobile home screen while battery saver is active; that is a specific fix, rather than a guarantee for every mobile performance problem.
If your acquired-item list crowds the map, 0.6.4 adds Settings → Interface control to hide corner items and keeps a long build from covering the minimap. This changes the display, not the items in your build.
Change one setting at a time and observe the same kind of scene. If only late, crowded fights slow down, say that in a report. A statement such as “the menu is smooth, but effects-heavy fights drop frames” gives the developer more information than “not working.”
Mobile movement, camera and full screen
Rotate your phone to landscape, as requested by the original game. Tap inside the player and use its on-screen movement stick and action buttons; the game provides touch controls rather than requiring desktop keyboard input. Use the camera area and the labeled aiming control while keeping the movement stick clear of your other thumb.
The 0.7.0 notes announce fewer mobile crashes and a more compact mobile interface. If a failure persists, record your device, browser, game version and whether the failure followed a busy scene, a window change or a graphics-context loss. The update is not a measured performance result for every phone.
Try the player’s full-screen control when the surrounding page leaves too little room. If touch input, orientation or a browser gesture keeps interfering, use Open original and compare the same game directly. Inspect Settings → Graphics and the battery-saver option for performance; changing screen size and lowering visual load address different issues. These are steps from the original interface and controls, not a claim of measured performance on your phone.
Sound after returning to the game
Click or tap inside the player and check the game’s own audio settings. Version 0.6.4 specifically fixes sound failing to resume after returning from another window in Safari. If silence remains, note whether it started after changing tabs, windows or full-screen state, and whether Open original behaves the same way. Reloading the frame also reloads the game, so record an active run before using it as a reset.
Missing run results or Stardust
Since 0.5.7, the game’s notes say that reopening after a browser close, reload or connection loss saves the recovered run’s earnings, including shinies. Version 0.6.3 specifically fixes recovered runs that were incorrectly rejected and says the affected results have been saved.
Version 0.6.4 further reduces legitimate runs being sent for review by mistake, especially with a poor connection. It does not promise that every pending result will be accepted or immediately ranked.
Version 0.7.0 adds automatic result saving when the connection fails at the end of a run. Restore the connection, reopen with the same identity and inspect the pending/save message and run history. A queued result and server acceptance are separate states. This does not turn a run deliberately started without server progress into a counted run.
- Reopen the original game using the identity you used for the run.
- Restore your connection and read any recovery or save message.
- Check progress and run history. If the server could not save a result, the game says it can send it again automatically the next time you open the game.
- Check the leaderboard state separately. A result under review can have its progress and Stardust retained while the score is not yet ranked.
- If the result is still missing, report the version, approximate run time, mode, character and exact message.
An offline run: progress not saved message is different from a pending server resend. Do not assume every missing result has already been recovered. Likewise, a saved result does not imply a leaderboard place, and result recovery does not imply mid-run continuation.
Guest progress and changing devices
Do not clear cookies, local storage or all site data as a first step for a guest-progress problem. The original game’s privacy notice says browser storage is used for sessions, settings and guest-related state, while player progress and results also involve its server. “Everything is only in local storage” is an unsafe description of this system.
Version 0.6.1 addresses guests losing progress after pressing Exit and signing back in. Update to the current game and use the same browser identity before trying a fresh profile. If you want an account, use the original game’s Save to account route and follow its instructions. This guide cannot inspect or migrate your guest record.
Change the game language to English
Outside an active run, open Settings → Language → Game language → English in the original game. The Language settings category is shown when you are not running a game; you do not need to start a new run to reach it. If you are looking through an in-run settings panel and cannot find Language, use the main-menu settings after that run rather than reloading an active battle just to change the text.
- From the original game’s main menu, open Settings.
- Choose Language, then Game language. If the current text is Spanish, those labels are Ajustes → Idioma → Idioma del juego.
- Select English instead of the automatic browser-language option, then return to the game’s menu and compare labels such as The League, Lab and Upgrades with this English wiki.
The game’s interface language is separate from your trainer name. The 0.7.0 note allowing registration with a name in any language concerns account-name characters; entering an English name or using Settings → Account is not the language-switching procedure. This wiki remains in English, while the embedded original game has its own language setting. The instruction describes the current menu, not a promise that preferences sync to every device or Guest context.
Keys, mouse buttons and gamepad selection
Use Settings → Keys to inspect your current bindings. Version 0.6.2 permits actions on middle click, right click and mouse side buttons. The big-map binding can also be changed. Follow the current on-screen prompt if you have remapped a capture or interaction key.
Auto-walk uses the default T binding in the update notes. As of 0.6.2 it lasts only for the current run, shows when active and switches off when you move backwards. If movement seems to continue unexpectedly, check that indicator and the key binding.
Version 0.6.1 fixes arrow keys or a gamepad moving upgrade cards on their own. If that symptom persists, include your control device and whether it happens on the menu, level-up cards or during movement in a report.
0.7.0 fixes WASD input in Firefox and saving remapped keys. Return focus to the game, inspect Settings → Keys and compare the binding with the key you press before changing browser storage. The patch also adds an adjustable controller dead zone and a default Y toggle for automatic Ultimate.
During live play, hold Tab to preview the map without pausing. While choosing an upgrade, Tab opens your team information so you can compare the offered card with your existing build, then return to the choice. These are different contexts; a live map preview is not a pause.
Prepare a useful bug report
Include the game version, browser and operating system, device, graphics quality, mode, Pokémon and exact steps. The original game’s report form can attach technical data; inspect that option before sending. Never include a password or authentication token.
For focus, full-screen or loading issues, include whether the same action works after Open original, as well as what happens in the embedded player.
If the apparent bug is a missing move, check source, level, League ownership and free slots first. If a challenge is complete but a member is still locked, check the encounter and capture stages. Those are gameplay conditions rather than graphics or saving failures.
Sources and scope
The original loading, graphics, touch-control and recovery rules were reviewed from the 0.6.3 interface/runtime and project privacy notice on 18 October 2026. The 0.6.4 announcement and 0.7.0 announcement, both dated 18 October, were read on 19 October for the added HUD, review, audio, recovery and control advice. The 0.7.0 lost-image and Tab/Y behavior was also read in its public runtime. Embedded-player steps describe the homepage controls. Device-specific outcomes can differ; no physical-phone performance test is claimed.
The purple-list and hover-detail instructions use the 0.7.1 announcement and current runtime, reviewed 19 October 2026, with an original release date of 18 October. Those two UI fixes do not replace the earlier graphics/recovery source dates or imply that every browser failure was reproduced.
The Settings → Language path and its outside-a-run condition come from the same 0.7.1 runtime and English interface strings, reviewed 19 October. It is a menu instruction rather than an account change or a new translation of this website.