Post the raid in one command. Run the whole guild from one bot.
One Discord command posts the night. Then Hootus checks signups against class and spec, marks who actually showed up from raid voice, keeps your Blizzard roster honest, and scopes PUGs to the raid. The WoW stuff a calendar bot was never built for.
The whole guild, run from Discord.
The overview is right here. Each piece has its own page when you want the detail.
/raid posts the night, auto-locks 30 minutes before pull, and closes itself when it is done.
Members verify a character, the roster syncs hourly. Alts and respecs included, no spreadsheet.
Every Tank, Healer, and DPS click checked against class and spec. The Mage cannot tank.
Build the lineup by moving names, on a desktop or a phone, then post it back to Discord.
Auto check-in when they hit raid voice, timestamped, with a flag for who left early.
Apply page to approve button. PUGs get a raid-scoped role that takes itself back after.
/lfg for dungeons, heroics, alt runs, or PvP, with the roles you need and a pinned board.
Native reserves with Gargul export, and a loot-fairness score for the officer meeting.
A taste of the Discord buttons. The real thing posts to your raid channel and pings the bench when a role goes missing.
Sign the slots. Watch it check the class.
Go on, fill the raid. Every signup is checked against class and spec before it lands, and the composition fills as you click. Then tell the Mage to tank and see how that goes.
This is the real rule, not a mockup. A Druid can tank, a Mage cannot, and the bot says so on the spot instead of the raid lead finding out at pull.
Signups say they're coming. Voice says they showed.
Join the raid voice channel and Hootus checks you in, with the timestamp to prove it. No counting reactions, no scrolling back through who swore they would be there. The lead can still fix any mark by hand, because the lead always wins.
- Auto check-in the moment someone hits raid voice, timestamped
- Slip out before the last boss and Hootus flags it
- Show-up and no-show rates over the tier, bench rotation tracked
- The post-raid report goes to officers privately, confirm before it lands
- FjorvaltPresentvia voice · 19:58
- BrightleafPresentvia voice · 20:01
- MournhowlPresentleft early · 21:30
- SkarnNo-showmarked by lead
Hootus reads who joined raid voice, not your combat log, so the override is there for the alt-runner and the raider with comms off.
Two flavours live. Same bot underneath.
The core works the same on every flavour. The per-expansion stuff is just deltas.
The core that ships the same on TBC, MoP, and every flavour after.
- Blizzard-verified roster sync
- Class and spec-aware signups (no Mage tanks, ever)
- Soft-res routing per raid post
- Recruitment apply page with officer routing
- Auto-lock at minus 30, bench ping, post-raid cleanup
- Per-guild Discord roles, channels, permissions
- Multi-instance raid posts (run two 10-mans on the same night)
- 9 raid types (Karazhan to Sunwell)
- 16 dungeons in /lfg
- Monk specs (Brewmaster, Mistweaver, Windwalker)
- 3-man scenarios in /lfg
- Difficulty tracking (Normal, Heroic, LFR, Flex)
Five minutes from invite to first signup.
No YAML, no config repo, no Discord-bot-hosting tutorial.
- 01
Add the bot
One click, OAuth handles the rest. It lands in your server with the permissions it needs and nothing it doesn't.
- 02
Walk the wizard
Pick TBC or MoP, point it at your channels, map your ranks. Five minutes, no config files, no YAML.
- 03
Push the raid button
Your first signup post lands in the raid channel. Nobody types 'who's tank tonight' for the rest of the tier.
Built for raid night, not bolted onto a calendar.
A general scheduler can post an event. Hootus is built around the WoW parts a calendar never had to care about.
- Post a raid with one command instead of clicking through a form
- A roster pulled from Blizzard, alts and respecs included
- Every signup checked against class and spec
- Attendance from raid voice, timestamped, not a list of who said they would come
- PUGs scoped to the raid, not the whole server
- Recurring raids and the web planner with nothing behind a paywall
The owl talks back.
Same bot that locks your raid also has opinions. Here's the kind of thing it says.
Empty group, nobody but the poster? I'll bow out quietly instead of announcing a party of one.
On an LFG that never filled
Owls Across Time Zones. Bring an Alt, Ping the Right Owls.
Real release names from the changelog
Locked the raid, pinged the bench, closed the post. You were asleep.
On a night it ran without you
One raider, one guild, one bot.
No startup, no team, no roadmap deck. Built for The Night Owls, grown for a second guild, free at the core and meaning to stay that way.
Things people ask.
What permissions does the bot need?
View Channels, Send Messages, Embed Links, Manage Channels, Manage Roles, Read Message History, Create Invites. The wizard explains each one. No admin, no scary scopes.Is my guild data safe?
Each server is its own sandbox. Character data comes from the Blizzard API on demand. Nothing is shared between guilds, no telemetry sold sideways.Which WoW versions are supported?
TBC Classic Anniversary and Mists of Pandaria Classic. The bot is built per-flavour. When new realms land, support gets added then, not promised now.Coming from Raid-Helper?
Raid-Helper is a strong general event scheduler. Hootus is built for one thing: WoW raid night. It knows your class, your spec, and your Blizzard roster, checks composition on every signup, and scopes PUGs to the raid. There's an honest, point-by-point comparison if you want the detail.What does it cost?
The core is free and plans to stay free. If a paid layer ever lands, it'll be for the heavy extras, clearly drawn, and the everyday raid-night stuff stays free. We're not there yet, and you'll know well before anything changes.
Get the raid up. Get back to playing.
Add HootusPlootus to your Discord, walk the wizard, and post your first raid with one command. Roster, signups, and PUGs handled by the time you log in.