# Rocket cars in a neon stadium

> A Rocket League-style stadium showcase pairs compact rocket cars and a metallic ball with glowing goals, crowded stands, a dark garage display, aerial action scenes, and a bright goal burst.

- Kind: Video
- Page: https://meetreference.com/v/video-rocket-cars-in-a-neon-stadium-a773a9/
- Ready-to-use agent handoff: https://meetreference.com/v/video-rocket-cars-in-a-neon-stadium-a773a9/agent.txt
- Exact prompt as plain text: https://meetreference.com/v/video-rocket-cars-in-a-neon-stadium-a773a9/prompt.txt
- Authorship: AI-made, per the source
- Made with: Not stated
- Model: Opus 5.5
- Built with: RocketSim
- Style: 3D & WebGL; game-cinematic, arcade, sci-fi, neon, sports
- Length and format: 1 min, 16:9 (1280x720 source)
- Playback: a muted visual reference. The original soundtrack is available only at the source.
- Shared by @LLMJunky in X, Sep 23, 2026: https://x.com/LLMJunky/status/2102847543042343072
- 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 video

These are the creator's published instructions, unedited.

## Prompt

```text
Build a polished browser-based 3D Rocket League-style game using Three.js.
Goal: Create a fully playable local web game that runs in the browser. The first screen should be the actual game, not a landing page.
Tech requirements:
Use Three.js for rendering.
Use a real physics engine, preferably Rapier.js, for car, ball, arena, wall, and goal physics.

Use TypeScript if the project already supports it, otherwise plain modern JavaScript is fine.
Use Vite for the dev server unless another stack already exists.
Keep the architecture clean: separate rendering, physics, controls, game state, UI/HUD, and assets.
Core gameplay:
Third-person controllable rocket car.

Large soccer ball with believable bouncy physics.

Enclosed arena with side walls, back walls, ceiling or high invisible bounds, and two goals.
Score detection when the ball crosses fully into a goal.
Reset after each goal with a countdown.
Match timer and score display.
Boost system:Boost meter from 0-100.
Hold boost key to accelerate with flame/trail effect.
Boost drains while active.
Boost pads around the arena refill boost.

Jump system:Single jump.
Optional second jump / flip if feasible.
Air control with pitch, yaw, and roll.

Car should feel responsive and arcade-like, not like a slow simulator.
Controls:
WASD or arrow keys: drive / steer.
Space: jump.
Shift: boost.
R: reset car.
C: toggle camera mode.
Esc or P: pause.
Camera:
Smooth chase camera behind the car.

Camera should follow car rotation and velocity while remaining readable.

Optional ball-cam toggle that keeps the ball in view.
Visual design:
Recreate a Rocket League-inspired feel, including branded-style presentation if desired.
Add a futuristic indoor stadium, colored goals, boost pads, arena trim, and energetic UI.
Add lighting, shadows, bloom or subtle postprocessing if performance allows.
Add clear team colors, goal colors, boost pad glow, trail effects, ball highlight, and simple particle effects.

Use generated, procedural, or available assets as appropriate.

Add a readable HUD with score, timer, boost meter, countdown, and goal celebration text.
Ensure the game works on common laptop screens and resizes correctly.
Physics feel:

Prioritize fun over realism.

The ball should be heavy but responsive.
Cars should have strong acceleration, drift-friendly turning, and stable recovery.
Avoid cars flipping uncontrollably from minor bumps.
Tune gravity, friction, restitution, angular damping, and impulses until gameplay feels good.
AI / opponent:
If time permits, add a simple bot opponent:Bot chases the ball.
Bot aims roughly toward the player goal.
Bot can boost occasionally.
Bot should be beatable, not perfect.

If bot is too risky, create a solo practice mode with two goals and a working scoreboard.

Implementation expectations:

Build the complete working game, not just a prototype shell.
Include all source files.
Add brief comments only where the logic is non-obvious.
Avoid overengineering.
Do not create a marketing homepage.

Verification:

Start the dev server.
Test the game in the browser.
Verify:The scene renders.
The car moves, turns, jumps, and boosts.
The ball collides with the car and arena.
Goals are detected correctly.
Score and timer update.
Reset after goal works.
Boost pads refill boost.
The camera does not clip badly or lose the car.
No major console errors.

Take at least one screenshot or use browser automation to confirm the canvas is nonblank.
Deliverable:
A local runnable browser game.

Provide the dev server URL.

Summarize controls and what was implemented.
Quality bar: Make it feel like an arcade sports game people would actually want to play for five minutes. Spend extra effort tuning car handling, camera smoothing, ball impact, boost feel, and goal feedback. A technically complete but boring physics demo is not acceptable.

A few more bits of feedback. I would like for you to test the game and work back and forth until you have a very strong match to the original Rocket League, including the car design for the Octane. It all should look nearly identical to the original. We are not going to sell or reproduce this. It's just for a visual test, so it is okay to make it look the same, as it will never be distributed.

I want there to be infinite boosts by pressing B, and I want the UI to look extremely polished, like a real game. Make sure that the actual map also looks like Champions Field and is a strong match for the original and very polished. It should look very good. The lighting and the gameplay should be true to life. The physics should feel correct according to the original game. Everything should work exactly the same as it did, from the flip resets to the tackles, to the goal explosions, to the smoke behind the ball when it goes fast, to all of the little small details that generally get missed. I really want you to pay attention to the details.

I really want you to work in a loop and make sure that you are really comparing it to the original game, and I want you to keep iterating until the assets in the game look legitimate and real. You have as many tokens as you want to complete this task. I'm not in a rush at all. I think I just want it to look and play as best as possible. So iterate and take your time.

You have as many tokens as you want to complete this task. I'm not in a rush at all. I think I just want it to look and play as best as possible. So iterate and take your time.

Use every available asset that you can find to improve the quality of your work. Leave no stone unturned. You literally can work for as long as you want and build something truly exceptional.
```

