Request fulfilled Average price + range in item database?

I like the price list you built - two recommendations, though:

1) once the game started and trades are performed, you could use this data to add the average and max price to the item entry on the website.

2) I would love to see an excel like list for all prices (maybe later on based on real D2R trades), Ready to filter and sort , this way you could sort all trades according to price, giving you an overview what you can afford with your current Wealth.

Line number | item Name | Type | item quality | historical or expected Price Range | Price |

Eth? |

Key price defining stat (e.g. ED for Grief or LL,STR for Andy, %MF for chancies)

Cthuzael wrote: 3 years ago

once the game started and trades are performed, you could use this data to add the average and max price to the item entry on the website.

See price-check - there is a tool you can use to search price history of items exactly as described. Search

Harlequin Crest as an example.

Cthuzael wrote: 3 years ago

2) I would love to see an excel like list for all prices (maybe later on based on real D2R trades), Ready to filter and sort , this way you could sort all trades according to price, giving you an overview what you can afford with your current Wealth.

Line number | item Name | Type | item quality | historical or expected Price Range | Price |

Eth? |

Key price defining stat (e.g. ED for Grief or LL,STR for Andy, %MF for chancies)

Perhaps when the trade section becomes more populated this is something you'd like to embark on yourself? I can assure you that sorting by 'price' will not work on the website side of things because Diablo 2's market has no official currency or way of pegging/sorting by 'price' - it is a bartering market where price is decided by many fators and reimbursed with many different types of items. Too many variable to ever possibly create what you're suggesting automatically, without someone (such as yourself) 'deciding' how to organise it all.

It might be possible, it all depends on how often each item is traded for a pseudo currency like pgems, runes, soj's, etc. Those can be converted down to the least common denominator (pgems).

It would be more difficult to do real time, but would be easier to setup a cronjob to have a rollup script that runs once or twice a day using the previous 72 hours of data (could be a longer/shorter time frame). Move from the lowest to the most valuable currency to try to convert it to pgems using the average value during the time frame. Find the value of low runs in pgems. Then you can get the value of mid level runes that are traded for lower runes or pgems. Then for HR that trade of lower HR or mid runes, you'll have their value in pgems as well. This builds the base for a price lookup table. This all assumes there is at least a significant number of trades of those currencies over the period of time, but if you have that it's just a matter of crunching the numbers to convert all the "currencies" to a common one.

Then when any item is traded, assuming it uses one of those "currencies", look up the latest rollup value for each item it was sold for, sum the values, and store it. Also add it to the lookup as well. Then over time for any item that traded for a currency you can build of history of it's value. Could even have build charts of each items value over time assuming there is enough trade data.

For items that trade for other items, check the lookup for any/all items that was traded for it. If all of them are present in the lookup you can sum them to calculate an estimated value. Even if found it won't work 100% of the time (since some items value can change drastically depending on the roll if multiple attributes vary, like an anni) but as long as it's labeled as the estimated value, it can still give a rough idea.

Like I said all that assumes there are enough trades using the common currencies. I imagine it won't be feasible until you see how much usage the trade portion of the site gets used once D2R is released as well as how people are using it.

Just figured I suggest a possible solution