Paddock Sprint

Cinevva's analyzer read this game's design doc and its source, then wrote the brief below. "Make your own" hands it to the game creator as your opening message, so you start from a real spec rather than a one-line idea.

Recreate a browser-based 3D arcade racing prototype titled “Paddock Sprint,” with a Spanish-language interface and a dark, polished motorsport visual style. Use a Three.js-like perspective 3D scene filling the viewport: a muted blue-gray sky/background with atmospheric fog, strong soft shadows, hemisphere fill light and a bright directional sun. The world is a large flat green grass plane containing a simple closed oval circuit. Build the circuit procedurally as a broad dark charcoal asphalt oval/ring with a grassy infield, white outer curb and red inner curb, plus repeated small white grid/start marks around the racing surface. Add a row of simple blue-gray pit buildings outside one side of the track and a tall white control tower nearby. The available circuits should be Monza, Silverstone, Spa, and Barcelona; they are all variants of this oval layout with different width/height proportions and road widths: Monza is approximately 38 by 24 world units, Silverstone 33 by 28, Spa 44 by 21, and Barcelona 35 by 25.

Place the player at the front of the grid in a low-poly/glTF-style race car, scaled larger than the opponents and colored according to the selected constructor: Ferrari red, Mercedes turquoise, Red Bull deep blue, or McLaren orange. Spawn five additional simulated rival race cars, each in a different bright color, for a total field of six. Rivals continuously drive around the oval at slightly different fixed speeds, while the player drives freely and their displayed race position is estimated from progress around the loop. There is no need to invent weapons, damage, pit stops, boosts, or detailed lap logic: the visible prototype is a straightforward driving demo. Keep the lap display as a “1/3” style race indicator as shown by the interface, even though the implemented mechanics primarily demonstrate movement and progress rather than a completed-lap system.

Before the race, show a large dark translucent rounded lobby panel in the upper-left area, with a subtle border, shadow, and glass-like styling. It must contain the title “Paddock Sprint,” the subtitle “Carreras arcade de circuito — prototipo jugable en navegador,” a Coche dropdown with Ferrari, Mercedes, Red Bull, and McLaren, and a Circuito dropdown with Monza, Silverstone, Spa, and Barcelona. Under those, show a readonly room-code field and a “Compartir sala” button, then a prominent red “Iniciar carrera” button. Add a status panel reading “Eres el administrador de esta sala. Elige coche y circuito.” and explanatory small text saying that the shared link creates a room with locally simulated rivals and that real synchronized players would require a WebSocket backend. Generate a six-character uppercase room code, allow the share action to copy a URL containing the room and guest parameters, and support a guest mode in which the car/circuit controls and start button are disabled and the status says the guest cannot control the administrator’s choices.

When “Iniciar carrera” is pressed, hide the lobby and show a heads-up display over the 3D scene. In the upper-left, display three dark translucent stat cards: position such as “1/6,” speed in km/h, and lap “1/3.” In the upper-right show a pill-shaped green “VERDE” flag. If the player leaves the usable racing band (inside the oval boundary or too far outside it), reduce speed and change the indicator to a yellow “AMARILLA” flag with a yellow/brown background; otherwise keep it green. Show a temporary centered toast reading “¡Luz verde!” at race start, and use similar short toasts for camera changes and room sharing.

Driving must support W or Up Arrow for throttle, S or Down Arrow or Space for braking, and A/D or Left/Right Arrow for steering. Acceleration should smoothly raise speed toward an arcade maximum of about 32 internal units, coasting should decelerate, and braking should decelerate strongly. Steering should be damped/smoothed and rotate the car in proportion to speed, allowing the player to follow the oval. Convert the internal speed to a displayed value around km/h by multiplying by approximately 8.7. Clear held keys when the browser loses focus. Also provide mobile touch controls at the bottom: left/right circular steering buttons and circular FRENO and GAS buttons, with red active styling.

Implement three camera choices accessible from bottom-right HUD buttons: “Cockpit” is a close camera near/above the car looking forward, “Tercera persona” is a trailing chase camera that can be freely orbited by dragging the mouse over the canvas, and “TV lateral” is a fixed elevated side camera looking across the circuit. The default should be third-person chase view. Add mouse drag camera orbit only in chase mode, with constrained pitch. At the bottom of the HUD, show the hint “WASD / Flechas · Ratón: cámara libre · Espacio: freno.” On narrow screens, make the lobby fit with reduced margins and show touch controls, while compacting the HUD cards and camera buttons.

Use clean geometric/procedural scenery and simple race-car models with cast shadows rather than adding unshown environmental features. The overall look should match the screenshot’s dark navy, slate, red-accented lobby UI layered over a muted, foggy, stylized racing world; labels and buttons should remain in Spanish exactly as described.