Last Gear: City Rush

By (@anita) · · Games

Last Gear: City Rush is a 3D futuristic arcade street racing game set in the sprawling coastal metropolis of Neo Vantis 2099. Players get behind the wheel of high-performance V12 and V10 wedge supercars to race across a continuous 3.6 km highway circuit spanning 7 distinct districts: Neo Vantis Downtown — Central skyscraper expressway and scenic Mediterranean hillside villas. Vantis Coastal Bayfront — High-speed oceanfront promenade sweeping toward the bay. Vantis Ocean Suspension Bridge — A monumental 1.24 km cable-stayed suspension bridge soaring above the open sea alongside maritime vessels. Mount Vantis Light Tunnel — A 720-meter mountain bore carved through a rocky massif, packed with glowing gold, cyan, and amber LED arch ribs, ceiling floodlights, and multi-tier neon wall strips. Skyline Elevated Viaduct — An upper-tier highway overpass emerging from the mountain tunnel exit. Reactor Industrial Sector — Heavy cargo harbor and refinery docklands. Century Grand Boulevard — The high-speed main straight returning to the Start/Finish line.

Tech stack

  • Google AI Studio (4 Argon)
  • Vercel
  • Gemini (4 Argon)

Prompt steps

  1. Step 1

    LAST GEAR: CITY RUSH
    Complete 3D Street Racing Game Development
    You are a senior Three.js game developer, 3D environment designer, vehicle gameplay programmer, AI racing engineer, and performance optimization specialist.
    
    1. GAME CONCEPT
    Create a visually impressive 3D street racing game set in a futuristic city called NEO VANTIS in the year 2099.
    The player drives a powerful sports car and competes against AI-controlled racing opponents on long roads surrounding the city.
    The racing environment must include:
    Long multi-lane highways.
    Large bridges crossing rivers.
    Beautiful riverside roads.
    Futuristic city streets.
    Elevated highways.
    Underground tunnels.
    Sharp turns and sweeping curves.
    Long straight roads for high-speed racing.
    City buildings, skyscrapers, streetlights, signs, and scenery.
    The world should feel like a continuous connected racing circuit, not a collection of disconnected small road sections.
    2. CORE GAMEPLAY
    Create a playable racing game with:
    One player-controlled sports car.
    5–7 AI racing opponents.
    Dynamic civilian traffic.
    Race countdown.
    Starting grid.
    Checkpoints.
    Lap system.
    Race timer.
    Position ranking.
    Finish line.
    Victory and defeat screens.
    Restart race functionality.
    The player must be able to finish an entire race from start to finish.
    3. VEHICLE SYSTEM
    Build a controllable 3D sports car.
    The car must have:
    Acceleration.
    Braking.
    Reverse.
    Steering.
    Speed-dependent handling.
    Nitro boost.
    Wheel rotation.
    Brake lights.
    Headlights.
    Collision detection.
    Basic suspension or body movement.
    Use an existing suitable 3D model only if its license permits use. Otherwise, create an original car using Three.js geometry.
    Do not depend on an animated human driver character.
    The vehicle must remain visible and properly aligned with the road.
    4. PLAYER CONTROLS
    Desktop:
    W / Arrow Up: Accelerate.
    S / Arrow Down: Brake and reverse.
    A / Arrow Left: Steer left.
    D / Arrow Right: Steer right.
    Space: Handbrake.
    Shift: Nitro.
    R: Reset vehicle if stuck.
    Mobile:
    On-screen acceleration button.
    On-screen brake button.
    Left and right steering buttons.
    Nitro button.
    Controls must be responsive and support holding buttons continuously.
    5. AI RACING OPPONENTS
    Create 5–7 independent AI racing cars.
    AI opponents must:
    Follow the racing route.
    Accelerate and brake intelligently.
    Maintain appropriate distances.
    Change lanes when necessary.
    Overtake other opponents.
    Avoid traffic vehicles.
    React to collisions.
    Make mistakes occasionally.
    Compete with the player naturally.
    AI cars must not simply move in a straight line or teleport to checkpoints.
    Each opponent should have its own color, speed characteristics, and driving behavior.
    6. DYNAMIC CITY TRAFFIC
    This is an important gameplay feature.
    Create civilian vehicles moving along the roads.
    Traffic must:
    Use different vehicle colors and types.
    Travel in appropriate lanes.
    Maintain spacing.
    Have varied speeds.
    Follow road direction.
    React to nearby vehicles.
    Create obstacles that the player must avoid.
    When the player's car hits traffic:
    Apply collision response.
    Reduce speed.
    Add a brief visual impact effect.
    Prevent vehicles from passing through each other.
    Traffic must not randomly spawn directly on top of the player's car.
    7. RACING ENVIRONMENT
    Build a long continuous racing circuit surrounding NEO VANTIS.
    Include these sections:
    Downtown highway: skyscrapers and neon signs.
    Riverside road: a long road alongside a detailed river.
    Grand bridge: a large bridge crossing the river.
    Elevated highway: roads above the city.
    Tunnel section: underground driving with lighting effects.
    Industrial district: factories, containers, and industrial buildings.
    City boulevard: wide roads with streetlights and traffic.
    Use connected road segments with smooth transitions and proper collision boundaries.
    Roads must have:
    Lane markings.
    Guardrails.
    Roadside barriers.
    Proper width.
    Smooth curves.
    Correct elevation.
    Collision boundaries.
    Do not create floating or disconnected road pieces.
    8. CAMERA SYSTEM
    Implement a smooth third-person racing camera.
    Requirements:
    Follow the player's car.
    Stay behind the vehicle.
    Smoothly interpolate movement.
    Look toward the direction of travel.
    Adjust camera distance at high speeds.
    Add subtle camera shake during collisions.
    Avoid clipping through buildings and terrain.
    The car must remain clearly visible at all times.
    9. GRAPHICS AND VISUAL EFFECTS
    Create a polished futuristic racing atmosphere.
    Visual features:
    Neon city lights.
    Detailed buildings.
    Realistic road materials.
    River reflections.
    Bridge lighting.
    Headlights and taillights.
    Tire smoke.
    Nitro flame effects.
    Speed effects.
    Motion blur where practical.
    Rain or wet road effects if performance allows.
    Prioritize stable frame rates over excessive graphical effects.
    10. USER INTERFACE
    Create a professional racing HUD displaying:
    Current speed in km/h.
    Nitro meter.
    Current race position (1st, 2nd, 3rd, etc.).
    Current lap and total laps.
    Race timer.
    Checkpoint progress.
    Mini-map or route indicator.
    Create:
    Main menu.
    Car selection screen.
    Race start screen.
    Pause menu.
    Race results screen.
    Restart and return-to-menu buttons.
    Use a modern futuristic racing UI with readable typography and smooth animations.
    11. GAME ARCHITECTURE
    Use:
    Three.js.
    TypeScript.
    Vite.
    Modular game architecture.
    Separate systems into modules:
    GameManager.
    PlayerCar.
    VehiclePhysics.
    RacingAI.
    TrafficManager.
    RoadSystem.
    CityEnvironment.
    CollisionSystem.
    CameraController.
    RaceManager.
    CheckpointSystem.
    AudioManager.
    HUDManager.
    InputManager.
    Use a consistent coordinate system and fixed or delta-time-aware physics updates.
    Do not put the entire game in one enormous source file.
    12. PERFORMANCE
    The game must run smoothly in modern desktop browsers.
    Requirements:
    Reuse geometries and materials.
    Use instancing for repeated buildings and scenery.
    Optimize shadows.
    Use object pooling for traffic and effects.
    Avoid unnecessary allocations in the game loop.
    Dispose of unused resources.
    Support responsive screen sizes.
    Provide a quality setting if necessary.
    13. DEVELOPMENT PRIORITIES
    Build the game in this exact order:
    PHASE 1:
    Working Three.js scene.
    One controllable sports car.
    Proper road.
    Third-person camera.
    Functional steering, acceleration, and braking.
    PHASE 2:
    Complete connected racing circuit.
    Bridges.
    River.
    City environment.
    Road boundaries and collisions.
    PHASE 3:
    AI opponents.
    Racing route following.
    Overtaking.
    AI collision avoidance.
    PHASE 4:
    Civilian traffic.
    Traffic collision system.
    Nitro.
    Vehicle effects.
    PHASE 5:
    Race countdown.
    Checkpoints.
    Laps.
    Position ranking.
    Finish line.
    Results screen.
    PHASE 6:
    Complete HUD.
    Main menu.
    Car selection.
    Sound effects.
    Visual polish.
    Mobile controls.
    14. IMPORTANT DEVELOPMENT RULES
    Do not build a static visual demo.
    Do not fake gameplay using animations alone.
    Every vehicle must have functional movement.
    AI opponents must genuinely follow the road.
    Traffic must move independently.
    The road must form a connected racing route.
    Avoid placeholder buttons that do nothing.
    Do not leave major gameplay systems unfinished.
    Do not remove working features when adding new ones.
    Test each phase before proceeding.
    Fix errors before adding more features.
    Do not copy proprietary game code, maps, vehicle models, textures, logos, or distinctive designs from other racing games.
    Create original game assets and visual identity.
    15. FINAL OBJECTIVE
    Deliver a complete, playable, visually polished 3D street racing game.
    The player should be able to:
    Open the game.
    Enter the main menu.
    Select a car.
    Start a race.
    Compete against AI opponents.
    Avoid moving civilian traffic.
    Drive across bridges, riverside highways, tunnels, and futuristic city roads.
    Use nitro.
    Complete all laps.
    Win or lose.
    Restart and play again.
    FIRST ACTION: Inspect the existing project and identify its current architecture. Preserve useful working code, remove obsolete motorcycle-specific gameplay, and begin with PHASE 1. Do not attempt to build every feature simultaneously.
  2. Step 2

    Implement dynamic weather conditions in the GameManager, such as light rain or neon fog, that affect road friction and visual atmosphere.
  3. Step 3

    Implement a screen-space motion blur effect when the player activates the nitro boost to enhance the sense of high-speed intensity
  4. Step 4

    Add simple billboard animations of spectators or moving city lights in the distant background to make the city feel more alive during the race.
  5. Step 5

    Implement a subtle camera shake effect that triggers specifically when the 'drifting' telemetry flag is true to increase the sense of speed.

Comments (2)

  1. cassy · · 1 like

    This is cool anita, I enjoy playing it. All the characters in the game look great, and the game runs smoothly.

  2. Anselm wrenna ·

    the game is amazing anita, the sounds and colors are amazing, well done<div><br></div>

6 likes · 2 comments · 7 views

Explore more on Prompted

Loading