We've gone through everything you told us about the Warcraft Logs review and worked down the list. Reading a night of Midnight Season 1 pulls should feel like reading your planner now, and there's one genuinely new tool in here: Compare vs Top, which puts your casts next to the best players of your spec. Or well, next to the people with PI padding their ass off on void orbs. Either way, a useful reference.
Your raid, laid out like the planner
The most common piece of feedback: the review was a wall of spell rows with a thin gray strip per player, and deaths hid behind a toggle. You spent more time working out whose row you were reading than reading it.
- Every player gets their own band. Spec icon, name, and class color on a card, the same way the planner shows your roster.
- Deaths sit on the player. Each band carries a skull and death count, and every skull on the timeline now tells you what killed that player. By default you see the first three deaths of each pull, the ones that usually decide it; one click shows them all.
- One pull gets its own layout. Narrow the review down to a single pull and it switches to one row per player with the actual cast icons on a real clock, like the WCL Top page.
- Controls sorted by what they do. What you're looking at (boss, fight, players) sits on one row; how it's drawn and what you're comparing on it sits on the next.
Compare vs Top
Knowing you cast a cooldown ten times across a night means nothing without a reference. The new Compare vs Top button gives you one: the top-ranked players of your spec on that boss.
- See when the best cast it. Each cooldown row is shaded with when top-ranked players cast that spell on their kills, behind your own casts.
- And how often. Next to each spell, your average casts per pull sits beside theirs: "You averaged 3.1 casts of Survival of the Fittest per pull. Top players average 4.3." Hover it for a phase-by-phase breakdown that flags where you fall furthest behind.
- No setup needed. It works on any imported report, on Heroic and Mythic, where rankings exist.
Skulls where you wiped, a trophy where you won
A new lane under the boss timeline marks where every pull ended: a skull for each wipe, stacked when several pulls died at the same point, and a trophy on the kill. One glance shows how the night went and where your walls are.
- Hover a marker to isolate those pulls. Everything else fades out, so you can read exactly what happened on that attempt. Click to keep it focused while you work, press Escape to go back to all pulls.
Logs that wouldn't import
A batch of fixes for reports that refused to load, or loaded for the wrong people.
- Group imports reach the whole group. Reports imported from a Group Hub were sometimes only visible to whoever clicked import. They now open for every member, including older imports that were stuck.
- The whole night in one review. When a report was synced in pieces, during the raid and again after, the review now shows every pull from that report in one place instead of fragments.
- A straight answer when a report is blocked. If Warcraft Logs won't let us read a report, the list now says so and points you to the fix, instead of showing an import button that goes nowhere.
Roster Report, easier to scan
- A Class column on the Summary. Sortable and class-colored, so you can order your roster role first, then class, then name, like a proper raid sheet.
- Item level you can read at a distance. Item-level cells on the Summary and Gear tabs are now tinted against your own roster's range, lowest red, highest green, so the outliers jump out.
- Sort on every tab. The Sort control now shows on all Roster Report tabs and adds a Class option, and your pick is remembered.
Around the app
- Lost in the Library's copy options? Public plan pages now have a "Which copy option do I need?" button that walks you through the four ways to take a plan, right on the page.
- Bulk signups show your roster again. The calendar's "sign up others" picker lists your members grouped by guild rank like it should.
- For the developers among you. When your app sends the public API a write it can't read, the error now names the exact field instead of a generic failure, and optional fields can be sent as null.
As always, feedback and ideas are welcome in Discord.