Once your first line is running, you can fine-tune how it behaves: when trains leave a stop, when they are called to a station, which stops they skip, and when they refuel. These rules work on any line, from a simple two-stop shuttle to a large rail network. Train networks have their own equivalents and handle most of this automatically.

By default a train leaves a stop the moment its station finishes loading or unloading it, even if the train is not yet full or empty. <b>Depart conditions</b> hold the train there until a rule is met instead. Select a stop, press <b>{0}</b> (1), and pick a condition such as:

<b>{0}</b>: wait until the train is fully loaded with all supplied products. Set this on a loading stop so trains always depart full.

<b>{0}</b>: wait until the train is completely unloaded of all compatible products. Set this on an unloading stop so all cargo is dropped off.

<b>{0}</b>: wait a fixed amount of time, for example to let stock build up between trains.

When a stop has several conditions, choose how each one joins the next with <b>AND</b> or <b>OR</b>. Consecutive <b>AND</b> conditions form a group that must all be met together, and the train departs as soon as any group is satisfied (AND is applied before OR).

Controlling when trains depart

A station's <b>{0}</b> tab decides when a train is called to it. Each cargo product has its own rules, which can be combined:

<b>Arrival sliders</b> (1): each product has a slider that requests a train only once its stock passes a threshold. By default the slider sits past the <b>∞</b> mark, so trains are always allowed. Drag it back and an unloading station calls a train only when its stock is at or below the value, while a loading station calls one only when stock is at or above it. Cargo already in transit is counted, so trains are never over-dispatched.

<b>{0}</b> (2): the maximum number of trains heading to the station at once. Keep it low at small stations to avoid pile-ups, and raise it where you need more throughput.