Changelog
What's new in Wipebot.
Agent the analysis itself, wherever you ask MCP Wipebot in Claude and ChatGPT Discord Wipebot in Discord
0.35.3 · 29 October 2026
Fixed
- "Who did the least damage?" shows the bottom of the meter. Asking for the least damage or healing now ranks only the damage dealers (or only the healers), least first, and the meter is drawn from the bottom: the lowest players get the bars and the top ones the line under them. Before, the meter showed the top ten with tanks and healers below the damage dealers, and the player the answer named only in the small print.
0.35.2 · 29 October 2026
Fixed
- A new guild best is called one. A night's pulls now say themselves whether the night's best wipe beat the guild's best before it, and mark the pull that did, so "P2 64.0%" against Monday's "P2 68.3%" can't be read backwards as a miss. Night by night, a night that got further than every one before says so too.
0.35.1 · 29 October 2026
Fixed
- Norwegian answers keep the game's English words. Answers and what's new posts in another language no longer translate the terms raiders say in English: "holy paladin", not "hellig paladin"; "guild", "armor", "pulls" and "healere", not "gild", "rustning", "trekk" or "helere".
0.35.0 · 29 October 2026
Added
- Top players from raids with your healer count. Comparing a healer's casts with top players now takes top parses from kills with as many healers as their raid had, and you can ask for any count: "the best holy paladin in a 5-heal kill?" is one ranking, where it took a minute and a half of hand-made queries.
- A night's pulls say what ended each. The list of pulls now gives each one's ending and when the wipe was decided, and how many pulls ended in each phase, so a wipe isn't blamed on a death a minute before it was decided; a mechanic's hits over the night add the raid's totals pull by pull.
- A player's night says which deaths a defensive would have saved. It now gives how many of their deaths a ready defensive or a healthstone would have survived, and on which pulls, and their best pull is one long enough to judge (a minute or more), not a 30-second wipe of opening burst.
Changed
- A night's picture counts a wipe by its phase. On a boss with phases, the night's best wipe and the guild's best before it now read as raiders say them ("P2 64%"), with Warcraft Logs' % in each pull's tooltip, and the guild's best in the text gives its phase too; a player's night does the same.
Fixed
- Orb carriers aren't blamed for their own orb. A damage over time that ticks as it's put on a player, like the Coiled Altar's Mutagenic Venom, was counted as hitting them from another carrier whose orb ran out at the same moment, even 75 yd away; it's now their own. Over a night, each such hit also says how far apart the two stood.
- Healing by spell keeps procs apart. Warcraft Logs folds some spells into another's row (Overflowing Light's absorbs under Holy Shock, a shaman's Tidewaters under Healing Rain), so a breakdown by spell counted them as that spell's heals; each now has its own row, and an item's effects carry its name.
- A player's spec is the one they played in the pulls asked about. A healer who tanked another boss that night was called "also Protection in some pulls" over a night they healed throughout, and in Discord got a tank's icon.
- Pull links open the pull named. A link to "pull 12" without the boss's name opened pull 12 of whichever boss came first in a night of several bosses; it now opens the boss the answer read, and a pull it can't place stays plain text.
- What Wipebot remembers is about the asker. A raider's note could rename another raider, in a channel and in that raider's own answers; notes are now only how to answer the one who asked.
- A potion drunk before the pull isn't "never cast". Comparing casts with top players flagged a pre-pull potion as never cast; a buff up as the pull began now reads "cast before the pull", and neither it nor an item not worn is marked red.
- Time at the resource cap is weighed against top players. A player's pull called Fury capped 19% of it a fix when top players of the spec cap as much on that boss; it's now flagged only beyond theirs, with their share beside it.
- Personals checks know the rest of the note. A player who pressed the raid cooldown the note plans for them at a "Big Personals" callout, or a tank who kept a cooldown for the hit just after, was marked as missing it; they're now counted apart, in the text and in blue on the Personals picture.
- Loot doesn't guess a difficulty's item level. When Wowhead's table of a boss's drops leaves out a difficulty (the Coiled Altar's had no Mythic row), the answer now says it isn't known instead of working one out, and an item's worth goes by the raider's own sim at the level they'd get it at.
- A boss's guide is the one for the difficulty you're on. Asked during a first Mythic pull, the guide for a boss cleared on Heroic earlier that night came as Heroic's; it's now the hardest difficulty the night pulled the boss on. A mechanic named under the wrong boss is looked for in the night's raid first, which is faster.
0.34.0 · 28 October 2026
Added
- Compare a mechanic with another night. "Did I take less Axegrinder than on Monday?" now gets each night per minute of the pulls, so a longer night doesn't look worse: the raid's and each raider's, their rank both nights, hits and the deaths it set up. In Discord it's one meter: tonight's bars, a tick at Monday's, and the change.
Changed
- Fewer pictures per answer, after the point they back. An answer posts one view, not the same meter again for another night; a mechanic's hits pull by pull are a button under its meter; two nights' best pulls aren't drawn as a picture of two bars; and a picture comes after the bullet it backs instead of between the headline and the answer. The asker's own row is ringed in a meter, and shown under the top ones when they're further down.
- Buttons say where they go. "My night on The Coiled Altar", "First death: Karadim" and "Open a pull on The Coiled Altar…" instead of "My night", "First death" and "A pull".
0.33.0 · 28 October 2026
Changed
- Meters in the real class colours. Each bar is drawn in its class's in-game colour, as damage meters do, with the name on it in black or white, whichever reads on that colour. In the light theme a bar gets an outline a shade darker, so a priest's white shows where it ends.
0.32.0 · 28 October 2026
Changed
- Names in channels. Wipebot names players in a server channel as it does in a DM: "who took the most damage?" or "who missed kicks?" is answered right where it's asked, instead of being sent to your DMs. It still answers in your DMs when you ask it to.
0.31.1 · 28 October 2026
Fixed
- A cooldown on the other side of a talent choice isn't counted as missed. A Holy Paladin with Avenging Wrath was told they used Avenging Crusader 0 of 5 times; talents whose spell is cast under another id than the tree grants are now known as not taken.
- The player card's cooldowns no longer pile up. Icons used close together stack in rows, each cooldown is named once in the legend by its icon, a spell never cast still gets its icon against top players, and labels keep clear of the next mark.
0.31.0 · 28 October 2026
Changed
- The personals picture shows defensive or not. A raider who pressed some other cooldown at the callout is drawn red like one who pressed nothing, instead of in a colour of its own.
0.30.3 · 28 October 2026
Fixed
- A question about personals gets only the personals picture. When an answer doesn't say which of the raid note's pictures it means, it gets the ones its headline is about, instead of kicks, cooldowns and personals all at once.
- Only callouts that say kick count as kick assignments. A job timed with an add's cast, such as "CC Mindcontrol", was checked and drawn as a kick nobody made; it's now listed as a callout not checked.
0.30.2 · 28 October 2026
Fixed
- Only callouts for personals are checked. A callout asking for something the log can't match to a press, such as grabbing an orb or CCing a mind-controlled player, was judged by whether the player pressed any cooldown around it, which said nothing. It's now listed as not checked, and the raid note's callouts picture shows only the personals.
0.30.1 · 28 October 2026
Fixed
- Ask right after a wipe. A question now reads the live log again as it comes in, so it sees a pull as soon as Warcraft Logs has it (about 5 to 10 seconds after the pull ends), instead of sometimes missing it for up to 30 seconds more when someone else had just asked.
0.30.0 · 28 October 2026
Changed
- Damage and healing meters together. Ask for the best DPS and HPS and the answer posts both meters, the top five of each, instead of only the damage meter, and the text no longer lists them again. A meter on its own still shows the top ten.
0.29.0 · 28 October 2026
Fixed
- "Did people press personals?" counts only defensives. A callout asking for personals or defensives counts a player only when they pressed a defensive (or a tank cooldown), not any spell; those who pressed something else instead are named apart.
Added
- The raid note's callouts, pull by pull. Over a night, each callout's players are drawn pull by pull: pressed what answers it, only something else, nothing, or dead, with how often they answered. An answer about callouts posts only this picture, not the kicks and cooldowns ones, and kick assignments or callouts fewer than three pulls reached aren't drawn (a late one-off drew one huge column).
0.28.1 · 28 October 2026
Fixed
- The pull picture counts a wipe by phase. On a boss whose phases each have their own health bar, such as the Coiled Altar, the pull's card says "P2 80.8%" instead of a bare 80.8% next to Warcraft Logs' whole-fight %s, which it now names "WCL". Its boss health line follows the next phase's boss instead of stopping at 0% when the first one dies, and answers say the phase with the %.
0.28.0 · 28 October 2026
Changed
- What's new posts only what raiders care about. A release whose changes are small tweaks or behind the scenes posts nothing in the what's new channel; its changes wait for the next post.
0.27.0 · 28 October 2026
Added
- Your own guild, without setup. In a server where nobody ran
/wipebot setup, a raider signed in with/loginasks "why did we wipe?" or "how did the night go?" without a link: the bot finds their guild's live report or latest night, from the characters they claimed on Warcraft Logs (their remembered character's guild first). Posts after wipes and raid notes still need setup. Signed in before? Run/loginagain so the bot learns your guild.
0.26.0 · 28 October 2026
Changed
- What's new comes with minor releases only. A patch posts nothing in the what's new channel: its changes come in the next minor release's post, which covers everything since the last one.
0.25.1 · 28 October 2026
Fixed
- A defensive pressed just before a debuff lands. "Was my bubble up for the orb?" reads a debuff on the player (a boss's mark) as well as a buff, and says when it came on while the defensive was still up, where before a bubble pressed a second early read as not covering it.
- A mechanic asked about on the wrong boss. Asked for a mechanic under a boss that doesn't have it, Wipebot finds the raid boss that does and reads its guide, instead of trying boss after boss.
- Out of credit, without "this month". When the bot's AI key runs out, raiders are told it's out of credit and that
/usageshows the budget, instead of "this month", which was wrong for a budget that doesn't reset. - "It's on its way to your DM". Asked to answer in DMs, the bot says the answer is on its way, not that it was sent while it was still being worked out.
0.25.0 · 28 October 2026
Added
- The steps an answer went through, kept under it. An answer ends with a small line of what it looked at, like "✓ Raid note · ✓ Roster · ✓ Compare with top players ×2", the steps shown while it was written.
/wipebot setup steps:turns it off for a server.
Changed
- Clearer pictures. The damage meter draws every class's bar at one lightness with the class colour as its end cap, so names read as well on a priest's bar as on a warlock's; the raid's night colours only the four most common ways pulls ended (the rest grey) and its list of endings is the legend; a raider's plan map over the night says what green and red mean and labels only their three furthest misses.
- Overheal read the way healers read it. Overheal is no longer treated as a healer's fault or compared across specs: it costs only when mana runs out or healing falls short in the damage spikes, and whether the raid needs another healer is read from the spikes. Each healer's healing with overheal comes per second from the log, not worked out from rounded percentages.
- Pushback checked point by point. When a raider disagrees or adds what they know, Wipebot checks each point: it changes what the new fact changes, keeps what the log still supports, and says which points it couldn't check instead of agreeing to all of them.
0.24.1 · 28 October 2026
Fixed
- The guild's raid night, not the Heroic run after it. Asked about the latest raid without a report, Wipebot takes the newest night on the difficulty the guild raids (Mythic, say), not a Heroic or alt run raiders logged to the guild's page the day after; and the guild's report list marks such a run as an easier one, not the raid night.
- Only the pull the answer is about under it. A question about other guilds' logs or the game no longer comes with the guild's own pull the bot looked at on the way.
0.24.0 · 28 October 2026
Added
- Healers' mana and Innervate. "Was I out of mana, and could I have had an Innervate?" is answered from each healer's mana until the wipe was decided, how low it went and from when, and each druid's Innervate: when, on whom and at what mana, or ready while a healer was under 30%; over the night, the pulls each healer ran low and whom the Innervates went to. In Discord, drawn as a picture.
0.23.0 · 28 October 2026
Added
- Who does what, before the pull. Asked about the next raid or a boss not pulled yet, the bot draws the saved raid note: each player's row under tanks, healers and damage, their planned cooldowns and callouts at their times, and their jobs and groups under their name.
- Head-to-head with a raid mate. "Why does Zebinomage do more than me?" sets two raiders side by side, on a pull or every pull on the boss both played: damage or healing per second alive, time alive, deaths, item level, and per spell casts per minute, average hit and crit, what's far apart marked; in Discord, drawn as a picture.
0.22.0 · 28 October 2026
Added
- The raid note over the night, drawn. Checking a raid note against every pull on a boss now posts two pictures: each kick assignment pull by pull (kicked, covered by another, went through, with the first cast that went through before a wipe ringed and counted by player), and each planned cooldown pull by pull (on time, a little off, late, not cast).
- Who gets hit, pull by pull. A mechanic's hits over the whole night add a second picture under the meter: each player's hits on each pull, the ones that led to a death marked, and the raid's total per pull.
- Damage spikes on the pull chart. The pull's chart marks each moment of raid damage taken at twice the usual or more, with its value, and lists the healer cooldowns used in the 10 seconds before it.
- What's new, in a channel of your choice. An admin picks a channel with
/wipebot news, and each new release posts there every change raiders would notice, a line each with its pictures. Off until an admin turns it on. - The server's language.
/wipebot setup language:Norwegianwrites what's new and the posts after wipes in it, and answers a question whose language doesn't show (a bare report link) in it; a question is still answered in its own language.
0.21.0 · 28 October 2026
Added
- Raid damage at a moment. "What was our raid DPS at 2:15 on pull 16?" is answered from the damage in a window of the pull, in a few seconds rather than a minute of the model working it out from raw data. Damage, healing, damage taken and casts all take a window, and a table of damage or healing now starts with the raid's total and per second.
0.20.0 · 28 October 2026
Added
- A saved raid note older than Viserio's says so. On a guild whose host connected its Viserio Cooldowns key, a note checked against a pull, or given for the next raid, says when the note was changed in Viserio after the copy Wipebot has was saved, so an officer knows to paste the new one.
- Private reports. Wipebot can read the private Warcraft Logs reports you may open, once you allow it: at
/wcl/privateon the connector's server (Claude and ChatGPT), or with/login private:Truein Discord. It's a second Warcraft Logs sign-in, so members who only read public logs never see it. A private report is read only for your own questions, never cached or shown to anyone else, and the records of those questions leave out what it showed.
Changed
- How many were on their spot. A check of a raid plan against a pull says, at each moment, how many players were on their spot out of those placed, so an answer's headline matches the count.
- What holds off the enrage. When a boss's enrage ends most pulls of a night, the review looks up what holds it off (a stack, a soak, a kick) and puts that first, before the deaths that left it short.
- Tighter answers. Only the opening verdict's first sentence is bold, bullets are at most two short sentences, and answers no longer end on what only the raiders who were there could know. A player's or boss ability's icon shows on its first mention only.
- Buttons in your language. A Norwegian answer's buttons are Norwegian ("Åpne i Warcraft Logs", "Mot toppene"), and a click's reply follows your Discord's language. Your own card offers **My night** instead of "Their night".
- The cost line comes last. In an answer with a picture it sits under the follow-up buttons, below a thin line.
- Shorter meters. A ranking of players draws the top 10 as bars and the rest on one line, so it no longer fills a phone's screen.
0.19.0 · 28 October 2026
Added
- Post the AI budget. Admins can post what the bot has spent and has left to the channel with
/wipebot usage post, with a bar of how much of the limit is spent. On the public bot it posts the server's share of the month's free answers.
0.18.0 · 27 October 2026
Changed
- Quieter follow-up buttons. The questions an answer suggests are grey buttons now, like the bot's other buttons, and clicking one takes off only that one: the others stay to ask next.
Fixed
- Warcraft Logs points left, on a shared bot. The cost footer and
/usagecount the bot's own share of the hour's points, on a copy that has one (WIPEBOT_WCL_SHARE), instead of the whole account's.
0.17.0 · 27 October 2026
Added
- Wipebot has a logo. A bot whose screen shows a boss's health falling, for the Discord app, the website and the connector: the server names it as its icon for the apps that show one. Its files are in [docs/brand](https://github.com/Enf0/wipebot/tree/main/docs/brand).
Fixed
- Questions without a report. Wipebot answers questions about the game, a class or a boss without a Warcraft Logs report, in a server not set up or before the guild's first raid, instead of only asking for a report link.
- /wipebot key on a guild's own bot says there's nothing to do and no longer offers to sign in with OpenRouter, which would only swap the host's key for another.
- The cost footer's Warcraft Logs points. They're counted once (they were added up several times over) and show what the bot has left this hour, like "80 (3,120/3,600 left this hour)", with your own apart when you're signed in on Warcraft Logs' new point system.
0.16.0 · 27 October 2026
Added
- Sign in with Warcraft Logs in Discord.
/loginsigns you in, as Claude and ChatGPT already do: your own Warcraft Logs points then pay first for what you ask, so the bot's last longer for everyone, and/usageasks Warcraft Logs whether yours are left. Hosts turn it on withWIPEBOT_WCL_CALLBACK([setup.md](https://github.com/Enf0/wipebot/blob/main/docs/setup.md)).
Changed
- The cost footer is a setup option.
/wipebot footeris now/wipebot setup footer:, beside the other settings.
Fixed
- /wipebot key and /usage on a guild's own bot.
/wipebot keyno longer says a guild's own bot answers from shared free answers, its buttons come in the order you use them, and/usagenames no other bot.
0.15.0 · 27 October 2026
Changed
- No more names in chosen channels.
/wipebot namesis gone: in every channel Wipebot names nobody and says what went wrong and how to fix it, and in a DM it names players, as before. Ask it in a channel to answer in your DMs for who missed what.
Fixed
- 0.14.0's slash commands show up. Discord turned down 0.14.0's commands over one description too long, so
/help,/usage,/wipebot keyand/wipebot footerwere missing.
0.14.0 · 27 October 2026
Added
- `/help` and `/usage` for everyone.
/helpsays what to ask, with examples, which commands you can use and how the server is set up; saying "help" to the bot gives the same at once./usageshows how many Warcraft Logs points are left this hour and when they come back, next to the AI budget below. Every command is listed in [features.md](https://github.com/Enf0/wipebot/blob/main/docs/features.md#discord-commands). - Tell Wipebot an answer was wrong. In Claude and ChatGPT, say an answer was wrong, missed something or took too long, and Wipebot offers to send a report to its maintainers: your question, the answer and what you said about it, sent only once you agree. Claude and ChatGPT never show a connector the conversation, so this is how we see the answers that need fixing.
- Damage on adds, wave by wave. Ask "who did the most damage on the last three sets of adds?" and Wipebot gives each wave's damage by player on a pull, on the adds of that wave alone.
- How much Holy Power each cast wasted. Ask "how much Holy Power did my Divine Tolls waste?" or "how many Holy Shocks did I press at 5 Holy Power?" and you get what you had before each cast and what was lost at the cap right after, for Holy Power, Combo Points, Essence and the other resources.
- Healers in other guilds' progress kills. Besides the fastest kills, Wipebot can now count what the latest or the first kills of a boss brought, up to 500 of them and by region: "how many healers did the last 20 progress kills on the Coiled Altar bring?", "of the first 400 kills in EU and US, how many 4-healed?".
- What an answer cost, under it.
/wipebot footerends answers with a small line: their cost, their Warcraft Logs points and, on a bot many servers share, the server's free answers left this month./usagealso shows what the server spent this month. - Bring your own key.
/wipebot keylets an admin answer the server's questions on its own OpenRouter key (sign in with OpenRouter, no copying keys) or an OpenRouter or Anthropic key they paste. It's kept encrypted and never shown again, andremove:goes back to the shared answers. - Ask without setting the bot up. In a server nobody ran
/wipebot setupin, mention the bot with a Warcraft Logs report link and it answers about that report, follow-ups included. Setup still adds the guild's latest raid without a link, posts after wipes and raid notes. - See the bot's AI budget, and chip in. On a bot that answers through OpenRouter, anyone can run
/usageto see what answering has cost this month, how much is left (and about how many answers that is), and how to contribute to it. Hosts set it up in docs/setup.md.
Changed
- Viserio Cooldowns and raidstrats.gg are connected by the host only. Both are still experimental, so
/wipebot viserioand/wipebot raidstratsare gone; the host connects them on the command line (wipebot viserio,wipebot raidstrats-login), and keys already connected keep working.
Fixed
- The boss's health at the end of a pull isn't cut off. The pull's picture had too little room on the right for a value such as 62.59%, which lost its last digit in Claude and ChatGPT.
- Kills and experience for a raider who missed the night. Asking about the season of a raider who isn't in the night's log (signed up, but out that night) now finds them on the guild's realm, instead of failing and searching other reports first.
0.13.0 · 27 October 2026
Added
- See your progress on a boss night by night. Ask "are we doing better on the Coiled Altar than last week?" and the picture now starts with your best pull of each raid night, named by the phase it reached ("P2 68%") and coloured by it, up to the kill. In Claude and ChatGPT, click a night to open it.
0.12.0 · 27 October 2026
Changed
- Wipes on bosses with phases are counted the way raiders count them. On a boss whose phases each have their own health bar, such as the Coiled Altar, a wipe reads "P2 68.3%", with Warcraft Logs' whole-fight % beside it, instead of only Warcraft Logs' 70.5%.
- Fewer "a healthstone would have saved you". A healthstone, potion or heal now only counts when there was a second to press it before the killing hit, and only for the health that was missing then. A big hit from full health followed at once by a tick can't be healed through.
- A restart doesn't end your conversation. When the bot restarts for an update, your next question or follow-up button goes on where the conversation was, instead of starting over without what it found.
- Ready for Warcraft Logs' new API limits. Once the account moves to the new point system, Wipebot notices by itself: members signed in to the connector spend their own Warcraft Logs points first, and when the hour's points for rankings run out, an answer says rankings are back in so many minutes and gives the rest instead of failing. Raiders' character pages are read less often too.
0.11.1 · 27 October 2026
Fixed
- Pictures sit next to what they show, now for real. The bot rarely placed a picture inside its answer, so it still came at the end. Any answer longer than three bullets now puts its picture right after the part it backs, or else (when the bot leaves it out or puts it last) right under its first line.
- Asking a follow-up no longer brings up link previews. Clicking a follow-up under an answer without pictures made Wowhead previews of its links appear under it.
- No advice to press a trinket you don't have. Compared with top players, an on-use item they wear and you don't is marked as not worn, not as never pressed.
- Everyone's damage on the adds. Asked who hit the adds on a pull, the answer has every player's damage on the most damaged kind, pets and totems included, instead of the top four and slow, wrong sums of its own.
- A cooldown written twice in the raid note isn't a miss. A note that plans the same player's cooldown twice a second apart (0:42 and 0:43) made every pull look like one of them was never cast. They're checked as one use now, and the answer says the note lists it twice.
- Posts after wipes keep to what you asked. Asked for a post only below 30 % or every 10th pull, the bot no longer posts after the other pulls, nor a message saying it won't post, and never an empty "(no answer)". The kill gets its post too.
- Notifications show the answer. An answer without pictures is a plain message again, so a notification shows its text instead of nothing. Answers with pictures still show only "attached images": Discord doesn't let those carry a preview.
0.11.0 · 27 October 2026
Added
- Pictures sit next to what they show. An answer about more than one thing, such as two bosses, puts its picture right after the part it backs instead of under the whole answer.
- "How did I do?" after each wipe. A post after a wipe in a channel, and every picture of a pull, has a "How did I do?" button: it shows you your own card on that pull, which only you see. It goes by the character the bot remembers for you; tell it once ("my character is ...").
- Follow-ups are buttons. Instead of ending with "want me to...?", an answer offers up to three follow-ups as buttons under it. Click one and it's asked for you, as if you had typed it; only the one who asked can click them.
- Rankings as a damage meter. When an answer ranks players, such as who took the most damage from a mechanic, who did the most damage or healing, who kicked or dispelled, or who hit the adds, it comes with a picture like an in-game damage meter: a bar per player in their class colour with the amount, per second and share, the raid's median, and for a mechanic the deaths that came soon after a hit. The answer names the few that matter instead of listing everyone.
- Your night when the raid ends. Where someone asked for posts after each wipe, the bot posts one last picture once the raid stops logging: in a channel, the night on the last boss, with **My night** for each raider's own card (only they see it); in a raider's own DMs, their night card.
Fixed
- Dying in the hit that wiped the raid isn't on your card to fix. A player's card listed a death to an ability that killed many at once, such as a missed kick letting Visceral Burst through, as their mistake. It now leaves it out: that hit wiped the raid, whoever's job it was to stop it. A death of their own before it still counts. The same now goes for a player's night, their pull and the defensives check: a death in a hit killing many is counted apart, and no defensive is called a miss there.
- The night of a boss says when an end-of-pull buff decided nothing. A buff the boss gained after the wipe was decided, or as its twin died, read like an enrage that ended the pull. It now says which it was.
- Answers with pictures arrive again. An answer with two pictures of the same player, such as their pull and their night, never came: Discord refused the message for a button the two shared. It now comes, with one view under it and the others a click away from its buttons, so a few pictures no longer fill the screen under a short answer.
- A Devourer Demon Hunter's Fury reads right. A Devourer's card said they gained a negative amount of Fury, since Void Metamorphosis drains it: the drain is now shown on its own, and what they gained and lost at the cap counts only real gains. A stat the log gives below zero, such as a Devourer's Versatility at times, is called out instead of read as their gear's.
0.10.0 · 26 October 2026
Added
- See the pull, not only read it, in Claude and ChatGPT. Asking why a pull wiped shows it drawn under the answer: boss health against the raid's damage taken, the phases, the boss's casts, and each death up to the moment the wipe was decided. Open it for lanes of raid and healer cooldowns and the list of deaths, and click a death to replay the pull from just before it.
- See a player's pull, and how they cast against the top. Asking how someone did on a pull shows a card in Claude and ChatGPT: their healing or damage per second alive, their rank and where it stands among the spec's ranked kills (or their parse on a kill), the time they lost, a ribbon of when they cast, sat capped or were dead with their cooldowns on it, and one click compares their casts per minute with top players of their spec. In Discord the same card comes as a picture, with the biggest differences against the top when you ask for that comparison.
- A player's night at a glance. Asking how someone did over a night on a boss shows a card in Claude and ChatGPT, and a picture in Discord: their healing or damage per second alive pull by pull, where they died and whether it counted (before the wipe was decided), the boss's health left at the end of each pull, the trend in thirds, and their cooldowns summed. Open it for a table of every pull; click one for that pull's own card.
- A kill's card says how fast and how clean it was, and a death a mechanic dealt outright is called that. The pull card of a kill shows its speed and execution percentiles against other kills of the boss. On a player's night and in the defensives check, a death with no hit logged after high health reads "killed outright" (nothing ready would have stopped it) instead of "can't tell".
- See the raid's night on a boss. Asking how the night went shows every pull as a bar of the boss's health left, coloured by what ended it, with the night's best so far and the guild's best before the night; then how the pulls ended and what killed each pull's first deaths, ranked. Click a pull for its own card; on a night with several bosses, switch between them. In Discord it comes as two pictures.
- See a death. Asking what killed someone shows the death drawn, in Claude and ChatGPT and as a picture in Discord: the hits in the 10 seconds before it with their health after each, the healing they got, the killing blow, the defensives they had ready, and who died with them. When a mechanic kills outright, with no hit logged while they were at high health, it says so instead of blaming the healing.
- A player's night says what keeps killing them, and whether they could have lived. The night card now leads with what killed them before each wipe was decided, most deaths first, with a chip per pull: green where a ready defensive or a healthstone would have kept them alive. Their output and deaths pull by pull follow; in Discord the two come as separate pictures, each readable on a phone.
- The pull and player cards say more at a glance. Each death on the pull's card shows what killed it, and a line says how the wipe stands against the night's earlier pulls and the guild's best (a new guild best in gold). A player's card lists up to two things that went well and two to fix: a death before the wipe was decided, time without casting, a capped resource, a cooldown left unused, where they rank.
- Click through the pictures. Under each picture are buttons for the next thing to look at: the pull's first death or a player's card, a player's casts against the top or their night, a pull of the night, and "My night" for your own. Only you see what you open, and it comes with its own buttons, so you can keep going. Buttons on older answers keep working.
- Pictures come whole, one under another. An answer with several pictures showed them side by side, each cropped to a tile until tapped; now each sits full width under the answer, with a button to its pull on Warcraft Logs, and a gold edge when the pull is a new guild best. A message also holds twice the text, so long answers come in fewer messages.
- The pull as a picture with the answer. Asking about a pull, and the post after each wipe, come with the same picture of the pull as in Claude and ChatGPT: boss health against the raid's damage taken, phases, the boss's casts and each death.
Changed
- Boss strategy that keeps up with nerfs. Asking how a boss works or what to know before a night now comes with Blizzard's hotfixes to that boss that are newer than the guides, so a nerf the guides haven't caught up with (fewer orbs, fewer targets) is in the answer. The guides' Mythic strategy now comes whole, through the last phase, and the ability list shows only the difficulty you raid.
Fixed
- Whose kick it was, from your raid note. When casts got through or a mechanic hit the wrong people, the answer could say the log doesn't show whose job it was, even with your raid note saved. Now it knows the guild has a note for that night and checks it, and for kicks whether the note assigns any.
- Notes at the top of a thread. Asking in a thread now reads the messages it opens with, such as a forum post and the notes posted under it, however old; before, only the last 12 hours were read.
0.9.0 · 25 October 2026
Changed
- Answers keep to what decided your question. A side story that didn't decide it is left out or offered in a line, and a big question (a whole fight, every raider's job) gets the part you asked for first, with the rest offered.
0.8.0 · 25 October 2026
Added
- Link your own notes in a question. Ask "how do we do Coiled Altar? <link>" with a link to a message, thread or channel, and the answer goes by what your guild wrote there over the guides. It reads only what you can read yourself, and needs the bot to read channel messages (
WIPEBOT_CHANNEL_CONTEXT=1). - Who's in for the coming raid nights, from Viserio Cooldowns. Ask "am I in on Coiled Altar tomorrow?", "who's benched?" or "who's coming Monday?": the answer reads the calendar's sign-ups and the week's setup per boss. An officer connects the group's key once with
/wipebot viserio. - A raid plan's scenes come with their links. An answer about a scene can link it on raidstrats.gg instead of naming its number.
- Raid markers, spec and boss ability icons in answers. A raid marker shows as its icon, whether the answer quotes a note's {skull} or says "the star marker"; each mention of a raider gets their spec's icon instead of bold; and a boss ability gets the icon you know from your boss mod. Lists of who does what go one raider per line. Answers also mark what was done with ✅ and the thing to fix first with ⚠️.
Changed
- The line under your question shows what the answer is doing. What it's reading right now, with the boss and pull ("Reading the raid plan (Coiled Altar)") and a spinner, what it has already looked at with a tick, and how long ago you asked.
Fixed
- Asking the bot about a boss you haven't pulled yet reads the saved note and plan. The note saved for tomorrow is given as it is, and the plan shown as drawn, as in Claude, instead of the bot saying it can only read them against a night with pulls.
- A note for a boss not pulled yet names its cooldowns, so each spell in the answer reads and links like the others.
0.7.0 · 25 October 2026
Added
- Ask about the guild's raid plan, with no pull to check it against. "What's our plan for Coiled Altar?", "Where do I stand in P2?" or "Who takes the orbs?" is answered from the plan as drawn on raidstrats.gg, scene by scene: each spot by the boss and the raid markers, what each number does from the plan's side panel, the notes, and what's drawn around them. A plan exported from Viserio with the night's names filled in answers for each raider by name.
Fixed
- Asking about a boss you haven't pulled yet works. The plan is shown as drawn and the newest saved note as it is, instead of an error saying the night has no such boss.
- A raid plan missing because the guild's raidstrats.gg login stopped working now says so. Instead of "none saved", the answer says the plans can't be fetched and an officer has to connect again.
- No more empty replay box. Questions about the raid plan answer in text, and the pull's replay with the plan's spots opens when you ask to see a pull against the plan. Over a whole night, the box shows the answer's map instead of nothing.
0.6.0 · 24 October 2026
Changed
- Posts after a wipe come sooner. A post starts from the pull, and the guides on what ended it, already looked up, so a typical one arrives about seven seconds sooner and the slowest about fifteen.
0.5.3 · 24 October 2026
Fixed
- A late taunt is no longer read as no missed taunt. The tank swaps now name a swap debuff that stacked past one while a tank held the boss, and when the other tank took it over, so "did I miss a taunt?" gets the late swap the log shows, still without calling it one tank's fault.
0.5.2 · 23 October 2026
Fixed
- ChatGPT no longer counts the replay viewer as a write. The two tools only the pull replay calls were listed under Write in ChatGPT, beside saving a raid note, as tools that may change something; they only read.
0.5.1 · 23 October 2026
Fixed
- The plugin's connector in Codex. Installed from its marketplace in Codex, also inside the ChatGPT desktop app, the plugin brought only the method for reading raid logs, without the connector to sign in to; it now brings both. ChatGPT's chats take the connector on its own.
0.5.0 · 23 October 2026
Added
- The plugin in Codex and ChatGPT. The same plugin, the connector with the method for reading raid logs, now also installs in Codex and the ChatGPT desktop app:
codex plugin marketplace addwith the plugin's repository, then install it from the Plugins directory and sign in with Warcraft Logs.
0.4.0 · 23 October 2026
Added
- What Wipebot is looking at. When an answer takes a while, a small line under your question shows which parts of the log Wipebot has read so far. It goes away when the answer is posted, and you're notified of the answer, not of the line.
- A realistic target against the top players. Asked what the top players of a spec do on a boss, Wipebot now also says where the spec's kills spread (the 90th, 75th, 50th and 25th percentile), so you have a level to aim at rather than the single best parse. For a healer, it shows how many healers each top log had and how much of their healing the top healer did, next to your own raid's, since a healer's numbers depend on the healers around them.
- A public copy for any guild. Wipebot now also runs at [wipebot.enfo.dev](https://wipebot.enfo.dev) for anyone with a Warcraft Logs account, free and best effort: in Claude, add the marketplace
Enf0/wipebot-plugin; elsewhere, addhttps://wipebot.enfo.dev/mcpas a connector. It shares one Warcraft Logs allowance, so each user gets part of it per hour, and questions that need new data can wait for the next hour.
Changed
- Someone who is no longer signed in to Wipebot from any app is forgotten 90 days later: their Warcraft Logs name and characters are deleted.
Fixed
- A text chart in an answer no longer shows spell links as raw markdown inside it.
0.3.0 · 23 October 2026
Added
- A raid note pasted late. Forgot to paste the note before the raid? Paste it afterwards with the pull it was used from, such as "from pull 7", and that pull and the later ones are checked against it, while the earlier ones keep that night's note saved before, if there was one.
- When the kick order changed. Checking the night's kicks against a note that only fits the later pulls, Wipebot says from which pull it fits and who had the slots before, and counts the kicks from there, so no one is blamed for a slot that wasn't theirs yet. Tanks covering someone's kick are read as backup, not as another order.
- Holy Power lost at the cap. Asked how a Holy Paladin or Preservation Evoker did, Wipebot now looks at their Holy Power or Essence as well as their mana: how long it sat full, how much was lost there and from which spells, on a pull and over the night, and how long the top players of the spec sit full on the same boss.
- Whose kick lost the pull. Over a night, Wipebot counts per player whose cast went through first on each pull lost to kicks, since the casts after it come too late to matter, and lists every such pull.
Changed
- Advice on how to play your spec, such as what to cast or spend and when, now follows its class guides: Wipebot reads the spec's guide before telling you what to change.
- The first "how did I do tonight?" about a night now answers about 20 seconds sooner: a player's night of 40 pulls is read in a few requests instead of eighty one after another.
- A saved raid note now counts only for the raid night it was pasted for, since the note changes each night with who comes: a night nothing was pasted for asks for the note instead of using another night's.
- A kick on someone's cast that another player took, such as a tank backing up, now counts as covered instead of missed: the cast was handled. Who missed most is now whose casts went through, and the pulls lost within seconds of kicks going through are named, with which assignments they were.
Fixed
- Who had a kick ready when a cast went through now counts every spell a player kicked with that night, so a player with a second interrupt on hand is no longer read as having none.
- A raid note changed during a raid no longer carries over to the next raid night: the night's pulls before a note pasted late used the last night's note instead of that night's.
- Asked who got caught by a mechanic that only puts a debuff on players, such as a wave that stacks one, Wipebot now ranks them by how often it caught them instead of by the little damage it dealt.
0.2.0 · 22 October 2026
Added
- Week over week. Ask whether the raid is doing better on a boss than last week, and Wipebot goes through each of the guild's raid nights on it: the pulls, the kill, the best wipe and what ended the pulls, night by night.
- Pulls by name. Ask about the kill, the best wipe, the last wipe, or the first or last pull of a boss, and Wipebot finds it without looking up its number first.
- One stretch of a pull. Who got hit by a mechanic can be counted for one stretch of each pull, such as the first set of orbs, without the rest of the pull mixing in.
- Answers in your DMs. Ask Wipebot in a channel to send something to your DMs, such as who missed their kicks, and it answers there as if you'd asked there, where it may name players. It only ever writes to the one who asked.
- The raid plan in the replay. In Claude, checking a pull against the raid plan opens the pull's replay with the plan's spots on it: a button for each time its mechanic happened, and at each, a red ring and a line from the spot of every player who stood off theirs.
Changed
- In Claude, the plugin's method now loads before Wipebot's first tool call on any raid question; smaller models such as Haiku had skipped it on most questions.
- A question that assumes its answer, such as "do we need more DPS?", now gets that checked first: the answer opens with what the log shows lost the pull. Asked what to change, Wipebot says whether to keep the plan or change it, which damage spike needs a healing cooldown, and whether more damage or another healer would help at all.
- Why a pull wiped now says whether it ended the way earlier pulls that night did, or got past the thing that ended most of them.
- How the night went now counts the pulls by what ended each, so the one thing that ends most of them stands out; why a pull wiped says plainly when it wasn't the boss's enrage or a damage check; and who was hit, stood where or had a kick ready comes with a reminder that whose job it was isn't in the log.
- Why a pull wiped now names the deaths that led into the moment that lost it, counts an ability that kills in pulses over a few seconds (a set of hits, a wave of adds) as one moment, and no longer starts a run of deaths at a player who was battle-ressed.
- Asking about the adds over the whole night now also gives, for the most damaged kinds, when each wave of them died and each player's damage on them over the pulls.
- Where everyone stood at a moment now also gives each player's distance to the player you ask about, such as the one carrying a mark the raid stacks on, so who was in range is measured rather than guessed from where they stood around the boss.
Fixed
- A late taunt is no longer called one tank's fault: the log shows who taunted when, not whose turn it was. Asked what stats to aim for, Wipebot gives the spec guide's priority and treats what the top players wear as a note beside it, not a new priority.
- Comparing your talents with the top players says which part of the tree each is in (class, spec or hero), so it no longer suggests swapping a class talent for a spec talent.
- In a DM, Wipebot knows you by your nickname in the guild's server, so a character named there is found without asking.
- When Warcraft Logs is down, questions about a raid night Wipebot has already read are still answered from what it kept, instead of failing on the first step.
- Comparing your talents with the top players no longer lists a spell with two versions on one choice node (such as Earthquake, Blizzard or Rain of Fire) as a talent you lack: Wipebot says you took the other version, and how the two differ.
- Asked about the whole night while the next pull is under way, defensives, healing, damage and healing breakdowns, the adds, and checks against the raid note or plan no longer count that unfinished pull: they leave it out and say so, as the other answers about the night already did.
- Asking whether a boss has an enrage now finds what the guides say about it, whether they call it an enrage or a berserk.
0.1.0 · 21 October 2026
Added
- Wipebot is open source. Any guild can run its own copy, under the GNU AGPL v3.0: the connector its members add to Claude, ChatGPT or another assistant, and the Discord bot. How to set it up: docs/setup.md.
0.0.11 · 21 October 2026
Added
- Save the raid note or plan from Claude or ChatGPT. An officer (by default the Guild Master and Officer ranks in the guild) pastes the note exported from Viserio, or the plan's export from raidstrats.gg, and asks Wipebot to save it for the guild. From then on, everyone's answers in Claude, ChatGPT and Discord check pulls against it without a paste. Anyone else's paste is used for that answer only.
- Officers save the raid note or plan by pasting it. An admin sets the officers' role with
/wipebot setup officers:; until one is set, the members who can manage the server are the officers. Officers also change or stop the posts after wipes someone else asked for in a channel./wipebot noteis gone: an officer pastes the note or plan in a message to Wipebot instead (Discord's file for a long paste works too), and/wipebot settingsnow lists what's saved. - Names in the channels you choose. An admin turns naming players on or off in any channel with
/wipebot names: there, and in its threads, Wipebot says who made the costly mistakes, as in a DM. It replaces the officers' channel in/wipebot setup, and names stay on where that was. - The adds over the whole night. Ask how the adds went on a boss across the night and see how many of each came and died over the pulls, the damage they took, their casts and who kicked them, and each pull in a line. When the log records no deaths for an add, Wipebot says it can't show the order they were killed in.
Changed
- Questions about defensives and raid cooldowns are answered a few seconds sooner the first time they're asked about a night.
- When the hour's Warcraft Logs allowance is nearly used up, the few questions that read many nights or pulls at once (the tanks' taunts over the weeks, attendance, the healing over a night, what a raider keeps dying to over the weeks) are left for later, with a note saying in how many minutes to ask again, so the other questions still get answers.
- Signing in from Claude or ChatGPT now shows which app is asking and where you go back to once you're signed in, before the Warcraft Logs login: one click goes on. A sign-in finishes only in the browser it was started in.
- Damage, healing, damage taken and casts over a pull or a night now stop where each wipe was decided, as Wipebot's other answers do, so what happened after the boss's enrage doesn't swamp the cause. Ask for the whole pull to include it.
- Checking soaks against the raid note, a player hit by almost none of their group's soaks is named as likely not soaking with that group, such as a reserve or someone moved since the note was written, rather than only counted as missing them all.
Fixed
- A moment's hiccup at Warcraft Logs no longer signs you out of Wipebot in Claude or ChatGPT.
- A boss named as one word, such as "twinfangs", is now found in questions about the night's logs, as it already was in the guides.
- Where several guilds share one Wipebot, asking in Claude or ChatGPT about "our last raid" now means your own guild's. It used to be the first guild's for everyone.
- A question asked while Wipebot was still writing a post after a wipe for you is answered even when that post takes too long or fails. It used to get "Something went wrong" as well. An answer under way when the next raid night's log starts now finishes, and when the logs take over a minute to load, Wipebot says so instead of waiting on.
- When many raiders get their feedback after the same wipe, every answer now finishes. With more than six answers at once, one used to stop halfway with "Something went wrong". And after an answer failed, asking again starts afresh instead of failing the same way.
- Rankings, attendance, a raider's logs and guides are no longer weeks old in the first answer after a quiet spell. That answer used to show what Wipebot had last read, however long ago, and only the next one was up to date.
- During a raid, a pull that ended while Wipebot was reading it now shows in full in later answers. Its deaths and numbers used to stop where the pull was when Wipebot first read it.
- When Warcraft Logs stops answering for a moment during a raid, questions about the night are answered from what Wipebot read of the log seconds before. They used to fail.
- After a patch, the spec cooldowns, talents and spell names Wipebot counts with are up to date within a day. They used to stay as they were until Wipebot restarted.
- A shaman back from Reincarnation, or anyone else who comes back to life by themselves, now counts as alive again, as after a battle res: in the players alive after each death, when half the raid was dead, and whether they could have cast a planned cooldown or kick. They used to count as dead until they died again.
- A Demon Hunter who dies stays dead in their time alive, time lost and cooldowns ready again until something brings them back. A cast Warcraft Logs adds by itself a second after the death used to count them alive for the rest of the pull.
- Who took far more of a boss's damage than the rest now counts the time a player was alive again after a battle res. A player brought back early used to look as if they'd stood in everything.
- Who had a kick ready when an add's cast went through now includes players brought back by a battle res. Once they had died, they used to be left out for the rest of the pull.
- A cooldown that came back only after the wipe was decided is no longer called ready again and unused on a raider's pull: by then no use was missed.
- When Warcraft Logs answers only part of a question about a night's pulls, Wipebot says so and to ask again. It used to fail with an unexpected error.
- When Warcraft Logs isn't answering, Wipebot now says so and asks you to try again in a few minutes. It used to say nothing at all.
- A post after a wipe no longer gives up while Wipebot is still answering your last question, and after a restart in the middle of the raid it posts about the latest wipe only, not about every wipe it missed. A question also no longer waits while Wipebot starts a conversation with someone else.
- "Was Bloodlust up when I pressed my cooldown?" now finds it whichever kind the raid had, such as Time Warp or Primal Rage, and a buff someone else gave you, such as Power Infusion, now shows at your casts too. Wipebot used to see only the buffs you gave yourself.
- Asked how a boss works on Normal, Wipebot now reads the guides' Heroic strategy. It used to read the Mythic one.
- Where a player's damage or healing on a wipe stands among their spec's kills is measured against every ranked kill again. Early in a patch it could count only the best 100, so the same player read as below the 25th percentile one time and above the 75th the next.
- One hit that kills ten players in a second is no longer split into deaths that count and "fallout" a few milliseconds later: when half the raid dies at once, every death of that moment counts, and the deaths in the seconds after it are fallout. Half the raid dead now means half, with a battle res counted, and a buff a council boss gains when its partner dies is no longer read as the moment the wipe was decided, nor as how the wipe ended or a reason to leave later deaths out of what killed the first players.
- What killed players in each pull's post counts only the deaths until the wipe was decided, so an enrage's fallout no longer tops the list, and no killer drops off the end. A pull still going reads as in progress, not as a wipe or a new best, the latest finished pull is the one meant when no pull is named, and a raider's night, who took most of each mechanic over the night and a raider's deaths over the weeks leave it out until it ends.
- Players alive after each death count a battle res, and many dying at once with no killing blow in the log reads as one moment that killed many, not as deaths one after another.
- An ability the log records under several ids, such as Virulence, is counted once: a death after hits of both no longer counts twice, and the night's killer, who took most of a mechanic and the abilities behind a damage spike each show it as one. How many hits landed within a second of each other now says, right beside the count, that the log can't tell one hit from two.
- A player's cooldown uses against possible uses count only until they died or the wipe was decided, so time dead and the fallout no longer add uses they could never have pressed. A night's count above what the base cooldown allows, such as 2/1, now says a talent or effect shortens it, as one pull's count did.
- A player's casting gaps are no longer excused as a raid-wide pause because most of the raid was dead: a pause is when most of the living stopped casting.
- A wipe compared with a kill now says how far behind the kill's pace the pull was and since when, whether the kill was over before the boss's enrage, and how many had died on each side by then, so a wipe lost to deaths no longer reads as a damage check. The side-by-side table is shorter.
0.0.10 · 19 October 2026
Added
- Who didn't kick as assigned? A kick order in the raid note, such as "Kick #1 left" called to one player as an add starts its cast, is now checked against the log: who kicked each cast, who didn't, and which casts went through, for a pull or the whole night. Whichever side's add starts casting first, each cast is put on the right player.
- Raid plans fetched from raidstrats.gg. An officer connects their raidstrats.gg login once with
/wipebot raidstrats, and nobody pastes plans any more: whenever an answer needs a plan, Wipebot fetches the guild's plans, in Discord and in Claude and ChatGPT alike, and keeps a new version when one changed.
Fixed
- Asked about casts that went through, Wipebot now names the players who never kicked on the boss that night. It used to give only their number, and could name the wrong ones.
- A boss pulled after a long break in the raid, such as the next boss after dinner, now shows up in Wipebot's answers. After a break of 20 minutes or more, Wipebot used to stop reading the night's log, and said the boss wasn't in it.
- Asked about the raid plan, Wipebot now says it fetched the plans from raidstrats.gg, as which account and when, and that a newer version was saved since the pulls were planned. Ask it to check against the newest version and it checks every pull against that one. It used to show only the version each pull was planned with, and said no raidstrats.gg login was connected when one was.
- Answers in Discord are easier to skim: they open with one short bold line, a player's name is bold only the first time it comes up, and the fix for the next pull comes first instead of last.
- A raid plan pasted to Wipebot stays the one it uses until the plan changes on raidstrats.gg. The next fetch used to replace it with the plan as last saved there, which leaves out a roster given only in the planner's link.
0.0.9 · 18 October 2026
Fixed
- Casts per spell, yours and the top players', now count spells Warcraft Logs files under another one, such as Infernal Bolt under Shadow Bolt, Void Blast under Mind Blast or Fatebound Coin under Hand of Fate. They used to be missing, or shown as not counted.
0.0.8 · 17 October 2026
Added
- The saved raid note and plan in Claude and ChatGPT. "Did people do their jobs?" and "was everyone on their spot?" no longer need a paste: Wipebot checks your guild's pulls against the note and plan your officers saved in Discord.
- Where do I want my cooldowns? Ask what the top players of a spec do on a boss and see when the top five pressed their major cooldowns, beside the boss's casts, and how many of the top 50 use each.
- Did the healers keep up? Ask about a pull or the whole night and see when the raid took the most damage, which abilities it came from, how much healing went into it, each healer's healing and overhealing in those seconds, and which healing cooldowns were used or still ready. Over a night, the spikes that came back pull after pull are grouped, so you can see which one gets no cooldowns.
Changed
- Sign in with Warcraft Logs. Connecting Wipebot in Claude or ChatGPT now asks for your Warcraft Logs account instead of Battle.net, and knows your characters from the ones you claimed there. Claim your main on warcraftlogs.com first. If you're already connected, you'll be asked to sign in once more.
- What killed a player now also says what each healer was casting in the last five seconds, and on whom.
- "Would a defensive have saved them?" now has an answer for Exhilaration, Survival of the Fittest, Desperate Prayer, Ice Barrier, Blazing Barrier and Rallying Cry, where it used to say it couldn't tell.
- Casts by player show how many a minute, so players on pulls of different lengths compare directly.
- Wipebot refers to players by their character's name, never guessing "he" or "she".
Fixed
- A raid-wide stun or knockback no longer counts as your casting gap: stretches when most of the raid cast nothing are left out, and named.
- A player brought back by a battle res counts as alive again: checks of the raid note's callouts and of who should have taken a mechanic no longer call them dead for the rest of the pull.
- A pull's timeline says the boss's health it ended at, and the wipe's percentage beside it when the two differ (Warcraft Logs weighs phases into the wipe's), so 8.95% and 6.4% for the same pull no longer look like a contradiction.
0.0.7 · 16 October 2026
Added
- Am I getting better? How you did over a night now ends with your trend: deaths before each wipe was decided and your damage or healing per second alive, over the first, middle and last third of the pulls.
Changed
- Who pulled? A pull where one player hit the boss and nobody else followed is now called out, and pulls the raid reset are marked.
- How you did on a pull now shows when the boss cast its main abilities (Imbibe on Vashnik) beside your cooldowns, so a raid cooldown held for the damage isn't read as a late one.
Fixed
- The pull timeline shows the boss's casts in the second they happened; they could show a second early.
- Reading a page of a class guide that an earlier answer linked works for Wowhead and Icy Veins pages too; it could fail with an error.
- Raid prep says how many players lack each consumable, not only who.
- Adds that the log splits over two units (Vashnik's Malignant Totems) no longer show more deaths than came.
- A buff both bosses gain at the end (the Coiled Altar's Soulbound) is listed once.
- An add's cast whose start the log puts on another unit (a Drowned Echo's Soulcoiler's Curse) is counted as one cast that went through, as Warcraft Logs counts it, so the kick counts agree wherever you ask.
- A channelled cooldown such as Divine Hymn counts once per use, not once per tick.
- Whether a defensive would have saved you no longer counts on Cloak of Shadows lasting its full 5 seconds: its immunity is sure only for a moment.
0.0.6 · 15 October 2026
Added
- One Wipebot. Wipebot in Claude and ChatGPT and in Discord are one now, with one name wherever you ask. Nothing to re-add: a connector you added before keeps working.
- Raid plans from raidstrats.gg. An officer pastes the plan's export (the planner's Export button) to Wipebot, or attaches it to
/wipebot note, and answers check where everyone stood against their spot: who was off it, by how far, and whose spot they took. A map shows the plan laid over where the raid stood, with a line from each missed spot to its player, or one player at every spread of the night. Paste it again after a change during the raid, and earlier pulls keep the version they were planned with. - Where did we stand when it went off? Ask where everyone stood when a mechanic happened, on any boss: each time a debuff ran out, the boss cast it or it hit, see who had it, who was hit by someone else's and how far apart they stood, on one pull or over the night, with a map of where you stood each time. In Claude and ChatGPT, paste the plan's export to check positions against it too.
- Your stats on the pull. Asking how you did or how your build compares shows the crit, haste, mastery and versatility your gear gave you on that pull, straight from the log, so two players of the same spec can be compared stat by stat.
- Anything else in Warcraft Logs. For a question no other answer covers, such as kills around your own item level rather than the fastest, the players in one fight of another guild's log, or events of one kind, Wipebot can now ask Warcraft Logs directly. Such answers take a little longer.
- Any guide or news page. Wipebot can search Wowhead, Method, Icy Veins and Warcraft Wiki and read any of their pages in full, so a question no other answer covers, such as the rest of a news post, a guide's other pages or a wiki article, is looked up rather than turned down.
- Is it a 4-heal fight? Ask what the top raids bring to a boss and see how many tanks, healers, melee and ranged the 50 fastest kills had, how fast each setup killed it, and links to the fastest kills.
- Who pulled? Ask who keeps pulling the boss early and get who hit the boss first on each pull, with what, how far ahead of everyone else, and a count over the night. The log has no pull timer, so it shows who opens and who goes on their own, not how early against the countdown.
Changed
- Who played well on the kill? Damage and healing by player on a kill now show each player's spec and parse, so players of different specs are compared by how they did for their spec, not by raw numbers.
- Did people press what the note called for? Callouts in the raid note, like "Big Personals" to everyone or a job for one player, are now checked against each pull: who pressed a defensive, raid cooldown or other spell around the call, and who had one ready and pressed nothing.
- The raid note over the whole night. Ask "who missed their soak most?" or "who pressed personals when the note said?" and get each player counted over every pull on the boss, in seconds rather than a minute: soaks of their group they missed while alive, each planned cooldown on time, early, late or not cast, and how often they pressed something at each callout.
- When do your cooldowns go out? How you did over the night now shows when you used each major cooldown on every pull, and when the first one usually went out, so "when does my first Arcane Surge go out?" gets the times and the outliers in one answer. Whether a buff was up when you cast a spell can be asked over every pull too.
- Your stats against the top players. Comparing your build with the top players now shows their crit, haste, mastery and versatility from their own logs next to yours, as shares of the total, so "how do my stats compare with the top?" gets numbers rather than only the guide's stat priority.
- Was it the mechanics? Comparing how you play with the top players now shows how much of the time your energy, rage or other resource sat full next to how much theirs did on the same boss, so "I was capped because of the mechanics" can be checked: they meet the same fight.
- Who took the bait? Asking who took a mechanic meant for one player, such as a mark the furthest player gets, lists each time someone else got it over the night: the pull, when, how long they kept it and whether the player it was meant for was still alive. It answers in seconds rather than going through the night pull by pull.
- Posts after each wipe are a few short lines you can read before the next pull: how it ended, what decided it, and what to do next.
- Comparing your build with the top players names the enchants they use on each slot where yours is missing or different, so "which enchant should I take?" is answered from the logs.
- Asking how hard a spell hits shows its hits, average hit and crit rate per player, so "why does their Starsurge hit harder than mine?" gets numbers.
- Asking about tank swaps shows when each tank used their taunt and when it was ready again, so "was the taunt on cooldown?" is answered from the log.
Fixed
- A kill no longer reads as the boss left at 0.01%, which made a clean kill sound like a near miss.
- On a fight with several bosses, a buff each of them gains, like the Entombed Sentinels' enrage, is counted once per pull rather than once per boss.
- Checking a raid note against a pull that ended early, or against a kill shorter than the note, now still lists the cooldowns planned after that point, so a review of the note covers all of it instead of saying the rest can't be seen.
- Adds the log records under two ids, such as some boss totems, are counted whole: how many died and how many were still up at the end no longer misses about half of them.
- Claude and ChatGPT ask you to sign in to Wipebot again less often: a hiccup while they renew the connection no longer signs you out.
- Dispel counts add up: each debuff applied was either dispelled or ran out, and a dispel that only took a stack off is counted apart. Before, the dispelled and ran-out counts could add up to more than were applied.
- A Restoration Shaman's healing by spell shows the health Spirit Link Totem took from healthier players on a line of its own, out of the total and the shares; before, it was a negative row that lowered them.
- Asking for your guild's other raid nights finds them without your server and region; before, the answer could stop to ask for them.
- On a night with a single-boss raid as well as the tier's, Wipebot knows which raid each boss is in, so "the first boss" is the raid's first and the answer says which boss it took; before, a boss from the other raid pulled first could be taken for it.
- A boss named any way ("Twinfangs", "Twin Fangs") finds its guides, all three of them; before, a name spelled differently from the guide sites could miss Method's guide or every guide.
- Asking about a boss's hotfixes finds every one of Blizzard's changes since the raid opened; before, only Blizzard's newest hotfix post was read, so changes from before the latest patch were missed.
- Asking about a boss's nerfs finds Wowhead's post about them and reads it; before, another boss with a similar name could hide it, and only the newest post about the boss was read.
- When a guide site or Warcraft Logs can't answer, the part of the answer that needs it says it's unavailable and the rest still comes; before, it could read as no defensives, no cooldowns or not ranked, or fail the whole answer.
- A defensive or raid cooldown cast as the talent that replaces it (Crusade for Avenging Wrath, the other Divine Protection) counts as used in a death's breakdown, the night's defensives and the raid note's callouts; before, it could read as never pressed.
- Abilities are found by name the same way in every question: capitals and accents don't matter, and a name the log doesn't have gets the closest ones it does.
- Posts after each wipe keep coming when Wipebot restarts during the raid; before, a restart ended them until someone asked again.
- A wipe is called a new best only when it beats the guild's earlier nights on that boss too, not just tonight's pulls; the answer says where the guild got before, with a link to that pull.
- A cooldown in the raid note that nobody has cast yet that night shows by its name, not as a spell number.
- Spell descriptions include what applies to one spec only, so Death Grip shows as a taunt for Blood Death Knights.
- Hit counts for an ability that has several versions in the log, like Raging Crosswinds on Sszorak, count all of them, not only the first.
- A cooldown used before the pull, like Stormkeeper, counts as used when your cooldown use is checked; before, it looked like a missed use.
0.0.5 · 14 October 2026
Added
- Posts after each wipe, wherever you ask. Ask Wipebot in any channel or a DM to keep you posted during the raid, with whatever you want to hear after each wipe of the live log, like who died first and why or what to fix on the next pull. You can ask before the raid starts logging: the posts start with the first wipe. Anyone can ask it to stop.
- An officer channel. Server admins can mark a channel only officers see in
/wipebot setup. There Wipebot names players and says plainly who made the costly mistakes, in answers and in the posts after each wipe. - What do I keep dying to? Ask what you keep dying to, or what to work on this week, and get your early deaths on each of the guild's raid nights in recent weeks: how often you died before the wipe was decided, how often first, and the abilities that come back night after night.
- Deaths with no killing blow. When the log names nothing that killed someone, the death's details now say where they were last seen and how far they had just moved, so being thrown or knocked off the platform shows.
- Did anyone have a kick ready? For each add cast that got through, the answer can say who was alive with their interrupt off cooldown when it began, from the interrupts each player used on that boss.
- What top players play on a boss, before you've pulled it. Ask what the top Balance Druids (or any spec) play on a boss and get what the best Warcraft Logs parses take: hero tree, the talents where they differ, how the guides' builds compare, trinkets, item level and kill time, links to the top logs and an import string to paste. It works for a boss your guild hasn't pulled yet, as soon as the first kills are ranked.
Changed
- Asking about tank swaps also shows which spells each tank has taken a boss with on the guild's recent raid nights, so whether a spell like Death Grip works as a taunt is answered from your own logs.
- Player names in answers are in bold, so you can find who's mentioned at a glance.
- Asking why a pull wiped starts from how it ended: one ability killing many at once, the boss's enrage, or deaths one after another, with when each came. A night's review names what killed the raid most, how often it was the first death, whom it killed and who took most of its hits.
- Asking how you did or why your damage is low weighs your biggest losses against each other: time dead before the wipe was decided, time without casting and time at your resource's cap, so the answer leads with what cost you most.
- In Claude and ChatGPT, each Wipebot tool says which questions it answers and how to read what it returns, and every tool has a readable name.
Fixed
- Asking how you did on a kill right after it no longer fails while Warcraft Logs hasn't ranked the kill yet; your parse shows once it has.
- Answers about an earlier night, asked while another report is current, link their spells to Wowhead again.
- ChatGPT no longer asks you to approve each Wipebot lookup: they only read your logs and the guides.
- A talent named in an answer no longer gets a Wowhead link to a shorter spell inside its name ("Lycara's Inspiration" linked as "Inspiration").
- The setup page's steps for ChatGPT match its current menus, and the server address has a copy button.
0.0.4 · 13 October 2026
Added
- Boss loot, and what's in it for you. Ask what a boss drops or whether there's anything good for your spec: each item's slot, stats and effect, the item level per difficulty, and which drops your spec's best-in-slot lists and trinket advice name.
- Did everyone do their job? Officers save the raid's assignment and cooldown note (the one exported from Viserio) with
/wipebot note, or by pasting it to the bot. Then ask who missed their soak or whether the cooldowns went out on time. Each soak is checked against its group (who wasn't in it, alive or dead, and who was in the wrong one), and each planned cooldown against when it was really pressed. In Claude or ChatGPT, paste the note into the chat. - Where do we stand among other guilds? Ask how the guild compares to the guilds just above and below it on the realm, in the region or worldwide: each one's progress and, for the boss you're on, how many pulls they needed and their best pull.
- Adds' casts, and who kicked them. The timeline and the adds tool show each add's casts with a cast bar, whether each was kicked (by whom) or went through, and when: "Broodling of Ithraz casts Visceral Burst x15: 8 kicked, 5 went through". Interrupts can be asked per player (who kicked how many) and per pull.
- Would a defensive have saved me? Looking at a death, Wipebot works out whether a personal defensive that was ready, or a healthstone, would have kept you alive through the hits that killed you. When several players died at once, it says which raid cooldowns were ready and whether the raid was stacked close enough for them.
- Everyone's healthstones and defensives. Ask who used their healthstone, potions and personal defensives on a boss and you get the whole raid in one answer: uses per player, and at how many deaths a defensive was ready but unused.
- Buffs at your casts. Ask whether a buff, or how many of its stacks, was up each time you cast a spell, like Starlord at your Starsurges.
- Wipebot in Claude and ChatGPT. Add Wipebot as a connector and sign in with Battle.net to ask the same questions as in Discord, in your own chats. It's open to members of the guild.
- Wipebot knows which characters are yours. Your Battle.net sign-in tells it which characters are yours, so "how did I do?" works without giving a name. Questions about reports start with the guild's own logs.
- Replay a pull. In Claude, asking where everyone was during a pull opens a replay you can play, pause and scrub at different speeds. Everyone moves in their class colour, and you can see the boss and which way it faced. Each death and the moment the wipe was decided are marked on the timeline. Hover over a player to see their spec and their distance to the boss.
- Wipebot remembers you. Once it knows which character you play, "how did I do?" works in every later chat without naming it. Ask it to keep a preference ("answer in English", "don't compare me with others by name") and it sticks to it from then on. Ask what it remembers about you, or tell it to forget, at any time.
- Pull maps. Ask "where was everyone when they died?" and you get the boss room at that moment. Every player is shown in their class colour, the dead where they fell, and which way the boss and each player faced. Everyone is named, and the players you asked about stand out.
- A stacking debuff reaching its highest stacks shows in the timeline ("Eternal Venom reaches 9 stacks on X"), and the boss casts that Lorrgs tracks for the fight are marked, to line pulls up by.
- Finding reports lists each boss with its pulls and kills, and can be narrowed to the reports a character is in.
Changed
- Downtime and dropped casts. "How did I do?" now shows the stretches where you cast nothing (when, and for how long) and the casts you began and dropped, each with its time, so you can check what was going on then. Next to the top parses, you see how much of their time was downtime and how often they dropped a cast, so movement the fight forces isn't held against you.
- Boss guides from three sources. Method, Wowhead's cheat sheet and Icy Veins, and every boss of the raid is found (The Twin Fangs, Vashnik, the Coiled Altar, Kith'ix and others were missing Icy Veins' page). When one site has no Mythic guide, the answer says so and uses what it has.
- A player's resource is the one their spec spends. Maelstrom, Essence, Holy Power and the rest are judged for capping; mana only for healers (an Elemental Shaman no longer gets "mana 100%").
- Whole-night questions are much faster on a raid night. On pulls nobody has asked about yet: how a player did over every pull about 70% faster, the raid's defensives and a table by pull about 95%, your deaths replayed about 60%, who stood in what over the night about 35%.
- When you cap your resource. Asking about your pull says not only how much of the time your focus, energy or rage sat at its cap, but when: the longest stretches, so you can see whether it's the opener, movement or an intermission.
- Mechanic hits count ticks apart from hits. A mechanic's damage ticks are no longer counted as separate hits. The count also flags a hit taken while the debuff from the last one was still up, with the time between the two.
- Items named in an answer link to their Wowhead page, the way abilities already do.
- Asking about a spec's rotation, cooldowns, defensives or talents gets the raiding sections of the guide (not the leveling or Mythic+ ones), longer, and with the date each page was last updated.
- Hotfix questions also report Wowhead's news about the boss or spec when Blizzard's running hotfix post hasn't caught up with the weekly reset's tuning.
- Interrupts and dispels add up: began, kicked (or dispelled), went through (or ran out), ended otherwise; a debuff hardly anyone dispels is marked as such, and dispels say on whom they ran out.
- Adds that leave without dying (despawned, transformed, gone with the kill) are no longer called "alive at the end"; a boss-type add that comes several times (the Drowned Echoes) is listed with the adds.
- One cast landing on several groups reads "Feasted on 6, then 6, then 7 players"; two abilities sharing a name read "Mutilate (2 abilities)", not "x2".
- A pull number without a boss, on a night with several bosses, picks the boss that has it or asks which, instead of failing on the wrong boss.
- A cooldown Lorrgs lists without a length (Elemental Ascendance) is still listed with its cast times, and one pressed more often than its base cooldown allows says so instead of "8/7".
- Casts under two ids or a replacing talent (Mutilate per hand, Incarnation for Celestial Alignment) count as one spell, for the player and the top parses, so Celestial Alignment no longer reads "0/2" when Incarnation was cast.
- "Far more" casts than top players is only flagged when the gap matters: one Bloodlust, potion, trinket or long cooldown on a short pull no longer is.
- Talents are compared with the top parses of the player's own hero tree when enough play it, and the comparison says how many do.
- A throughput cooldown used less than it could be says when it came back and in which phase, or that the player died first.
- A name with a typo ("torvk" for Torvek) still finds the player when it's close to just one name.
- Asking about a player on a boss they weren't on, or about an ability nobody used that night (a talent they didn't take), gets an answer that says where they were or names the closest abilities, instead of a plain "not found".
- "Did I often die where a personal would have saved me?" is answered in one step over all your deaths on a boss, and is much faster.
- In Claude and ChatGPT, questions about the latest raid work without naming a report: Wipebot takes the guild's latest raid night, as it does in Discord.
- Long conversations stay quick: after many questions in one place, Wipebot starts a fresh one with the recent messages instead of carrying every earlier answer along. Roughly 30-40% off the time and cost of answers late in a long conversation.
- Wipebot offers feedback DMs after each wipe only when you ask for it in a DM and clearly want to keep up between pulls, not after every question about your own play.
- When Wipebot restarts for an update, it finishes the answers it's working on first instead of dropping them.
- Answers in Discord have tidier lists.
- Wipebot has its icon in Claude and ChatGPT, and a new website: what you can ask (questions about the game too), the two ways to use it, setup and this changelog on pages of their own.
- Replying to Wipebot just to tag a raidmate, to show them its answer, no longer gets a reply. A question in such a reply still gets one.
Fixed
- "No ranked kills" when there were. After a patch Warcraft Logs starts its rankings afresh, and for a while the new season's lists are empty: every comparison with top parses and kills, a player's season history and the guild's ranks then came back as "no ranked kills yet". The rankings of the season before are used until the new ones fill. An answer Warcraft Logs gave only in part is no longer kept for a day either.
- A death recap no longer fails for a player who had an immunity (Divine Shield, Ice Block, Cloak of Shadows) ready.
- Comparing a build against a guide no longer claims a player lacks the other hero tree's talents when the guide's import string carries both trees.
- An add's death counted twice no longer gives "34 came, 59 died".
- An ability named inside a longer one ("Soul Exhaustion", "Avenging Wrath") no longer gets the shorter ability's Wowhead link.
- Asking Wipebot about another night ("what went wrong on Monday's raid?") no longer stumbles on finding the guild's reports before answering.
- Asking for the guild's reports no longer passes off a raider's pug logged to the guild's page as a raid night: those are marked.
- On long pulls with a lot going on, some answers looked at only the first part of the pull.
- When Battle.net doesn't answer, you stay signed in, and signing in says so instead of failing with an error.
- A player brought back with a battle res shows alive again on pull maps and in the replay, instead of staying dead where they first fell.
- On a fight with several bosses, each boss gets its own marker on pull maps and in the replay.
- In the replay, the marks showing which way a player or the boss faced no longer blink off as they turn.
0.0.3 · 12 October 2026
Added
- Your pugs and alt runs count too. Ask about a character's logs from any group, including pugs, other guilds and alts, and those runs are looked at the same way as the guild's.
- Parses by the spec you played. If you change spec or role during the night, each pull is judged as the spec you played on it, and parses use that spec's numbers.
- Guild rankings and attendance. You can ask "who's our best dps?" and get the raiders ranked as on the guild's rankings page. Ask who raided which nights and get attendance over the last few weeks.
Changed
- No more posts after every wipe. Wipebot no longer posts in the channel after each wipe. If you ask about your own pull during a live raid, it can send you your own feedback in a DM after each wipe.
- Answers keep up with the conversation. Each answer sees what was said in the channel since the last question, so if one raider corrects something, the next answer knows it. A reply to the bot counts as a question even without a ping.
- The report's date is stated, so an older log isn't called "tonight".
- Pugs that raiders log to the guild's page are no longer treated as a guild raid night. They aren't followed live, aren't picked as the latest raid, and are left out of attendance.
- Report overviews show each kill's speed and execution rankings and the guild's progress rank. Build checks now give your talents as an import string.
- Wipebot answers in the language you ask in, keeps to the raid, and doesn't call people out by name in server channels.
- Answers no longer end with a list of sources.
Fixed
- Percentiles against a spec's ranked kills were wrong for popular specs. How far a wipe got now uses the same measure as Warcraft Logs, which matters on bosses with phases.
- A buff a boss gains when its partner dies is no longer read as an enrage. A raid cooldown from a damage dealer or tank counts when it actually reached other players.
0.0.2 · 11 October 2026
Added
- A player's season. Ask about a player's history and you get every ranked kill they've had this season, from any report, with the date, parse, item level and a link to the log.
- Smarter coaching. Advice now looks first at waste: resources at their cap, charges left full, buffs and DoTs falling off, cooldowns held for nothing. It also judges healers' mana pacing and cooldown use, and tanks' active mitigation. A question about your night covers every boss you pulled.
- The latest raid night. With no live log, questions go to the guild's latest real raid night instead of a small side log. If you're not in that report, Wipebot looks through the guild's other recent reports before asking which character is yours.
Changed
- After a wipe, Wipebot posted a single short answer about the pull (what lost it, what set it up and the one change to make) in place of a summary and a separate reply.
- Answers are faster, and follow-up questions about the same report come back almost at once.
Fixed
- A player who left partway through the night was judged on bosses they never pulled.
- Guilds on some realms couldn't be found during setup.
- When asked how far back the logs go, only the latest few reports were seen.
0.0.1 · 10 October 2026
Added
- First version. Wipebot follows the guild's live Warcraft Logs report in Discord and answers raiders who @mention it or send it a DM. Server admins set it up with a single command.
- Why did we wipe? Wipebot finds what ended a pull, like an enrage, too few players left for a mechanic, adds left alive or a cascade of deaths. Then it traces the pull back to the first mistake. Deaths after the wipe was decided count as fallout.
- Coaching for players. Ask "how did I do?" or "why is my damage low?" and it checks your deaths, the mechanics you took, your throughput against the top players of your spec, your casts and cooldown timing, and your talents, gear and consumables.
- The whole night. Ask what keeps wiping the raid, who keeps taking avoidable mechanics, and whether everyone came prepared. Each pull can be compared with a kill of the same boss.
- Tank swaps. Ask about tanks and you get every taunt in order and each tank's debuff stacks.
- Answers about boss strategy and class play draw on current guides, spell tooltips and recent hotfixes.
- Wipebot introduces itself by its name in your server, keeps small talk short, and asks for your character only when a question needs it.