Beacon
The landscape of user interface customization in World of Warcraft has shifted dramatically with the arrival of the Midnight expansion and patch 12.0.7. For years, players relied on a single powerhouse addon to track buffs, debuffs, cooldowns, and boss mechanics. However, recent changes to the game API have rendered many legacy tools obsolete. Enter Beacon, a community-driven fork designed to bridge the gap and restore functionality to your screens when the original project paused updates. This article explores how this innovative tool is keeping the spirit of deep customization alive during a transitional period for the game.
Why Beacon Exists in the Current Meta
Blizzard's latest restrictions on accessing certain combat values, often referred to as "secret values," broke a significant portion of existingWeakAuras setups. Triggers relying on health, power, specific auras, or combat log events simply stopped firing because the game no longer exposes that data to addons in the same way. The original development team halted shipments for the 12.0 game API to assess these new boundaries. Beacon emerged as an independent solution with a clear mission: get a WeakAuras-style editor loading and functioning on patch 12.0.7 immediately, working around restrictions piece by piece.
It is crucial to understand that this is an early access build, currently sitting at version 0.1.0. While it loads cleanly without Lua errors and offers a fully functional display editor, it does not yet support every trigger type found in the predecessor. The developers are prioritizing triggers that still work within Blizzard's new rules, specifically focusing on Boss Mod triggers and custom event-driven logic.
What Works and What Does Not
If you are looking to download Beacon to fix your raid frames or cooldown trackers, you need to know its current capabilities. The addon successfully handles:
- The Full Display Editor: You can create regions, sub-elements, conditions, animations, and groups just like before.
- Save and Load Functions: Your custom displays are preserved safely in their own database.
- Boss Mod Triggers: Timers and announcements from DBM (Deadly Boss Mods) and BigWigs function correctly.
- Custom Triggers: Event-driven scripts that do not rely on hidden combat values operate as expected.
Conversely, there are notable limitations due to game-side restrictions. Aura, spell, cooldown, unit, health, power, and standard combat log triggers are currently unavailable. Because Blizzard hides these values from addon code in the 12.0 environment, no addon can read them reliably until the developer provides new APIs. If your custom code attempts to read these hidden values, it may degrade rather than function fully. This is not a bug in Beacon for World of Warcraft but a fundamental change in how the game client operates.
Installation and Compatibility Across Expansions
Installing this addon follows the standard procedure for any modification. You place the files, which include Beacon, BeaconOptions, BeaconModelPaths, and BeaconArchive, into your Interface/AddOns folder. On the character selection screen, you may need to enable "Load out of date AddOns" if the version check fails. Once in-game, you can open the interface with the slash commands /beacon or /bc.
While Beacon is currently optimized for Retail patch 12.0.7, the conversation around UI mods often spans multiple versions of the game. Players still enjoying Classic, TBC, WotLK, Cataclysm, or MoP generally do not face these specific API restrictions, meaning the original WeakAuras often suffices there. However, for those on the cutting edge of Retail, knowing how to install this specific fork is vital for maintaining a competitive edge in raids and Mythic+ dungeons.
For users who prefer a streamlined setup process without manually moving files between folders, the foxygame.net launcher offers a compelling alternative by featuring a curated addon catalog where you can locate Beacon and handle its version compatibility automatically. This one-click install approach ensures that you always have the correct build for the current patch, removing the guesswork from updating your UI after a game maintenance window.
Coexisting with Legacy Addons
A common concern among players is whether installing this fork will conflict with their existing setup. Rest assured, Beacon uses its own saved variables and does not touch your existing WeakAuras database. You can keep both installed simultaneously; they will not fight over settings. However, note that Beacon does not automatically import your existing WeakAuras strings or database. You will need to rebuild or re-import specific strings compatible with the new trigger types supported by the fork.
The Roadmap Ahead
The development team is moving fast. The roadmap includes re-enabling more trigger types as solutions for handling them in patch 12.0 are discovered. Future updates aim to support importing WeakAuras and Wago strings directly, as well as finding ways to show protected values like health and power through the limited APIs that still accept them. General polish and stability improvements are also high on the list.
In conclusion, while the transition to the Midnight expansion has introduced hurdles for UI customization, the community response has been swift. Beacon represents a resilient effort to maintain the depth of information available to players. By focusing on what works now—Boss Mods and custom events—it keeps raiders informed while waiting for broader API access. As the addon matures, it promises to become the definitive solution for Retail players navigating these new restrictions.