Circuit-Established Landing Pad Requests Not Truly Fulfilled
Posted: Sat Sep 27, 2025 9:30 pm
Hello all,
After being alerted to this by a user in a mutual Discord, I have run into what I believe is a bug when it comes to setting Cargo Landing Pad (CLP) requests using Circuit Logic.
1. What did you do?
The goal of said circuitry is to have X quantity of specific items in a planet's Logistics Network, and request quantities from Space Platforms to settle any shortages. To this end, a Comcast Combinator (containing the items I want and the max quantities I want on hand) is connected via red wire to an Arithmetic Combinator, whose green wire input is tied to a Roboport with "Read logistic network contents." The logic on the Arithmetic was set to "EACH Red MINUS EACH Green" (what I want, minus what I have, equals what I still need), and then the output connects directly to the CLP, which has "Set Requests" as its active Circuit Mode. I then added a Logistics Request on the Constant for Bioflux x1000 and added 552 Bioflux to the CLP by hand. There is a ship in orbit that has more than 600 Biofux in its capacity.
2. What happened?
There is a request controlled by the Circuit Network for 448 Bioflux, but hovering over the request with my mouse shows the request is being satisfied with the 552 Bioflux that is within the CLP. No Bioflux is coming in from the orbiting platform until the amount in the CLP is less than the amount being requested by the circuit network.
3. What did you expect to happen instead? It might be obvious to you, but do it anyway!
Expectation was for 500 Bioflux (five stacks) to come down from the orbiting ship, bringing the on hand Bioflux total over 1000 and satisfying the request by turning the value of BioFlux on the inbound red wire to a negative number, as a negative value cannot be requested. I was also expecting the behavior of requests controlled by the circuit network to only factor in the circuit network (and no other source) to bring material down, and not check the request against the amount of the item in the CLP -- that behavior should be meant for requests manually established in the CLP interface.
4. Does it happen always, once, or sometimes?
Always, though I am confident that this behavior began only recently, and that it operated as I had believed it should have in the past (see #3).
Screenshots and Log File: Thank you.
After being alerted to this by a user in a mutual Discord, I have run into what I believe is a bug when it comes to setting Cargo Landing Pad (CLP) requests using Circuit Logic.
1. What did you do?
The goal of said circuitry is to have X quantity of specific items in a planet's Logistics Network, and request quantities from Space Platforms to settle any shortages. To this end, a Comcast Combinator (containing the items I want and the max quantities I want on hand) is connected via red wire to an Arithmetic Combinator, whose green wire input is tied to a Roboport with "Read logistic network contents." The logic on the Arithmetic was set to "EACH Red MINUS EACH Green" (what I want, minus what I have, equals what I still need), and then the output connects directly to the CLP, which has "Set Requests" as its active Circuit Mode. I then added a Logistics Request on the Constant for Bioflux x1000 and added 552 Bioflux to the CLP by hand. There is a ship in orbit that has more than 600 Biofux in its capacity.
2. What happened?
There is a request controlled by the Circuit Network for 448 Bioflux, but hovering over the request with my mouse shows the request is being satisfied with the 552 Bioflux that is within the CLP. No Bioflux is coming in from the orbiting platform until the amount in the CLP is less than the amount being requested by the circuit network.
3. What did you expect to happen instead? It might be obvious to you, but do it anyway!
Expectation was for 500 Bioflux (five stacks) to come down from the orbiting ship, bringing the on hand Bioflux total over 1000 and satisfying the request by turning the value of BioFlux on the inbound red wire to a negative number, as a negative value cannot be requested. I was also expecting the behavior of requests controlled by the circuit network to only factor in the circuit network (and no other source) to bring material down, and not check the request against the amount of the item in the CLP -- that behavior should be meant for requests manually established in the CLP interface.
4. Does it happen always, once, or sometimes?
Always, though I am confident that this behavior began only recently, and that it operated as I had believed it should have in the past (see #3).
Screenshots and Log File: Thank you.