Yes I already have an interrupts named with all the planets and their targets are those planets. The new interrupt created can have a different target, if you try my blueprint but use Gleba you'll see the name no longer matches the destination.
I'd be fine with the parameters not changing the ...
Search found 4 matches
- Sun Aug 09, 2026 5:34 am
- Forum: Not a bug
- Topic: [2.1.14] Parameterised space platform blueprints don't change interrupt targets and create duplicate interrupt names
- Replies: 3
- Views: 1108
- Sat Aug 08, 2026 8:47 am
- Forum: Not a bug
- Topic: [2.1.14] Parameterised space platform blueprints don't change interrupt targets and create duplicate interrupt names
- Replies: 3
- Views: 1108
[2.1.14] Parameterised space platform blueprints don't change interrupt targets and create duplicate interrupt names
What did you do?
I use interrupts on my space platform that are named -> [Planet], contain a circuit condition for that planet's signal, and have that planet as the target. When creating a blueprint for this space platform I then parameterised the planet signal so that I can change which planet ...
I use interrupts on my space platform that are named -> [Planet], contain a circuit condition for that planet's signal, and have that planet as the target. When creating a blueprint for this space platform I then parameterised the planet signal so that I can change which planet ...
- Thu Jul 09, 2026 1:43 pm
- Forum: Ideas and Suggestions
- Topic: Reusable wait condition chunks for Trains and Space Platforms
- Replies: 7
- Views: 774
Re: Reusable wait condition chunks for Trains and Space Platforms
Have you tried using groups and train interrupts? In my set up I'm able to have generic cargo trains that go to cargo pick up stations when they're enabled and from that inventory they're able to automatically go to that resource's cargo drop off station. That cargo train is part of a "cargo" group ...
- Mon Jul 06, 2026 7:50 am
- Forum: Ideas and Suggestions
- Topic: Space platform requests set by circuits should not default to "All"
- Replies: 8
- Views: 983
Re: Space platform requests set by circuits should not default to "All"
Couldn't agree more. The 2.1 changes are great but it makes space buffer stations very difficult to achieve.
For example if I want to keep a supply of uranium fuel cells at a space station over Gleba then the station will request all the cells I keep on Gleba before a resupply ship can make it ...
For example if I want to keep a supply of uranium fuel cells at a space station over Gleba then the station will request all the cells I keep on Gleba before a resupply ship can make it ...