Currency consistently incorrectly calculated

[MyLego]

Currency is consistently incorrectly calculated in the tabulation view even when it is correctly calculated in the map view.

I have toggled the switch to hide low value single items. (Since this throws the calculations off by quite a bit).

I also do get a couple of error when I look at the logs on a pretty consistent basis. 2020-01-11 18:04:13.592 [warn] ItemParser.js > Error checking inventory keys: Error: SQLITE_ERROR: near ")": syntax error and also this though I don't think this affect this specific issue. 2020-01-12 01:05:35.488 [info] ClientTxtWatcher.js > Error inserting event 20200112010535 -> master Jun, Veiled Master: [Riker Maloney, Midnight Tinkerer: Not in this place of filth!] : Error: SQLITE_CONSTRAINT: UNIQUE constraint failed: events.id, events.event_type

[MyLego]

log.txt

[MyLego]

The error seems to be almost entirely in proportion to the items removed by the ignore-function. Unfortunately only almost. Some maps are still off by a chaos or a couple of chaos but that may very well be a rounding error.

It's unlikely that this is a wanted effect and it is mostly caused by, in my case, the overvaluation of item bases that throw off the evaluation massively if you pick up any rares at all.

[briansd9]

Hi, thanks for your feedback. Which of these solutions do you think is better?

1) For items under the limit, don't price them at all (which means that information about the value of these items is permanently lost even if you decrease or remove the limit later)

2) Display a label explaining the difference (something like "___ c in low-value items hidden"): https://i.imgur.com/ONFrEW2.png

[MyLego]

Out of those two options the primary difficulty is that the listing in Main displays the value including the hidden items when that is the view you will most often use. I would be happier if the main view was dynamically updated based on the setting you choose.

That said, I think there are a couple of point from a usability stand point that could be examined here. The primary use of hiding objects is to hide 1c uniques that won't sell and to hide bases that won't sell even if they are priced at several c. It would be very valuable to be able to just nix bases as such with an option, no matter if they were permanently scrubbed. * A tangential issue is also that if you have a high value gem that you use for single target it will be calculated into the total depending on what you have equipped when you switch zones. It may be hard to implement this dynamically but if it was possible to manually add gems that are just not counted even with the risk that it would not count a pickup it would help immensely.

[YakMaster]

Personally I would prefer the value shown in the main map list was the net lower value (without low value items included) as Total A.

Then in the detailed view for each map it could list A (above) +B (low Value items) =C (Grand Total). as per your image.

Is there a way to get the main map list to show more than the last 10 maps? There is room for 20+ on the screen but half is blank/black.

cheers

[briansd9]

After a league of trying out different things, I've decided to go with completely ignoring items that fall under the limit (no value will be stored for them unless they're 6S/6L).

Regarding other comments:

• Swapped out gems shouldn't count as loot, fixed in the next release.
• Still thinking about what else to show on the front page (perhaps net worth / xp tracker / ? any other ideas?)