I can only speak for myself and my experience.
Knowing the %-value is not the point.
It's all about knowing when an item appears in the filtered list.
1.
The %-value is constand. The h-value is relativ.
When the consumption of ore stops the %-value remains the same. The h-value increases.
So the filtered list with h-values does not show the current state correctly.
e.g.
State A: 100.000 ore field (100% - 10h)
State B: consumption stops at 5.000 ore (5% - 0,5h)
=== h filtered list (12h) ===
A does appear in the list (have to lower the h-value to make it disappear, can not do this for each ore field individually)
B does appear in the list (but if you wait long enough it will go away)
=== % filtered list (10%) ===
A does not appears in the list (and will never)
B does appears in the list (and stays at the same point, rescan to make it disappear)
2.
It kept the filterd list small.
In the past, when an item appears in the filtered list, it prompts me to do something.
--> get a new ore field
--> clean up the old field (replace minigdrills and scan it again to get a better time) [rescan is not necessary with your new calculations, NICE!]
3.
I personally prefer to work with constant values. This gives me better control over the list.
The amount and size of every ore field is different. However, this has no influence on the %-value.
After writing all this, I've come to the conclusion that I don't like the lack of control over the filtered list.
regards
Scumbag
