A raid signup bot that knows a Druid from a Mage.
Slash command, signup post, buttons, done. The bot checks class against role on every click, tracks composition live, locks the raid 30 minutes before pull, and pings the bench when someone ghosts. All of it where your guild already hangs out.
Druid clicks tank, bot says yes.
Mage clicks tank, bot says nice try.
One signup post. Buttons that check your spec.
Post a raid with /raid create and the embed lands in your raid channel: leader, instance and difficulty, scheduled time, soft reserves, per-class signups with spec and role emoji, and bench, tentative, and absent sections that fill in as people click.
A raider hits a role button and the bot confirms the character can actually play it. Healers can bring an alt without signing up again, leave a note on their row, drop a parse link, or confirm their addons on the way in. Non-members get pointed at verification or the public link instead of a wall.
- Tank, Healer, DPS, Tentative, Absent, or Withdraw, one button each
- Class and spec checked before the role sticks
- Bring an alt without signing up twice
- Leave a note, a parse link, or confirm your addons on the way in
- FjorvaltProtection WarriorTank
- BrightleafRestoration DruidHealer
- SkarnCombat RogueDPS
- EmberwickFire MageNice try
The signup embed in Discord. The owl turns down a role the character can't fill before it ever reaches your lineup.
The raid runs itself near pull time.
A scheduler ticks every minute. It locks, benches, builds voice, DMs the lineup, and archives when it's over. You show up and pull.
Auto-lock 30 minutes before pull
The scheduler locks signups and benches the overflow before the stone, so the lineup that posts is the lineup you raid. No frantic last-minute shuffle while people zone in.
Bench pings when someone ghosts
Tentatives get a 30-minute nudge to confirm. Raiders who never signed get a 24h and a 2h DM, away mode respected, the 2h skipped when the roster is already full. The owl chases people so you do not have to.
Voice and start DMs on lock
Lock the raid and the bot spins up a voice channel, drops everyone into groups, and DMs each confirmed signup their role, party, voice, soft reserves, and assignments. One voice room per instance for the bigger nights.
Auto-archive when it is done
Finish posts a farewell, a loot summary, and the attendance widget, then closes the voice channel and archives the thread. The raid cleans up after itself instead of lingering in the channel list until next Tuesday.
- No guild membership, no account setup, just Discord identify
- Type a character name, the page pulls the armory data
- Pick a main role and an optional alt role
- A raid leader approves, the player gets a one-time invite at lock
Need a PUG tank? Hand them a link.
Make a raid public and you get a signup page anyone can open. The player types a character name, the page pulls the armory data, and they apply. A raid leader approves in Discord, and the approved PUG gets a one-time server invite the moment the raid locks.
There's also a guild-wide link for your own roster: existing characters get signed in with no Discord account at all. Both validate class and spec against your flavour, same as the buttons do.
Recurring series, voice, and the web planner.
The Tuesday raid shouldn't be a manual chore every week. The deeper editing lives on the web when you want it.
Recurring raid series
Set a weekly or every-N-week cadence and the scheduler drafts the raids ahead of time, asks for approval, and posts each one a few days out. The Tuesday Karazhan run shows up on its own.
Raid voice channels
Lock the raid and the voice channel appears, scoped to the people in it, PUG guests included. When the raid finishes it closes again. No orphaned voice rooms cluttering the server.
The web planner
Drag names between groups, bench the overflow, post the lineup back to Discord. Edits sync to the Discord embed live. A companion for officers who'd rather drag than type.
No more 'who's tank tonight'.
The chore was never the raid. It was the bookkeeping around it.
You know the drill. The weekly 'who's tank tonight' spam in chat. A pinned message with reaction emoji. The 7:55 scramble of 'wait, do we have a second tank', a Boomkin who reacted with the shield emoji because it looked cool, and three healers all assuming the other two signed.
The bot does the bookkeeping. Class and spec checked at the button, composition counted as you go, the lineup locked before pull, and the people who ghosted already pinged. The owl handles the part nobody volunteered for.
Calendar with a tank emoji vs. raid ops.
- A calendar that doesn't know what a Druid is
- A Mage can click tank and nobody notices until pull
- You count healers by hand at 7:55 every week
- Recurring events sit behind a paywall
- Nobody gets pinged when they ghost the raid
- Class and spec checked on every signup
- Composition tracked live as people click
- Auto-lock, auto-bench, auto-voice, auto-archive
- Recurring raid series with an approval queue
- Bench pings and unsigned nudges on a timer
Push the raid button.
Add HootusPlootus, walk the wizard, post your first signup. The owl checks the comp, locks the raid, and pings the bench. Nobody types 'who's tank tonight' for the rest of the tier.
Back to everything it does