Inspect Stockpiles to show Average Q

[Ardennesss]

Like subject says, ability to inspect a stockpile and get back the average quality of what's inside it. Thx.

[Granger]

Also amount of items, minimum, maximum and median, please.

[synaris]

+1 granted, if the quality difference is significant my village always sets stockpiles apart from each other.

[Aceb]

Nope. Stockpiles are always created by player, so player should be responsible for handling them. Average is easly misleading on top of that if You're living in your own chaos.

[ctopolon3]

same with barrels & cistern

[MagicManICT]

same with barrels & cistern

Difference being that these storage containers average the quality of their goods. If you stick 10L of q100 water into a barrel with 90L of q10 water, you change the water to q10.9 (if I did my math right*... out of practice with mixing concentrations). Same is true of any liquids (milk, wine) or substances handled as liquids (flour, seeds). Stockpiles do not change the quality of products they contain. You have a list of items of varying quality, and sometimes even mixed items, such as a pile of 4 rabbit skins, two bear skins, and a five cow skins, all 11 of which are different quality.

Anything other than a list of what is in that stockpile is uninformative. In the cases of the pile being homogeneous items (such as pumpkins), the list of qualities would be enough. It would be very convenient, and a very nice thing, if we could click on an item in that list and it would be selected out to inventory.

edit: actually, thinking about this for a few minutes, and I believe q19 would be the right answer: 10 * 100 + 10 * 90 = 1900 / 100 = 19. this is what happens when you've been out of school so long and don't actually work in such a field.

[jorb]

Not too keen on iterating over them on demand to present heuristics, no.

[Granger]

It is possible to do it without iteration, at least for average quality by updating a 'sum of quality' property for the pile the in the data structure (amount is already maintained) whenever items are added/removed. Shouldn't be that expensive (both from a coding and runtime perspective).