Use the campaign as a teaching sequence

The opening campaign introduces core mechanics through objectives. Read the current task and its sub-objectives before building. Mission scripts may expect a particular connection, vehicle category, station or delivery result; a network that looks equivalent may not satisfy the exact condition.

A safe objective workflow

  1. Pause when a new task appears.
  2. Read every objective and optional condition.
  3. Inspect highlighted locations and existing assets.
  4. Build only what the objective currently requires.
  5. Run the service until the task visibly updates.
  6. Save before the next major construction step.

Avoid common mission mistakes

Do not demolish provided infrastructure until you know it is replaceable. Do not assume a later objective will accept an improvised route created early. Keep mission-related lines clearly named so you can distinguish them from optional services.

When progress does not update, verify the literal requirement: cargo type, source, destination, vehicle, quantity or station. Observe whether delivery reaches the final consumer rather than merely a nearby terminal.

Economy and optional building

Treat optional routes carefully. A campaign map can tempt you to build a full free-game network, but mission budgets and scripted progression may reward restraint. Complete the required service first, then decide whether optional expansion supports future objectives or only adds cost.

When a task appears stuck

  • Confirm every required object still exists.
  • Check that the intended line uses the highlighted stop or terminal.
  • Watch one complete delivery cycle.
  • Remove incompatible mods and retry from a clean save if behavior is abnormal.
  • Reload a save from before the objective if essential infrastructure was removed.

This page intentionally avoids claiming mission-specific steps that have not been verified. Detailed walkthroughs should be published only after each objective and trigger has been tested.