Gameplay guide
Jetdash: Cloudline Courier
Thrust is height control, not a permanent speed boost
In Jetdash: Cloudline Courier you hold Space, Up, the screen or Thrust to rise and release to descend. Forward travel continues while you manage altitude. Keeping the input held is therefore not a safe default: it can carry you above the next opening. The edge arrow previews the upcoming gate, so read it before you reach the obstacle rather than reacting when the opening is already beside the character.
Distance increases the pace. Later patterns add narrow moving gaps and staggered double gates. Look at both openings before committing to a long climb. A position that clears the first column may leave too little room to fall through the second. Use shorter holds to settle near the next opening, and release early enough to account for the change in height.
Shield timing and a useful practice loop
E or the Shield control restores protection on a sixteen-second recharge. The shield absorbs one impact; another unprotected collision ends the run. It buys a correction, not permission to ignore the gates. Check whether it is available before choosing a risky route. When it absorbs a hit, immediately return attention to the next safe gap rather than pressing the control repeatedly.
For an early practice run, focus on alternating short rises and releases through the first gates. Next, follow the preview arrow without waiting for an emergency correction. Finally, practice one double-gate pattern with the shield available. Compare the point where you began the climb with where the safe opening actually moved. The game is endless and scored per run; it does not contain a fixed campaign ending or a guaranteed completion time.
Device controls and saved records
Mouse, keyboard and touch all feed the same rise/release rule. Keep touch interaction inside the game surface, and release before using portal controls. Losing focus, changing tabs or pausing releases the input and pauses audio; resume deliberately. The best score and sound setting are stored locally. Storage being blocked should not prevent play, but it can prevent the record from surviving a reload.
The scene, interface and audio are a local Canvas/Web Audio reimplementation based on an MIT-licensed core mechanic. Credit and the upstream license remain with the release. If loading fails, use the page retry control and include the device, browser and visible error in feedback. No MIDI controller or downloaded application is needed for this game.
Game language: en / zh / es / fr / nl / pl / tr