Monsoon Drive

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 playable third-person 3D driving/walking game titled “Monsoon Drive,” set in a compact original Indian urban district called “Riverside Ward.” Use a browser-friendly Three.js-style scene with a perspective follow camera, soft shadows, fog, and a stylized low-poly realistic look. The initial camera follows an animated casual male character on foot, with an interactable homemade blue/teal motorcycle parked nearby at approximately (-4, 0, 7). The player begins on foot and can walk around the district using a virtual analog stick or keyboard-style directional input; holding Shift makes the character run. Face the character in the direction of movement and use idle/walk/run animations when available.

Build the district on a large sandy/beige ground plane with a simple street grid: a broad dark central road, parallel side roads, and crossing roads, all with small pale lane dashes. Surround the roads with blocky apartment buildings in warm beige/tan colors, rows of dark blue windows, and occasional red awnings. Include street lamps, leafy green low-poly trees with brown trunks, a small green park with benches, a red-roofed market strip/stalls, and a petrol station forecourt with a white canopy, red pumps, and a tall sign. Add a simple traffic signal mast near the road. Populate the streets with moving sedan traffic, a parked/player sedan, and several police cars; include a handful of animated pedestrian clones around the ward. Keep the environment bounded visually by atmospheric blue-gray fog.

The player can approach a nearby vehicle and press ENTER or the on-screen ENTER button to enter it. Entering a traffic sedan changes the mode to “Sedan”; entering the motorcycle changes the mode to “Motorcycle,” hides the on-foot character, and lets the selected vehicle drive. Press ENTER again to exit and place the character beside the vehicle. Vehicle control uses the analog stick: pushing forward accelerates, pushing backward reverses, horizontal input steers, and speed is clamped to a moderate arcade range. Add BRAKE and HANDBRAKE touch buttons; braking reduces velocity, while handbrake also reports a traffic violation. The ACTION button causes a crime/traffic violation on foot and, while driving, displays an action/checkpoint toast. Traffic vehicles move along their headings and wrap back into the district when far outside it.

Add a wanted system from zero to five stars. Speeding at high vehicle velocity, pressing ACTION while on foot, pressing Space on keyboard, or using HANDBRAKE raises wanted by one and displays “Traffic violation reported — patrols alerted.” Police patrol vehicles pursue the current player, motorcycle, or sedan while wanted is above zero; if one gets very close it reduces wanted and displays “Patrol boxed you in.” Wanted gradually decreases after a period without a new crime. Display cash as ₹2,400 initially and allow the HUD score/cash value to remain visible.

Use a smooth over-the-shoulder follow camera: closer and slightly lower while walking, farther and higher in a vehicle, looking toward the character or vehicle. Include a CAM button that flips the camera side. Include an N/night toggle on keyboard that switches from bright daylight to a dark blue night background/fog with dimmer lighting, and updates the mode label between “Daylight” and “Night.”

The fixed touch-first interface should match the supplied visual style: full-screen canvas with a dark navy/black translucent glass HUD, thin pale blue borders, rounded corners, subtle blur/shadows, white sans-serif typography, and cyan accents. At top-left show a card with “MONSOON DRIVE,” “Riverside Ward,” and the current mode (“On foot · Daylight,” “Motorcycle · Daylight,” or “Sedan · Daylight”). At top-right show a mission card initially reading “Mission 1 · Parcel Run,” “Take the motorcycle to the blue marker before the timer expires,” plus “Wanted ☆☆☆☆☆ · ₹2,400.” Provide a MISSION button that cycles the displayed mission text among: “Mission 1 · Parcel Run,” “Mission 2 · Flyover Sprint” with “Drive the car through the three amber gates around the ward,” and “Mission 3 · Red Route Escape” with “Raise your wanted level, then lose the patrols before the timer ends.” Reset a 90-second mission countdown when cycling missions, but do not require visible mission objectives if they are not implemented.

At the center of the initial screen show the onboarding overlay: large “Riverside Ward,” explanatory copy “A compact, original Indian city district built for touch-first driving. Walk to the motorcycle, then take the parcel across the flyover,” and a rounded aqua pill saying “Tap ENTER / ACTION near a vehicle.” Allow the hint to be dismissed by clicking it. Put the controls at the bottom: a large outlined circular analog stick on the lower left with a pale aqua draggable knob, and six rounded dark buttons in a 3-by-2 grid on the lower right labeled CAM, ENTER, ACTION, BRAKE, HANDBRAKE, and MISSION. Show brief bottom-center toast notifications for entering/exiting vehicles, mission changes, night/day changes, and violations. Make the layout responsive, with larger controls on desktop and touch/pointer support on mobile. Do not add rain, a working blue parcel marker, actual flyover geometry, gate checkpoints, or mission completion logic unless explicitly implementing them; the described source mechanics primarily provide the mission text, timer, movement, vehicles, wanted system, and HUD.