# Cartoon endless runner over parallax hills > Fun Game, a bright one-button runner: a round cartoon character jumps over block obstacles with faces as the speed climbs, over parallax hills and clouds, with sounds and a best score. One of OpenAI's GPT-5 launch examples, made from one short prompt. - Kind: Game - Live game: https://gpt5-coding-examples.vercel.app/fun-game - Page: https://meetreference.com/v/cartoon-endless-runner-parallax-hills/ - Ready-to-use agent handoff: https://meetreference.com/v/cartoon-endless-runner-parallax-hills/agent.txt - Exact prompt as plain text: https://meetreference.com/v/cartoon-endless-runner-parallax-hills/prompt.txt - Authorship: Not stated - Made with: Not stated - Model: GPT-5 - Built with: Plain JavaScript - Style: Games; endless runner, 2d, cartoon, parallax, casual, single html file - Shared by OpenAI in GitHub, Aug 7, 2025: https://github.com/openai/gpt-5-coding-examples/blob/main/examples/fun-game.yaml - Prompt fidelity: Verbatim. This is the complete prompt exactly as the creator published it. ## Before you start Guidance from Reference, separate from the creator's instructions. 1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present. 2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized. 3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed. 4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting. 5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use. ## Recreating this game These are the creator's published instructions, unedited. To adapt it: Change "Name: Fun Game" and "Goal: Jump over obstacles to survive as long as possible." to your own game, and keep the look lines ("colorful, with parallax scrolling backgrounds", "cartoonish and be fun to watch") or swap in your own style. ## Prompt ```text Create a single-page app in a single HTML file with the following requirements: - Name: Fun Game - Goal: Jump over obstacles to survive as long as possible. - Features: Increasing speed, high score tracking, retry button, and funny sounds for actions and events. - The UI should be colorful, with parallax scrolling backgrounds. - The characters should look cartoonish and be fun to watch. - The game should be enjoyable for everyone. ``` ## What it looks like Written by Reference from the recording frames, not by the creator. A side-scrolling runner in bright cartoon colors: a round pink character with big eyes hops over pink block obstacles with faces, under puffy clouds and a glowing sun. - Color: Sky blue fading to lavender, white clouds, a pale yellow sun, layered blue hills, striped green grass, and coral-pink obstacles. - Type: Small rounded pills along the top for the game's name, score, best, speed, and sound. - Framing: 16:10, flat side view. The character stays near the left edge on the grass line while obstacles scroll in from the right; most of the frame is sky. - Structure: Running on open grass, obstacles of different heights arriving, jumps over a tall block and groups of small ones, and fresh runs after misses, with the score resetting and the best score kept. Storyboard, nine frames spread across the recording: https://meetreference.com/media/cartoon-endless-runner-parallax-hills/storyboard.webp - Frame 1 at 1.2s: https://meetreference.com/media/cartoon-endless-runner-parallax-hills/f1.webp - Frame 2 at 3.6s: https://meetreference.com/media/cartoon-endless-runner-parallax-hills/f2.webp - Frame 3 at 6.0s: https://meetreference.com/media/cartoon-endless-runner-parallax-hills/f3.webp - Frame 4 at 8.4s: https://meetreference.com/media/cartoon-endless-runner-parallax-hills/f4.webp - Frame 5 at 10.8s: https://meetreference.com/media/cartoon-endless-runner-parallax-hills/f5.webp - Frame 6 at 13.2s: https://meetreference.com/media/cartoon-endless-runner-parallax-hills/f6.webp - Frame 7 at 15.6s: https://meetreference.com/media/cartoon-endless-runner-parallax-hills/f7.webp - Frame 8 at 18.0s: https://meetreference.com/media/cartoon-endless-runner-parallax-hills/f8.webp - Frame 9 at 20.4s: https://meetreference.com/media/cartoon-endless-runner-parallax-hills/f9.webp ## How it was made, per the creator - One-shot: yes, a single prompt with no follow-ups - Notes: OpenAI's README says every demo in the collection was generated in a single GPT-5 or GPT-5.2 prompt with no code written by hand. The result is one HTML file. Which coding tool ran it isn't stated. > generated entirely in a single GPT-5 or GPT-5.2 prompt, without writing any code by hand > (OpenAI) ## Links - Play game: https://gpt5-coding-examples.vercel.app/fun-game - Original post: https://github.com/openai/gpt-5-coding-examples/blob/main/examples/fun-game.yaml - Code for every example: https://github.com/openai/gpt-5-coding-examples