Olympus Guild Addon for WoW Forever: Census and Layer Hop in 5 Steps [2026]

By Indie Kings | October 2, 2026

Updated October 2, 2026: The Olympus guild federation passed 10000 beta members in WoW Forever and now tracks that army in one live census window per the dnl-gentile/olympus-addon GitHub README. This guide shows census plus layer hop setup in 5 steps so Alliance PvP members can find guilds, read zones and join the right layer with consent.

Image: Olympus census window. Credit: dnl-gentile via GitHub.

What the Olympus addon is

Olympus is a fan made guild federation addon for WoW Forever, built around the Alliance PvP community led by Asmongold, per the dnl-gentile/olympus-addon GitHub README. The README describes a federation that grew past 10000 beta members across many guilds capped at 1000 members each, which is why a normal guild roster cannot show the full picture. The addon answers that scale problem with one Blizzard style window that lists every Olympus guild live, with census totals, online now counts, zones per continent, hover details and hierarchy views.

The same README presents the project as open source under MIT with 168 commits at the time of review, which signals active iteration during beta rather than a one off release. That history matters because beta clients change fast and guild tooling must keep pace with roster churn, layer behavior and chat limits. Readers should treat commit count as context for momentum, not as a quality score, and should always pull the latest release before raid night [NEEDS VERIFICATION].

The core promise is simple to state and hard to build. One window shows the whole federation so a member can see where players are, who leads each guild, which guilds recruit and which layer holds the main force. Per the dnl-gentile/olympus-addon GitHub README, the window covers census totals plus online now plus zones per continent plus hover details for deeper inspection. That combination turns scattered guild rosters into a single readable map of a 10000 person army.

The hierarchy view is called Realm in the addon, and it lists King plus Lords plus Captains plus Treasurer plus mentors plus level race plus recruiting status, per the dnl-gentile/olympus-addon GitHub README. Layers are named per top member in that view, which makes it easier to say where you are and where you need to go during world PvP or guild events. If you have used guild roster tools before, expect a familiar Blizzard style layout with federation wide scope that the stock UI does not provide [NEEDS VERIFICATION].

Two limits frame the whole guide. First, only members of Olympus named guilds participate in federation features such as layer hop and rank channels, per the dnl-gentile/olympus-addon GitHub README. Second, this is a fan addon and it is NOT official Blizzard software, per the dnl-gentile/olympus-addon GitHub README. That fan status affects support paths, update speed and trust decisions, so get the file from the official repository and verify version notes before you install [NEEDS VERIFICATION].

Beta forgets addon data at login, per the dnl-gentile/olympus-addon GitHub README. That line explains why settings, caches or local census snapshots may reset between sessions during Forever beta. Plan for re sync time after each login during events, and do not assume that a zone count from last night is still exact tonight. The sections below show how to rebuild that picture in minutes with the 5 step flow.

Census and layer hop in 5 steps

The fastest way to use Olympus is to follow one pass in order. Confirm membership, install and open the window, read census and Realm, join chats and layer hop with consent, then mind privacy and key sealing. Each numbered item below expands that checkpoint with what to click, what to expect and what to verify from the README. Steps that go beyond the README are marked [NEEDS VERIFICATION] so readers can separate documented behavior from practical setup tips.

