About This File
I always disliked how the AuctionHouseBot handled selling and buying items randomly in the recent TrinityCore releases. It used the in-game npc seller price to determine both the sell and buy prices on the AH for the bot resulting in prices being to damn low (generally) or really too high (less often) and sold strange random items sometimes never sold by players.
With this version of the AuctionHouseBot, the sell and buy prices are worked out from an external table in the world database called auction_prices which simply contains item ids and their price in copper. ONLY items belonging to this table can be sold or bought by the bot and their price in the table is used to determine both the sell price and the buy price.
The contents of the auction_prices table has been generated using sampled AH data from several private servers and will be updated from time to time.
General rules :
The chance of an item being bought when the price is higher than the table price is a decaying exponential.
The exponential decays later if no other instance of an item is sold. E.G. If you have a monopoly on [Copper Ore] then the bot knows that the price of [Copper Ore] is a bit higher than usual.
The bot will NEVER buy an item if another instance of that item is sold for less. This is simply more realistic.
An item sold by a player that can be bought from a npc using base money will never be bought by the bot even if it appears in auction_prices, to avoid exploit. They still can be sold by the bot, though.
Of course, a code is never perfect. Should you have any suggestion for the bot behavior, problems to report or improvements to make in the code, feel free to leave a comment.
- Move the 6 .cpp files to your \src\server\game\AuctionHouseBot TrinityCore source directory and replace the existing ones
- Don't forget to commit them if you use git
- Recompile your core
- Apply the auction_prices.sql statement to your world database
- Apply the update.sql statement to your world database, if there is one. [Repeat step 5 only for each future update]
What's New in Version 1.0
- updated description and tags
changes applied by @Balkron