- Proposal
- It would be a huge QoL feature to have additional columns available when changing the view of a container. Being able to display the resource name and resource class would make filtering much easier.
- Justification
- Currently, filtering is only possible by the displayed name, such as "Copper" or "Iron". However, resources of the same type can be scattered throughout the list, making them difficult to manage.
- Motivation
- Finding a specific resource in a container is horrible. Keeping track of your stock is a nightmare. Even when filtering the items in a list, a stack of 200k can be at the bottom of the list and 2 stacks of 1000k can be in between.
One implementation idea would be a separate type of container, crafted by Architects, that can only store resources. Only this container type would display the additional columns.Benefits:
- Provides additional value to the Architect profession.
- Offers a clean implementation without affecting existing container functionality.
- The container could have a base storage capacity of <x-amount> and optionally support storage modules from DE to expand its capacity.
