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
Different logistic groups are merged for platform requests?
Re: Different logistic groups are merged for platform requests?
Hi CTT,
Yes, your assumption is exactly right. Factorio currently merges all logistic groups for the same item on the platform hub. The game engine doesn't keep track of separate source conditions (e.g., "planet" vs. "platforms") for the exact same item across different groups; it combines them into a single request, which causes the conflict you are seeing.
How to solve it:
Do not use two conflicting groups for Calcite on the same hub. Remove the group requesting 0.
Instead of trying to prevent the drop from the platform's outbound settings, manage it from the ground or via circuits. You can configure the Cargo Landing Pad on Nauvis to filter out or ignore drops from that specific static platform, or hook up the platform hub to the circuit network to strictly control drop conditions.
In Space Age, mixing different request conditions for the same item on a single hub will always result in merged logic!
Yes, your assumption is exactly right. Factorio currently merges all logistic groups for the same item on the platform hub. The game engine doesn't keep track of separate source conditions (e.g., "planet" vs. "platforms") for the exact same item across different groups; it combines them into a single request, which causes the conflict you are seeing.
How to solve it:
Do not use two conflicting groups for Calcite on the same hub. Remove the group requesting 0.
Instead of trying to prevent the drop from the platform's outbound settings, manage it from the ground or via circuits. You can configure the Cargo Landing Pad on Nauvis to filter out or ignore drops from that specific static platform, or hook up the platform hub to the circuit network to strictly control drop conditions.
In Space Age, mixing different request conditions for the same item on a single hub will always result in merged logic!
Re: Different logistic groups are merged for platform requests?
That clears up my confusion, thank you for your reply!
Yes actually it can be managed with other workarounds, and even shouldn't be much of a problem if requesters are fully supplied and not starving, but still it caught my attention and i was wondering if i was doing something wrong.
Yes actually it can be managed with other workarounds, and even shouldn't be much of a problem if requesters are fully supplied and not starving, but still it caught my attention and i was wondering if i was doing something wrong.