Lane Rush

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.

Rebuild a portrait-friendly 3D endless lane-dodging arcade game titled “Lane Rush.” Use a Three.js-style perspective scene with a low-poly, clean Kenney Car Kit aesthetic. The camera is a high third-person chase view behind and slightly above the player car, looking down a long road toward the horizon; it should subtly follow the player’s horizontal position. The background is a bright pale-blue sky with atmospheric fog, a flat green grass field on both sides, and scattered simple low-poly roadside trees made from brown cylindrical trunks and green cone foliage. Light the scene brightly with soft shadows.

Create a straight dark charcoal road about three lanes wide, extending far into the distance. Put thin yellow/orange shoulder lines along both road edges and repeated white dashed lane markers separating the three lanes. The three lane centers are clearly distinct, with horizontal positions approximately left, center, and right. The road and scenery should continuously scroll toward the camera to communicate forward motion while the player remains near the bottom/front of the road. Recycle lane markers and trees when they pass the camera so the run is endless.

The player is a small stylized race car centered near the bottom of the view, using a red/orange Kenney race-car model if available, with a simple low-poly fallback car if external assets fail. It can occupy exactly one of the three lanes. Lane changes are discrete but smoothly animated: pressing left moves one lane toward the left and pressing right moves one lane toward the right, clamped at the outer lanes. Support keyboard A/D and Left/Right arrows, plus two large translucent circular mobile buttons at the bottom corners containing left and right arrow icons. Add a brief lane-change cooldown so repeated input does not skip lanes instantly; visually lean the car slightly while it moves.

Spawn traffic obstacles from the far end of the road, initially at the center of the horizon-side road, and move them toward the player at the current road speed. Each obstacle randomly chooses a lane and is one of: a blue/colored sedan, a green truck, or an orange traffic cone. Sedans are most common, trucks less common, and cones somewhat less common; use Kenney sedan/truck/cone assets when available and simple geometric low-poly fallbacks otherwise. Detect collisions based on horizontal lane overlap and longitudinal distance. A collision ends the run immediately. Obstacles that pass beyond the player without colliding are removed and award a bonus: sedans and cones award 25 points, trucks award 40 points.

The score also increases continuously over time at approximately 12 points per second. Start the road speed at 16 units/second and increase it gradually with score, capped at 34, making obstacles and scenery scroll faster and reducing the traffic spawn gap as the run gets harder. Spawn traffic roughly every 1.02 seconds initially with random variation of up to 0.45 seconds, tightening toward a minimum gap around 0.46 seconds as speed rises. After a crash, slow the world toward a crawl rather than abruptly stopping it, but stop scoring and spawning active new traffic.

Implement a minimal HUD over the 3D scene. At the top-left, show a dark translucent rounded panel with large bold white text such as “Score 36  Best 0,” updating the integer score continuously. At the top-right, show a matching translucent panel with the instructions “A/D or ←/→ to change lanes” and “Don’t hit traffic,” right-aligned. The UI should use white text, subtle shadowing, rounded corners, a faint border, blur/glass effect, and responsive sizing for portrait screens. Keep the mobile controls visible along the bottom: two large semi-transparent white/gray circular buttons with inset highlight and shadow.

When the player collides, show a centered dark translucent rounded game-over panel with a large “Crash!” heading, the final line formatted like “Score 0 • Best 0,” the message “Beat your run by dodging longer.”, and a gold/yellow gradient “Restart” button with a strong lower shadow. Restart must work from that button, the Space key, or the R key; it resets score, speed, traffic, player lane, and the game-over overlay. Persist the best integer score locally between runs. Add small synthesized arcade blips for lane changes and successful passes, plus a deeper crash sound, only after browser audio has been initialized by user interaction. Keep the visual presentation uncluttered and faithful to the shown screenshot: broad dark road dominating the foreground, blue sky and green verge, simple trees, small colorful traffic ahead, and no weapons, laps, boosts, collectibles, jumping, braking, or other mechanics.