Cloud Orchard Delivery Game Builder Prompt

The cloud orchard delivery game prompt turns a cheerful sky-island image into a contained playable challenge. A glider carries fruit between three orchard stops. Gentle wind affects the route, but the game rewards planning rather than punishing reflexes.

Copy the cloud orchard delivery game prompt

Build an original 2D browser game called Cloud Orchard Delivery. The player steers a small glider between floating orchard islands and delivers exactly three crates of fruit in a fixed route. Use a single visible map with a start island, three marked landings and a return dock. Show the current delivery target, remaining crates and a simple wind arrow. A landing counts only when the glider enters the marked zone slowly enough. Give the player a soft bounce or reposition after a rough landing; never erase all progress for a single mistake.

Implement left/right steering, a gentle lift control and a slow-down control for landing. Provide on-screen buttons and keyboard controls. Wind lanes must be visible as moving cloud bands and described in text. Define a predictable wind cycle so the game can be learned; do not randomly change the force while the player is crossing a gap. Use locally generated shapes or original art and keep the game fully offline with no account, advertisement, analytics or external assets. Return source code, run instructions, a rules panel and a short manual test checklist.

Design a fair three-stop route

Place the first delivery near the starting dock so players learn steering and speed. The second crosses one mild wind lane, and the third requires choosing a safe approach to a smaller island. Before coding, draw the route and estimate whether the glider has enough time and lift to reach each stop. If a gap is impossible under the defined controls, adjust the gap instead of making the wind unpredictable.

Keep the camera stable enough to show the destination before the player must act. A minimap or direction marker can help, but should not replace a readable main view. Make crates visible on the glider and remove one only after a confirmed landing. The delivery count and destination label must update together so the interface never claims success before the game state changes.

Three controlled variations

• Add a calm weather mode with weaker wind and wider landing zones for first-time players.
• Create an autumn harvest palette while keeping the island geometry and delivery order the same.
• Offer a route-planning mode with a visible predicted glide arc, without changing the core controls.

Quality review and next steps

Play the route using keyboard alone and then using the on-screen controls on a narrow viewport. Test pausing, restarting, a missed landing, repeated contact with the same stop and returning to the dock after all three deliveries. The third crate must not disappear before the correct landing, and the win message must appear only after return.

Measure whether the challenge comes from understandable choices. If the glider stalls or falls unexpectedly, show the cause through the wind indicator or a clear motion cue. Avoid flashing failure screens or a short timer. A gentle game should give the player room to correct a path and learn from a failed approach.

Make the status text readable against the sky and never rely on crate color alone. Label controls and provide a reduced-motion setting for cloud effects. Write a short instruction panel that explains wind, landing speed and progress. If using sound later, keep it optional; this design must work silently.

The image is a concept illustration for the proposed game, not proof that a playable build exists. Ask the coding assistant to provide actual files and a reproducible run step. Review the game on desktop and phone sizes before claiming the route works. Save the tested control values with the delivered source.

Browse more original ideas in the AI Craft Pad prompt library. The W3C interaction patterns can guide accessible controls.