## What it looks like

Written by Reference from the video frames, not by the creator.

Bright arcade-style soccer stadium with small rocket-powered cars and an oversized ball; one view shows a vehicle customization screen.

- Color: Vivid green and orange field markings, deep navy and purple stadium shadows, glowing yellow-orange goal accents, and bright white lights.
- Type: Glossy, simplified 3D game graphics with bold outlines and luminous effects; compact sans-serif interface text.
- Framing: Wide stadium views place the field and goal across the foreground, with the ball, cars, and stands set against the arena. The garage view centers a vehicle beside a dark menu panel.
- Structure: A curved indoor stadium surrounds a striped soccer field, with goals at the ends and tiered spectator stands above. Cars and a large ball occupy the play area; the garage scene has a vehicle preview and stacked menu options.

Storyboard, nine frames spread across the video: https://meetreference.com/media/video-rocket-cars-in-a-neon-stadium-a773a9/storyboard.webp

- Frame 1 at 3.7s: https://meetreference.com/media/video-rocket-cars-in-a-neon-stadium-a773a9/f1.webp
- Frame 2 at 11.2s: https://meetreference.com/media/video-rocket-cars-in-a-neon-stadium-a773a9/f2.webp
- Frame 3 at 18.7s: https://meetreference.com/media/video-rocket-cars-in-a-neon-stadium-a773a9/f3.webp
- Frame 4 at 26.1s: https://meetreference.com/media/video-rocket-cars-in-a-neon-stadium-a773a9/f4.webp
- Frame 5 at 33.6s: https://meetreference.com/media/video-rocket-cars-in-a-neon-stadium-a773a9/f5.webp
- Frame 6 at 41.1s: https://meetreference.com/media/video-rocket-cars-in-a-neon-stadium-a773a9/f6.webp
- Frame 7 at 48.5s: https://meetreference.com/media/video-rocket-cars-in-a-neon-stadium-a773a9/f7.webp
- Frame 8 at 56.0s: https://meetreference.com/media/video-rocket-cars-in-a-neon-stadium-a773a9/f8.webp
- Frame 9 at 63.5s: https://meetreference.com/media/video-rocket-cars-in-a-neon-stadium-a773a9/f9.webp

## Links

- Watch: https://x.com/LLMJunky/status/2102847543042343072
- Original post: https://x.com/LLMJunky/status/2102847543042343072
- Discovery collection: https://data.openchamber.dev/opus-5-5-videos/v/llmjunky-2102847543042343072