One message per raid, kept up to date
As people sign up, change their minds or are benched, the same message is edited, so the channel stays tidy. A raid called off says so.
For Guildheim, the World of Warcraft guild addon
Your raids, posted to Discord. Kept up to date.
Guildheim Companion sends your guild's raids, loot and attendance from the game to your Discord channel. Each raid gets one message, and as people sign up, that same message changes.
Version 0.1.0 · 43 MB · Windows 11, 64-bit
#raid-sign-ups
Molten Core
Thursday 5 November 2026 20:00 (in 3 days)
Team: Main raid
Fire resistance gear, please. Invites from 19:45.
18 of 40 signed up · Tanks 3/4 · Melee 6/12 · Ranged 5/14 · Healers 4/10
🛡️ Tanks (3): Thorgrim, Brannoc, Hildra
⚔️ Melee (6): Vossa, Grimtusk, Ardent, Selwyn, Morrow, Kael (late)
🏹 Ranged (5): Ysolde, Pellin, Quill, Nerith, Ashka
💚 Healers (4): Mira, Osric, Lunewyn, Talwen
❔ Tentative (1): Dovan
🪑 Bench (1): Rook (edited)
The same message, edited each time someone signs up. The names here are made up.
How it works
From the game to your channel
An addon cannot reach the internet. So Guildheim writes its posts into its own saved file, and Guildheim Companion, a small program on one officer's computer, sends them on.
-
In the game
Guildheim writes the post
Make a raid, take sign-ups, record the night: Guildheim keeps each post ready.
-
At a /reload or log-out
The game saves it
Each time you type
/reloador log out, the game writes Guildheim's file. -
On your computer
The companion sends it
It posts what is new and edits what changed, so each raid keeps its one message.
What it posts
A tidy channel your raiders can read
No pings, no link previews
Nothing it posts mentions anyone, so an "@everyone" in a raid's note stays plain text.
Quiet until the game saves
It sits beside the clock on Windows, or in the menu bar on a Mac, and starts with your computer if you like.
Loot and attendance after each raid night
Once the night is over: what dropped and who got it, and who was there, late or left early. If you choose a day, a look back at the guild's week as well.
Loot: Molten Core, 5 November 2026
2 bosses killed · 3 items
Lucifron
Choker of Enlightenment → Mira
Magmadar
Earthshaker → Grimtusk
Striker's Mark → Ysolde
Attendance: Molten Core, 5 November 2026 (17)
For Molten Core, 20:00
Ardent, Ashka, Brannoc, Grimtusk, Hildra, Kael, Lunewyn, Mira, Morrow, Nerith, Osric, Pellin, Quill, Selwyn, Talwen, Thorgrim, Ysolde
⏰ Late: Kael
🚪 Left early: Pellin
Download
Guildheim Companion 0.1.0
For Windows and Mac. Nothing else to install alongside it. It needs Guildheim 0.2.2 or later in the game.
Windows
Windows 11, 64-bit · Windows 10 not tested
SHA-256, to check the download
f8f41536472c61ecd4df5165bb902e8ab7dfbe5232a255be02431dabadd9d01b
Mac
macOS 15 (Sequoia) or later
SHA-256, to check the download
Apple chip
12b813512adedee4585b41b5d15351fae5fa0d04bfd515d7e0f78a0f0cdd76f8
Intel
14e3f78c773f1140f61d462b85affcfdb84a198fc1bc092aef346f17e39904af
It is not signed with a paid certificate, so the first time you run it your computer asks whether to trust it. What you will see.
Setting it up
Four steps, once
-
In the game
With Guildheim 0.2.2 or later, switch on Discord companion at the bottom right of the Raids page's Loot view, or type
/heim companion on. Then type/reload. -
In Discord
Someone who may manage the channel opens its settings (the gear beside its name), then Integrations, Webhooks, New Webhook and Copy Webhook URL.
-
Download and run it
Unzip it and run it. The first time, your computer asks whether to trust it: see below.
-
On its Set up page
It finds World of Warcraft's folder by itself (or click Choose…). Pick the game and your account, paste the webhook beside your guild, click Save, then Send a test message and look in the channel.
It starts from now. Whatever
Guildheim already holds when you set it up counts as sent, so your channel is not filled with old posts. The
first post comes at your next change and /reload.
Only one person in a guild should run it, or every raid is posted twice. Guildheim tells you if someone else in your guild already has it switched on.
The first time you run it
Your computer will ask first
Guildheim Companion is not signed with a paid certificate, so your computer cannot tell who made it and asks you once. To be sure your download is the one published here, compare its SHA-256, a fingerprint of the file, with the one under its download button.
Windows
- Unzip the download (right-click it, Extract All…) and open the folder it makes.
- Run GuildheimCompanion.exe.
- Windows shows "Windows protected your PC". Click More info, then Run anyway.
To check the download first: in PowerShell, Get-FileHash .\GuildheimCompanion-0.1.0-windows.zip.
Mac
- Drag Guildheim Companion into your Applications folder, and open it.
- macOS says Apple could not check it: click Done.
- Open System Settings, Privacy & Security, scroll down, click Open Anyway beside Guildheim Companion, and confirm with your password. (Since macOS 15, right-click and Open no longer gets past it.)
To check the download first: in Terminal, shasum -a 256 and the zip's name.
If you tick Start when I log in and later move the program, tick it again.
Privacy
What it reads, and what it sends
It reads
Only the posts Guildheim writes for it, in Guildheim's saved file under your World of Warcraft folder's
WTF. Nothing else of the game's, and it never writes into the game's folder.
It sends
Those posts, to the one Discord webhook you paste in, and nowhere else. It does not check for updates, count anything or send anything about you or your computer.
Your webhook stays with you
Its address is kept on your computer only, and shown hidden. Anyone with it can post in the channel: if it gets out, delete the webhook in Discord and make a new one.
Its own files
Its settings, a record of what it has sent, and a log: %APPDATA%\GuildheimCompanion on Windows,
~/Library/Application Support/GuildheimCompanion on a Mac.
This page has no cookies and no counters, and loads nothing from anywhere else.
What's new in 0.1.0
- Posts Guildheim's raids to your Discord channel, and keeps them up to date. Each time the game writes Guildheim's file (at /reload and logout), it posts what is new and edits what changed in place, so a raid keeps its one message as people sign up. A message deleted in Discord is not posted again.
- No pings and no link previews. Every message is posted as "Guildheim", mentions nobody, and shows no preview under a link.
- Set up once: it finds World of Warcraft's folder by itself (or you choose it), with the game and the account that have Guildheim's file. Paste each guild's webhook address (it is kept on your computer only, and shown masked), and Send a test message to see it reach the channel.
- Start from now, or post what is there: by default, what Guildheim already holds when you set it up counts as sent, so the channel is not filled with old posts.
- Status and Log pages: when it last read the file and what it last sent for each guild, anything stopping it, and a log of what it did.
- For Windows and Mac: Windows 11 (64-bit), and macOS 15 or later in two downloads, one for Macs with an Apple chip (M1 or later) and one for Intel Macs.
- Runs in the tray. Closing the window keeps it running (the notification area on Windows, the menu bar on a Mac, where its Dock icon opens the window again); quit from the tray icon's menu, or the Status page's Quit, which asks first. Cmd+Q on a Mac, and logging out of the computer, quit it at once. It can start when you log in to the computer (off unless you tick it).
- One copy at a time, so nothing is ever posted twice; a second copy says the first is running.
- Copes with Discord and the internet: it waits when Discord asks it to slow down, tries again (from a minute up to every 15 minutes) when there is no internet, and stops at once, asking for a new address, if the webhook is deleted.
Removing it
Quit it (its icon beside the clock or in the menu bar, or the Quit button on its Status page), then delete the program and its own folder (under Privacy, above). If you ticked Start when I log in, untick it first.