Space platform requests set by circuits should not default to "All"
Posted: Mon Jul 06, 2026 7:15 am
When setting a space platform's requests via circuits, the request source will be both platforms and planets, with no way to set them otherwise. This is incredibly limiting. There should be a way to limit circuit based requests to either platforms or planets, or either.
One concrete example for why this is necessary is that if it were possible to configure circuit based requests to only be fulfilled by other platforms, it would become possible to send an item from a freighter to an orbital station, then send that item from the orbital station to a different platform, by controlling the orbital station's requests via latches. This would enable hub-and-spoke logistics, which would be useful both for intra-system shipping of items like green belts and for promethium logistics at the solar system edge.
I feel like there are many forms this could take in terms of UX, whether a radio button selector for planet/platform/all, or a Set Request Source checkbox which allows passing signals for the planets or for platforms into the hub, or some other method.
One concrete example for why this is necessary is that if it were possible to configure circuit based requests to only be fulfilled by other platforms, it would become possible to send an item from a freighter to an orbital station, then send that item from the orbital station to a different platform, by controlling the orbital station's requests via latches. This would enable hub-and-spoke logistics, which would be useful both for intra-system shipping of items like green belts and for promethium logistics at the solar system edge.
I feel like there are many forms this could take in terms of UX, whether a radio button selector for planet/platform/all, or a Set Request Source checkbox which allows passing signals for the planets or for platforms into the hub, or some other method.