You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MCPSee a raid plan as raidstrats.gg draws it. Asked for the plan as it is ("what's our plan for this boss?"), Wipebot shows each plan with the names saved on its spots: in ChatGPT the plan itself, its scenes a click apart and your own spots lit when you ask where you stand; in Claude a link that opens it.
MCPThe replay shows the phases, the boss's health and what it casts next. The replay's timeline is coloured by phase, each named under it, and a phase the fight went back to keeps its colour. A frame at the top left gives the boss, the phase and its health as the pull plays, a new bar for each phase's boss as raiders count it ("P2 97.5%"). At the top right, "Coming up" counts down the boss's next casts in the log over the coming 20 s, those Lorrgs tracks in bold.
MCPExplore a raid night on Wipebot's website, under the demo's answers. On wipebot.enfo.dev, below Wipebot's answers about a real Mythic night, the night is drawn with the same view Claude and ChatGPT show: each pull's boss health left, coloured by what ended it, and a click on a pull opens its deaths, cooldowns and replay. A view's "Ask" button puts its question in the demo's box. The demo's recorded answers were asked again with today's Wipebot, and show its own pictures.
Changed
MCPA player's night sits in the chat on a phone. In Claude the card no longer paints its own grey box over the chat, the pull numbers beside each cause of death are smaller chips (still a finger's tap), and their key sits above them where the scroll button can't cover it. The verdict reads "2 of those 8 deaths were survivable with a ready defensive or a healthstone", the box under it says "Astral Shift at both, a healthstone at 1" so the two never read as three deaths, and the headings are shorter ("Deaths that count", "Survivable", "What killed Enfo").
Fixed
DiscordSigning in turns raid notes and plans on at once. On a bot many servers share, such as the public Wipebot, /wipebot setup kept saying "You aren't signed in yet" to an admin who had signed in with /login private:True: only the plain /login counted. Either sign-in counts now, and an admin who signs in in the server is told right away that notes and plans are on, without running /wipebot setup again. What it says while they're off is shorter, and when your characters aren't in the guild it names the Warcraft Logs account you signed in with.
AgentDamage spikes are measured second by second. The raid's damage taken came from Warcraft Logs' graph, which averages a long pull over some 20 s at a time, so short bursts were flattened: a Twin Fangs kill had no spike and showed its three busiest stretches, its highest 5 s 1.53M/s, where the log's damage taken table gives 1.9M/s. Each second's damage is now worked back out of that graph, as the table gives it: that kill has five spikes, the one with the most damage 6:29-6:37 at 1.82M/s with no healing cooldown in it, and an Entombed Sentinels pull that had none shows three. A pull's four spikes with the most damage come in full and the others in a line with the healing cooldowns up in each ("4:49-4:54 (5 s) 1.85M/s: Ascendance (Enfo) at 4:53"). A pull with no spike at all shows its busiest 5 s, called so, in place of busiest stretches. The pull timeline's 5 s averages and the pull card's damage line and peaks read the same numbers, the table's: Sszorak pull 13's peak at 2:30 is 6.68M/s, where it read 5.73M/s, and a wipe's last burst stays in its last seconds instead of marking the 5 s before it.
AgentComparing with the top players no longer turns a defensive or a stat into a gap to close. Against the top Restoration Shamans on a Vashnik kill, Earth Elemental's "3/5" sat among the cooldowns, and an answer told the player to cast it because most top players had. Defensive, tank and movement spells now have a line of their own, which says they answer a moment (a big hit, a death, movement), so how often the top players cast them isn't a fault. The top players' stats now also say that a gap from them is no reason to take a stat over one the guide ranks higher: a Farseer, whose guide puts Mastery first, was told to take Crit over it because the top players had more Crit.
AgentA timeline of one ability shows when the boss cast its main abilities. Asked about the Malignant Totems' Malignance on a Vashnik wipe, the timeline listed every hit but not the boss's Imbibe that set the totems off, and the answer put that Imbibe at 1:51 instead of 1:48. It now ends with the boss's casts that Lorrgs tracks in the same window ("Imbibe 0:24, 1:48 · Malignant Catalyst 0:30, 0:35, 1:09, 1:14, 1:54"). For an ability the boss casts itself, it ends with the raid and healing cooldowns pressed around each cast (on the kill, "1:48: healing cooldowns Divine Hymn (Namsus) 1:39, Spirit Link Totem (Enfo) 1:46; raid cooldowns Rallying Cry (Nalaw) 1:46, Anti-Magic Zone (Nexsozz) 1:46, Darkness (Fappachino) 1:47"), so "did we have cooldowns for Imbibe?" is answered from what was pressed at each Imbibe, not only from where the damage spiked.