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 hom
投稿本文
この文章は X の元投稿からです。
Rocket League-style browser game with boosts, goals, and bot chase AI
GAMING = SOLVED (v2) - Opus 5.5 is CRACKED!!!
RocketLeagueBench is basically saturated at this point.
I received a lot of hate mail from the Rocket League community over the last video I made, but its serious cope.
You might think AI created games are bad, or can only look good if they reference existing material, but you're wrong.
Even if we say that they're not great now, I think it's pretty clear that we're <12 months away from being able to make games indistinguishable from major studios.
All it takes is a bit of time, taste, and prompting and you can honestly build some crazy ish right now.
Whether or not something already exists is fairly immaterial. If you can describe it well enough, you can build it.
This is by far the best looking Rocket League clone I've ever made.
Unbelievable. Opus 5.5 drove this end-to-end, including the cinematic video you see here.
The map is insanely good.
The Octane meshes and audio were imported, but the rest was entirely generated by Opus (physics based on RocketSim).
The best part? It only used 3% of my Weekly usage (x20 plan).
It was very slow though. It took about 2 hours for the initial pass, and then about 8-10 prompts to get to this point you see now.
Far from perfect but it's only been a day ;)
Enjoy!