World of Warcraft · Lua · Side Project November 2026

Warpact
One Pact, Several Guilds

I went back to World of Warcraft on WoW Forever, and my guild, FEARLESS, wanted to link up with the other Balkan Horde guilds on the realm: one shared chat, a private room for guild leaders, and a way to find crafters across all of us. The game offers nothing like that, so we built an addon. The features were the easy part. The work was in the client's quirks.

The Problem

There are several small guilds from the same region on the realm. Everyone knows each other from Discord, but in game we are scattered: who is online in the other guild, who can craft that item, how do guild masters talk without alt-tabbing every five minutes?

The idea was a pact. Not a merger, just a shared layer on top of each guild. Every guild keeps its own name, ranks and bank, and the pact adds a common chat, a common member list and a common crafting directory.

Starting Over

The first attempt was a fork of an existing community addon. It worked inside one guild, and the moment a second guild was added to test, nothing came through. Reworking someone else's design around our needs would have taken longer than building something focused, so I started from scratch and gave it a name that fits the Horde: Warpact.

As with my other side projects, I described what I wanted to an AI assistant (Claude Code), and it wrote the Lua. My part was the requirements, the testing in game, and a lot of screenshots from guildmates.

What It Does

→
Census. Every guild in the pact with its members, notes, classes and levels, grouped by guild.
→
Crafter. A professions directory across the whole pact, including cooking, fishing and first aid, browsable by profession or by guild, with recipe search.
→
Pact chat. One chat for everyone in the pact, with mute, kick and ban.
→
Officers chat. A private room for guild masters and officers only. Ordinary members never see the tab.
→
Vox populi. Simple voting: click the number to vote, click again to take it back.
→
Layers. Which layer of the world you are on, so people can meet on the same one.

The pact has one master, who adds guilds from inside the game. No editing of Lua files, because not everyone in a guild is comfortable with code. The master can appoint up to five deputies, and until he does, nobody else can change anything. Other guilds don't create a pact; their guild master asks to join.

The Client Drops Messages

Addons talk to each other through hidden addon messages. On most clients you would open a custom channel for the pact and broadcast there. On WoW Forever, addon messages sent to a custom channel never arrive. Only guild, officer and whisper messages get through.

So Warpact runs a small relay network. In each guild, one online player becomes the reporter, chosen by a fixed rule so every client agrees without negotiating. Reporters whisper each other across guilds, and each repeats what it hears to its own guild. Every message carries an ID, so nothing is shown twice and nothing loops. When a reporter logs off, the next one takes over.

Lesson A client can look like the classic game and run much newer code underneath. Half of the fixes came from that gap: events that don't exist, functions that moved, messages that are silently dropped. Test on the real client, not on what the documentation of another version says.

Keeping Everyone in Sync, and in Line

The pact record carries a revision number. A change spreads through the reporters, and anyone who missed it, offline or on an older version, catches up the next time their client says hello. One early bug was exactly that: a guild removed from the pact never found out, and kept the pact as if nothing happened. Stale copies are now corrected actively.

The other worry came from the guild leaders: what stops someone from installing the addon, founding their own pact and inviting people? Warpact is locked to one founded pact, edits are accepted only from the master or a deputy, and deputies can only add guilds, never remove them. The same least-privilege thinking I use at work, applied to a game.

Chat That Feels Native

Most feedback was about chat. Opening an addon window to type one line is clunky; people want to press Enter, like everywhere else in the game.

→
Short tags. Pact lines appear in the normal chat with a red [C], officers lines with a blue [O]. Clicking the tag opens a chat box labeled the same way.
→
A PACT tab. Name a chat tab PACT and the addon finds it: pact chat goes there, everything else is hidden in that tab, and the tab blinks on new messages, also with UI replacements like ElvUI.
→
Enter follows the tab. In the PACT tab, Enter writes to the pact. In General it is the game's own chat. After a whisper, the next Enter stays on the whisper, the way WoW behaves.

The constraint behind all of it is security. WoW protects certain actions, and an addon that touches the game's chat box the wrong way can leave commands typed in chat, like /cast or /target, blocked afterwards. So Warpact never changes the game's chat box. It uses its own input box placed where the game's would be, a key binding that exists only while you are in pact mode, and the game's standard message filters to hide lines. My first idea, faking a channel with a whisper to yourself, failed on the first try in game, because the functions it relied on don't exist on this client.

Testing Without Logging In a Hundred Times

You can't run unit tests inside the game, so the project has a simulator: a fake WoW Forever with several players, guilds, whispers, guild messages, combat lockdown and chat tabs. It refuses events the real client doesn't have, which is how it caught a bug that left the whole Crafter page blank in game. On top of it run more than 250 automated checks covering the relay network, the pact lock, moderation, voting and chat.

The other half of testing was the guild. The loop was short: someone posts a screenshot on Discord, the fix goes into a new build the same evening, and the next screenshot shows whether it worked. Many small versions, each one removing one real annoyance.

Where It Stands

The guilds in the pact see each other, chat across guilds works, and Crafter answers the question that started it all: who can make this? The next step is publishing Warpact on CurseForge so other guilds on WoW Forever can form their own pacts.

It's a game, but the lessons were the same as in any integration project: learn how the platform really behaves before designing around it, give people only the rights they need, and ship small changes to the people who use them every day.