Your first hour in Nova City
This is not a placeholder checklist. It is a first-session route for launch day: what to test first, what to ignore, how to avoid fake tier-list conclusions, and how to turn one hour of play into reusable notes.
Build a reliable mental map of controls, movement layers, combat response and city activities before judging strength, builds or farming routes.
Do not publish tier claims, do not chase every map icon, do not call a route “best” before testing setup time and failure recovery.
Priority table
Settings, camera, subtitle and performance stability
Do firstMovement layer comparison: street, transit, rooftop
Do firstOne repeatable combat loop and failure labels
Do after baselineOne city role plus one fallback activity
Do after baselineTier list, damage math, final build claims
Avoid in hour one60-minute route
Set the baseline before chasing icons
- Open settings first: camera sensitivity, subtitle language, input device, HDR/brightness and performance mode. If movement feels wrong, every later combat and traversal judgment becomes noisy.
- Mark the current account state: unlocked agents, available vehicles, phone functions, map layers and tutorial restrictions. This becomes the comparison point for later changes.
- Do not start evaluating tier, build or “best route” yet. During the first ten minutes the only goal is to make the controls and UI readable.
Learn movement as three layers
- Street layer: test walking, sprinting, traffic behavior, cornering, road interruptions and whether missions punish route exposure. This layer matters when you need exact stops.
- Transit layer: compare taxi, bus, subway or vehicle pickup cost. The fastest-looking option is not always best if the setup time is long or the exit point is poor.
- Vertical layer: test swing, climb, rooftop approach and landing safety. Record where vertical movement actually saves time and where it only looks stylish.
Run one combat loop, not ten random fights
- Use the first low-risk fight to identify the basic loop: read enemy weapon, dodge or block with intention, confirm the opening, disarm or convert nearby props, then reset distance.
- Change only one variable per fight. If you switch agent, route, enemy type and weapon all at once, you cannot know what actually improved the result.
- Write down failure reason using plain labels: late dodge, bad camera, unsafe disarm, no exit, overcommit, wrong target. This is more useful than saying “combat feels bad”.
Choose one city role and one fallback
- Police-style content should be evaluated by information flow: scan, question, search, cite, restrain and resolve. Do not judge it only by combat reward.
- Courier or vehicle content should be evaluated by route pressure: pickup time, traffic, failure penalty, exit line and whether vertical movement can replace driving.
- Social-media or NPC incidents should be evaluated by trigger clarity. If you cannot tell why an event started, mark it as observation, not a farm route.
Stop and build tomorrow’s checklist
- Keep three findings: one route that saved time, one combat habit that caused damage, and one city activity worth repeating. Delete everything that is only hype.
- Update your next test with a clear question: “Does rooftop movement beat taxi here?” or “Does this agent reduce failure rate?” Specific questions produce reusable guides.
- If a system is still locked, do not fill the gap with guesswork. Mark it as LOCKED / WATCH and return after the relevant tutorial or patch note appears.
What to write down
Fastest proven route: origin, destination, method, setup time, failure point.
Combat failure reason: late dodge, bad camera, unsafe disarm, no exit, wrong target.
City activity value: trigger clarity, reward clarity, repeatability and whether it unlocks another system.
Unknowns: anything still locked, unconfirmed or based only on trailer footage. Mark as WATCH instead of filling with guesses.
Pre-launch warning: ANANTA has public trailers, official site material and hands-on reports, but final launch balance, reward cadence and full progression rules can still change. Treat this as a launch-day testing route, not a final meta guide.