[Feature] Trying to add 'Market Value' price source
KevinTyrrell opened this issue ยท 1 comments
- Problem:
Minimum Price, especially for Classic WoW, tends to be incredibly useless. This is because often times players or bots will randomly post items for low price, causing 'Minimum Value' to believe the auction is a price that it is not. E.g. [Arcanite Bar] usually costs 100g. One day a bot posts one [Arcanite Bar] for 40g. You scan the auction house and AuctionDB now claims [Arcanite Bar] is 40g Minimum Buyout. Then, you might accidentally sell [Arcanite Bar] for way less than it is actually worth.
- Solution
A 'Market Value' price source can take all of the scans in the last month, remove the outliers (e.g. [Arcanite Bar] for 950g), then return the average using some statistics functions to produce a reliable 'price' of what the item is worth.
To do this, AuctionDB would need to save not just one scan, but many. I noticed that it seems like AuctionDB seems to overwrite the past scan with the current one. This essentially means that AuctionDB has no concept of what items actually cost, only what they cost right now.
To enable saving multiple scans over time, and delete ones that age too long (e.g. remove scans from 5 months ago automatically), how much changing would need to be done to MoLib, AHDB, etc?
