Network lab · FIELDNOTE 04

A clearer way to manage your lines

An editorial workflow for organizing a network before it becomes difficult to read.

OFFICIAL INFORMATION · PRE-RELEASE

The redesigned Line Manager supports editing in the world, automatic naming patterns, vehicle distribution options and dragging stops to reorder them.

Official source: Urban Games · Episode 5: Highlights ↗Published July 30, 2026. Summary of the cited announcement; release details may change.

Give each line a readable purpose

Our suggested naming convention is purpose, corridor, then variant: “Passenger / North–Central / Local”, for example. This is an editorial convention, not an official preset. A readable name should tell you what a line is meant to do before you inspect individual vehicles. Use the same order of information throughout your network.

Editorial perspective

Treat a line as a small set of promises: where it goes, what it carries and which connections it serves. Keep an external note of the reason for an unusual stop or detour. When a route later behaves unexpectedly, that note can help distinguish an intentional design choice from an accidental edit.

A change log worth keeping

Before a substantial route edit, record the current stops and the symptom you are investigating. After the edit, observe the same part of the network under comparable conditions. Avoid calling an improvement a success after a single arrival. A proper post-launch guide should also document how assigned vehicles react to reordered stops; we have not verified that behavior in a playable build.

A note on evidence

This is a source-based pre-release explainer. Editorial suggestions are proposed ways to investigate the game, not verified gameplay results.

Read our editorial policy →