CITY INTEL
01 / VERIFIED VISUAL LAYERDense streets, vertical routes, transit links and high-frequency incidents make this the city-navigation benchmark.
What is the mission’s success condition before choosing a route?
Exposure, interruption and a blocked exit.
Keep a second route layer available before committing.
Official briefings and the TGS demonstration describe small social verbs, spontaneous incidents and profession-specific actions. Together they form the day-to-day layer beneath the main story.
Pet cats and trigger small everyday events while moving through public spaces.
OFFICIAL BRIEFINGGang clashes and spontaneous trouble turn ordinary routes into response decisions.
OFFICIAL BRIEFINGOfficial material explicitly mentions snooping on passersby phones as part of city interaction.
OFFICIAL BRIEFINGAttention, posts and internet popularity are framed as mission progress—not a decorative feed.
OFFICIAL BRIEFINGTGS hands-on footage showed database scans, weapon frisks, citations and handcuff interactions.
TGS PLAYTEST OBSERVATIONDevelopers say switched-out characters continue their own routines, letting you resume where their life moved next.
OFFICIAL BRIEFINGDirect answers, with the evidence level stated rather than implied.
It is the benchmark area for city navigation: dense streets, vertical routes, transit links and frequent incidents mean almost every movement decision you will make elsewhere shows up here first.
Neither wins by default here — this is the one district where traffic density genuinely competes with vertical routing. Decide by whether your objective needs a precise street-level stop; if it does, the rooftop line costs you the landing.
Official material presents it as a high-frequency incident area, though no spawn rate has been published. Practically that means routes through it should always carry a fallback, because interruption is the normal case rather than the exception.