1. Step 1: Confirm Olympus guild membership on the right character. Federation features only work for members of Olympus named guilds, per the dnl-gentile/olympus-addon GitHub README. Open the stock guild panel and check that your current character shows an Olympus guild tag before you troubleshoot missing census rows or greyed hop buttons. If you have alts outside the federation, switch to the guilded character first because cross character sync across non member rosters is not part of the documented design [NEEDS VERIFICATION]. The Join Olympus screen can help unguilded players find recruiters through rate limited /who queries with do not contact flags respected, per the dnl-gentile/olympus-addon GitHub README. Use that finder during active hours, wait through rate limits instead of spamming invites, and respect any do not contact marker you see. If no recruiter answers, try a different zone or time rather than repeating requests in chat [NEEDS VERIFICATION]. Membership also determines channel access. Rank channels include Olympus plus Captains plus Lords, per the dnl-gentile/olympus-addon GitHub README. A character outside those ranks or outside the federation will not see the same chat set, so missing channels usually point back to guild tag or rank rather than to a broken install.
2. Step 2: Install the addon and open the main window. Get the addon from the official dnl-gentile/olympus-addon GitHub repository and check that the release notes match Forever beta 1.60.1 or another tested build listed below, per the dnl-gentile/olympus-addon GitHub README. Standard WoW addon install flow places the extracted folder in the Interface AddOns directory with a client restart after copy [NEEDS VERIFICATION]. Confirm the addon appears as enabled on the character select addon list before you log into the world [NEEDS VERIFICATION]. Open the main Blizzard style window once in game through the documented button, minimap icon or slash command [NEEDS VERIFICATION]. Expect one window that aggregates every Olympus guild live, not a set of separate guild roster tabs. If the window opens empty, wait for the first census sync to complete, then check version mismatch nudges described in a later section. Beta forgets addon data at login, per the dnl-gentile/olympus-addon GitHub README, so allow a short rebuild window after each login before you judge counts as wrong. Bug reports go to the author through the repository path described in the README, per the dnl-gentile/olympus-addon GitHub README. Include client build, addon version and steps to repeat when you file, because federation bugs often depend on guild size, zone load or layer state [NEEDS VERIFICATION].
3. Step 3: Read census, zones and Realm hierarchy. Start with census totals and online now to gauge federation strength at a glance, per the dnl-gentile/olympus-addon GitHub README. Totals answer how large the federation is across all guilds, while online now answers how many are actually available for grouping, mustering or world PvP. Use zones per continent next to see where those online players stand, then hover for details when you need guild by guild or zone by zone breakdowns. The hover layer is where the window earns its keep during events, because it turns a flat headcount into a map of pressure across Eastern Kingdoms, Kalimdor and event zones [NEEDS VERIFICATION]. Read Realm hierarchy after the map view. King plus Lords plus Captains plus Treasurer plus mentors are listed with level race and recruiting status, per the dnl-gentile/olympus-addon GitHub README. Layers named per top member sit in the same view, which lets callers say join the layer named for a specific leader instead of reading numeric layer IDs that players forget under stress. Recruiting flags deserve a separate look. If your guild seeks members, confirm that your recruiting marker is accurate so Join Olympus seekers can find you. If you seek a guild, use recruiting flags plus online counts to pick an active guild in your time block rather than a full but quiet roster [NEEDS VERIFICATION]. Level race entries show progression competition across the federation, which is useful context during beta leveling pushes but not a substitute for direct officer notes on requirements [NEEDS VERIFICATION].
4. Step 4: Join rank chats, answer decrees and layer hop only with consent. Join the rank channels that match your standing. Channels include Olympus plus Captains plus Lords, per the dnl-gentile/olympus-addon GitHub README. Pinned lines keep orders visible at the top of those chats, which helps late arrivals catch up without scrolling hundreds of lines during an event. Watch for decrees in the same flow. Decree types include Call to Arms plus Muster plus Royal decree plus Tabard inspection, per the dnl-gentile/olympus-addon GitHub README. Each type carries a different social weight, from rally calls to formation orders to cosmetic checks, so read the pinned text before you move. Version check and update nudges also travel through the addon, per the dnl-gentile/olympus-addon GitHub README. If you see an update nudge, update before you report chat or hop failures, because mixed versions are a common cause of missing messages during beta [NEEDS VERIFICATION]. Layer hop is the most sensitive action in this step. The flow offers one click ask to join the King layer with consent flows on both sides, plus vouching rules and 90 second guest handling, per the dnl-gentile/olympus-addon GitHub README. Only members of Olympus named guilds participate. The requester asks, the other side must consent, vouching rules gate who can vouch for guests, and guest state lasts 90 seconds under the documented handling. Do not treat a hop request as a teleport order. Wait for accept, confirm the layer name after arrival, and release or re request cleanly if consent times out [NEEDS VERIFICATION]. Block terms including shared lists filter chat noise across those channels, per the dnl-gentile/olympus-addon GitHub README. Keep block lists current during large events and lean on pinned lines for orders rather than reposting the same call every minute.
5. Step 5: Mind privacy because channels are public to channel members and sealing needs a key. Channels are NOT encrypted by default. Anyone on the hidden channel can read all ranks, per the dnl-gentile/olympus-addon GitHub README. That single sentence should shape every message you send in Olympus, Captains or Lords chats. Assume that presence on the channel equals read access to that channel, regardless of nominal rank labels. Seal with /oly key when you need restricted talk, per the dnl-gentile/olympus-addon GitHub README. Key sealing is the documented path to narrow readability rather than relying on rank names alone. Rotate or re issue keys through officer paths when membership changes, and confirm that the members who need access have sealed correctly before you share sensitive plans [NEEDS VERIFICATION]. Limit what is visible by limiting what you type. The privacy table in the next section maps common data types to practical controls, including what census shows, what chat shows and how key sealing changes exposure. As a rule, keep rally times in pinned public lines, keep exact ambush details sealed or off addon chat, and keep personal details out of federation wide channels [NEEDS VERIFICATION]. Report issues and privacy questions to the author through repository channels rather than testing exposure by posting bait in live chats, per the dnl-gentile/olympus-addon GitHub README. Clean reports protect the federation while the fix ships.

