Stop building loops. The tutorial rewards symmetrical track layouts because they look tidy, but Iron Roads scores you on throughput per tile, not aesthetics. Your first hour should be spent learning which constraints are real (geography, token scarcity) and which are decorative. Most new players burn their starting cash on extra trains before they've proven a route actually bottlenecks. Buy one train, watch it for two full trips, then decide.
The Anti-Tutorial: What the Game Under-Explains
The tutorial teaches you to lay track, buy trains, and connect stations. It does not teach you that track order determines priority at junctions, and this single system destroys more networks than any other mechanic.
Here's how it actually works. When two trains approach a crossing, the game resolves conflicts based on which track segment was placed first. Earlier track has priority. The tutorial mentions this in passing, but doesn't show you that deleting and replacing a track segment resets its priority. This means you can "promote" a main line by rebuilding it after your spurs, forcing branch trains to yield without signals, gates, or complex interlockings.
Most players discover this after building elaborate bypasses that never trigger. The bypass trains sit idle while main-line traffic jams because the bypass track was laid first. Reverse your build order. Lay spurs and sidings before your trunk lines. The game gives you no visual indicator for this, so you must track it mentally or use the demolition tool as a priority editor.
The second under-explained system: resource tokens are not currency. They are scoring multipliers and unlock conditions. You earn tokens by completing town requests, but spending them on new regions or train types reduces your final score. The game presents tokens as "money you also need to hoard," which creates paralysis. The actual math: tokens spent on map expansion are gone from your final tally, but tokens spent on trains that complete more requests can pay for themselves. The break-even point depends on route length and cargo type, which the tutorial never surfaces.
Third hidden variable: passenger anger decays, but cargo deadlines do not. A passenger waiting five minutes is annoyed. A factory shipment waiting five minutes is failed. New players prioritize passenger routes because the angry-face feedback is visceral. Cargo routes fail silently until you notice the token income flatlined. Build your first cargo line before your second passenger loop. The board-game scoring rewards completed contracts over happy commuters.
Early Mistakes That Kill Runs
Buying trains before proving the track. A train costs tokens upfront plus ongoing maintenance in the form of track congestion. One train on a well-ordered route outperforms three trains on a messy one. The mistake feels productive—more trains equals more movement—but Iron Roads punishes queueing harshly. A single junction conflict can back up five trains for in-game hours. Start with one train per route. Add a second only when you can point to a specific idle period in the schedule.
Overbuilding for future expansion. Track is cheap to lay but expensive to delete; you lose the placement priority information and must rebuild carefully. Players lay double-track "just in case" through narrow terrain, then find they've consumed the only tiles that could have held a factory connection. The geographically-induced space constraints are real and brutal. Build what you need for the current contract plus one tile of flexibility. No more.
Ignoring the "refine your network" loop. The store description mentions this explicitly: you earn tokens by refining, not just expanding. This means deleting, rebuilding, and re-sequencing track to improve throughput. Most players treat this as endgame optimization. Do it after every second contract completion. The token bonus for efficiency improvements scales with network size, so early refinement habits compound.
Chasing passenger happiness over contract completion. Happy passengers generate a small token bonus. Completed contracts generate tokens, unlock new industries, and advance the map. A town with angry passengers but fulfilled cargo will still progress. The reverse stalls. Set route schedules to cargo deadlines first, passenger flow second.
The Three Decisions That Shape Your Run
Decision 1: First expansion direction. The map presents multiple towns. One has a passenger-only station. One has a factory with a cargo contract ready. One is distant but connects to a resource node. Choose the factory town. The initial cargo contract is designed to be completable with starter track and one train. Completing it unlocks the second train type and generates enough tokens that your next expansion is funded, not scraping.
Decision 2: When to buy your second region. The game gates regions behind token thresholds. The temptation is to hoard until you can buy the next region outright, then expand explosively. This is usually wrong. Regions increase contract variety but also geographic complexity. Buy the second region only when your first region has three active contracts with no idle trains. This proves your network can absorb more nodes without choking. Buying earlier spreads you thin; buying later wastes potential token income from unactivated contracts.
Decision 3: First train type specialization. The game offers a faster passenger train and a slower cargo train with higher capacity. The passenger train looks appealing because speed reduces anger. But the cargo train's capacity means fewer trips per contract, which means less track wear and fewer junction conflicts. If your first region has mixed contracts, buy the cargo train. You can schedule it for passenger routes in off-peak hours. The passenger train cannot efficiently haul cargo. Asymmetric flexibility beats symmetric specialization early.
What to Do Differently
Build ugly on purpose. Symmetrical networks feel good to look at but hide inefficiency. Start every session by laying one terrible-looking spur that cuts a corner, then use track priority to make it work. If you can't explain why a specific train is yielding at a junction, stop expanding and fix it. The rest of the run is just applying that discipline at larger scale.
