LoA Pandaria: Playerbots Bring MoP 5.4.8 to Life at 1,000 Bots

By Indie Kings | October 26, 2026

Updated October 26, 2026: LoA-Pandaria-Playerbots is a GPL-2.0 Mists of Pandaria 5.4.8 server core with a full playerbots module, populating the world with AI controlled characters that quest, group, run dungeons and queue battlegrounds, and the author's benchmark says about 1,000 bots cost a median of just 2 milliseconds per world update.

Image: giant panda via Wikimedia Commons.

Pandaria's first full bot population

The 1LineAtaTime/LoA-Pandaria-Playerbots repository, 24 stars and 4 forks, is a fork of the Legends of Azeroth Pandaria 5.4.8 core with its own module layer, and the README's scope list reads like the mod-playerbots feature set rebuilt for the MoP engine. Random bots live in the world: roaming, questing through the Cataclysm and Pandaria zone chains, hunting and gathering, and traveling by flight path, boat, zeppelin and portal. They join real players in groups with follow, assist, loot and ready check behavior, and follow their leaders onto boats, zeppelins and moving transports without teleporting to catch up. The dungeon finder gets bots that queue, accept and run any 5-player dungeon from Classic through Mists with encounter strategies for the bosses that need them, battlegrounds receive objective play for every map's flags, bases, carts and siege vehicles, arenas cover skirmish and rated, and a chat layer adds greetings, battleground chatter and duels around the cities so the population does not feel like statues. Class rotations cover every MoP class and specialization, including the Monk, with PvE and PvP priorities, interrupts, defensives and pet control. Thanks for the underlying core are credited explicitly to the Legends of Azeroth authors and contributors.

The 2 ms benchmark

Playerbots historically melt server performance, so the performance section is the fork's actual thesis: reworked bot tick scheduling with per bot update delays keeps the world update averaging a few milliseconds with roughly 1,000 bots online, a median of 2 ms in the author's own 1,000 bot runs, reported at no extra CPU cost. Measurements are built in rather than anecdotal: the .server info command prints update time statistics for the last 500 world updates, mean, median, 95th and 99th percentile and max, so an operator can see exactly what a bot population costs on their hardware instead of taking the README's word for it. Testing gets the same treatment: a headless client in contrib/headless-client is a scriptable, graphics-free 5.4.8 client that logs in as a real player so grouping, queues, duels, quests and transports can be exercised automatically, plus GM commands named .botscenario that place, group, queue and probe bots in reproducible scenarios, and per feature log channels with performance counters in the config.

What operators need

The requirements are modern and specific: Linux, Windows or Mac on AMD64 or AArch64, MySQL 5.7 or 8.0 through 8.1, CMake 3.27.2 or newer, OpenSSL 1.1.1 or 3.0 through 3.1.1, Boost 1.85 or newer on Windows and 1.81 above on Linux, GCC 13 or Clang 12 or newer, and Visual Studio 2019 or better with the 10.0.22621 SDK on Windows. No game data ships at all: data extractors run from your own 5.4.8 build 18414 client, enUS locale, and bots specifically need enUS DBC files plus the movement maps, whose generation takes several hours because bots path with mmaps everywhere. Releases carry Windows x64 binaries for worldserver and authserver, the extractors, the four SQL schema dumps including playerbots.sql, and optional PDB debug symbols for readable crash reports. First boot with bots enabled creates the bot accounts and characters and takes a while, and four databases, auth, characters, world and playerbots, get created from the release dumps. Bot population is configured through AiPlayerbot settings like MinRandomBots, MaxRandomBots and RandomBotAccountCount, and the module turns off with one flag.

Repo card

Item	Detail
Project	LoA-Pandaria-Playerbots by 1LineAtaTime
Base	Fork of the Legends of Azeroth Pandaria 5.4.8 core
Client target	Mists of Pandaria 5.4.8, build 18414, enUS for data extraction
License	GPL 2.0
Repo stats	24 stars, 4 forks
Bot behaviors	Questing, roaming, grouping, dungeon finder, battlegrounds, arenas, transports, chat
Class AI	Every MoP class and specialization incl the Monk, PvE and PvP priorities
Headline benchmark	About 1,000 bots at a median 2 ms world update, measured in the author's runs
Measurement	.server info prints mean, median, p95, p99 and max over the last 500 updates
Test harness	Graphics-free headless client plus .botscenario GM commands
Requirements	MySQL 5.7 or 8.0-8.1, CMake 3.27.2+, OpenSSL 1.1.1 or 3.0-3.1.1, Boost 1.85+/1.81+
Releases	Windows x64 servers, extractors, four SQL dumps, PDB symbols

FAQ

What is LoA-Pandaria-Playerbots?
A fork of the Legends of Azeroth Mists of Pandaria 5.4.8 core that adds a full playerbots module, filling the world with AI controlled characters alongside real players.

What can the bots actually do?
They quest through expansion zone chains, group and follow real players onto moving transports, queue the dungeon finder and battlegrounds, drive vehicles, and chat and duel around cities.

How expensive is a large bot population?
The author's benchmark with reworked tick scheduling reports a median 2 ms world update at about 1,000 bots, and .server info lets you measure it yourself.

Is the Monk supported?
Yes, class rotations cover every MoP class and specialization including the Monk, with PvE and PvP priorities, interrupts, defensives and pet control.

Does it ship game data?
No, data extractors run against your own 5.4.8 build 18414 client, enUS locale, and movement map generation takes several hours because bots path with mmaps.

How is it testable?
Via a scripted graphics-free headless client that logs in like a real player and GM commands that build reproducible bot scenarios.

Bottom Line

MoP has been the hardest expansion to give a second life, and its private server scene had two options, faithful emptiness or a disabled feature set. This fork argues the third route, and the serious part is not the shiny feature list but the benchmark honesty: publishing a distribution of update times for the last 500 ticks is how you let an operator audit the bot tax on their own hardware instead of trusting a screenshot. A headless client plus scripted scenarios means the bots live in CI as much as in the world, which is more than most retro projects say about their code quality.

Sources

GitHub 1LineAtaTime/LoA-Pandaria-Playerbots README (feature scope, performance section, requirements), accessed 26 October 2026
GitHub API repository metadata for 1LineAtaTime/LoA-Pandaria-Playerbots, accessed 26 October 2026