Feature map

This section maps the five documented pillars to what each one shows and when to use it. All feature facts in the table are per the dnl-gentile/olympus-addon GitHub README. Practical timing notes outside the table are marked [NEEDS VERIFICATION] where they reflect beta event habits rather than README text.

Census rewards a two pass habit. Glance at totals and online now for strength, then drill into zones per continent when you need to move players rather than admire numbers. Hover details fill the gap between federation scale and street level action, such as which guild holds a zone or which continent thins out late at night [NEEDS VERIFICATION].

Realm hierarchy rewards name based calls. Saying the layer named for a visible leader is faster and less error prone than reading layer numbers over voice during PvP. Pair that with recruiting flags so seekers and officers find each other without blind whispers across 10000 members [NEEDS VERIFICATION].

Layer hop rewards patience. The consent flow protects both sides, vouching keeps guests accountable and the 90 second guest window keeps layer state clean. Request once, wait for the answer and confirm arrival before you pull or start an event timer [NEEDS VERIFICATION].

Decrees plus pins plus block lists reward brevity. One clear decree plus one pinned line beats fifty repeated chat lines. Shared block terms cut spam across shards of the same conversation, while version nudges keep everyone on the same message format during beta churn [NEEDS VERIFICATION].

Privacy and channel limits

Privacy in Olympus starts from one clear README warning. Channels are NOT encrypted and anyone on the hidden channel can read all ranks, per the dnl-gentile/olympus-addon GitHub README. Sealing with /oly key is the documented control for narrowing that exposure. The table below translates that warning into daily choices.

The practical rule is to match channel to sensitivity. Public federation chat carries rally times, muster points and tabard checks. Sealed talk carries ambush timing, exact layer stacks and officer decisions. Personal contact details belong outside addon channels entirely [NEEDS VERIFICATION].

Key hygiene matters more as the roster turns over. Beta guilds recruit fast, alts multiply and ranks shift after events. When officers change or a key leaks into a wider chat, re seal and confirm receipt rather than assuming the old key still bounds the audience [NEEDS VERIFICATION].

Do not contact flags and rate limits deserve the same respect as key discipline. The Join Olympus screen finds recruiters via /who with rate limits and do not contact flags, per the dnl-gentile/olympus-addon GitHub README. Treat a flag as a hard stop, slow down when the addon warns about limits and move on to another recruiter or time slot instead of forcing contact.

Finally, remember that block terms filter noise but do not create secrecy. Shared block lists hide spam from view, they do not encrypt the underlying channel. If a message must stay private to Captains or Lords, sealing is the control to use, not a block term [NEEDS VERIFICATION].

Build compatibility and install notes

Compatibility is stated plainly in the README. The addon is built for Forever beta 1.60.1, and it is also tested on Classic Era 1.15 and Anniversary 2.5, per the dnl-gentile/olympus-addon GitHub README. Match your client to one of those lines before you report a bug, because beta drift explains a large share of roster and chat issues. If you run a newer beta than 1.60.1, expect possible breakage until the author posts an update [NEEDS VERIFICATION].

