Runes of Magic addons: WoW-style UI mods for a classic MMO

Runes of Magic is a free-to-play fantasy MMORPG that launched in 2009, and its "modding" is the kind familiar to anyone who played World of Warcraft in that era: client-side interface addons written in Lua. There is no world-altering modding here, because it is a server-authoritative MMO, but the addon system gives players deep control over the UI, and a surprising amount of it still circulates today.

How the scene is shaped

Like classic WoW, Runes of Magic exposes an addon API that runs in the game client. Addons cannot change the game world or grant an unfair advantage; what they do is reshape the interface and surface information. The community built damage and healing meters, map and minimap enhancements, inventory and bag managers, quest helpers, and tooltip extensions. These live on CurseForge, which has long hosted Runes of Magic addons, and on GitHub, where maintained addon packs collect the most useful ones with sensible defaults already configured.

The toolchain primer

Addons are plain folders you place inside the game's directory. Under the install you create or open an Interface folder, and inside it an AddOns folder, then unpack each addon into its own subfolder there. The structure mirrors WoW: every addon has a .toc file whose name matches its folder, XML files that define frames and load the code, and Lua files that hold the logic. There is no separate loader to run; the client reads the AddOns folder at launch, and an in-game panel lets you toggle individual addons.

Why the addons outlived the hype

Runes of Magic arrived in 2009 as one of the more ambitious free-to-play MMOs of its day, with a dual-class system and player housing that gave it real staying power. The game has changed hands and shrunk from its peak, but the addon API it inherited from the WoW-style template never went away, and that is why a returning player in the present day still finds working interface mods. Old MMOs tend to keep whatever client-side customisation they shipped with, because that code runs locally and does not depend on the publisher maintaining anything.

Underneath the user-facing addons sit shared libraries, the same pattern WoW used, where common code for timers, configuration, and UI widgets is packaged once and reused by many addons. Installing a popular meter or map mod often pulls in a couple of these libraries as dependencies.

What you'll find on OpenMods

OpenMods indexes projects published in public repositories, which suits Runes of Magic well, since a good deal of its addon work lives on GitHub alongside CurseForge. For the broadest historical selection, CurseForge is the main archive. OpenMods is a natural home for the maintained, open-source addon packs and libraries the community still updates.

Practical notes

• It is UI only. Addons reshape the interface; they do not and cannot alter the server-run game.
• The path is Interface\AddOns. Each addon goes in its own subfolder there.
• Names must match. An addon's .toc file shares the name of its folder, or it will not load.
• Prefer maintained packs. An old MMO accumulates abandoned addons, and curated packs save you testing dead ones.

For the step-by-step setup, see the Runes of Magic addons guide.