[2.0.13] Asteroid collector has chunks stuck in limbo
Posted: Fri Nov 01, 2024 4:03 pm
1) have asteroid collector fill up
2) read the contents via circuit network
3) note that the circuit networks reads more items than are actually in the collector's storage
I assume it's because the arm of the collector also contains a few items. But they are completely invisible.
(This would also mean that the problem gets bigger the higher quality your collector is because higher quality means more arms which means more possibilities for items to be in limbo.)
The circuit network sees more items than are in the storage:
Why this is a problem: If you use the circuit network to get information about the actual content of the collector the data you will get will be partially wrong. This can lead to problems if you for example set the crusher recipes with the data read from the collector.
If you now hook up a crusher to that which automatically selects the recipe than it would set it to the iron chunk recipe (because internal order when multiple signals are received) but it then gets stuck because there is no iron chunk in that storage that could be put into that crusher.
Proposed solution
a) if it's possible,
b) if my theory of why it's happening is correct,
c) if it wouldn't lead lead to more issues and
d) if there is no other way:
Just don't count the items that are currently "in the secret arm inventory" (I assume they are kinda like inserter hands).
And yes, I'm aware that my specific situation could probably be fixed with a selector combinator but that does not address the weird and unexpected behavior of having some items "in limbo".
2) read the contents via circuit network
3) note that the circuit networks reads more items than are actually in the collector's storage
I assume it's because the arm of the collector also contains a few items. But they are completely invisible.
(This would also mean that the problem gets bigger the higher quality your collector is because higher quality means more arms which means more possibilities for items to be in limbo.)
The circuit network sees more items than are in the storage:
- 1.png (444.21 KiB) Viewed 574 times
Why this is a problem: If you use the circuit network to get information about the actual content of the collector the data you will get will be partially wrong. This can lead to problems if you for example set the crusher recipes with the data read from the collector.
If you now hook up a crusher to that which automatically selects the recipe than it would set it to the iron chunk recipe (because internal order when multiple signals are received) but it then gets stuck because there is no iron chunk in that storage that could be put into that crusher.
Proposed solution
a) if it's possible,
b) if my theory of why it's happening is correct,
c) if it wouldn't lead lead to more issues and
d) if there is no other way:
Just don't count the items that are currently "in the secret arm inventory" (I assume they are kinda like inserter hands).
And yes, I'm aware that my specific situation could probably be fixed with a selector combinator but that does not address the weird and unexpected behavior of having some items "in limbo".