Last time: the train that fixes things. This time: the things it fixes.
https://store.steampowered.com/app/4540370/Rail_Route__Expect_Delays/
Hey dispatchers,
Trouble comes to your railway in two ways. Some of it you bring on yourself. Leave a corridor without maintenance long enough and it starts to fail. The rest just happens, even on a network you keep in good shape. Expect Delays has both. None of it ends your run. Every incident has a way out, and you stay in the chair and sort it.
Here is what can show up on your board.
Rail elements wear out
Leave a switch or a signal too long without care and it starts to malfunction. Every throw or passage costs about 15 seconds after that, and a smooth junction turns into a queue. Track does the same and drops to a slow order. Nothing here blocks the line. Trains keep moving, just slower. Stay on top of the maintenance, or send the service loco over to fix it in one pass.
Trains break down
A train stops dead on a live track. The segment is blocked and the queue behind it grows. You can wait it out, route the traffic around, or send the service loco to couple up and tow it clear, same as last post. Most breakdowns come from worn-out stock, so looking after your trains pays off. Once in a while a perfectly healthy train fails anyway. Nobody is fully safe.
Delays creep in
This one has two shapes. A train from the border shows up a few minutes late and your timetable drifts. Or a train already running on your network gets held for a bit, at a platform or out on the line. On a tight schedule even a short slip spreads fast. And when the delay is not your fault, we do not put it on your score.
Trains stop arriving on the dot
One smaller thing runs underneath all of this. Border trains used to land exactly on the whole minute, every time, which felt robotic. Now each one drifts by a few seconds either way, so arrivals scatter the way real ones do. This part is just for looks. It is not a delay, it does not touch your score, and your planned timetable stays exactly as written. Set it to Off, Subtle, or Normal to taste.
Weather rolls in
A storm settles over part of the map. The mild kind just slows things down. Half speed on every track under the cloud, marked in icy blue, and it lifts on its own with nothing left behind. The bad kind does real damage. Condition drops across the whole sector and stays down until a service loco runs through it. A network you kept spotless suddenly needs a repair trip.
The power goes out
An electrical fault knocks out an area and takes the automation with it. The signal sensors in that zone stop routing trains for you, so the junction is yours to run by hand until the power is back. Route it manually, or send the loco through. It comes back on a timer, or sooner if the loco pays a visit.
You decide how rough it gets
None of this is forced on you. Turn each kind on or off when you start a game, and set Disruption Frequency anywhere from Off to Relentless. There are quiet stretches between events, so they do not all land at once. Want an easy run? Leave it on Rare. Want a real test? Push it all the way up.
Next time
Where the service loco lives, and why the spot you choose for it decides everything. Your new office: the maintenance depot and mainly - its automation! Stay tuned.
Built from your ideas. A few of the threads behind this one:
- Random Failures: tested by the situation, then rewarded for handling it
- Disruption events: more going on than a steady timetable
- Signal failures to manage as a challenge
Thanks to everyone who keeps posting. We read all of it.
The Bitrich team
https://store.steampowered.com/app/4540370/Rail_Route__Expect_Delays/