Maximizing Your Server Economy: How To Add More Items To AHBot In World Of Warcraft Emulation

Expanding your server's auction house inventory requires a dual-phase approach involving the modification of the mod-ahbot configuration file and the direct manipulation of the world database item tables. By adjusting the MinItems and MaxItems thresholds alongside item quality filters, administrators can increase total listings from the standard 200 items to over 10,000, ensuring a vibrant, player-driven economic simulation.

Pre-Operation Configuration and Database Planning

Before attempting to scale the Auction House Bot (AHBot) inventory, you must understand that the bot functions by scanning your existing item_template table and selecting items that meet specific criteria. If your auction house feels empty, it is rarely because of a lack of items in the database, but rather because the bot’s internal filters or quantity caps are set too conservatively. This process is applicable to most modern AzerothCore and TrinityCore distributions utilizing the common mod-ahbot or the legacy AuctionHouseBot C++ scripts.

To successfully scale your economy, you will need the following prerequisites:

• Administrative access to your server's root directory and the specific configuration folder, typically located within the /etc/ or /bin/ folders of your core.
• A robust database management tool such as HeidiSQL, MySQL Workbench, or DBeaver to execute queries and inspect item flags.
• A compiled version of the mod-ahbot module integrated into your worldserver source code.
• Estimated Time: 20 to 45 minutes depending on the volume of custom SQL entries required.
• Standard Hardware Benchmarks: Ensure your server has at least 4GB of RAM, as an AHBot listing 20,000+ items simultaneously can increase memory overhead for the worldserver process.

Comprehensive Workflow for Increasing AHBot Item Density

Step 1: Adjusting the Global Item Count Thresholds

The most immediate method to add more items is to edit the configuration file governing the bot's behavior. Navigate to your server's configuration directory and locate the file named mod_ahbot.conf or worldserver.conf, depending on your specific build. Within this file, you must search for the Seller Configuration section.

Find the variables labeled AuctionHouseBot.Seller.Enabled and ensure the value is set to 1. Following this, locate the specific quantity settings for each faction. These are usually divided into Alliance, Horde, and Neutral categories. You will see lines such as AuctionHouseBot.Seller.Items.Alliance.Amount.Ratio. To increase the total number of items, you must increase the numerical value assigned to these ratios or find the hard-capped Min and Max settings. For instance, if your MaxItems setting is currently at 500, increasing this to 5,000 will signal the bot to pull more entries from the database during its next refresh cycle.

Warning: Setting your MaxItems threshold excessively high (e.g., above 50,000) on a low-specification VPS can lead to significant latency spikes during the bot's "re-stocking" phase, which typically occurs every few hours.

Step 2: Modifying Item Filters and Quality Ratios

Even if you increase the maximum allowed items, the bot may still fail to list more items if your quality filters are too restrictive. The AHBot uses a probability-based system to decide which items to post based on their rarity (Grey, White, Green, Blue, Epic, Legendary).

In your configuration file, locate the Item Quality Ratio settings. These are often represented as a series of numbers separated by commas or individual lines for each quality level. If the ratio for Epic (Purple) items is set to 0, the bot will never post them regardless of how many exist in your database. To add more variety and volume, ensure that the ratios for Common, Uncommon, and Rare items are balanced. A standard high-population configuration might use a ratio like 100 for White items, 80 for Green items, and 20 for Blue items. By increasing these specific numbers, you force the bot to select from a broader pool of entries in the item_template table.

Step 3: Removing Flags that Block AHBot Selection

The bot will ignore any item that is marked as "Soulbound" or has specific "Flags" in the world database that prevent it from being auctioned. If you have custom items or specific gear you want the bot to sell, you must ensure their database entries are compatible.

Connect to your MySQL database and open the world database. Locate the item_template table. Look at the column labeled Bonding. For an item to be listed by the AHBot, this value should generally be set to 0 (No bonding) or 2 (Bind on Equip). If an item is set to 1 (Bind on Pickup), the bot's internal logic will automatically skip it to prevent players from buying items that cannot be traded. Additionally, check the Flags and FlagsExtra columns. If an item has a flag that prohibits it from being sold at an auction house, you must clear that flag using an SQL Update command to make it "visible" to the bot.

Pro-Tip: You can use a batch SQL command to change all Bind-on-Pickup items in a specific level range to Bind-on-Equip, which instantly makes thousands of new items available for the bot to list.

Step 4: Forcing a Database Refresh and Restock

After modifying your configuration and database flags, the changes will not appear in the game immediately. The AHBot maintains a cache of currently listed items. To see your new, larger inventory, you must trigger a restock. You can do this by restarting the worldserver process, or if your module supports it, by using an in-game command such as .ahbot rebuild or .ahbot reload.

