More filters for custom filter zones

[Stu33]

Is your feature request related to a problem? Please describe.

I'd like to implement some new filters that could be used in custom loot zones. I've got some ideas which I'll describe here, but would welcome comments and suggestions before I put time into implementing them.

• Containers by content:
  • Currently the game treats containers as matching the zone that the majority of their contents would sort to. I don't propose to change this, but would allow it to be overridden in a custom loot zone.
  • Non-empty containers where all contents match some filter.
  • Containers where at least one contained item matches some filter.
  • Refinements to choose whether nested containers must themselves match the filters, or whether only their own contents must match.
• Match only perishable or only non-perishable items (regardless of whether the item is food)
• Match by whether a container is sealed, and by whether such sealing completely stops contents perishing.
• Match only empty containers. (Can currently be achieved by matching c:container and excluding names with ">" in them)
• Match only completely empty items - not containing items, ammo, electrical charge, software, etc.
• Match only fully charged items - those filled to capacity with ammo or electrical charge.
• Match only faulty items, only damaged items or only degraded (can't fully repair) items.
• Match items with removable gun mods, MOLLE attachments or similar.
• Match by temperature (frozen, cold, hot) - although this can be done easily by matching text in the item name.
• Match manuals by whether the player can learn anything from them (recipes, proficiencies, skill levels).

Solution you would like.

I'd like to implement this in a way that will keep as many players as possible happy rather than just myself.

Describe alternatives you have considered.

Some of these desired filters can be achieved in existing game builds by carefully matching parts of the item name. It's annoying and verbose to do this however.

Additional context

No response