WRS · Warcraft Raiding Studio
One place to plan, assign and review a mythic raid.
The web app, desktop sync and in-game addon share one guild database, and an AI assistant has read all of it.
No mail app? Write to contact@nsi4.com
- Phase. The phase the encounter is on, and where it stands in the fight.
- Cooldowns. Each healer's major cooldowns, placed by the officer or the AI.
- Mechanics. Each ability tagged: raid AoE, movement, add spawn.
01 Problem
A mythic raid runs on six tools that never talk.
A progression night pulls from Warcraft Logs, Raider.IO, Raidbots, a shared spreadsheet and Discord. Assignments live in one place, the roster in another, and the addon on screen knows about neither.
Officers spend hours copying data between them, and every copy is a chance for the wrong healer to be on the wrong cooldown at pull time.
And the guild's own history sits on other people's servers. When one of them is down, so is the plan.
02 Constraints
It has to hold up mid-pull.
- Timing
- Assignments reach every raider's addon before the pull timer ends
- Ownership
- The guild's history stays in the guild's database, not a third party's
- Testing
- Every feature runs in RETRY's mythic progression before release
03 What We Built
One guild database behind every surface.
Four surfaces share it, and every feature and the assistant read from the same data.
How the data moves
- SyncCombat logs processed in the background and synced to the guild database
- StoreOne guild database behind every surface
- PlanRoster, calendar, assignments and loot, planned in the browser
- AdviseThe assistant drafts from the guild's own data; an officer decides
- RaidThe addon shows each raider their assignment and records the fight
Surfaces
Web app
Roster, calendar, assignments and loot, planned in the browser.
Desktop sync
Processes combat logs in the background and syncs them to the guild database. No manual uploads, no waiting on a third-party site.
In-game addon
Imports the raid's strategy, shows each raider their assignment in the fight, automates routine utilities and records what happened.
Mobile
Calendar and notifications. Planned, not yet built.
What it does
Raid planning AI
Roster building, healing cooldown plans and combat assignments, edited visually. The assistant drafts; an officer decides.
Audit AI
Readiness checks at guild, team, player and character level, with the assistant's suggestions on what to fix first.
Calendar
Events, sign-ups and availability in one place, with reminders and roster suggestions.
Guild and teams
Guild data synced automatically. Several raid teams, each with its own roles and permissions.
In-game
Strategy import, live assignments on screen and performance tracking during the pull.
Loot AI
Suggestions weighed by performance, attendance and character progression.
The assistant
Ask in plain language
“Show me our healing cooldown gaps on this boss.” “Which DPS have the best single-target for this fight?” Answers come from the guild's own data.
Knows the whole history
Performance history, roster, character progression and the encounter itself, read as one context.
Speaks up first
It flags what nobody asked about: “Interrupt coverage is weak in phase 3.” “Three raiders haven't gemmed their new gear.”
04 Evidence
Built with RETRY, one progression night at a time.
Every feature runs in RETRY's mythic progression before it ships. This is what an officer sees on a raid night.
- Team summary. Average item level and gear score across the roster.
- Tier sets. Who has their set, piece by piece.
- Issues. Sockets, enchants and crafting still to fix, per raider.
WRS AI · Sample conversation
Illustration
Suggest healing assignments for the next boss.
Based on your roster and last week's pulls: put your Resto Druid on tank 1 and save Tranquility for the two heavy AoE phases. Your Holy Paladin was strongest on spot healing; keep them on melee. I've drafted the full plan with cooldown timings.
Show me where we lost the tank last week.
Pull 7, phase 2: the tank swap came 3 seconds late. The plan now marks the swap on both tanks' addon timers.
05 Stack
What it runs on.
- Surfaces
- Web app · desktop sync · in-game addon
- Data
- Guild-owned database; combat logs parsed on the raider's machine
- AI
- Assistant with read access to the guild's full history
- Status
- Alpha, tested with RETRY
- Built with
- Blazor · SQL Server · Lua addon
Waitlist
Raid with WRS next tier.
Guilds join in small groups while WRS is in alpha. Tell us your guild, realm and raid nights.