Skip to main content
Discord ops bot for WoW Classic guilds

Nobody asks who is tanking tonight again.

One command posts the raid. From there Hootus checks every signup against class and spec, reads who actually showed up from raid voice, and keeps the roster straight with Blizzard. Your officers get the evening back.

Free at the coreNo card, no trial, raiding in five minutes
Karazhan · Tuesday 20:004/10
Tanks
1/2
Healers
1/3
DPS
2/5
  • FjorvaltProtection Warrior
  • BrightleafRestoration Druid
  • PyreclawFire Mage
  • HexweaveAffliction Warlock

Go on, fill the raid. This is the real rule, not a mockup: a Feral Druid can tank, a Fire Mage cannot. Tell the Mage to tank and see how that goes.

What it takes off you

Four jobs you stop doing.

Not a feature list. This is the part of raid night that quietly disappears the week you add him.

  1. Used to be: asking in general

    Signups that check themselves

    Tank, Healer, DPS, every click measured against the character behind it. A Feral Druid can tank, a Fire Mage cannot, and Hootus says so on the spot instead of the raid lead finding out at pull.

  2. Used to be: a roster spreadsheet

    A roster that stays honest

    Members confirm a character on the armory once. After that it syncs from Blizzard hourly, alts and respecs included. No more 'is Fjorvalt actually 70 yet'.

  3. Used to be: counting reactions

    Attendance you never had to take

    Raiders join raid voice, Hootus checks them in with the timestamp to prove it, and flags whoever slipped out before the last boss.

  4. Used to be: chasing the applicant

    Recruitment that lands in Discord

    A public apply page for your guild, the application posted to your officer channel, and one button that hands out the roles.

Attendance

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.

Karazhan · attendance0 checked in
  • FjorvaltProtection WarriorPresent
  • BrightleafRestoration DruidPresent
  • ArrowsongMarksmanship HunterPresent
  • MournhowlFeral Combat DruidLeft early
  • SkarnCombat RogueNo-show

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.

  • Checked in on arrivalHit raid voice and the mark lands with a timestamp. Nobody counts reactions again.
  • Early leavers flaggedSlip out before the last boss and Hootus notes it, so bench rotation stays fair.
  • The lead always winsEvery mark is editable. The post-raid report goes to officers privately, confirm before it lands.
Setup

Five minutes from invite to first signup.

No YAML, no config repo, no Discord-bot-hosting tutorial.

  1. Add the bot

    One click, OAuth handles the rest. It lands in your server with the permissions it needs and nothing it doesn't.

  2. Walk the wizard

    Pick Classic Era, TBC, or MoP, point it at your channels, say which Discord roles open what. Five minutes, no config files, no YAML.

  3. Push the raid button

    Your first signup post lands in the raid channel with the role buttons on it. That one command runs every Tuesday after this.

One bot, every flavour

Three flavours live. Same bot underneath.

The core works the same everywhere. The per-expansion stuff is deltas on top of it.

  • Vanilla

    Classic Era

    7 raid types, Molten Core through Naxxramas. Levels 1 to 60, the original nine classes.

  • Burning Crusade

    TBC Anniversary

    9 raid types, Karazhan through Sunwell. 16 dungeons in /lfg, plus totem coverage.

  • Mists of Pandaria

    MoP Classic

    Monk specs, 3-man scenarios in /lfg, and difficulty tracking for Normal, Heroic, and Celestial dungeons.

Identical on all three

  • Blizzard-verified roster sync
  • Class and spec-aware signups (no Mage tanks, ever)
  • Your softres.it link carried on every raid post
  • Buff coverage on the raid post, with its own list per flavour
  • Recruitment apply page with officer routing
  • Auto-lock at minus 30, bench ping, post-raid cleanup
Command to post a raid
1Command to post a raid
Roster sync from Blizzard
HourlyRoster sync from Blizzard
Live flavours
3Live flavours
At the core, always
FreeAt the core, always
Why Hootus

Built for raid night, not bolted onto a calendar.

A general scheduler can post an event and count who clicked. It has no idea what a Feral Druid is, whether your Warlock has the gear, or that Tuesday is a lockout. That is the whole gap.

It also has never heard of your addons. Raid night happens in the game, so Hootus hands the finished lineup to Method Raid Tools for the raid leader, and reads the Gargul loot log back in once the night is done. One export out, one paste in, nobody retyping thirty names into a raid frame.

  • 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
  • The lineup exports to MRT, and your Gargul loot log pastes back in
  • PUGs scoped to the raid, not the whole server
  • The web planner and every raid tool, with nothing behind a paywall
Battle.net

Prove a character once. Carry the proof to the next guild.

Connect Battle.net once. It needs no guild, only a Discord login, and the claim it writes belongs to your account rather than to a server. Turn up in another Discord running Hootus with one of those characters on their roster and you land approved, class role on. Nobody re-checks the armory.

Ashen Vigil, a server you just joined12 seconds in

Welcome to Ashen Vigil. You are already verified.

FjorvaltMirage Raceway · Protection WarriorVerified

Warrior role handed out, main set, two more alts matched off the same roster.

Those are the ones on the roster here. Whatever else you play stays yours, this server never sees it.

Recognition needs the character sitting on that guild's own Blizzard roster, same region, same flavour. Not joined them in-game yet? Then you verify the normal way, same as everyone. What travels is the proof and only the proof: the new guild sees the characters it already had, and learns nothing about where else you raid.

For community servers

Not a guild? Put real groups in your channel.

If you run the realm discord, the class server, or the place everyone on your server ends up, the relay posts groups that guilds have opened to pickup players straight into a channel of yours. Filtered to your realm and your flavour, updating as spots go, gone when the group closes.

You install nothing. Pick your filters, hit create, and Discord asks which server and channel. No bot joins, no permissions change hands, so there is nothing to review later and nothing to remove.

  • Groups posted by guilds that opened them to pickup players
  • Filtered per channel by flavour, region, realm, and content type
  • A board that rewrites itself, or one post per group
  • No bot in your member list, no permissions handed over
  • Free, and off the moment you delete the webhook
Locked the raid, pinged the bench, closed the post. You were asleep.
Hootus, on a night it ran without you

No startup, no team, no roadmap deck. Hootus was built for The Night Owls because running raid night out of three browser tabs stopped being funny. He grew for a second guild, and he is free at the core because that is what he was on day one.

Questions

Things people ask.

The short answers are here. Permissions, data, supported flavours, and money, in that order.

  • What permissions does the bot need?
    Nineteen, and Administrator is not one of them. Reading and posting, Embed Links and external emoji for the class icons, five thread permissions for raid threads, Manage Channels, Connect, Speak and Move Members for raid voice, Manage Roles and Manage Nicknames for verification, Create Invite for the raid links, and Kick Members, which is only used when an officer asks or when someone removes themselves at the welcome step. The wizard names every one and what it is for.
  • 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. The exception is the guild page you publish yourself, below.
  • What goes public when I open recruitment?
    A guild page and a listing in the directory at /guilds, both readable with no login: guild name, realm, region and faction, raid nights, the seats you need, roster size, the raids you ran in the last 90 days, your blurb, your Discord invite, and the bosses your raid logs credit you with. Never a member name, an application, an attendance mark or a loot roll. Search engines are let in by default and one switch in settings turns that off.
  • Which WoW versions are supported?
    Classic Era, 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.
  • What does it cost?
    Nothing today. Free at the core, and that is not moving. If a paid layer ever lands it covers heavy extras, clearly drawn, and you will hear about it well before anything changes.
Pull on cooldown

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.