Grouping Container Block Inventories
Not Enough Votes
It would be SUPER convenient if when container blocks on the same (mutiple might work?) grid are grouped together (meaning the create block group function in the console UI), they appear as a single entry in the inventory tab. Then they share storage, or maybe can be organized in different selectable manners. One being they all fill equally as items are added, or fill entirely one at a time. I feel like that would dramatically reduce inventory management clutter.
I like this feedback You can't vote. Please authorize!
You can't vote. Please authorize!
You can't vote. Please authorize!
You can't vote. Please authorize!
You can't vote. Please authorize!
You can't vote. Please authorize!
You can't vote. Please authorize!
Wholehearted yes from me. So much less inv. screen bloat.
Wholehearted yes from me. So much less inv. screen bloat.
I like the idea but you would need to consider what would happen should the conveyor network be disrupted. I think as a UI option it might be nice but in actual what is where might be trickier. It would also make having separate inventories for ores, ingots and components tricky. I can also see frustrations arising if you are using sorters with black or white lists that would prevent you from taking stuff out but there would be no indication as to why.
I like the idea but you would need to consider what would happen should the conveyor network be disrupted. I think as a UI option it might be nice but in actual what is where might be trickier. It would also make having separate inventories for ores, ingots and components tricky. I can also see frustrations arising if you are using sorters with black or white lists that would prevent you from taking stuff out but there would be no indication as to why.
Idea:
- sorters exist but are not strictly necessary, they can be used as one-way culverts for the flow of items, have the ability to set the "collect all" flag for example for emptying mining drones. Manual movement of items through the sorter is possible.
- storage containers have a configurable white list and black list of items and automatically move and store the corresponding items (so the container is also a bidirectional pass-through sorter)
- storage containers have an adjustable "filling priority" - the container with the higher priority pulls the whitelisted item from the container with the lower priority. Two containers with the same priority and the same white list do not move items between them. Manual movement of items is possible.
- Containers have a configurable "collect all" flag - pulls all items (except blacklist items) from other containers, except items that are on the whitelist of the respective containers (i.e., "correctly stored") Two containers with the same "collect all" flag do not move objects between each other unless they have different priorities.
- Refinery-type processing blocks have a configurable white list and a black list of processing inputs.
- Assembler-type processing blocks have the input stack divided into several segments of equal (or even unequal?) size. The filling of the stack segments cannot be repeated. The purpose is to prevent the input stack from overflowing with one kind of objects.
The processing block always has a higher priority than the storage container.
Translated with DeepL.com (free version)
Idea:
- sorters exist but are not strictly necessary, they can be used as one-way culverts for the flow of items, have the ability to set the "collect all" flag for example for emptying mining drones. Manual movement of items through the sorter is possible.
- storage containers have a configurable white list and black list of items and automatically move and store the corresponding items (so the container is also a bidirectional pass-through sorter)
- storage containers have an adjustable "filling priority" - the container with the higher priority pulls the whitelisted item from the container with the lower priority. Two containers with the same priority and the same white list do not move items between them. Manual movement of items is possible.
- Containers have a configurable "collect all" flag - pulls all items (except blacklist items) from other containers, except items that are on the whitelist of the respective containers (i.e., "correctly stored") Two containers with the same "collect all" flag do not move objects between each other unless they have different priorities.
- Refinery-type processing blocks have a configurable white list and a black list of processing inputs.
- Assembler-type processing blocks have the input stack divided into several segments of equal (or even unequal?) size. The filling of the stack segments cannot be repeated. The purpose is to prevent the input stack from overflowing with one kind of objects.
The processing block always has a higher priority than the storage container.
Translated with DeepL.com (free version)
I would like to see the container view on the same grid separated into joined networks.
This would save having to drag something to see if the inventory box area goes dark, indicating no connection between inventories.
I would like to see the container view on the same grid separated into joined networks.
This would save having to drag something to see if the inventory box area goes dark, indicating no connection between inventories.
Replies have been locked on this page!