Chromatic dust is a good floor price and I had seen them listed in the AH for less than that (not recently though).
Yes, it does mean a deposit... I believe it is 10% of the vendor price for the item so listing dust will be 15s each. That is going to hurt supply a bit but this should also increase the average price for dust to at least 2g each.
I believe that’s the price to kill a tailoring/enchanting shuffle.
It’s viable for me now at 1.5g for dust and 12g for shards. Sure only like 2-3k gph but that runs during the day while doing other stuff.
No vendor shuffle works anymore by my math, clear they want people playing content for gold instead.
DBRecent? What's that?DBRecent is the "market value" of an item from the last data snapshot from Blizzard, or roughly an hour ago. Any data from older or newer than the last data snapshot is not used in the calculation.
ExampleLet's say you are looking at healing potions at the auction house, and nothing has changed since the last data snapshot. It does not matter how many of each listing exist. Remember, the "classic" WoW games use stacks, while retail does not. Again, how many of each listing does not matter, the number of auctions or stacks is irrelevant, and are shown to illustrate how DBRecent works.
- 11x 10s
- 457x 1g
- 73x 1g50s
The "market value" of these, or DBRecent, is (10s + 1g +1g50s) / 3 = 86s67c for "classic" since copper coins are used for those games, and 87s for "retail" since that game does not use coppers at the auction house, and 67c is rounded up to the nearest silver. DBMarket, or the "market value" over a
weighted 14 day period, weighing the 3 most recent days over the older 11 days, could be quite different.
How do we use it to improve the Default Material Cost Method?Instead of using an embedded max(min()) as suggested in Part 1, we are going to use a simple min() and return the lowest cost option for a material. We are also going to include our purchase history, but rather than AvgBuy which is from our entire accounting history, we are going to use SmartAvgBuy, which is the average purchase value of our current inventory.
min(smartavgbuy, dbrecent, dbmarket, crafting, vendorbuy, convert(dbmarket))
The inner workingsFull disclosure: the above improvement works for all game versions, yet it works best with retail WoW, where we can buy the exact amount of materials from the auction house. Classic has stacks, meaning often you are buying more of a materials than you need to process your crafting queue. Still, it is better, and the main reason why SmartAvgBuy is included.
After buying all the materials you need and before you start processing your queue, SmartAvgBuy will have a value (and still could have a value after processing your queue with Classic because you have leftover materials). As you use up your materials, once you have 0 of something, SmartAvgBuy will not have a value, which is why the min() works.
If your purchases are the least expensive, that's great, until you have 0 of something. Then the rest of of the string kicks in: comparing DBRecent to DBMarket. In the end, it does not matter if you have leftover materials: the string will always use the least expensive cost for the material, and the best part is that you aren't locked into material costs measured over days! You either have "now" (SmartAvgBuy) or "an hour ago" (DBRecent) if they are valid.
