🛡
Encounter-first setup
Build assignments per boss instead of forcing raid leads through generic templates that do not fit TBC mechanics.
CURRENT SITE
What the planner is for
It is not trying to be everything. It is trying to make raid prep faster, clearer, and less annoying.
👥
Roster-aware planning
Keep tanks, healers, utility, and special roles readable, so the important parts are visible before pull, not buried in clutter.
🗺
Visual assignment flow
Canvas-style encounter views and boss-room placement are there to make assignments understandable at a glance.
T4 CONTENT
Built around the raids people actually need right now
Karazhan
One-off mechanics, role swaps, event bosses, and weird assignments.
From Attumen to Nightbane, Karazhan needs structure without turning into a wall of text.
Gruul’s Lair
High King Maulgar
Split targets, interrupts, tanks, mage tanking, utility and kill order.
Gruul’s Lair
Gruul
Clean raid positioning, cave-in handling, and readable assignments for everyone.
Magtheridon’s Lair
Cubes, interrupts, banishes, infernals, room positions.
This is exactly the kind of fight where visual planning beats dumping macros in raid chat.
UPCOMING
Planner data, straight into the addon.
The next part of Raiding.app is an in-game addon flow inspired by AngryAssignments. The goal is simple: build the setup on the website, import it into the addon, and stop rewriting the same assignments by hand.
Website → Addon
Generate raid-ready assignment data from the planner.
Readable in raid
Boss notes and role responsibilities where players actually need them.
TBC-first
Made around TBC Anniversary needs, not some vague all-expansion compromise.