Log Rx is a combat log analysis and raid management site for TBC Anniversary Classic. It reads your Warcraft Logs reports and turns them into a per-player grade, a whole-raid audit, shareable raid assignments, and season-long trends, and it gives your guild one home for roster, attendance, recruitment and report history.

Your first ten minutes

1. Sign in with Discord. Log Rx reads your username, avatar and the servers you are in, nothing else.
2. Try the demos before you bring a key: Rotation Compare, Raid Review, Assignments and Raid Trends run on a stored report and need no account.
3. Create a free Warcraft Logs API client and paste its id and secret in Settings. Your key is encrypted and never shown again; every analysis you run uses it.
4. Add your character in Settings with its guild picked, so officers can seat you and your absences reach your team.

Rotation Compare grades a single player on a single fight. The grade is their Raider Performance Score (RPS), a role weighted read of throughput rank, active time, mechanic execution, deaths and preparation. It is not a rotation grade. Beside the score it lines the player up against the top 10 ranked players for the spec, or against anyone else in a log (a guildmate, an applicant, yourself on another night), so you can see where casts, uptime, resource use and cooldown timing differ.

Running an analysis

1. On the Rotation Compare page, paste a Warcraft Logs report link. It loads immediately.
2. Pick the boss pull from the fight list, then the player to grade.
3. Read the grade card first. The four bars under the score say which category cost the most.
4. Open the rotation timeline. Gaps between casts are shaded; the legend names every ability. The raw uptime lives in the tooltip on the adjusted tag, not on the number.
5. Use Targeted compare to put yourself against one other player from the same fight and see the deviations side by side.

Reading the results

The timeline and the sections below it are the diagnostic: dropped uptime on a debuff you own, missed casts of a priority ability, a cooldown left sitting, downtime where you were not attacking. Fix the largest loss first; one big leak moves the grade more than several small ones.

Raid Review audits a whole raid night: who performed, who died to what, who came prepared, how each boss went. It reads up to three reports as one night, follows a log that is still being written, and can read a combat log file straight from your computer with no key.

Loading a night

Paste a report link on the Raid Review page. You can load up to three reports at once when a night is split across logs or you run more than one group; each report gets its own badge so you always know where a pull came from.

• Log Rx Direct Drop a WoWCombatLog.txt onto the page and it is parsed in your browser. Nothing is uploaded, no key is needed, and the result is the same Raid Review view minus the Warcraft Logs parse rank.
• Live follow Point Raid Review at a log that is still recording and it checks every 30 seconds, announcing each new kill as it lands. It refuses to start when your key budget is nearly spent and stops itself on repeated errors.

Raid Breakdown and Raid Audit

The breakdown lists every boss with kills and wipes, raid wide damage, healing, damage taken and deaths, with per player rows you can expand. Trash is included, so totals and consumable counts reflect the whole night.

• Spell Uptime How well the debuffs your raid owns were kept up. Boss grades the boss alone; Boss + adds counts any enemy. Time a boss spends immune is never counted against you.
• Spell Use How many times each player cast an ability, counted from the cast events, so dispels, interrupts and cooldowns are confirmed.
• Consumes and Engineering Flasks, elixirs, pots and food per boss and across trash; sappers, drums and other gadgets.
• Mana and RPS Resource management and the same RPS the rest of the site uses.

Deaths and the death map

The Deaths panel names who died to what, including trash pulls and melee killing blows that the Warcraft Logs table leaves out. Under each boss card the death map plots every death on the room art for all fourteen Hyjal and Black Temple bosses, so a positioning problem is visible in a second.

Send a report to Raid Trends

If you belong to a guild on Log Rx, each report carries a tag control that files it under one of your raid teams and feeds the team trends. Log Rx suggests the most likely team from who is in the report. For many past reports at once, use the Reports tab on your guild page.

Every raider gets one 0 to 100 score per encounter. Rotation Compare, Raid Review and Raid Trends share the same scoring engine, so a number means the same thing wherever you read it. A score is a Performance Grade (90 percent) plus a Required Elements grade (10 percent).

Performance Grade (90 percent)

Four categories are each graded 1 to 5, then weighted. The thresholds below are the same for every role; the weights shift by role further down.

Required Elements (10 percent)

Pass or fail checks: no gear issues, a weapon buff, pots used, a flask or elixir, and a food buff. The grade is the fraction passed. Weapon buff applies only to classes that use oils, stones or poisons; the others are graded out of four.

Final score and letters

RPS = (weighted performance average / 5) x 90 + (elements passed / total) x 10. Letters: S 95 and up, A 85 to 94, B 70 to 84, C 55 to 69, D 40 to 54, F under 40.

Role-aware weights

