About the game

Time ground-only jumps while an automatic runner advances toward a 1,000-distance target.

Reach the distance target while keeping a life

Pixel Pilgrim is an automatically moving runner. Time your jumps over gaps and stone blocks, and collect sparks when the landing path is safe. The implemented distance target is 1,000 in-game units; losing all three lives ends the attempt before that target.

A score increase is not the finish condition. Forward distance keeps increasing during the running simulation, so the task is to protect the remaining lives long enough to reach the route target.

One jump input, with a ground check

Space, Up arrow and a tap or click on the game canvas attempt a jump. The jump only starts when the character is on the ground. There is no mid-air second jump in this version, and left/right inputs do not steer this runner.

Make the first attempt small:

Start the round and let the countdown finish.
Try one jump from the ground and watch the landing.
Wait for the next obstacle before pressing again. Repeatedly tapping while airborne does not keep lifting the character.
Watch the distance and life indicators together. Leave a risky spark alone if collecting it would put the next landing into an obstacle.

Points and lives do different jobs

Signal	Current meaning
Distance toward 1000	Progress toward the route-complete condition.
Three life markers	The remaining margin before an early loss. Obstacle contact can cost a life.
Score	Time in the run, sparks and clean obstacle passes contribute points; the combo affects these gains.
A collected spark	Adds points; it does not restore a life or remove the next obstacle.
Route completion	Reaching the distance target adds a bonus based on the lives still held.

The current runtime tracks a clean-pass combo. Passing an obstacle without contact increases it; contact resets it. The combo increases the time-based point rate and spark gains, while clean passes add a bonus. The displayed × indicator is not a uniform multiplier applied to every point. It does not replace the 1,000-distance finish condition or restore lives.

Work out why a jump failed

What happened	Check	What to change
A second tap has no effect	The character is still airborne.	Wait for a landing before the next jump input.
A life is lost after a spark pickup	The spark did not protect the following landing.	Prioritize the obstacle and landing path, then add safe pickups.
The character keeps moving without Left/Right	Forward movement is automatic.	Use jump timing rather than directional steering.
Score rises but the attempt is not complete	Distance has not reached the target.	Follow distance and remaining lives, not score alone.
A key seems ignored	The round may be paused, counting down or not focused.	Start or resume, focus the game, then try one Space or Up input from the ground.

Reset the decision, not the whole plan

After a failed run, change the timing of one jump or skip one risky pickup. Keep the other choices similar so you can tell what happened. Pause before stepping away; this is an in-game pause, not a promise that closing the tab preserves your run.

The rules were checked on 13 October 2026 against the current Pixel Pilgrim runtime and a normal Space input followed by pause. This check does not establish compatibility with every device or a guaranteed completion time. Narrow start panels can be scrolled to reach Start.

If you prefer selecting lanes to timing ground-only jumps, Neon Divide uses three lanes and an ongoing score run. Compare the two tasks on the arcade page.