World of Warcraft

Special module. 0.99 € per month on top, bookable in the dashboard. Builds on the Termine (events) module.

The events module answers "who is coming?". A guild has a different question: is the line-up complete? Twenty acceptances are worthless if eighteen of them are damage dealers.

/wow raid what:Wednesday raid date:24.10. time:20:00 game:WoW: Forever size:40 players instance:Blackwing Lair

Every command starts with /wow: raid, list, characters, guild, panel, cancel, setup. The same thing can be created in the dashboard — it is the same raid, not a second list.

One click to sign up

Three buttons sit under every raid: Mit Charakter (with character), Vielleicht (maybe), Absagen (decline).

Anyone who has entered their characters once (see below) presses with character — and is in. With several characters there is one more question: which one. With none comes the hint on how to add one.

The long way: role and class

The selection without a character stays underneath — for the guest who comes along once and should not have to work through character management.

First the role — Tank, Heiler (healer), Nahkampf (melee), Fernkampf (ranged) — then the class. In that order, because the other way round does not work: a druid can fill all four roles, the bot would have to guess.

The class selection is filtered by the role. Anyone who picks Tank gets Krieger, Paladin, Todesritter, Mönch, Druide and Dämonenjäger to choose from — and no Magier.

If someone does sign up incorrectly, the bot turns it down and says why as well: "Ein Magier kann nicht Tank spielen — nur Fernkampf." That is not schoolmastering. A tank entered by mistake is noticed by nobody until someone is missing on raid night.

What is still missing

At the top of the post, not the bottom:

👥 20 Spieler (Mythisch) — 🛡️ 2/2 · ➕ 3/4 · ⚔️ 5/7 · 🏹 6/7

Es fehlt noch: 1× Heiler, 2× Nahkampf, 1× Fernkampf

Once the line-up is complete, the post turns green. That is the information a raid leader is looking for while scrolling through.

What the line-up looks like

A header row of three columns at the top — date, time, count — and the sign-ups below in columns of three:

📅 26 September 2021    🕐 19:45        👥 11/20

🛡️ Tank (2/2)           Jäger (2)        Priester (2)
 1 Xorgok                6 🏹 Larun        8 ➕ Belugia
 2 Sephiroth             7 🏹 Kinnell      9 ➕ Mageira

The number in front of the name is the order of sign-up. It is not decoration: it decides who is in the raid and who moves to the bench once it is full. Showing what that depends on saves the argument about it.

The class crests sit in the column headers and in the class line below. They are application emojis of the bot: uploaded once, usable in every server — you give up none of your fifty emoji slots for them and have nothing to set up. The bot uploads them on the first start after the update and never again.

The split is set in the dashboard:

• By class (default) — tanks in their own column, everyone else by class. The view every guild knows from Classic, because buffs, consumables and loot hang on the class. Each name carries its role icon, because a druid can be anything.
• By role — tank, healer, melee, ranged. Fits Retail better: there the role is what counts, and thirteen class columns would be thirteen nearly empty boxes.

An image can be set to sit below the line-up — the guild's or the instance's banner.

Discord converts the time into each reader's own time zone. In a guild with people from three countries that is the difference between a time and an arithmetic problem.

Raid sizes

Size	Tank	Heiler	Nahkampf	Fernkampf
Mythisch+ (5)	1	1	3	3
10 Spieler	2	2	3	3
20 Spieler (Mythisch)	2	4	7	7
25 Spieler	2	5	9	9
Flexibel	no limit

The numbers per role are more generous than the total — otherwise a raid with three healers instead of four could never fill up.

Bench instead of a refusal

Anyone who no longer fits goes on the Bank (bench) — not outside. In a guild that is a difference: the bench is a role, not a no. Whoever accepted first is in the raid; the order decides, not the mood.

Class distribution

Below the line-up it says how often each class is present. Anyone with five mages and no priest would rather notice that now than on raid night — some group buffs exist only once per class.

The thirteen classes

Krieger, Paladin, Jäger, Schurke, Priester, Todesritter, Schamane, Magier, Hexenmeister, Mönch, Druide, Dämonenjäger, Rufer — each with the official class colour.

Which role a class can play is fixed in the bot and does not have to be configured.

Characters

In a guild, a character name and a Discord name are two different things, and on raid night the first one counts. So every member enters their characters once: name, class, role, game.

/wow panel puts the panel for it into a channel. Three buttons: add character, my characters, guild overview. A command you have to know is one half the guild never uses — a panel in the raid channel gets clicked.

Adding is clicking, not typing: game, role and class come from menus, only the name is typed. What does not fit is turned down — a mage tank is as wrong as a character as it is as a sign-up.

Your main is the one you are suggested with — one per game. The same person plays an evoker in Retail and a dwarf priest in Forever, and both are their main, each in its own game. The first character of a game becomes the main by itself; it can be changed under my characters.

How many characters per member is set in the dashboard (default: six, counted per game). If the guild only raids one of the two games, turn on This game only there — the bot then stops asking.

The roster then reads @Timo · Schakar (Krieger) instead of just @Timo · Krieger. Whoever signs up by hand stays in there without a character name — then they come without one.

The guild overview

/wow gilde and the The guild card in the dashboard answer the question that comes before planning: can we even fill this raid? Four columns, one per role, with the guild's mains — and below them the line that helps most: which class nobody plays. In Forever, group buffs hang on classes, and a guild without a single priest would rather find that out here than in front of the boss.

Only mains are counted. Someone with three characters is still one player — counting all of them would give a guild of eight people twenty tanks on paper.

In the dashboard the card is read-only. A character belongs to the member who entered it; the raid lead should see what is there, but not rewrite anyone's main.

A channel of its own for the raid

On request, a text channel appears an hour before the raid and disappears again afterwards — for everything that would otherwise bury the announcement: who is driving, who still needs stones, who is running late.

Only those who said yes get in, the bench included (whoever steps in has to have read the plan), plus the raid lead — even if they never signed up themselves. Anyone who says yes later is added.

It can be switched on per raid (/wow raid raid_channel: or the checkbox in the dashboard); the default, the lead time, the category and whether it is private are in the module settings.

It is only deleted once nobody is left in the raid's voice channel. Cleanup runs two hours after the start, and a 40-man takes longer — deleting the channel with the plan in it mid-raid would be exactly the wrong moment.

For the private channel the bot needs the Manage Roles permission. Without it the channel is created open rather than not at all: an open raid channel beats no raid channel.

What comes along from the events module

A reminder beforehand, a voice channel by itself, repetition for the weekly raid night, a cancellation with a notification — all of that comes from Termine and works here in exactly the same way.

When the module is missing

Without a booked WoW module the line-up cannot be chosen in the first place; the bot says so when you create the event. If the subscription runs out while a raid is still pending, the post stays — only signing up stops. A raid that disappears in the middle of the week would be worse than one nobody signs up for any more.