Bounce Back in browser

Game files

No own files requested before opening movement

Controls

Keyboard controls

Account

No sign-in in checked entry

Mobile gameplay

Not tested

Full session

Not tested

HTTP link check

HTTP 200; 0 redirects (2026-10-20)

Basis: project instructions and limited desktop entry observation. Observations: Oct 20, 2026. Conditions organized: October 20, 2026.

A short D input moved relative to island landmarks without sign-in or own files. A pointer attempt did not establish boomerang flight; dash, combat, shops, saves and mobile remain unverified.

Project type: Native browser game

Frank Force's repository identifies an original JavaScript boomerang roguelite and links the checked demo. A Zelda homage is not an actual Zelda port or a general-purpose emulator.

Classification organized October 20, 2026 from the recorded source and check notes; not a new gameplay test.

This Bounce Back browser guide covers Frank Force's repository-linked GitHub Pages demo, with BounceBack as the source repository's spelling. It is an original boomerang roguelite and a Zelda homage, not an actual Zelda release or a general-purpose emulator. The initial island displayed the game's title, a JS13k 2019 label and Frank Force attribution. A short D input moved relative to the island landmarks and shifted the scene, providing a concrete desktop movement result before any extended progression was attempted.

We reviewed the source and opened the demo on October 20, 2026. The author also links a competition build; that is a separate entry path that was not tested here. Our pointer press left an aim marker but did not establish a boomerang in flight or its return, so movement and throwing are deliberately recorded differently. The public screenshot shows the actual starting island with three hearts, one boomerang and zero gems. That is not a completed level, a combat recommendation or proof that stored progress was restored.

Guide published 2026-10-20. Source reviewed 2026-10-20. Author release-page publication: Not established. The live title identifies JS13k 2019, but an exact original publication date for this GitHub Pages deployment was not established.

Game files

The checked demo opened its island without asking for a ROM, owned-game installation, archive or other visitor-supplied game data. It loaded its own online resources. The competition's small-size context is not a measured transfer size for today's complete page, and we did not inventory downloads or verify an offline cache. No source build, dependency installation or alternative engine was required for this visit. The directory links to the creator's destination rather than supplying a playable mirror, converted package or commercial game files. Our local image is observation evidence, not a substitute for the external runtime.

Controls

The README documents WASD for movement, mouse aim, click to throw and Space to dash. Holding D for 250 milliseconds produced movement relative to nearby landmarks. A pointer press of 150 milliseconds left an aim marker, but the inspected images did not establish boomerang flight, a hit or retrieval. We did not exercise Space or the other movement directions. The gameplay filter therefore records keyboard input based on the actual D response, not a fully tested keyboard-and-mouse combat scheme. Read the author's bindings while keeping the unverified throw and dash separate from basic movement.

Account

No sign-in, email, name field, payment or registration preceded the starting island and short movement. We did not contact a community, submit a score or open an external account. The source describes an in-game shop and persistent resources, but we did not enter the shop, buy an item or inspect any later access condition. Nothing in this entry check establishes a cloud profile or synchronized save. Bookmarking the guide only stores its identifier in this directory; it cannot retain the external character, gem balance, inventory or level state on another device or browser profile.

Mobile gameplay

Not tested. Our observation used a desktop keyboard and a pointer attempt, not a phone, touchscreen or connected controller. We did not find or test an alternative touch layout, rotate a device or check whether simultaneous movement and aiming are practical on mobile. A browser page that scales to a smaller screen is not evidence of responsive game input there. This guide's narrow-width layout and uncropped image are reading checks only. They should not be presented as a phone performance benchmark, an input-latency result or verification that a visitor can finish a level without desktop controls.

Full session

We stayed around the starting island and did not clear an enemy encounter, finish a level, inspect later islands or reach an ending. Three hearts, one boomerang and zero gems were visible in the recorded image; those counters are not evidence of tested damage, retrieval or resource collection. The author's save-related feature description was not checked by reloading or recovering a run. We also did not verify a speedrun mode or any endgame unlock. A responsive rightward move is useful evidence, but it does not establish the roguelite's complete progression, difficulty or save reliability.

HTTP link check

An independent request to the exact case-sensitive killedbyapixel.github.io/BounceBack/ address returned HTTP 200 with zero redirects on October 20, 2026. Certificate checking remained enabled. This is the demo linked in the original repository's project information, not an invented lower-case route or a third-party mirror. The document response is recorded separately from D-key movement and the unconfirmed pointer throw. It does not verify all level assets, another build, online services or future availability. If a later visit behaves differently, identify the exact destination and stage before comparing it with this limited opening check.

The creator's README contains mechanics and tips beyond the small action sampled here. Use it as the source for the intended throw and dash bindings, not as evidence that our browser attempt exercised them. The unchanged recorded boomerang count alone would not tell you whether a throw happened and returned; this is why we do not infer a successful throw from a later still image. Likewise, a feature described as saving gems or maximum level needs a separate persistence test before it becomes a recovered-save result. We did not perform that test or clear stored data. The visible JS13k 2019 label is historical context and is not silently reused as an exact release date for the currently hosted files. Different competition and development builds can have different interfaces, so keep this demo's observation attached to its actual URL rather than applying it to every edition with the same title.