Raid recap Discord bot: every raid, posted without typing

What is a raid recap bot?

A bot that posts what happened in last night’s raid, so the guild doesn’t depend on an officer writing it up. A good recap answers the questions people ask the next morning: what died, what dropped, who got it, and who was missing.

Most recaps are written by hand, which means they’re late, short, or don’t happen. The officer who raided until midnight is the one person who doesn’t want to spend another half hour on a summary. A recap bot only works if it already knows what happened, which is why it needs a record of the raid, not just the signup sheet.

What does a GuildPro recap show?

Bosses killed and how long each took, wipes per boss, every drop with who received it, and a line comparing signups with who zoned in. That last line is the one officers end up reading first.

Section	What it shows
Bosses	Each kill, with its fight length
Wipes	A count per boss, when there were any
Loot	Who received what. The first 12 items, then a count of the rest
Attendance	How many signed up and how many zoned in, naming anyone under “Signed yes, never showed”

If everyone who signed up came, the recap says so. A raider who offered several characters on a flexible sheet and played one isn’t listed as a no-show.

On the website, the same recap also puts each drop under the boss whose loot table lists it, and has filters by item quality. If the night was matched to a Warcraft Logs report, it adds a damage and healing table and a Hall of fame & shame with awards for the night.

How does the recap get made without anyone typing it?

The GuildPro addon records the raid while you play, and the free companion app uploads it when the game saves. GuildPro then ties the raid to its signup sheet and builds the recap.

1. During the raid, the addon records boss pulls, kills, wipes, who is in the group, and loot. On WoW Forever, boss pulls come from the game’s own encounter start and end signals, so the addon doesn’t need the combat log.
2. When the game saves, the record is written to disk. WoW only saves addon data on /reload, logging out or quitting. A /reload after the last boss is the habit to build.
3. The app uploads it within a few seconds of the save.
4. GuildPro ties it to a sheet. It looks for a signup sheet starting within 12 hours of the raid, ties the best match, and closes it. That is what lets the recap name no-shows.

One raider with the addon and the app is enough. If two or three raiders run it, their uploads of the same night merge into one raid, which fills gaps if someone disconnects. Everything a recap shows is on the recaps docs page.

How do I post the recap to Discord?

Two ways: an officer selects Post to Discord on the Recaps page, or anyone types /recap in a channel. They post the same night in two different shapes.

The full options are on the /recap command page.

Is the recap posted automatically?

The recap is built automatically. Posting it is your choice, and it takes one click. GuildPro doesn’t post into your channel without someone asking. That keeps an officer in control of a night that went badly, and lets them choose the awards first.

In practice, the officer’s job after the raid goes from writing a summary to pressing one button the next morning. If your officers would rather not do even that, anyone in the guild can type /recap.

What should a guild do with recaps?

Use them as the shared record of the night, so nobody argues from memory. A recap posted the morning after settles “who got the trinket” and “how many wipes was it” before anyone asks.

The no-show line is the part that changes behaviour. A count of missing raiders gets ignored. A name gets a conversation. Keep that conversation private, though. The recap names who didn’t come, and the officer follows up in a DM, not in the channel.

Over weeks, the same records feed the guild’s Attendance and Loot pages, so the recap isn’t a one-off post but the first page of the history. Our raid attendance tracker guide covers how that history credits the bench.

Raiders can also share their own night. The My recaps tab lists the raids one of your claimed characters was in, and Share makes a public link with only your attendance, your loot and the boss list. Nobody else’s name is on it.

What about WoW Forever raids?

Forever recaps work the same way, starting with the first raids on 9 December. Barrow Deeps, Hyjal Summit and Onyxia’s Lair all open that day, per Wowhead’s raids hub. Their bosses haven’t been announced in full yet, which is why the figure above uses placeholders.

Before then, run the addon on a guild dungeon night and check that the app’s Activity list shows an upload. Then you aren’t finding a setup problem on the first raid night.

For everything else your guild should settle before 4 November, see the WoW Forever guild checklist. If you’re still choosing a signup bot, read our Raid-Helper comparison.