Assignments builds a raid plan on top of the boss maps and runs it on the night. Seats hold your raiders, Raid Prep holds blessings, marks and healer priorities, each encounter holds pins, sequences, backups and required mechanics, and the play view gives every raider their own job list in kill order.

Building a loadout

1. Create a loadout on the Assignments page and pick the encounters you are planning for. Every Hyjal and Black Temple boss comes with a map and sensible defaults; Tier 4, Tier 5 and Sunwell are there too.
2. Fill Seats and Groups. Prefill from your guild team roster, mark absent raiders so they vanish from every picker, and arrange groups one to eight.
3. Set Raid Prep once for the lockout: greater blessings per class, normal blessings per player, tank marks, a healer priority list per tank, quick sections for the common ability families, and Jewelcrafting neck chains.
4. Place assignments on each map: pins, player tokens and drawing tools, with a per-phase default view. Sequences carry timed steps in plain trigger language (on pull, after the previous step, every so many seconds, at a phase, on a cue).
5. Add backups that step in only while a seat is empty, required mechanics with slots that resolve through seats or whole groups, and a trash plan: Hyjal waves and Black Temple packs.
6. Start a new loadout from an official template when one fits the raid.

Working together

A loadout saves itself a few seconds after you stop editing and keeps unsaved changes on your device for a day. Two editors can build the same plan at once; each save weaves into the other's open editor, and if you both change the same section your own version wins on your screen with a small note.

Running the night

• Play view A clean read-only view for raiders, in night order: each boss's trash right before the boss, in kill order. Four tabs: Simple (the default, the whole night in one scroll), Detailed (every assign in full sentences, with a floating next-stop pill), Lead (who covers what on every boss), and Map (the plan's maps with each boss's abilities).
• Lead view and print The lead's focused boss view with lockout chips and a summary rail, and a printable boarding pass per raider.
• Live updates When the lead saves, every open play view refreshes on its own. No mid-raid page reloads.
• Clean share links A view link or an edit link is a short /s/ address; it never carries the token in the page you land on.
• WeakAura export and the addon Export callouts as a WeakAura string today. A Log Rx companion addon that mirrors the play view in game is in development.
• Share a comp Export the composition and groups as an image for Discord, or import a guild team's roster and saved boards straight into the editor.

Raid Trends tracks a team across lockouts. Where the other tools read one report, it reads the season: how throughput, deaths and boss speed move week over week, how teams compare, and how each raider develops. The report opens in a Read layer, opens its evidence in Dense, and drills into any row on click.

Getting reports in

A report shows up once it is tagged to a team: use the tag control in Raid Review, or the Reports tab on your guild page to add and feed many at once, with a queue for re-feeds. Phase and raid date are read from the report. When a measurement improves, Re-feed re-runs old weeks under the current rules so the history stays comparable.

Reading the report

• Summary The week at a glance: the team's numbers, personal records for the raid, and the movement since last lockout.
• Progression Clear times and boss combat time across nights, with the full-clear rule applied so a partial night is never a record.
• Bosses Per encounter speed and execution across weeks; click a row to drill into the pulls behind it.
• Players A box score per raider, a player board that ranks the team, and raiders per boss, with consistency, form and the character sheet at pull.
• Audit Consumables, engineering and mana per lockout, so a recurring habit shows up as a trend, not a one-night surprise.

Compare and share

Put teams side by side, or add one benchmark report at a time. Share cards render a team, guild or raider image from the share icon, and a read-only share link shows trends to someone outside the guild. The classic Overview stays behind a switch for anyone who prefers it.

The Mechanics page covers every encounter in the current content: all 33 bosses across Hyjal, Black Temple, Tier 4, Tier 5 and Sunwell, with their abilities, adds and the mechanics your raid has to handle. Prep a first pull, settle a debate, or teach a new raider what to expect.

The same catalogue drives the ability icons on the pins in Assignments, the required mechanic slots and the Lead tab, so the names you read here are the names the planner uses.

Registering a guild gives you a home for roster, raid teams, attendance, recruitment, and report history. Register or join from Settings. The guild page opens on Overview, which lists what needs an officer and the raid nights this week, then has Roster, Attendance, Reports, Settings, and Log tabs. Officers and the guild master get the controls; raiders get a clear read-only view of most of it.

Roster

