30 SECONDS | 16:9 | PHOTOREALISTIC AAA OPEN-WORLD GAMEPLAY CAPTURE | REAL PLAYER-CONTROLLED GAMEPLAY

Prompt

30 SECONDS | 16:9 | PHOTOREALISTIC AAA OPEN-WORLD GAMEPLAY CAPTURE | REAL PLAYER-CONTROLLED GAMEPLAY | MULTISHOT CONTINUOUS PLAY SESSION FICTIONAL GAME CONCEPT — Original next-generation Indian open-world crime game. This must look like authentic footage recorded while someone is actually playing a finished console game. It is NOT a trailer, NOT a cinematic sequence, NOT a pre-rendered cutscene, NOT an advertising film and NOT a collection of posed shots. The visual language should feel like a real gameplay recording: ordinary moments, imperfect player input, believable game physics, contextual animations, systemic NPC behaviour, restrained HUD, natural camera following and small unpredictable events occurring independently of the player. No GTA logos, Rockstar assets, copied characters, copied vehicles, copied interface graphics or copyrighted UI. The inspiration is the FEEL and systemic quality of a modern premium open-world crime game, not a reproduction of GTA. CORE GAMEPLAY FEEL The protagonist is continuously player-controlled. The third-person camera is attached to the player/gameplay camera system rather than operated by a cinematic director. Camera distance remains consistent with a normal console third-person open-world game. Slight horizontal player-controlled adjustments are visible. Camera rotation is not perfectly smooth. Small corrections, brief obstruction, imperfect framing and natural camera lag are allowed. The player does not move like an actor performing choreography. Walking, jogging, sprinting, turning, stopping, entering vehicles, exiting vehicles, climbing and mounting motorcycles use contextual game animations selected automatically by the game. Animation transitions have tiny imperfections and momentum. The player can hesitate, change direction, overshoot slightly or adjust movement. The world does NOT wait for the player. Traffic continues moving. Pedestrians continue their routines. Shopkeepers continue working. Vehicles occasionally change lanes. People cross roads at different times. Rain continues independently. Distant sirens occur independently. Background events do not synchronize themselves around the protagonist. The result should feel SYSTEMIC rather than scripted.PLAYER CHARACTER Indian male protagonist, late 20s. Short dark hair, trimmed beard, faded black overshirt, dark jeans, white sneakers. Consistent face, body proportions, hairstyle and clothing throughout the entire recording. Natural third-person character rendering with realistic skin, cloth simulation, wet clothing and physically plausible movement. COMPANION Indian male, late 20s. Short dark hair, light stubble, olive-green overshirt and dark trousers. Companion uses believable AI navigation. He does NOT remain perfectly glued to the player. He may fall several meters behind, choose a slightly different path, avoid pedestrians, wait briefly at an obstacle or catch up naturally. WORLD Dense fictional Indian metropolitan city combining Mumbai-scale density with North Indian street architecture. Monsoon evening. Wet asphalt. Flooded gutters. Auto-rickshaws. Motorcycles. City buses. Taxis. Private cars. Roadside food stalls. Chai shops. Small pharmacies. Apartment blocks. Flyovers. Railway infrastructure. Construction barriers. Utility cables. Advertising boards. Pedestrians carrying umbrellas. Delivery riders. Street vendors. The city must feel continuously simulated rather than dressed specifically for the camera. No empty streets created simply to make the protagonist visible.INTERFACE CRITICAL DO NOT permanently display the entire HUD. The interface is STATE-BASED and CONTEXTUAL. During ordinary walking/free-roam: • Only a restrained minimap/navigation element may remain visible in the lower-left. • No permanent mission banner. • No permanent speedometer. • No permanent objective text. • No permanent interaction button. • No permanent wanted stars. • No unnecessary health/ammo meters. • Large areas of the screen remain completely free of interface. The minimap is compact, translucent and integrated into the gameplay presentation. It represents the nearby road network and immediate surroundings rather than looking like a generic circular radar pasted onto the screen. Player position is subtle. Navigation/mission route appears only when an active objective requires navigation. When the player enters a vehicle: • Vehicle-specific information may briefly appear. • Contextual interaction information fades after the action is completed. • Do NOT add a permanent racing-game speedometer. • Do NOT add a large vehicle dashboard overlay. When the player becomes wanted: • Wanted status appears in the appropriate upper HUD region. • Use a restrained six-slot wanted indicator inspired by modern open-world game readability. • It appears ONLY after police attention begins. • It does not remain visible during normal free roam. • During pursuit, additional recognition/search information may appear contextually. • Police search information is represented spatially through the minimap/search area rather than filling the screen with icons. When the player is being searched for: • The minimap can communicate a localized search area. • Police positions are NOT represented as a collection of glowing enemy dots. • Avoid videogame clutter. • The player should understand the situation primarily through the world itself: sirens, police vehicles, blocked roads and visible search behaviour. When interacting with an object: A tiny contextual interaction prompt appears briefly near the relevant object. Example: [button icon] ENTER or [button icon] TAKE or [button icon] TALK The prompt is small, understated and disappears immediately after the interaction. Never use giant floating labels. Never use giant “PRESS E” graphics. Never use arcade-style UI.━━━━ MISSION PRESENTATION━━━━ Mission information is understated. At the beginning of an objective, a small unobtrusive notification can briefly appear and then disappear. Example: LOSE THE TAIL No giant center-screen title. No cinematic typography animation. No giant mission-card transition. No floating objective text permanently occupying the image. After the objective is understood, the world itself communicates what happens next.00:00–02.5 FREE ROAM Player exits a cramped apartment building into a busy wet street. Third-person gameplay camera follows approximately 2.5–3 meters behind the character. Player briefly adjusts the camera to look toward traffic. A bus passes. Two pedestrians cross in front of the player. A motorcycle squeezes between vehicles. A vendor pulls a cart. None of these events acknowledge the camera. The player starts jogging toward a parked dark sedan. No mission banner. No cinematic establishing shot. Only restrained gameplay UI. 02.5–05 VEHICLE ENTRY Player approaches the sedan. Only when close enough, a tiny contextual interaction prompt appears beside the vehicle. [button] ENTER Player activates it. Prompt disappears. Character opens the door, enters naturally and starts the engine. Camera transitions automatically into the game’s normal third-person driving camera. No cinematic transition. No camera spin. No dramatic angle. 05–07.5 NORMAL DRIVING Player accelerates into traffic. No speedometer dominating the screen. Driving contains slight human imperfection. Player turns too late. Corrects steering. An auto-rickshaw moves unexpectedly into the lane. Player brakes. The sedan’s suspension reacts. The rickshaw continues forward. Its driver briefly honks. Traffic behind reacts naturally. No synchronized traffic choreography. The minimap remains subtle.07.5–10 MARKET ROAD Player turns into a dense market street. Camera follows steering input naturally. A pedestrian steps toward the road. Player slows. Another pedestrian continues walking without reacting. A vendor pulls his cart away from the sedan. A motorcycle passes close to the driver’s side. Rainwater sprays from tires. The environment remains active independently. No NPC looks directly into the camera. 10–12.5 COMPANION / OBJECTIVE Player stops near a chai stall. Companion exits the passenger seat. He walks around the vehicle instead of instantly teleporting beside the player. Player waits briefly. A small contextual mission notification appears: LOSE THE TAIL It fades away. Distant police sirens become audible. No giant objective marker. No dramatic UI animation. 12.5–15 POLICE ATTENTION A police vehicle becomes visible several streets behind. The player begins moving. Only now does the wanted interface appear. Minimal six-slot wanted indicator in the upper HUD region. The minimap changes subtly to communicate police search activity. No red-screen effect. No giant warning banner. No police icons covering the map. The police vehicle approaches through normal traffic. 15–17.5 TRAFFIC ESCAPE Player accelerates through a narrow lane. An auto-rickshaw brakes unexpectedly. Player swerves. The sedan clips a lightweight plastic barrier. The barrier moves physically. The vehicle suspension reacts. The player continues. Police follow using believable road navigation. Police do not spawn directly behind the vehicle. No impossible rubber-band acceleration. 17.5–20 FLOODED INTERSECTION Player reaches a flooded intersection. Vehicle slows because of water resistance. Tires push water outward. Reflections distort naturally. Water droplets appear briefly on the gameplay camera surface. Player decides to turn into a narrower side street. The vehicle struggles slightly through the water. No cinematic slow motion. No dramatic camera change. 20–22.5 ABANDON VEHICLE Player stops beside a crowded market. Vehicle shows visible damage accumulated from the chase. Player exits. The normal third-person foot camera resumes. Companion exits separately. Police arrive several seconds later and stop near the abandoned sedan. The police do not magically know exactly where the player went. Their behaviour suggests an active search. Wanted/search interface remains contextual. 22.5–25 FOOT ESCAPE Player sprints through a narrow pedestrian lane. Camera follows naturally. Pedestrians move aside inconsistently. One person steps away. Another barely reacts. Player reaches a low roadside barrier. Contextual vault animation triggers. Player vaults over it. Companion follows using pathfinding and arrives slightly later. No superhuman parkour. 25–27.5 MOTORCYCLE Player reaches a parked motorcycle. Only at usable distance: [button] RIDE Prompt appears briefly. Player mounts. Companion reaches the motorcycle and mounts the rear seat. Engine starts. Rear tire pushes water from the pavement. Camera transitions into the normal motorcycle gameplay camera. No cinematic motorcycle shot.27.5–30 OPEN-WORLD ESCAPE Player accelerates beneath a massive flyover. Dense nighttime traffic surrounds the motorcycle. Police sirens remain audible behind. The player turns through traffic. Police gradually lose visual contact. The wanted/search information begins reducing naturally as the pursuit state changes. Traffic lights continue cycling. Buses stop. Pedestrians continue walking. Shops remain open. Rain continues. The world does not freeze because the sequence is ending. END ON ORDINARY GAMEPLAY. No hero pose. No dramatic final camera push. No title card. No cinematic fade. The recording simply stops as if the player ended the capture. CAMERA RULES STRICT GAMEPLAY CAMERA. No drone. No helicopter. No crane. No dolly. No orbit. No cinematic tracking. No 360-degree character rotation. No impossible camera acceleration. No shallow-depth-of-field cinematography. No rack focus. No lens-flare effects. No anamorphic movie look. No deliberate composition for the viewer. Camera priority is PLAYER CONTROL and READABILITY. Minor camera collision. Natural camera obstruction. Small follow lag. Slight framing imperfections. The camera occasionally gets partially blocked by vehicles, pedestrians or environmental objects. This imperfection is intentional. NPC SYSTEM NPCs operate independently. Different walking speeds. Different clothing. Different destinations. Different reactions. Some use phones. Some carry bags. Some enter stores. Some wait for traffic. Some talk. Some ignore the player completely. Some react only when the player gets too close. Police officers search areas rather than behaving like scripted enemies. Traffic follows road lanes and reacts to braking, obstacles and congestion. NPC behaviour should appear GENERATED BY GAME SYSTEMS, not individually choreographed for the recording. PHYSICS Realistic vehicle weight. Suspension movement. Brake distance. Wet-road traction. Tire deformation. Water resistance. Object displacement. Character momentum. Motorcycle balance. Pedestrian avoidance. Vehicle damage accumulates. No snapping. No floating. No teleportation. No perfectly synchronized animation.VISUAL QUALITYPhotorealistic next-generation game-engine rendering. Physically based materials. Detailed Indian architecture. High-density traffic. Realistic skin. Wet clothing. Rain accumulation. Real-time reflections. Dynamic lighting. Volumetric atmosphere. Dense environmental geometry. Realistic vehicle interiors and exteriors. But the final image must retain the subtle imperfections of REAL GAMEPLAY CAPTURE. Do NOT make it look like a pre-rendered cinematic.AUDIOPurely diegetic gameplay sound. Engine RPM. Gear changes. Tire spray. Brake squeal. Horns. Auto-rickshaw engines. Bus engines. Rain. Footsteps. Pedestrian chatter. Market vendors. Police radio. Distant sirens. Motorcycle engine. Environmental city ambience. Distant train. Music, if present, is extremely subtle and gameplay-reactive. No trailer booms. No cinematic impacts. No dramatic sound-design stingers. CONTINUITYSame protagonist. Same companion. Same sedan. Same motorcycle. Same clothing. Same weather. Same city. Same traffic density. Vehicle damage persists. Character position persists. Wanted/search state persists. World geography remains consistent. Transitions happen because the PLAYER performs actions, not because the video needs the next shot. ANTI-SLOP DO NOT GENERATE: movie trailer cinematography cinematic montage hero shots perfectly framed gameplay permanent HUD giant mission text giant objective markers permanent speedometer permanent wanted stars arcade minimap floating labels giant “PRESS E” prompts glowing NPC outlines enemy markers everywhere synchronized NPC reactions police spawning beside player perfect traffic choreography teleporting companions instant vehicle entry instant vehicle exit weightless character movement perfect camera movement dramatic lens flares shallow cinematic depth of field slow motion fake film grain video-game advertisement look AI-generated concept-art appearance pre-rendered CGI CUTSCENE BEHAVIOR FINAL TARGET: It should look like someone captured an ordinary 30-second section of a real, commercially released next-generation open-world Indian crime game while PLAYING IT. The viewer should notice the GAME SYSTEMS before noticing the cinematography. The world should feel alive even when nothing important is happening. The interface should appear only when gameplay requires information. The player should feel like they are controlling the character rather than watching a character perform. AUTHENTIC GAMEPLAY > CINEMATIC BEAUTY. SYSTEMIC BEHAVIOR > SCRIPTED REACTIONS. PLAYER INPUT > CAMERA DIRECTION. CONTEXTUAL UI > CONSTANT HUD. WORLD SIMULATION > VISUAL SPECTACLE.

@Diplomeme

You may also like