How to Add More Items to AHBot in World of Warcraft
If you're running a private World of Warcraft server using emulator software like TrinityCore or AzerothCore, you've probably already met AHBot — the Auction House Bot that populates your in-game economy with buyable and sellable items. By default, AHBot works with a limited item pool, which can make your auction house feel sparse or repetitive. Knowing how to expand that item list is essential for server admins who want a richer, more realistic in-game economy.
What Is AHBot and Why Does Item Count Matter?
AHBot (Auction House Bot) is a server-side tool that automatically lists items for sale in the in-game Auction House, simulating player-driven market activity on servers with low or no real player traffic. Without it, the AH sits empty, making crafting, farming, and trading feel pointless.
The number and variety of items AHBot lists directly affects:
- Economy depth — more items means more crafting materials, gear, and consumables available
- Server feel — a stocked AH creates the illusion of an active playerbase
- Gold sink balance — item pricing and availability influences how currency flows through your server
By default, many AHBot configurations use conservative item counts or exclude large portions of the item database to avoid performance strain. Expanding the item pool requires editing configuration files and, in some cases, the bot's item filter list.
Understanding the AHBot Configuration Files
Before you can add more items, you need to know where AHBot gets its instructions. Depending on your server emulator, the relevant file is typically named:
ahbot.conforahbot.conf.dist(TrinityCore, AzerothCore)
This file controls how many items are listed per auction house faction (Alliance, Horde, Neutral), item quality thresholds, price multipliers, and which item classes are included or excluded.
Key Configuration Parameters to Know
| Parameter | What It Controls |
|---|---|
AHBot.Items.Grey | Number of grey (poor quality) items listed |
AHBot.Items.White | Number of white (common) items listed |
AHBot.Items.Green | Number of green (uncommon) items |
AHBot.Items.Blue | Number of blue (rare) items |
AHBot.Items.Purple | Number of purple (epic) items |
AHBot.Items.Orange | Number of orange (legendary) items |
AHBot.Items.Yellow | Number of yellow (artifact) items |
AHBot.MaxStack | Maximum stack size per listing |
AHBot.ItemsPerCycle | How many items are re-listed per bot update cycle |
Increasing the numeric values in these fields directly expands how many items of each quality tier appear in the AH. 🎮
How to Add More Items Step by Step
Step 1: Locate and Open Your AHBot Config
Navigate to your server's configuration directory. Find ahbot.conf — if only ahbot.conf.dist exists, copy it and rename the copy to ahbot.conf. Open it in any plain text editor.
Step 2: Increase Item Count Values
Find the lines corresponding to item quality tiers. They typically look like:
AHBot.Items.White = 100 AHBot.Items.Green = 100 AHBot.Items.Blue = 50 Raise these numbers to your desired counts. Servers with active testing or solo play often benefit from values in the 200–500 range per quality tier, though the right number depends on your server's player count and hardware capacity.
Step 3: Adjust Item Class Filters
AHBot can be configured to include or exclude specific item classes — categories like weapons, armor, trade goods, recipes, and consumables. Look for parameters like:
AHBot.Class.Xwhere X corresponds to WoW's internal item class IDs
Setting these to 1 enables that item class; 0 disables it. If your AH is missing tradeskill mats or recipes, this is usually why.
Step 4: Expand the Item ID Whitelist (If Used)
Some AHBot implementations use an explicit whitelist — a text file listing allowed item IDs. If your setup includes an itemlist.txt or similar file, you'll need to add item IDs manually. You can source item IDs from:
- Your server's
item_templatedatabase table - Community databases like wowhead (for reference, cross-checked against your server's DB version)
Step 5: Restart the World Server or Reload AHBot
Changes to ahbot.conf typically require a full world server restart. Some emulators support in-game GM commands to reload AHBot settings — for example:
.ahbot reload Check your emulator's documentation for supported reload commands, as these vary between TrinityCore, AzerothCore, and other forks.
Variables That Affect Your Results 🛠️
Expanding AHBot's item pool isn't a one-size-fits-all adjustment. Several factors shape what actually works well for a given server:
- Server hardware — Higher item counts mean more database queries per cycle. Lower-spec machines may see performance degradation with very high values
- WoW client version — AHBot behavior and configuration options differ across emulators targeting different expansions (Vanilla, TBC, WotLK, Cataclysm)
- Database completeness — Not all private server databases include every item. AHBot can only list items that exist in your
item_templatetable - Player count — A solo or very small server needs far fewer listings than one with dozens of concurrent players
- Economy goals — A server designed for fast progression needs different item availability than one aiming for a more authentic slow-burn economy
Common Issues When Expanding Item Pools
Items not appearing after restart: Double-check that you edited ahbot.conf and not the .dist template. Confirm AHBot is enabled (AHBot.Enable = 1).
Only certain quality tiers show up: Item class filters may be blocking categories even when count values are high. Review each class filter setting.
Server lag or slow AH loading: Very high ItemsPerCycle values can strain database performance. Reducing cycle frequency while keeping total item counts high is often a better balance.
Duplicate listings or pricing anomalies: Price multiplier settings interact with item count — more items at misconfigured prices can break your economy faster than an empty AH.
The Part That Depends on Your Setup
The item counts, class filters, and whitelist entries that work well for one server often need significant adjustment for another. A WotLK server running on a dedicated machine with 50 players has almost nothing in common — from a configuration standpoint — with a solo Vanilla server on a home PC. The mechanics of how to expand AHBot's item pool are consistent, but finding the values that create a balanced, stable economy for your specific server is a process of iteration. Your database version, expansion target, hardware, and what kind of player experience you're building all pull in different directions.