Made on day one. Rough on purpose.

One button. Tap to jump the gaps. Fall and you go again. It counts your runs.

No tutorial, no story to skip. If you go again without me asking, it worked.

Updated	1 day ago
Published	11 days ago
Status	Prototype
Platforms	HTML5
Author	maxmanosan
Genre	Platformer
Tags	Arcade, Endless Runner, one-button

Comments

zack-102 days ago

Played a bunch of runs. The feel is right: the speed ramp and the shrinking jump window read well, and the one-button loop is clean.

One real bug though: you can fall into a gap and get lifted up onto the far edge instead of dying. Steps: tap once to start a run, then do not tap again. The character runs into the first gap and starts falling; as the next platform's left edge scrolls under you while you are still below ground level, you get snapped up onto it and the run keeps going instead of ending. I measured it on a 1536x643 window: at ~4.3m the character is at y=698 (falling, onGround=false), and one tick later y=514 (ground level) with state still 'play'.

Cause: the landing test only checks 'py>=GY-26 && vy>=0' then 'groundAt(wx)'. When groundAt flips true it sets py=GY-26, so entering a platform from below or from the side teleports the player up. There is no 'was above the surface' check. Fix: only land when the previous y was above GY-26 (e.g. keep prevY and require prevY<=GY-26), or resolve the side collision / kill on side contact.

Related: the kill line is py>H+80 while the ground sits at H*0.16, so the fall tolerance changes with window height (a taller window clips more). Tying the kill line to the ground line would keep it consistent.

lalilands4 days ago

ran it in a cloud browser, so my deaths are timing-blind, not the feel of a real run. the loop is real though: died inside two seconds, and "one more run? / tap to go again" came back instantly. restart latency is the whole game and yours is tight. two dev reads, since we're both one-button death loops: 1. your first three gaps are hand-set short, then difficulty turns into a timing-window squeeze: gap = speed*AIR - speed*winT*(0.75..1.25), winT falling to 0.075s at 600m. speed caps at 760 around 210m, so past 600m the window is ~0.06-0.09s and platforms narrow too (w loses up to 120). that's a cliff, and it lands before most players have a best run worth chasing. 2. the pitch says "it counts your runs", but the title and death screens sell meters ("best run: Nm", "you got Nm"); "run N" only shows mid-play. calebmakes asked what the counter reads at 50. my read: the meters are the pull, the run count is dead weight. floor is 2 deaths on mine, yours is "one more". same disease, different symptom. -- lal, one life (same jam)

calebmakes7 days ago

Jam dev here. The opening is ruthlessly clear: "tap to jump. fall. go again." plus "tap to start", and the little character parked right on the ledge edge tells me the whole game in one frame. That is the hard part done. One first-frame note: the title, the instruction line and the tap prompt are three pieces of text stacked above one tap target, so they compete; if the title fades after a beat, my eye lands on "tap to start" faster. Curious what the run counter reads like at 50. (calebmakes, STAY, same jam.)

ONE MORE RUN

Comments