Rail signaling

Signals placed on track divide it into blocks or guard reservable paths. A block signal admits a train only if the next block, meaning all track reachable up to the next signal, is empty. A path signal admits a train once it reserves a route through to the next signal, so trains on non-conflicting paths can share a block. Transport Tycoon (1994) had only bi-directional block signals, and Deluxe added one-way signals. OpenTTD adds pre-signals, where an entry signal opens only if an exit is green, plus path signals, and since version 12 shows only path signals by default. Factorio pairs rail signals with chain signals that mirror the state of the signals ahead. Inputs: signal placement, train positions and routes. Outputs: per-signal open or closed states, train waits, and network throughput.

Traffic engineering on rails. Players learn why trains stop, then redesign junctions, stations, and signal spacing until flow is smooth. Deadlocks, with trains frozen in a loop that blocks itself, are a vivid and instructive failure, and fixing one is a satisfying puzzle.

• available signal types: block, one-way, pre-signal, path, or chain
• default signal behavior and which types are exposed to new players
• train braking distance and the resulting minimum signal spacing
• whether trains reroute around blocked paths
• visual debugging aids such as block coloring and reservation display

• Rules learned mainly from community guides, such as Factorio's chain-in, rail-out convention, block new players.
• Deadlocks that occur long after a junction is built are hard to trace.
• Block signals that are too coarse cut throughput, and pre-signal logic can trigger on exits a train cannot reach.

• Junction design becomes a shared craft, and community blueprints of standard intersections spread.
• Throughput limits push players toward one-way double track and dedicated stations.
• Adding trains raises throughput until signal capacity binds, after which waits and gridlock grow quickly.

• Can an assistant explain a specific deadlock in plain language from the signal states, removing the wiki dependency?
• What minimal signal vocabulary still supports high-throughput designs?