[2.0.32] The number of unsatisfied logistic network requests depends on which type of chest items are stored in

Bugs that are actually features.
terrenna
Burner Inserter
Burner Inserter
Posts: 6
Joined: Wed Feb 12, 2025 6:17 am
Contact:

[2.0.32] The number of unsatisfied logistic network requests depends on which type of chest items are stored in

Post by terrenna »

Description
The number of unsatisfied logistic network requests depends on which type of chest items are stored in:
  • Items in storage chests are added to logistic network contents and subtracted from unsatisfied logistic network requests (as read via circuit signal from a roboport).
  • Items in any other chest type are also added to logistic network contents, but not subtracted from unsatisfied logistic network requests.
The inconsistent handling makes the value of unsatisfied requests read from a roboport depend not only on requests and availability, but also on the type of chests the items are stored in, which seems unintentional, because there is currently no way of knowing whether an unsatisfied request is actually an unsatisfied request or whether the requested items just happen to be stored in the wrong kind of logistic chest.
Steps to reproduce
Create a requester chest, set it to request 100 iron plates. Create a chest of each type, add one iron plate to each. Check logistic network requests and contents circuit signals at roboport. It reads unsatisfied requests: 99, contents: 4. Remove iron from storage chest. Now it's at 100 to 3, indicating that only the storage chest contents are subtracted from the number of unsatisfied requests.

In the attached image I have illustrated the difference between storage chest and active provider chest as an example.
Possible solution
Depending on when you count a request as satisfied (available on logistic network, item reserved by logistic robot, item picked up by logistic robot, item arrived at requester chest), either behavior could be argued to be intentional, but probably not both at the same time. That being said, the "Satisfaction" value of the request (visible in the tooltip when hovering the mouse over the icon of the logistic request in the GUI of the requester chest) remains 0/100 until the item has arrived, so if the chest's satisfaction is considered the same satisfaction as that reported by the roboport, the values should probably match.
chests1.png
chests1.png (771.1 KiB) Viewed 358 times
Rseding91
Factorio Staff
Factorio Staff
Posts: 15540
Joined: Wed Jun 11, 2014 5:23 am
Contact:

Re: [2.0.32] The number of unsatisfied logistic network requests depends on which type of chest items are stored in

Post by Rseding91 »

Thanks for the report however this is working correctly. Items in storage chests will be moved to any requester wanting them and so they are not "unsatisfied" (missing from the network as a whole).
If you want to get ahold of me I'm almost always on Discord.
terrenna
Burner Inserter
Burner Inserter
Posts: 6
Joined: Wed Feb 12, 2025 6:17 am
Contact:

Re: [2.0.32] The number of unsatisfied logistic network requests depends on which type of chest items are stored in

Post by terrenna »

Rseding91 wrote: Tue Apr 22, 2025 1:36 pm Thanks for the report however this is working correctly. Items in storage chests will be moved to any requester wanting them and so they are not "unsatisfied" (missing from the network as a whole).
The same is true for provider chests, right? Because they behave differently, hence the bug report.
Post Reply

Return to “Not a bug”