Different logistic groups are merged for platform requests?
Posted: Sat Aug 01, 2026 10:10 am
Hello, i have a problem:
I have 1 static platform over nauvis. This platform requests calcite for it's own use, but only from "platforms", because another calcite-providing platform roams around and drops calcite to where needed. Nauvis ground base also requests calcite, but since i don't want the static platform to drop it's calcite to ground (should be supplied by the roamer instead), i added a logistic group with requesting 0 calcite from planet (which effectively prevents platform to drop calcite to ground). Now, for this static platform's 2 different calcite requests to exist at all (1 for requesting from roamer, 1 for preventing drop), they are in 2 different logistics groups. HOWEVER, when nauvis ground base has enough calcite and the static platform runs out, it requests calcite from the ground base, despite the calcite request was set to "platforms-only". It seems the 2 different calcite requests are merged internally, and the platform-only-calcite-request is being satisfied from the ground silo, despite that shouldn't happen imo.
Anyone else has this kind of problem? Is there a way to solve it? Thanks in advance
I have 1 static platform over nauvis. This platform requests calcite for it's own use, but only from "platforms", because another calcite-providing platform roams around and drops calcite to where needed. Nauvis ground base also requests calcite, but since i don't want the static platform to drop it's calcite to ground (should be supplied by the roamer instead), i added a logistic group with requesting 0 calcite from planet (which effectively prevents platform to drop calcite to ground). Now, for this static platform's 2 different calcite requests to exist at all (1 for requesting from roamer, 1 for preventing drop), they are in 2 different logistics groups. HOWEVER, when nauvis ground base has enough calcite and the static platform runs out, it requests calcite from the ground base, despite the calcite request was set to "platforms-only". It seems the 2 different calcite requests are merged internally, and the platform-only-calcite-request is being satisfied from the ground silo, despite that shouldn't happen imo.
Anyone else has this kind of problem? Is there a way to solve it? Thanks in advance