Ridge 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.

Create a playable browser 3D arcade downhill game titled “Ridge Rush.” Use a third-person chase camera behind and slightly above a small stylized mountain bike, looking down a long sloped trail. The camera should smoothly follow the rider’s horizontal position and keep the bike centered in view. Build the scene with a muted alpine palette: a dark desaturated green-gray trail, pale sage raised banks on both sides, atmospheric teal/green fog, soft hemisphere fill light, and a warm directional sun with shadows. Place a large pale snow-colored low-poly cone-like mountain/ridge in the distant background.

The player avatar is a compact low-poly bicycle with two dark torus wheels, a dark frame/seat and bright orange frame/fork details, with a simple rider represented by a tan head/body sphere and a flattened yellow helmet. Start the bike near the bottom of the trail, at the center lane. The trail is a long rectangular downhill surface with raised side banks, broad enough for five approximate lanes. The bike automatically rides forward; there is no brake, jump, attack, or acceleration control. Its forward speed starts around 11 and gradually increases with distance up to about 19.

Core gameplay: steer left and right to dodge obstacles while continuously descending. Support keyboard A/D and left/right arrow keys, plus two large touch/mouse hold buttons at the bottom corners showing left and right triangles. Horizontal steering should move the bike at roughly 7.2 units/second, clamp it within the trail at approximately x=-5.1 to +5.1, and visually lean/rotate the bike slightly while steering. Populate the trail ahead with roughly 34 randomly arranged obstacles across five lanes: mostly pine trees and some rocks, with varied scale and position. Use recognizable low-poly pine tree and rock/cliff obstacle models or equivalent simple low-poly stand-ins. Obstacles approach because the bike moves forward down the track.

Collision rules: when the bike intersects a tree or rock, increment the crash counter, reduce speed by about 2.5 but never below 7, nudge the bike sideways away from the obstacle, and temporarily hide the hit obstacle for about 650 ms before it reappears. Crashes do not immediately end the run. The run ends automatically after approximately 112 meters. Track distance continuously and display whole meters. Save the best distance score in local storage and show it on subsequent visits.

HUD and screens: Use a dark translucent, rounded, glass-like overlay UI with thin light borders and a clean modern sans-serif font. At the top, show separate rounded pills for DISTANCE with the current value in bright mint, BEST with the saved best distance, and CRASHES with the current crash count. At the bottom, show the left and right rounded square steering controls. Before play, show a centered dark translucent rounded panel with the large title “Ridge Rush,” the subtitle “Bomb down the mountain, thread the trees, and keep your wheels on the trail.”, a mint “Start ride” button, and the hint “A / D or ← / → to steer · mobile buttons below.” Starting resets distance, crashes, speed, bike position, and obstacle visibility and hides the panel. On game over, show a centered panel headed “Wipeout” or “New best!”, state “You rode [distance] m and hit [number] obstacle(s).”, show “Best score: [best] m”, provide a “Ride again” button, and include the hint “Keep carving between the trees and rocks.” Keep the game responsive for portrait mobile screens and desktop, with the 3D canvas filling the viewport and touch interaction preventing page scrolling.