Fan status shapes expectations. This is a fan addon and it is NOT official Blizzard software, per the dnl-gentile/olympus-addon GitHub README. Blizzard support will not fix federation sync, and server side changes can alter census or layer behavior without warning. Track the GitHub repository for release notes, version check nudges in game and author guidance after each Forever beta patch [NEEDS VERIFICATION].

Install hygiene helps across all three supported builds. Download only from the official dnl-gentile/olympus-addon GitHub repository path, verify the release tag matches your client line and keep a copy of the prior working version until the new one proves stable in your guild [NEEDS VERIFICATION]. Standard extraction into Interface AddOns plus a full client restart remains the baseline flow on desktop clients [NEEDS VERIFICATION]. Version check and update nudges inside the addon warn when the federation moves ahead of you, per the dnl-gentile/olympus-addon GitHub README. Treat a nudge as a hard prompt during event weeks. Update, relog, allow census to rebuild and then rejoin rank channels before you conclude that data is missing.

Beta data loss is normal on Forever right now. Beta forgets addon data at login, per the dnl-gentile/olympus-addon GitHub README. That means local caches and settings may clear between sessions. Keep key material stored safely outside volatile addon storage where officers instruct, re seal after relog if needed and rebuild census before prime time rather than during muster [NEEDS VERIFICATION].

When something still fails, report it cleanly. Bug reports go to the author, per the dnl-gentile/olympus-addon GitHub README. Include client build such as Forever beta 1.60.1 or Classic Era 1.15 or Anniversary 2.5, addon version, guild name and size context, zone and layer at failure time, plus exact steps to repeat. Clean reports shorten fix cycles for a 10000 member federation where every broken sync multiplies across hundreds of clients [NEEDS VERIFICATION].

License context is brief but useful for officers who redistribute packs. The project is MIT licensed, per the dnl-gentile/olympus-addon GitHub README. That license permits broad reuse with attribution under its terms, but guild pack maintainers should still link the upstream repository, preserve license notices and avoid shipping stale forks that split version state across the federation [NEEDS VERIFICATION].

FAQ

What is the Olympus addon in one sentence?
It is a fan federation addon that shows every Olympus guild live with census, Realm hierarchy and consent based layer hop in one Blizzard style window, per the dnl-gentile/olympus-addon GitHub README.

Who can use census and layer hop?
Only members of Olympus named guilds participate in federation features, per the dnl-gentile/olympus-addon GitHub README, so confirm guild tag and rank before troubleshooting.

How does layer hop consent work?
One click asks to join the King layer with consent on both sides plus vouching rules and 90 second guest handling, per the dnl-gentile/olympus-addon GitHub README.

Are officer chats private?
No, channels are NOT encrypted and anyone on the hidden channel can read all ranks, per the dnl-gentile/olympus-addon GitHub README, so seal sensitive talk with /oly key.

Which game builds are supported?
Forever beta 1.60.1 is the build target with Classic Era 1.15 and Anniversary 2.5 also tested, per the dnl-gentile/olympus-addon GitHub README, and beta forgets addon data at login.

Is this an official Blizzard addon?
No, it is a fan addon and NOT official Blizzard software, per the dnl-gentile/olympus-addon GitHub README, so get updates from the GitHub repository and send bug reports to the author.

Bottom Line

A 10000 member federation cannot run on guild roster tabs alone. Census plus Realm plus consent based hop compress that scale into one window where leaders can see strength, name layers by leader and move players with permission rather than spam. Update to the matching build, confirm Olympus membership, seal what must stay private and let pins plus decrees carry the public plan.

Start with the 5 step pass on your main guilded character. Read totals before you move anyone, read Realm before you call a layer, request hops instead of demanding them and re check version nudges when data looks thin. That loop keeps a beta scale army readable through patch churn and login resets.

Sources

Feature, privacy, compatibility and scale facts in this guide are per the dnl-gentile/olympus-addon GitHub README. Practical install paths, timing habits and event tips outside quoted README behavior are marked [NEEDS VERIFICATION].

• dnl-gentile/olympus-addon GitHub README