Work on porting MultiBot to ACE3 has started! You can test it by grabbing the feature/ace3-migration branch. It’s about 11% complete, so the addon is still running in a hybrid mode, but we’re already seeing noticeable gains in smoothness.

User interface for AzerothCore-Module "Playerbots" by Playerbots team https://github.com/mod-playerbots/mod-playerbots.
Tested with American, German, French and Spanish 3.3.5 Wotlk-Client.

Simply place the files in a folder called "MultiBot" in your World of Warcraft AddOns directory.
Example: "C:\WorldOfWarcraft\Interface\AddOns\MultiBot"

Start World of Warcraft and enter "/multibot" or "/mbot" or "/mb" in the chat, or use the minimap button.

This is a fork of the original MultiBot addon by Macx-Lio.

The reason for this fork is that I submitted several pull requests to the original repository, but since the creator, Macx-Lio, is currently unavailable, those changes could not be merged.

To allow the community to benefit from the additional features and improvements I have implemented, I’ve published this fork as a temporary solution.

All credit for the original addon goes to Macx-Lio. I do not claim ownership of this project — I’m simply maintaining a working version until development resumes on the main repository.

Thank you for understanding.

Screens:

	This Picture shows the default MultiBot-Interface after start.
	The horizontal Buttonbar is the Main-Control. Commands from the Main-Control go to all bots in a Group or Raid. Differences in functionality are commented on in the tooltips.
	The vertical Buttonbar is the Playerbot-Selection. Here you will find the Characters of your Account. There is a button for each Character.
	The Tooltip of a Character-Button shows you the Class and Name of the Character. This should allow you to identify your characters.
	With a Left-Click you can load your Character and have him automatically added to the Party or Raid. The horizontal Buttonbar that appears is the Playerbot-Control.
	You can use the Buttons on the left to adjust the Combat-Behavior of your Playerbot.
	With the first Button on the right you can summon your Playerbot.
	With the second Button on the right you can add or dismiss your Playerbot from the Party or Raid.
	With the next three the Buttons you can adjust the Non-Combat-Behavior of your Playerbot.
	The last button on the right opens the Inventory of the Playerbot.
	A Left-Click on the Inventory-Button opens the Inspect- and Inventory-Window of your Playerbot. Notice: The Inspect-Window only will be open if the Playerbot is in reach.
	The Inventory will automatically open in Sell-Mode. In the Sell-Mode a left click on a Item will sell it. Notice: You must have a Merchent as Target.
	With this Button you can switch to the Equip-Mode. In the Equip-Mode a left click on a Item will equip it. Notice: Only works with Equipment.
	With this Button you can switch to the Use-Mode. In the Use-Mode a left click on a Item will use it. Notice: Only works with usable Items.
	With this Button you can switch to the Destroy-Mode. In the Destroy-Mode a left click on a Item will destroy it. Important: There is no security Quest and it will work with every Item.
	Items can be viewed regardless of the selected Mode. Means: View-Mode is always active.
	With a left click on the Character-Button you can hide and show the Playerbot-Control.
	With a left click on the left Scroll-Button you can hide and show the Playerbots.
	With a left click on the right Scroll-Button you can hide and show the Friendbots.
	The vertical Buttonbar is the Friend-Selection. Here you will find the Characters of your Friendlist. There are max 10 Buttons visible.
	With this Button you could browse throu your Friendlist. Each click will show the next 10 Characters. If you reach the End it starts from the Beginning.
	You can limit the Selection to make it easier to find the wished Friendbot.
	Simply press one of these Filter-Buttons to narrow down the Selection.
	As you can see, the browse button has disappeared. This is because the Filter reduced the Selection to less than 10 Friendbots.
	The filter shows you the current limitation. In this example, we filtered to Warrior.
	This button is the result of our filter. The functionality is almost identical to that of the Playerbots. Therefore we save ourselves a further explanation.
	This is the Tank-Attack-Button. A left click on the Button let all Tanks attack you Target.
	This is the Attack-Actionbar. A left click on the Button executes the selected Action. A right click on the Button will show and hide the Optional-Actions. To replace the selected Action, right click a Optional-Action. To execute a Optional-Action, left click it. The default Action is "All attack my target".
	This is the Modebar. A left click on the Button enables and disables the selected Mode. A right click on the Button will show and hide the Mode-Selection. To select another Mode, left click the Mode-Option. The Mode will activated by selection. The default Mode-Toggle is "passive".
	This is the Stay-Follow-Toggle-Button. A left click on the Button sends the Stay-Command to the Party or Raid. Another left click on the Button sends the Follow-Command to the Party or Raid. The Icon will show the current State. The default State is "Follow".
	This is the Flee-Actionbar. A left click on the Button executes the selected Action. A right click on the Button will show and hide the Optional-Actions. To replace the selected Action, right click a Optional-Action. To execute a Optional-Action, left click it.
	This is the Formation-Selector. A left click on the Button will show and hide the Options. A left click on the Option-Button will send the corresponding Formation-Command to the Party or Raid. A right click on the Button will ask the Party or Raid for the current Formation.
	This is the Beastmaster-Control. A left click on the Button will show and hide the Actions. A left click on the Action will send the corresponding Command to your Target, Party or Raid. It supports the "mod-beastmaster"-Module of the Azerothcore. These Buttons work with Target, Group and Raid.
	This is the MultiBot-Control. A left click on the Button will show and hide the Controls. Here you will find the "reset", "reset botAI" and "naxx"-Commands for your Bots. These Buttons works with Target, Group and Raid.
	This Button will send the "drink"-Command to the Party or Raid.
	This Button will send the "release"-Command to the Party or Raid.
	This Button will send the "revive"-Command to the Party or Raid.
	This Button will summon all active Friend- and Playerbots.

