OlympusMute: the receipts
Every claim about the OlympusMute addon, with the code, the version table and the file it leaves on your drive.
This page exists so you do not have to take my word for any of it. Nine builds, downloaded from CurseForge on 2026-09-25 and read end to end. Everything below is checkable by you in about forty minutes.
CurseForge — all files · 404 Media · author’s post · the slur list
The nine builds
Ten version numbers, nine files. 1.0.2 is not on CurseForge. It is in the changelog (“auto-declines group invites from muted players”), and diffing 1.0.1 against 1.0.3 shows exactly those functions arriving — HandlePartyInvite, DeclinePartyInvite. Not a cover-up: a same-afternoon build superseded within hours. Note the download column.
| Version | Uploaded | Size | Downloads | Lines of Lua |
|---|---|---|---|---|
| 1.0.1 | Sep 22 | 5.3 KB | 1 | 418 |
| 1.0.2 | — | pulled | — | — |
| 1.0.3 | Sep 22 | 6.1 KB | 1 | 508 |
| 1.0.4 | Sep 22 | 7.1 KB | 1 | 599 |
| 1.0.5 | Sep 22 | 7.8 KB | 1 | 666 |
| 1.0.6 | Sep 22 | 8.9 KB | 240 | 786 |
| 1.0.7 | Sep 23 | 10.3 KB | 334 | 957 |
| 1.0.8 | Sep 23 | 13.7 KB | 1.6K | 1165 |
| 1.0.9 | Sep 24 | 24.6 KB | 1.1K | 1362 |
| 1.0.10 | Sep 24 | 26.7 KB | 702 | 1484 |
The first five builds have one download each — the author’s own upload checks. Nobody ran them. Traction starts at 1.0.6.
It cannot report anyone
Grep every build for every function that could report, message, or ignore a player. Every count is zero, in all nine:
SendAddonMessage 0 ReportPlayer 0 SendMail 0
SendChatMessage 0 C_ReportSystem 0 AddIgnore 0
The only outbound call in the entire addon is SendWho — the same /who any player can type. No loadstring, no load, no RunScript; nothing is loaded dynamically. It also wraps issecretvalue and refuses to store anything the client marks protected, which most addons never bother with.
“It streamlines false reports” — if you read that as the addon files reports, that is wrong and was never true. The author’s description is accurate: client-side, no ignore list, nobody notified.
It only stores players who match
Every path that writes a player to the list is gated on the guild name matching a keyword you set. Walk past a thousand players and it keeps none of them, unless their guild matches:
if IsOlympus(guild) then Block(guid, name, guild)
elseif guild then Unblock(guid, name) — different guild: deleted
Six Block() call sites, all guarded. The default keyword list is one word, olympus, with a three-character minimum and a comment reading “stops ‘a’ from muting half the server”. The keyword is yours to change.
The file it leaves on your drive
A chat message does not carry the sender’s guild, so the filter cannot check one. It reads a saved list instead — which means the list has to persist. It is written to WTF\Account\<ACCOUNT>\SavedVariables\OlympusMute.lua as plain text, and it looks like this:
["names"] = {
["brightblade-whitemane"] = "OLYMPUS",
["thokgar-whitemane"] = "OLYMPUS II",
["mordrek-faerlina"] = "OLYMPUS IX",
},
["guids"] = {
["Player-5827-0A1B2C3D"] = "brightblade-whitemane",
["Player-5833-0C2D9E10"] = "mordrek-faerlina",
}
Character name, realm, guild, and a permanent per-character ID, for every member of that guild you have walked past. Sorted. Deduplicated. Nothing in it ever expires — the addon makes no call to time(), date() or GetServerTime anywhere, and holds no timestamps. It only grows.
Nothing about you is stored. Your own character ID is held in memory to avoid muting yourself and is never written to the file.
There is no export button, and none is needed
The in-game list is drawn as a text label — you cannot select it, copy it, or dump it to chat. No export command exists in any build. It does not matter. The file is already the export, in the simplest parseable format there is.
And the author said how it was built:
Was there any AI involvement in making it? — Yes, it was vibe coded, mostly made it for myself, never expected it to get this much traction.
Which is the point. A working addon in an afternoon, by someone with no particular intent. Parsing the file it produces and walking the list is the same afternoon by the same method — and that second program never gets uploaded, reviewed, or written about.
What I am and am not claiming
Not claiming: that the author built a harvester, that he intended any of this, that anyone has misused the file, or that the outlets coordinated anything.
Claiming: to make a mute button you need a mute list; that list is a roster; it is on thousands of drives; nothing expires; and at that scale whether somebody eventually points a script at one stops being a question about intent and becomes arithmetic.
Three outlets wrote this up inside twenty-four hours. One interviewed the author and printed his own summary of his own tool as the description of how it works. Not one of them appears to have opened it. It is nine downloads and a text editor.
Check it yourself, onichan. That is the whole point of this page. 💜