Jetpack Courier is a journey across a scrolling route, collecting five parcels and landing at the delivery deck on the far right. You do not shuttle every parcel back to the starting pad. The important planning units are the next parcel, the next obstacle gap and the next place you can land for fuel.
Collection and delivery are different events
Touching a parcel adds it to the collected total. Delivery happens only when you land on the final delivery pad with every parcel collected. Merely reaching that deck early is insufficient, and passing over it is not a landing. Check the collected counter before treating the final approach as the end of the run.
The route contains intermediate safe pads as well as the starting pad and final deck. A landing refills fuel and updates the recovery checkpoint. The far-right deck is visibly labelled DELIVERY DECK. Think of the trip as successive sections across the world, not a sequence of trips back to the first platform. The time limit is 90 seconds and the third crash ends the run.
Control velocity before trying to hold a position
Horizontal input accelerates the courier, while damping gradually reduces horizontal velocity. Releasing Right therefore does not instantly stop rightward travel. If you aim for the centre of a pad and release only when already above it, the remaining drift can carry you beyond the landing area.
Thrust works against gravity. Releasing it does not instantly make the courier descend: an upward-moving courier first slows its climb. Conversely, pressing it during a fall takes time to reverse downward velocity. Watch movement over a short interval rather than treating the thrust button as a direct height selector. Practise near a pad before combining a height change with a long sideways crossing.
Treat a gap as space for the whole courier
The first major low obstacle calls for gaining height before reaching it. Farther along, a ceiling obstacle and a floor obstacle form a corridor. Flying arbitrarily high is therefore not a general safety policy. Look at both the top and bottom boundary of the opening before committing to the crossing.
The engine checks the courier’s rectangular body against obstacles. A centre point that appears inside the gap does not prove that the head or feet clear it. Settle the vertical motion before the narrow passage where possible, then use small adjustments while crossing. Climbing too early can hit the ceiling; waiting too long can leave the feet below the safe opening.
Landings refuel, but do not erase horizontal drift
A descending crossing onto a safe pad refills fuel and stops downward motion. Unlike Rocket Lander, this game does not require meeting a gentle vertical-speed threshold at the pad. The harder challenge is overlapping the pad on the descent while staying clear of hazards. That difference matters when transferring habits between the two games.
Landing also does not explicitly cancel horizontal velocity. A moving courier can slide across and leave the pad unless you manage the sideways input. Use the stop to confirm the fuel gauge and reset your plan for the next obstacle. Leaving immediately with uncontrolled drift can waste the advantage of a well-placed checkpoint.
Recover from a crash by checking what persisted
A nonterminal crash returns the courier to the most recent checkpoint with fuel restored and velocity reset. Previously collected parcels remain collected; the crash is not a complete reset of your delivery progress. The elapsed time, however, is not refunded. Recollecting an already taken parcel only spends more of the remaining route budget.
After recovery, read the collected count, locate the checkpoint and name the next missing parcel. Diagnose the failed section: late climb over a low obstacle, too much ascent into a ceiling, insufficient space for the body, or horizontal overshoot of a pad. Change that one approach before resuming. Falling below the play area or flying too far above it can also cause a crash, so climbing away from every difficulty is not an escape route.
Two experiments to try
EXPERIMENT 1
Measure the movement left after release
Start near the broad first pad and use a fresh attempt if the courier has already travelled far along the route.
- Lift clear of the pad with a brief thrust input.
- Apply Right briefly, then release the horizontal control while observing the continuing drift.
- Return toward the pad and try releasing the horizontal input earlier before a descent.
What to observe
Watch when horizontal travel actually diminishes and whether the landing leaves the courier moving across the platform.
Why this comparison is useful
Input, velocity and position are different parts of the control problem. Earlier release creates time for damping; the pad does not perform every part of the stop for you.
Your change and observation:
EXPERIMENT 2
Make one pad a deliberate checkpoint
Choose the next intermediate pad rather than aiming straight for the final deck.
- Collect the parcel on the approach if you can do so without abandoning the landing line.
- Descend onto the pad and check that fuel returns to full.
- Pause to name the next parcel and the upper and lower limits of the next obstacle gap.
- Continue with that section as the immediate goal.
What to observe
Check whether planning from a stable pad reduces uncertain mid-air corrections. If a later crash happens, note which pickups and checkpoint remain.
Why this comparison is useful
The route offers recovery structure. You can use it to isolate a difficult section without pretending that a crash restores the spent time or grants unlimited attempts.
Your change and observation:
Check your decision
After collecting three parcels, you crash and return to an intermediate pad. What should your next plan assume?
Answer and explanations
Use the persistent progress to plan the next missing pickup, while recognising that the remaining time and crash budget are smaller.
- Those pickups remain collected; check the counter and continue toward the missing parcels.
Supported. The crash resets position, velocity and fuel, but does not clear the parcel flags.
- Every collected parcel must be returned to the starting pad again.
Not supported. Delivery occurs at the far-right deck after all five are collected.
- The clock restarts, so there is no cost to the crash.
Not supported. Elapsed time remains spent and the crash count increases.
Your next practice session
Practise reaching one intermediate pad with a deliberate landing, then extend the same plan by one parcel-and-obstacle section.
Scope and checks
This guide describes the current Playfield implementation. The experiments are proposed ways to practise, not measured player results. Rules were checked against the game source; the written scenarios and explanations received a separate review.
- Jetpack Courier flight and checkpoint rules — Primary implementation inspected for the stated mechanics. The practice experiments are proposed exercises, not reported human playtest results.
- Jetpack Courier route and delivery-deck display — Primary implementation inspected for the stated mechanics. The practice experiments are proposed exercises, not reported human playtest results.
Playfield Arcade · Updated 4 October 2026 · Original practice design, AI-assisted writing and code.