Page 1 of 1
"Stop exists" interrupt condition
Posted: Sat Nov 01, 2025 12:04 pm
by djrvywfbjr
TL;DR
Interrupt condition to check whether a given train stop exists.
What?
Same as the "stop is full/not full" conditions we already have, except check for whether it exists instead.
Why?
It's not uncommon that I find myself building a provider station for some item before the item is needed elsewhere. When using generic interrupts, this means I have to turn the station off until there's a corresponding requester station that the interrupt would send the train to, or a train will come in, load up, and then no-path at me. I understand why this design decision was made, but there needs to be some deliberate action I can take to turn it off (such as adding a "stop exists" condition). Using a "stop is not full" condition instead breaks priority as interrupt firing is not ordered by stop priority, so it's not a good solution.
Re: "Stop exists" interrupt condition
Posted: Sun Nov 02, 2025 1:02 pm
by Epb7304
+1 more flexibility is always good
Can you think of a way to disable your provider stations until a requester station exists? or perhaps even until a requester station can actually use the train? (Circuit network)
Re: "Stop exists" interrupt condition
Posted: Sun Nov 02, 2025 3:52 pm
by eugenekay
Epb7304 wrote: Sun Nov 02, 2025 1:02 pmCan you think of a way to disable your provider stations until a requester station exists? or perhaps even until a requester station can actually use the train? (Circuit network)
Wire the Requester stations to a global Circuit network (or Radar) to send a "Demand signal" when they are actually low on resources (and exist). Only enable the Provider stations when there is a Demand for the items that they produce.
Re: "Stop exists" interrupt condition
Posted: Mon Nov 03, 2025 7:17 am
by Shadowhawk
Why not have the requester stations trigger the train, in that case the train can do other things if your defences are all wel enough supplied.