I agree, it just seems more intuitive, the faster you go, the more damage you (should) take up to maximum damage.

It is a useful tool to be able to send messages from platform to silo without actually sending items. You could get around it by requesting unusual items that you were sure not to have in inventory but being able to use non-items is cleaner.

I decompressed it over 2.0.77. It failed to start: "Failed to load mods: __quality__/prototypes/recycling.lua:48: attempt to perform arithmetic on field 'default_icon_size' (a nil value)".

I'm on Linux. I think it's a leftover file causing trouble or something.


You can’t do that. You need to ...

Did you uninstall the old version? apparently this is required...

Again apologies for my imprecise language.
We are agreed that once a train is en route, there is no need to distinguish between destination full or no path.
If the train is not en route, it is at a station, and for an interrupt to trigger it is trying to leave the station. At that point there are ...

Assuming we achieve a separate "Destination full while at station" condition, what is your proposed use for separate "Destination full while en route" and "No path while en route" conditions? I don't have a clear picture of why these should trigger different behaviors.


Sorry if I wasn't clear ...

"Station or path unavailable while en route": all no-path events and any destination-full events that occur while underway.

"Scheduled destination full": all destination full events that would otherwise result in a train sleeping at a station. Sleeping at a station is a special case, because ...

I do agree that Destination Full is not the same as No Path, and it would be useful to be able to treat them differently.

Oh yes I have wanted this for a while! viewtopic.php?p=625399

+1

While we are dreaming of things we would like to see... train groups are wonderful, you can set up in one place how you want a whole group of trains to behave. And with interrupts, you can set up interrupt conditions... and choose which interrupts you want for specific train groups.
So how about ...

Delightful! Excuse me while I go add a Load Bearing Coconut to my train system

TL;DR
When you insert a manual temporary stop in a train schedule, any interrupt that would trigger on leaving the current stop should trigger.


What?
When a train in automatic leaves a stop, it checks for any interrupts and applies them. The same should happen when the player forces the train ...

Would be great if this was an option when placing a blueprint of a train. First train works great, print down second following train and instead of two distinct trains I get one messed up joined train.

TL;DR
Train stops currently show trains that have that stop in their schedule. They should do the same, possibly in a separate tab, for trains that access that stop via an interrupt.


What?
When an interrupt triggers, it will insert a temporary stop for the target of the interrupt. If you ...

I'm doing a Nullius run right now and I agree it would be nice to have something like this for trains. We can read all the contents of buildings including these kind of by products, why not trains?
As a work around maybe you could use inactivity?

I put the actual signals on green, and the constants from the constant combinator on the red wire. Then I check the value on the green wire, is it what I want or not, and AND it with EACH on the red wire to select which signal to output as EACH. Note the constant values have to be distinct because ...

Sounds like a neat idea. I suspect it might be a hit to UPS - thinking of a common steel chest, 48 slots, potentially 48 different items of different qualities, so the chest has to be scanned every swing to determine which is the highest or lowest quality item. And how would you handle choosing the ...

Tertius wrote: Sat Mar 28, 2026 11:39 am I intend to publish a book titled "Steam Achievement Tea‑Leaf Reading" later this year.

Ooh I have some tea-leaves you can use
Also, I would buy this book!

Yep we have been asking for this for a long time!
viewtopic.php?t=85453