When the rebuild command is executed, the bot deletes all current listings and performs a fresh scan of the item_template table based on your updated MaxItems and Quality settings. Monitor the worldserver console during this process; it will typically output a message indicating how many items were successfully loaded into each auction house. If the number is lower than your desired MaxItems, it means the bot has run out of items that meet its bonding and quality criteria, and you may need to further loosen your database filters.

Step 5: Utilizing Include and Exclude Lists for Granular Control

If you want to add specific items that are not appearing naturally, many AHBot modules support an "Include" list. This is often a separate table in your database named ahbot_items or a similar variation. By inserting specific Item IDs into this table, you can bypass the bot's random selection logic and force it to prioritize these items.

This is particularly useful for adding profession materials like ores, herbs, and leathers, which are often in high demand. You can manually insert the Item IDs for Copper Ore, Tin Ore, and Iron Ore into the inclusion table, ensuring that the bot always keeps a steady supply of these items available regardless of its other random selections. This creates a more "full" feeling in the auction house by targeting the specific categories players check most often.

Technical Parameters and Configuration Thresholds

The following table outlines the critical configuration variables found in the mod_ahbot.conf or worldserver.conf files that directly impact the volume and variety of items listed.

Troubleshooting Common AHBot Inventory Failures

The Auction House Remains Empty After Configuration Changes

• Root Cause: The bot is unable to find items that match its criteria, or the Seller functionality is disabled in the configuration.
• Actionable Fix: Verify that AuctionHouseBot.Seller.Enabled is set to 1. Then, check the worldserver.log for SQL errors. Often, the bot fails because the item_template table is missing columns expected by the module version you are using. If the logs show "0 items found," use an SQL query to ensure you have items in the database with a Bonding value of 0 or 2.

Bot Only Lists Grey and White Items

• Root Cause: The Quality Ratio settings in the configuration file are skewed heavily toward lower-tier items, or higher-tier items are flagged as Bind on Pickup.
• Actionable Fix: Adjust the AuctionHouseBot.Seller.Item.Quality ratios to favor Uncommon (Green) and Rare (Blue) items. Additionally, execute an SQL command to check if your Epic items have the "Auctionable" flag. You may need to update the item_template table to change bonding types for high-level gear if you want them to appear.

Severe Server Lag During AHBot Refresh

• Root Cause: The MaxItems setting is too high for the server's CPU/RAM, or the refresh interval is too frequent.
• Actionable Fix: Lower the total item count to a more manageable number, such as 2,000 per auction house. Increase the interval between bot cycles (AuctionHouseBot.Seller.UpdateInterval) to ensure the server is not constantly recalculating thousands of prices and listings.

Items Are Listed but Have Impossible Prices

• Root Cause: The item_template "BuyPrice" or "SellPrice" is set to 0, or the bot's price multiplier is incorrectly configured.
• Actionable Fix: Inspect the database entries for the affected items. If an item has a 0 copper value in the database, the bot cannot calculate a proper auction price. Set a baseline SellPrice for your custom items. Alternatively, adjust the AuctionHouseBot.Price.Multiplier in your config file to normalize the listings.

Frequently Asked Questions

Can I make the AHBot sell custom items I created?

Yes, as long as your custom items are present in the item_template table and have a Bonding type of 0 or 2. You can further guarantee their appearance by adding their Item IDs to the ahbot_items_include table in your world database, which forces the bot to recognize them during its next scan.

Why does the bot delete my items when I post them?

The AHBot usually includes a "Buyer" component in addition to a "Seller" component. If AuctionHouseBot.Buyer.Enabled is set to 1, the bot will periodically purchase items listed by players. To prevent this, you can disable the Buyer settings in your configuration or adjust the price thresholds so the bot only buys items it considers a bargain.

How do I limit the bot to only sell items from a specific expansion?

To restrict the inventory to a specific expansion, such as Burning Crusade, you must use an SQL query to update the item_template table. You can set a custom flag on all items with a RequiredLevel or ItemLevel above a certain threshold (e.g., 70), or modify the bot's source code to filter by the expansion ID column if your core supports it.

Is it possible to have the bot only list profession materials?

Yes, you can achieve this by setting all other item quality ratios to 0 and specifically adding the Item IDs for ores, herbs, and cloth to the bot's inclusion list. Alternatively, you can use an SQL command to set the "Flags" of non-profession items to a value that the AHBot is configured to ignore, effectively filtering the entire auction house.

Does increasing the AHBot inventory affect database size?

The auctionhouse table in your characters database will grow significantly in terms of row count, as every listing is a unique entry. While this doesn't drastically increase the file size on your disk, it can make manual database backups slightly slower. It is recommended to regularly clear the auctionhouse table if you plan on performing major bot reconfigurations.

Enhance Your Server's Economic Vitality

Mastering the AHBot configuration is the most effective way to provide a consistent gameplay experience for players on low-to-medium population servers. By fine-tuning your item quality ratios and database flags, you ensure that your world feels populated and that essential progression materials are always accessible.