Transport Fever 3 Line Manager: Edit Stops Without Losing the Route

Find the right line before editing it

Open Line Manager from the toolbar. Narrow the top list by bus/truck, tram, train, ship or aircraft mode, or use the viewport filter for lines visible on screen. Search is combined with any active filters; if an expected line disappears, clear the filters before assuming it was deleted. Select its row to show that line's vehicles and ordered stops below. Tick just that line to isolate it in the world view.

If the top list shows a problem icon, select the line and look for red exclamation marks beside affected segments in the stop list. Hover the marker for the connection message. Check that segment and terminal reachability before rebuilding the whole route; changing tracks or signals can also create a warning.

Once you have found the correct service, give it a name that says where it goes and why. ‘Passenger / North–Centre / Local’ and ‘Cargo / North–Port / Transfer’ are our examples, not built-in presets. A consistent order makes similar lines easier to compare, but renaming alone does not change how vehicles move.

Check the entire stop sequence after an edit

The official manual describes the line as an ordered list that returns from the last entry to the first. That closing leg is easy to overlook. For the intended journey A → B → C → B → A, write the repeating sequence as A, B, C, B. A, B, C instead describes a different return leg. These letters are a planning example, not a suggested map.

The July 30 interface blog describes dragging stops into a new order and editing them in the world. After either change, read around the changed position, including the wrap back to the first stop. Use the table above as an edit checklist. It is quicker to catch a missing return visit here than to infer it from a vehicle several stops later.

Keep a small change record you can actually use

Before changing a busy line, take a screenshot of its stop order and write one sentence about the problem: ‘The return journey skips B’, for example. After the edit, record the new order and the observation that would count as success. Here that means seeing a vehicle serve B on the return leg, not merely seeing it leave C.

For a bigger experiment, keep a save copy and change one feature at a time. If a new station, different vehicle and revised route all arrive together, a better result will not tell you which change helped. The record need not become a spreadsheet. The original screenshot, one question and one observed result are enough to make the next edit more deliberate.

When the route looks right but vehicles still bunch

Separate routing from spacing. The official July 9 developer reply describes automatic spacing as approximate: loading and interference can change the gaps. A neat stop list does not mean equal arrival intervals.

Watch where a pair starts travelling together. If they begin close together, investigate their initial placement. If the gap closes repeatedly at one stop, watch what happens there before sending another vehicle. If arrivals are reasonably separated but loads are uneven, record the load as a separate observation rather than assuming it proves bunching. These are ways to locate the problem, not a promise that a single distribution setting fixes every line. Compare several journeys over the same stretch before keeping the adjustment.