[2.1.9] Platform-Platform or Platform-Planet transfer gridlock (not construction)

Bugs that are actually features.
WestKMag
Manual Inserter
Manual Inserter
Posts: 2
Joined: Thu Jul 02, 2026 3:44 am
Contact:

[2.1.9] Platform-Platform or Platform-Planet transfer gridlock (not construction)

Post by WestKMag »

TLDR: There are replicable cases where platform-to-platform logistics transfers do NOT take place even though the tooltips, radio buttons, and filters suggest they absolutely should. Specifically, multiple logistics requests for the same item (even if one is from the planet, the other from a platform, or they are otherwise mutually exclusive and shouldn't gridlock) will gridlock.

I searched for similar bugs but nothing quite replicates what I'm getting at here. The closest I've seen is the one where construction requests gridlock delivery of items, so the source of the problem might be the same.

See screenshots and save file for an example. In this case, logically, the (Gleba) Exporter should be dropping Stack Inserters to Fulgora. However, it is not, and no reason is given. I've narrowed it down to the fact that ANY second logistics request of the same item from the source (in this case, the Stack Inserter request in the ship's maintenance logistics section) will gridlock the system no matter what. This is especially interesting because the maintenance request is set to ONLY pull from platforms, so sending it down to the planet should be no problem. Likewise, the "main" logistics requests under the ship's "exports" section is set to ONLY pull from platforms as well, so again, sending down to a planet should not cause a gridlock.
Gleba Exporter (Source).png
Gleba Exporter (Source).png (1.72 MiB) Viewed 116 times
Fulgora (Destination).png
Fulgora (Destination).png (3.07 MiB) Viewed 116 times
There seems to be some sort of background behavior where the ship considers a logistics request as being "fulfilled to itself and by itself" and thus won't deliver anything that it is requesting from a platform in its own vicinity... but I might be wrong on that. I understand the likely *intended* behavior is to avoid ships infinitely transferring stuff between them, but in this case its too strict and is preventing things that should be possible.

What did you do?

Set any logistics request for a platform-to-platform or platform-to-planet transfer while also requesting the same item in another logistics spot of the source platform (like for ship maintenance).

What happened?

No transfer takes place/the two platforms are gridlocked, even though there is sufficient quantity in the source to allow transfer without violating the source's own logistics request. It seems that having more than one logistics request of ANY item on a platform makes it unable to transfer the item to another platform. This is VERY similar to the other bug where construction requests block transfers, but slightly different and might rely on a different bug fix.

What did you expect to happen instead? It might be obvious to you, but do it anyway!

I expect the transfer to take place. Based on radio buttons, filters, and tooltips, the source (A) should be able to transfer the item to the destination platform or planet (B) if fulfilling the request does not violate its own requests. See attached save, I have multiple instances where this is not true. The most obvious is the screenshot I provided. The (Gleba) Exporter has enough Stack Inserters in inventory to fulfill the logistics request of Fulgora landing platform without going below the amount in the maintenance section (50)... so the transfer should take place but it doesn't. I'd have to completely delete the separate logistics maintenance request for the transfer to take place.

Does it happen always, once, or sometimes?

*Almost* always. The only logistics requests that will allow a platform-to-platform (A to B) transfer require that the source (A) does not have a logistics request for the same item it is trying to transfer, or that the other transfer MUST be from a single planet no matter what. (B) will never receive the item otherwise.
Attachments
factorio-current.log
(8.81 KiB) Downloaded 2 times
Drew Space Age 2.1.9 bug 1JUL26.zip
(33.51 MiB) Downloaded 3 times
Genhis
Factorio Staff
Factorio Staff
Posts: 960
Joined: Wed Dec 24, 2014 8:19 am
Contact:

Re: [2.1.9] Platform-Platform or Platform-Planet transfer gridlock (not construction)

Post by Genhis »

Thanks for the report. If I understand it correctly, your Exporter platform requests 25 stack inserters from other platforms on all planets. Then you have a second request for 100 stack inserters only from Gleba platforms. You want to supply stack inserters to Fulgora if needed but still keep 25 on your platform. This isn't possible with requests - if an item is requested, it can't be provided anywhere else. Feel free to open a suggestion about this topic if you think we should change it.
Post Reply

Return to “Not a bug”