• The ledger Your character pool grouped by role and spec, the team strip across the top, and the bench at a glance. Officers move characters between teams.
• Availability and marks Raiders set the nights they can raid and mark themselves out, tentative or benched for specific dates with a reason; a vacation is one range.
• Boards Saved group layouts one to eight per team, shared as an image.
• Import and claim Pull your guild roster or a report roster from Warcraft Logs in bulk; raiders claim their own characters, and same-name duplicates merge instead of piling up.
• Recruitment Needs with priorities and a Recruit Slot placeholder, a profile with about text, leads and expectation groups, and the recruitment card: four poster layouts (The Poster, The Ladder, The Manifesto, The Letter), your own background art, and proof numbers from Raid Trends such as the Hyjal and Black Temple records, boss combat time and raid DPS.

Attendance

Absences posted on the website or through the Discord bot land in one place. Officers see a confirm queue, an upcoming view they can filter to one team, and a history of who missed which nights. Availability notes ride along with an absence.

Reports

A permanent archive of each team's Warcraft Logs reports by raid night, newest on top, and the bulk feed into Raid Trends. Paste one or many links; each report is dated and titled from Warcraft Logs with your key connected. Feed one, feed everything not yet in, or queue many re-feeds and let one worker run through them while the tab is open; Unqueue and Clear queue undo it. Reports show an In Trends badge once filed.

Settings and Log

Guild Settings holds the details, the default role for new members, the Discord invite shown to recruits, and the danger zone. Members show their Learn progress as Practitioner and Coach tags. The Log is a plain-language activity feed of who changed what.

The Log Rx Attendance bot lets raiders post absences from your Discord server, and everything they post lands on the roster and attendance history. There is nothing to keep in sync by hand.

Setting it up

1. On your guild's Attendance tab, use the invite button to add the bot to your Discord server.
2. Run /setup in the channel where absence posts should appear. The bot posts a how-to for your raiders there and pins it. That is the whole setup.

Commands

• /out Post an absence with dates, an optional reason and your availability. The bot posts it with Confirm and Cancel buttons.
• /absences The upcoming absences for the next two weeks; add a team name or letter to filter.
• /myabsences Your own upcoming absences, each with a button to remove it.
• /claim Link roster characters with no owner to your account. An unclaimed character cannot be reached by any callout.
• /claimprompt For officers: posts the unclaimed list once, as alphabetical dropdowns, so a whole raid can claim in one pass; each pick is answered privately.
• /setup For officers: sets the channel that receives absence posts, and posts and pins a how-to for your raiders there.
• /howto For officers: posts and pins a fresh how-to in the attendance channel, with your calendar as it is today. Nothing else changes.

Officers confirm an absence as a simple acknowledgment; the poster or an officer can cancel one. The bot can also post a raid night reminder listing who is out that evening. For help with the site itself, the community Discord has support channels.

The Settings page is where you manage your own account: your Warcraft Logs key, your characters, your guilds, your analysis preferences, and the account itself.

• Warcraft Logs API key Log Rx is bring-your-own-key. Create a client on the Warcraft Logs API page and paste the id and secret; the secret is encrypted at rest and never shown again. Your key sets your rate limit, and results are cached so a report analyzed once is cheap for everyone who opens it after.
• Characters Add each character with class, spec, server, faction and guild. With the guild picked, adding a name your guild already imported claims that character instead of duplicating it.
• Guilds Register a guild you administer on Discord, or join one you are a member of. The server list is read at that moment only.
• Analysis preferences Defaults the tools use when you open a report.
• Delete account Removes your key, characters, memberships, progress and marks, and hands shared plans to a co-editor. A guild master hands the guild over first.

The Terms and the Privacy pages spell out what Log Rx stores and why, in plain language.

Most tools can hand a view to someone else. A shared view shows what has already been computed, so the viewer needs no key, and a banner makes clear it is read-only.

• Rotation Compare and Raid Review Share links carry the current report, and in Rotation Compare the selected fight and player, so a teammate opens exactly what you see.
• Assignments A clean /s/ link for viewing or for editing, a play view raiders keep open all night, a comp image, and a WeakAura string.
• Raid Trends Share cards for a team, the guild or one raider, and read-only trend links for people outside the guild.
• Recruitment The recruitment card exports as an image sized for Discord and forum posts, with your Discord invite on it.

A handful of habits make every tool sharper.

• Feed every raid night. The more reports reach Raid Trends, the more its trends mean. The Reports tab catches a whole season up in one queue.
• Let the roster do the bookkeeping. Keep team membership, availability and marks current and attendance history, assignment imports and the recruitment card stay right on their own.
• Use stable seats. When each raider sits in the same spot across bosses, callouts are easier to learn and mistakes drop.
• Fix the biggest leak first. In Rotation Compare and the audits, one large loss is usually worth more than several small ones.
• Put the bot in your raid Discord. Raiders already live there, and every absence they post keeps the roster and history correct.
• Watch the two-minute clip. The Courses mode has a short lesson for every feature on this page, with a practice path that ends inside the product.