Skip to main content
The planner

Drag a name, drop a tank, post the lineup.

A web raid planner built for the officer doing Karazhan from a phone on a train, not the one with three monitors. Move signups between groups, swap a healer for a tank, bench the third Ret, and send the lineup back to Discord when it reads right.

A companion, not a tax·The bot still does it all from Discord if you'd rather type
The lineup that lives in a Discord message,
except you can drag it.
Same raid, same signups, same Discord thread. The planner is the place you arrange them by hand instead of retyping a list every week.
The mobile story

Built to plan a raid one-handed.

Most raid tools assume you are at a desk. This one assumes you are on the bus with twenty minutes before pull. The hard part of dragging on a touch screen is that a touch is also a scroll, so the planner splits the two on purpose.

  1. The grip drags

    A handle on the left of every row. Press it and that one name lifts. Touch sensors, not a desktop hack bolted onto a phone.

  2. The rest of the row scrolls

    Drag from the grip, scroll from anywhere else. The list still moves under your thumb, so a thirty-person signup does not trap you at the top.

  3. The three-dot menu when dragging is fiddly

    Touch drag misses sometimes. The menu on each row does the same moves without the aim: change role, send to a group, bench, set an alt.

Karazhan · Tuesday 20:00
Group 1
  • FjorvaltTank
  • BrightleafHealer
  • SkarnDPS
Bench
  • PyreclawRet

A decorative sketch of the planner, not a screenshot. The grip drags, the role tag sits on the right, and the bench is its own column.

What it actually does

Four moves that earn the planner its place.

Not 'powerful' or 'seamless'. The things your hands do on raid night.

Drag a name, drop a tank
Open the raid, see everyone who signed up, and build the night by moving names between groups, the unassigned pool, and the bench. Drop someone into a group and it goes there. Drop them on the bench and they sit.
It checks the spec before it lets the drop land
Drag a Mage onto the tank slot and it stops you, same as the signup does. The drop only sticks if that character's spec can actually fill the role. No lineup that falls apart the second you read it back.
Auto-place when you do not want to think
One button fills every unassigned signup into groups. Tweak from there or leave it. Good for the Tuesday clear where the comp writes itself and you just want the post out.
Read the note they left, right on the row
Whatever someone typed when they signed up sits on their row while you plan. "Can only stay till 22:00", "bringing the resto alt instead", "late, traffic". You see it as you place them, not after.
Buff coverage

It reads your buffs before the raid does.

On supported flavours, the planner looks at how you split the groups and tells you what is covered and what is missing. Two shamans in one party and none in the other, no Blessing of Salvation on the caster group, a totem element nobody is dropping. The kind of thing you find out at the boss otherwise.

  • Reads the lineup group by group and flags melee, caster, or mixed
  • Lists which buffs and totems are covered and who is bringing them
  • Calls out the key buff nobody slotted and the shaman piled into one group

The buff data is TBC, so coverage is sharpest for TBC lineups. The rest of the planner does not care which flavour you run.

Group 1 · caster
  • Arcane BrillianceMage
  • Wrath of Air TotemShaman
  • Blessing of Salvationmissing

A decorative example, not a live readout.

The officer moves

Two things only a planner can do.

The stuff that does not fit in a signup button.

Set an alt for someone, on their behalf

Someone signed their main, then said in chat they'd bring the healer alt instead. You don't make them withdraw and sign up again. Swap the character for them from the planner and the lineup updates. They keep their slot, you keep your sanity.

Two ten-mans on the same night

Splitting the raid into two tens? Plan both at once without them tripping over each other. Place names into one run, then the other, and post each lineup to its own thread. Nobody ends up double-booked because two officers were editing the same list.

Posted to #karazhan
Tonight's lineup
  • Group 1Tank · Heal · 3 DPS
  • Group 2Tank · Heal · 3 DPS
  • Bench1 Ret, hoping

A decorative example of the post, not a screenshot.

Back to Discord

The lineup posts where the raid already is.

You planned it on the web, but the raid happens in Discord, so that is where the lineup lands. Send it to the raid thread or a channel you pick, as a clean composition the group can read at a glance. No copy-paste, no retyping the comp by hand, no second source of truth to keep in sync.

The planner is a companion to the bot, not a replacement for it. Everything you can drag, you can also do from Discord if you'd rather type.

The honest part

Where the new planner is, and isn't.

We'd rather tell you than have you find out.

The drag-and-drop planner is the redesigned one, and it turns on per guild behind a beta flag in settings. It is not the universal default for every server yet. If your guild hasn't flipped it on, you get the older planner, which holds the same raid data with a plainer interface.

It also renders for the supported flavours, TBC Classic and MoP Classic. Buff coverage in particular leans on TBC buff data, so that analysis is most meaningful for a TBC raid. Everything is built per-flavour on purpose. When the new planner reaches yours, it shows up. We don't promise dates we can't keep.

Pull on cooldown

Stop retyping the lineup every week.

Add HootusPlootus, walk the wizard, and build raid night by dragging names instead of counting reactions. The lineup posts back to Discord when it reads right.

Back to every feature