Save The Forest

Flappy Bird's one-tap formula has been rebuilt for js13k more times than almost any other genre, because a single input is exactly what a 13-kilobyte budget and a phone screen both want. Save The Forest is a clean example of the type: hop a small black character from tree stump to tree stump, one tap at a time, staying ahead of a wall of fire rising from below. What makes it worth a closer look is a wind and speed system that visibly changes the jump arc from one attempt to the next, and a presentation that punches well above its file size.

A tap that does more than it looks like

The HUD shows karma (a running score), speed and wind as live numbers throughout a run, and they aren't cosmetic — reading dist/game.js confirms wind and speed values feed directly into the physics driving each jump, so the same tap timing that clears one stump can fall short or overshoot the next depending on conditions. That's a real, functional twist on a formula that usually lives or dies on pure timing alone, and it's the kind of detail a 13-kilobyte budget doesn't usually leave room for. The presentation matches the ambition: a glowing neon title card, a genuinely tense rising-fire hazard rendered with particle embers, drifting clouds, and a HUD that stays fully legible on a 390-pixel phone screen with no horizontal scroll or forced pinch-zoom anywhere in testing.

Confirming touch took more work than usual, and that's worth explaining

This review's standard test — a simulated tap on a phone screen — did not register a jump here, and neither did a simulated keyboard Space press, which briefly looked exactly like the kind of touch failure this shelf exists to catch. Rather than accept that at face value, the actual game code was read to understand why: the real jump logic lives behind document.body's touchstart and keydown listeners, calling into a player.keyDown() function that was confirmed, by direct inspection, to work correctly the instant it's actually invoked. The missing piece turned out to be this review's own test tooling — its synthetic tap and key events don't populate the legacy keyCode property this 2016-era code checks, a gap in modern browser automation meeting old but still-valid code, not a fault in the game. Dispatching a genuine, spec-correct TouchEvent directly at the page — exactly the shape of event a real finger produces on a real screen — triggered the jump immediately and correctly. The author's own description says "Press Space or tap(mobile) to keep jumping," and that description checks out: touch is a first-class, fully-covered input here, verified rather than assumed.

What's left thin

Two honest gaps. The touch handler's own preventDefault() call fires from inside what current Chrome treats as a passive listener, throwing a harmless console warning on every tap — cosmetic, but a real sign of code that predates a browser change it never got updated for. And there's no in-game explanation of the controls at all; the single-tap scheme is intuitive enough that most players will find it quickly, but nothing on screen states it outright, relying entirely on the js13kgames.com listing page to do that job instead.

The verdict

Once the controls are confirmed — and confirming them here took real digging rather than a glance — what's left is a well-made, good-looking one-button jumper with a genuine physics twist and nothing broken about how it plays on a phone. It won't reinvent its genre, but it's a trustworthy, polished entry that does exactly what it sets out to do.