Port Multibot to ACE 3

• Milestone 1 (Baseline / safety net): In progress.

  • Baseline behavior is mostly known through manual validation.
  • Migration checklist is tracked in docs/ace3-migration-checklist.md and must be updated per PR.

• Milestone 2 (Add ACE3 libs): Completed.

  • ACE3 libraries are loaded in MultiBot.toc.

• Milestone 3 (Initialization lifecycle): Mostly completed, hardening pending.

  • OnInitialize and OnEnable are in place.
  • Legacy frame-based startup/event code still exists in a few places.

• Milestone 4 (Command system): Completed.

  • Central alias registration is used for core commands via RegisterCoreCommandsOnce in lifecycle init.
  • Runtime command invocation paths are centralized through RunRegisteredCommand (slash + minimap click + helper dispatch).

• Milestone 5 (Event bus migration): Completed.

  • Dispatcher architecture drives core/quick-bar/UI whisper flows.
  • Legacy CreateFrame + RegisterEvent + SetScript listener blocks have been removed from addon runtime paths.

• Milestone 6 (SavedVariables -> AceDB): Completed.

  • AceDB bootstrap/runtime migration is now complete for supported SavedVariables paths; one-way versioned legacy cutovers are in place with guarded legacy creation and post-migration cleanup to avoid stale duplicate persistence.

• Milestone 7 (Minimap/options integration): Completed.

  • Minimap hide/angle, global frame strata, options timers/throttle, Spec dropdown positions, Hunter/Shaman quick-bar positions, Hunter pet stance state and Shaman totem choice state now run through AceDB-backed helpers with one-way versioned legacy cutover and guarded legacy fallback (no legacy table creation on pure read paths).

• Milestone 8 (AceGUI UI refactor): In progress.

  • UI/MultiBotOptions.lua panel content has been migrated to AceGUI widgets while preserving category registration and slash/open flows; remaining screens continue screen-by-screen.

• Milestone 9 (Localization and text pipeline): Completed.

  • Core locale loader + per-locale payload files are integrated (Core/MultiBotLocale.lua, Locales/MultiBotAceLocale-*.lua).
  • Core/MultiBotInit.lua, Features/MultiBotRaidus.lua, Core/MultiBotEvery.lua, Core/MultiBotEngine.lua, Core/MultiBotHandler.lua, Strategies/MultiBotDruid.lua, Strategies/MultiBotPaladin.lua, Strategies/MultiBotMage.lua, Strategies/MultiBotWarlock.lua, Strategies/MultiBotPriest.lua, Strategies/MultiBotShaman.lua, Strategies/MultiBotHunter.lua, Strategies/MultiBotRogue.lua, Strategies/MultiBotDeathKnight.lua, and Strategies/MultiBotWarrior.lua migration sweeps are completed for legacy MultiBot.tips.* runtime reads.
  • Core/MultiBot.lua bootstrap MultiBot.tips initialization lines were validated/documented as intentional non-runtime-tooltip compatibility paths.
  • Remaining UI literal cleanup is completed for Milestone 9 scope (GM shortcut labels, Raidus group title formatting, shared UI defaults for page/title labels) while preserving technical/protocol identifiers (e.g. internal "Inventory" button/event keys).

• Milestone 10 (Data model and table lifecycle hardening): Planned.

  • Normalize runtime stores and remove ad-hoc table creation paths via centralized getters/validators.

• Milestone 11 (Scheduler/timers convergence): Planned.

  • Route scattered timers/OnUpdate loops to a constrained scheduler strategy (AceTimer where appropriate, existing loops retained when safer).

• Milestone 12 (Observability, diagnostics and perf guardrails): Planned.

  • Add lightweight debug/perf toggles and migration diagnostics to validate behavior without chat spam.

• Milestone 13 (Release hardening and deprecation window close): Planned.

  • Close migration fallback window, document upgrade path, and freeze compatibility guarantees for release.