Suggestion: more sortable values in lists

[Nandorianen]

Item browser is awesome. But I think it can be further improved by adding some more values to some lists. Shouldn't be hard to do, I assume.

Armor: layer, coverage, environmental protection, acid protection. Ranged weapons: ammo type, ammo capacity, aim speed, reload time, burst mode. Comestibles: material, use_action.. Materials: item type, number of recipes (to easily find useless stuff you can cut up to get more plastic chunks, for example). Qualities: separate columns for recipes using this item as a tool vs as an ingredient, if possible. Same goes for construction. Ideally these should be separated everywhere. Containers: weight, volume (empty). Skills: levels after 10, construction and vehicle construction action (if possible). Monster catalogs: death_drop. Construction categories: skill level required.

[Sheco]

I see, the lists have the bare minimum common variables I thought would be interesting to have, while keeping the table manageable without it being to wide.

We could add some variables to some of the tables, it wouldn't be hard, as long as the table is not too wide, I'm ok with that.

What do you think?

[Nandorianen]

Yeah, I thought that would be the main issue.

At a glance current table dimensions seem to be optimized for 4:3 resolutions. Is this intentional? If that is something that should be left as is, I think we can work around the issue in most cases by narrowing some columns. For example, "quench" in consumable category can be cut in half without losing anything. Most columns in general seem to have rather luxurious space reserves that can be cut into.

Secondly, while adding columns for numbers shouldn't take away too much space, strings are another issue. This problem can be mitigated by

• shortening text to the shortest functional length;
• encoding it and leaving legend in the tooltip or just as a text above table. For example, display close-to-skin layer as 0, normal as 1, over-the-clothes as 2, strapped as 3.