Compatibility and troubleshooting

When a browser battle will not start or accept keys

Start by identifying what is on screen: the site's poster, a package launch screen, a game menu, a speech bubble, or an active dodge. Those states need different actions. Reloading every time can erase the attempt without fixing the cause. These steps follow the player implementation and our 22 October 2026 opening tests of Lancer, Asgore and Mettaton EX.

1. The poster is still visible

Click the site's Play button once. It loads the game from gamebox.bvnplay.online only then; seeing the poster before pressing Play is normal. Wait for the game host to finish loading. If the request is blocked or the host is unreachable, the page's own text can still work while the game cannot. Check that JavaScript is enabled and report the affected page and browser through Contact. A page that loads successfully does not prove every separate game file was reachable.

2. A green flag or title screen appears

The packaged Scratch games have their own click-to-start screen. Click its green flag. Some games add another title screen: the tested Mettaton EX package explicitly asks for Z. A loaded frame is not the same as a running battle. Asgore's creator also warns that starting may sometimes need a second attempt; check focus and the visible start prompt before reloading.

3. Keys stopped after clicking outside the frame

Click inside the visible game, then try a short directional tap. The browser must send keys to the embedded game rather than to a page button or another tab. We encountered waiting inputs during testing and regained the intended interaction by returning focus to the canvas. Keep movement keys released when selecting browser controls, then click back into the game. Do not type sensitive information to test focus; a directional key is enough.

Use the current build's controls, not another character's controls. Lancer uses arrows, Z and X. Asgore's return key is B. Mettaton's tested slow key is X; its packaged input flag did not respond to the Shift alternative in the creator's instructions. See the individual guides for the exact distinction between tested inputs, source mapping and author notes.

4. The screen is waiting after an attack

Read the speech, let it finish if it is still typing, then tap and release the confirmation key. In Lancer and Mettaton, waiting at dialogue was not a network freeze. Holding Z for a long time is not always equivalent to a sequence of taps: Lancer's menu scripts wait for key release. Conversely, do not leave an already moving attack meter unattended while you inspect another tab. Our late Asgore input lost the damage opportunity even though the enemy turn continued.

5. The game is small on a phone or in landscape

The site scales the stage to available space; it does not rewrite a game's input system. Most listed fights still require a physical keyboard. The home battle simulator offers its own Mobile choice, but that does not establish touch support for every other project. Use the scrolling Bosses menu to reach later entries in a short landscape viewport. Fullscreen may be available in supported browsers after launch; if the button is hidden, browser support or the current context may not allow it.

We checked webpage layout at 320x740, 390x844, 844x390 and 1280x800 in Chromium. Those checks found contained content/footer layouts and a reachable last boss-menu entry after the overflow fix. They are not real-device touch tests, Safari tests, or promises about every fullscreen implementation. Tell us your device and orientation when reporting a layout problem.

6. Restart and saved data are different things

On compatible packaged Scratch builds, the site's enabled Restart button sends a restart message to the game. It becomes available after the package reports that it started. It is not a universal save editor, and Bad Time Simulator uses a different runtime without that Scratch bridge. Reloading is a fallback for an unresponsive build, but it discards the current in-memory attempt. Do not assume it preserves a checkpoint.

Some packages map Scratch cloud variables to localStorage on the game host. Clearing site data can therefore remove scores, settings or progress; clearing only the main site's data may not clear the game host's data. We do not recommend clearing everything as the first fix. Read the storage disclosure and keep any progress you need before taking a destructive browser-reset step.

What to send with a reproducible report

Include the battle page, the visible state, browser/device, orientation, exact key sequence and whether clicking the game changed the result. A cropped screenshot is useful; remove private tabs and personal text. Link the relevant step in the build comparison if it differs from your experience. Our test scope makes clear which endings and devices remain untested, so a report need not assume every difference is a regression.