Skip to content

Wipebot 1.0.0

Choose a tag to compare

@github-actions github-actions released this 11 Nov 14:13
· 108 commits to main since this release

Added

  • Agent A trend by pull: is it getting better over the night? Damage, healing, damage taken, casts and one ability's hits are now drawn pull by pull: a bar per pull, a kill capped in gold, and the median pull of each third of the night as a dashed line. A reset is hollow and left out, and the card's sentence states the thirds, as the answer now does from the same three medians ("The raid's healing per second: 1.67M in the first third of the 32 pulls, 1.65M in the middle and 1.87M in the last (each third's median pull)."). One player's trend is in their class colour, and in Discord the asker's row is drawn under the raid's. In Claude and ChatGPT a bar opens its pull, "Open trend" lists every pull's numbers, and a ranking over several pulls has "By pull".

    Healing by pull over all 33 Sszorak pulls: a bar per pull, pull 9 hollow as a reset, three dashed lines at 1.67M, 1.65M and 1.87M for the thirds of the night, and under them Enfo's own healing in the same pulls

  • Agent Ask about one raider's part of the raid note. "Did I do my part on that pull?" now gets that raider's own soaks, planned cooldowns, kicks and personals, on a pull or over the night, with the raid's counts beside them for scale. It used to come back with every player's rows to find one in. For the next raid it gives their jobs alone. A raid plan shown for one raider gives their spot or their row of the side panel, the plan's notes, who stands at the same place and who shares their circle. Cooldowns the note planned for after the wipe was already decided are now given as a count and the next three, where every one of them used to be listed. The picture that comes with a night's check, or with the note for the next raid, holds that raider's part as well: their kick assignment, their planned cooldowns and their row of each callout.

    The Personals picture asked for Zebinomage alone on Sszorak over 42 pulls: one row, a square per pull, green where they pressed a defensive, a red cross where they pressed none, a green outline where one was already running, and 15 of 23 at its end

  • Agent Ask when an ability was cast and whom it hit, or what a player pressed. "When was I hit by it, and for how much?" and "what did our druid press between 0:30 and 0:50?" now get an answer with each event to the millisecond. A pull's timeline narrows to one ability (its casts, its hits on players with their amounts, its debuff going on and off, the deaths it dealt) or to one player's casts and deaths, in your own log or a top player's. It names everyone a debuff reached its highest stack on in the same moment, where it named only the first in the log, and asked who kept a debuff to the end, the answer gives the span and each time's players ("2:36-3:01: ran out on 18: 2:36 ... · 3:01 ..."), where it had one row at the middle player's time. Other questions no ready-made analysis covers now come back with the time into the pull and every name, each fight as boss and pull number and each phase as P2 or I1. An answer too long to read is cut to its first rows and says how many were left out, where it used to be refused.

  • MCP Rankings are drawn in Claude and ChatGPT too. "Who did the most damage?" and "who keeps getting hit by Tempest?" came with a meter in Discord and text alone in Claude and ChatGPT; both now get the card there. It opens with one sentence on who is first against the median ("Deathadim is first with 2.14 hits per minute of the pulls they were in, 2.5 times the median of the 22 players ranked."), then the top eight players' bars in their class colours, "Open ranking" for everyone's, and a mechanic's hits per player per pull. An answer that ranks several things opens one ranking and keeps the others to one line each. In Discord the meter's picture leads with the same sentence.

    Tempest over the night's 32 Sszorak pulls (its reset left out) as a card in the light theme: "Deathadim is first with 2.14 hits per minute of the pulls they were in, 2.5 times the median of the 22 players ranked.", the killing blows, the deaths within 6 s of a hit and the median, the top eight players' bars in their class colours, and the buttons Open ranking and By pull

  • MCP A card says what you have open, and links to its log. After a click on a pull or a replay stopped at 1:28, "why did this one go wrong?" now comes with a line saying what is on screen: "The user is now looking at Sszorak pull 13 (report KBYT4xXn7VNjDgh8)." It used to reach Claude or ChatGPT with nothing to say which pull or moment that was. Claude and ChatGPT read it with your next message where the app takes such a line. Every card also links to its pull, or to the night's report, on Warcraft Logs.

    Sszorak pull 13's card in the light theme: Open pull and Replay on the left under the chart, and "Warcraft Logs" with an arrow at the right end of the same row

Changed

  • Discord Admins: run /login and /wipebot setup once to keep raid notes and plans. On a bot many servers share, such as the public Wipebot, they are now read and saved only once an admin has done it, also on a server set up before. The admin needs a character in the guild among those they claimed on Warcraft Logs. Until then, /wipebot setup says that notes and plans aren't read or saved, and answers about the logs and posts after wipes work meanwhile. A Wipebot of your own works as before.

  • Agent Every card leads with its verdict. A card used to open on a row of numbers; it now opens with one sentence on how the pull ended, such as "The boss gained Unbound Ferocity at 2:32 and kept it to the end, with 16 of 20 alive". It can also say what would have kept someone alive, what ended the most pulls of a night or, asked night by night, which night got furthest, and Wipebot's code writes it from the same facts as the answer, so the two can't disagree. Under it come at most four numbers, one chart and two buttons, in Claude and ChatGPT and, without the buttons, in Discord's pictures. A player's card no longer gives a verdict the answer doesn't give: a rogue dead for 100 of a pull's 152 s was shown a green "Above the 90th percentile of ranked kills". It no longer lists what went well and what to fix, and leads with the death as the answer counts it ("Died at 0:53, before the wipe was decided at 2:32: dead for 100 of those 152 s (65%)."), or with their output and rank.

    Sszorak pull 13's card: under the title one sentence, "The boss gained Unbound Ferocity at 2:32 and kept it to the end, with 16 of 20 alive.", then the boss's health left, the deaths before 2:32 and the first death, the pull's chart, and the buttons Open pull and Replay

    Draiman's pull on Sszorak pull 13: the card leads with "Died at 0:53, before the wipe was decided at 2:32: dead for 100 of those 152 s (65%).", then three numbers (damage per second alive, the time lost before 2:32, and the death at 0:53) with no count over the cooldowns, and their casting over the pull with no percentile scale

  • Agent A death's recap says first what did the damage, and whether they could have lived. The killing blow is often a small tick after the hit that did it: the recap adds up the last 10 s by ability and names the biggest hit with the health it left. One death "to" a 50k tick was caused by a 378k hit two seconds before. Right after that, it says whether a ready defensive or a healthstone would have kept them alive, where that used to close the answer, and a defensive on cooldown says until when. On the death's card a save that was missed is now marked with a minus as something to do differently, as on the player's night, and no longer with the plus of what went well. A death that wasn't the player's to stop is no longer replayed as theirs: asked how a druid died, Wipebot named Barkskin as what would have kept them alive in a hit that killed four. The answer now says what the death was to the wipe (before it was decided, after it as fallout, or one of a hit killing many), the card leads with that for fallout or a hit killing many, and both replay only a death that was the player's own. A healthstone that would have saved them is said with "if they had one". A death with no killing blow shows on its card where the player was last logged: 113 yd from the raid after moving 63 yd in 3 s fits being thrown or knocked off.

    Scopidruid's death on Sszorak pull 13: the card leads with a minus and "A healthstone (if they had one; none used this pull), used in time, would have kept them alive.", then its numbers and the hits and their health in the 10 s before the death

    Draiman's death on Sszorak pull 13 in the light theme: "Died at 0:53, no killing blow recorded." with a mark, under it "Last logged position at 0:51: 113 yd from the middle of the rest of the raid (90% of them within 29 yd of it), after moving 63 yd in the 3 s before" and what that fits, then the card's numbers and the hits before the death

  • Discord Answers during a raid are short enough to read between pulls. While your guild's report is being logged, an answer in Discord is the verdict and at most three one-sentence bullets, the fix first, with the rest as follow-up buttons. At other times a who, when or how many gets two bullets, a pull three, and a night, a player or a plan five. A bullet is its point in bold and one sentence with the one or two numbers behind it, 30 words at most. The warning sign marks only the one change to make. A follow-up you were already offered isn't offered again, and a greeting gets no buttons. Once Wipebot has read what it needed, the line under your question says "Writing the answer" where it said "Thinking".

  • Agent A first question about a pull comes back faster. A first look at a player's pull now waits about 3.5 s less, and a comparison with top players about 7 s less, as Wipebot's requests to Warcraft Logs no longer queue at four a second. The guide sites are asked at the old pace. Wipebot also has less to read before it answers: a pull's summary is a sixth to a half shorter on the pulls measured and opens with how the pull ended. A night read pull by pull is one row a pull: about 40% shorter on a night of 33 pulls. A player's night says once what its rows mean: about a quarter shorter. That something isn't in the log is said once, and only when the answer turns on it.

  • Agent Who a mechanic hit most is ranked by the pulls each player was in. Players are now ranked by hits per minute of the pulls they were in, so one who sat out half the night no longer ranks below someone hit as often per pull. The meter ranks them as the answer does, and each row says how many pulls that was. A death within 6 s of a hit is now called "a death within 6 s of a hit", whatever killed them, and no longer a death the mechanic "set up". A player's casts per minute over the pulls they were in now stand beside the night's rate, which for a healer in 12 of 33 pulls was a quarter of their real one.

    Tempest over the night's 32 Sszorak pulls as the picture Discord gets: the raiders by hits per minute of the pulls they were in, Deathadim first at 2.14 and Krøpling second at 1.64 with "55 hits (+61 ticks) in 23 pulls, 22.60M" on their bar, 48 killing blows and 95 deaths within 6 s of a hit as numbers above the bars, and the hits per player per pull under them in the same order

  • Discord Wipebot's own messages are in Norwegian when your question is. The answers already followed the question's language; now so do the line under your question, the steps, the buttons and menus, and what Wipebot says when it can't answer. A question too short to tell gets the server's language (/wipebot setup language:). Wipebot's Norwegian keeps the game's words as raiders write them ("pullet", "deaths", "adds"), and Norwegian answers keep more of them ("damage", "HP") and give a time in the fight as "på 3:13".

  • Agent One set of colours in every chart, made to be told apart. How a night's pulls ended, the abilities in a death and the kinds of callout in a note share four colours that stay apart for red-green colour-blind readers, in the light theme and the dark. Past four is "other", drawn hollow. Gold, orange, red and green were tuned again to read as text, and a kick that went through or a cooldown not cast is a red square with a cross. Class colours now read on a light card, where a priest's white and a rogue's yellow all but vanished: a name keeps its class's colour at a lightness that reads, and a bar keeps the true colour with an edge.

    Sszorak over 33 pulls in the light theme: each bar in one of four colours for what ended the pull, the endings past four drawn hollow, and the same colours in the key under the bars

    A rogue's pull opened in the light theme: the name Draiman and the dot on the scale in a dark olive instead of the class's pale yellow

  • MCP Discord A night's card is half as tall, and a whole night leads with its bosses. The card for a night's pulls is now its sentence, its numbers and the chart of the pulls, with the lists under "Open night". Asked about the whole night, it starts with every boss, its pulls and its kill or best wipe, no longer the last boss alone. A player's night is shorter the same way, and the night's card counts "10 of the 33 pulls", where it had "10 of 32" over a list of 33. While a card loads, grey blocks show where its parts will be, instead of a tall box with a spinner that jumped, and one that can't be read says why, with "Try again" where that helps. In Discord, when a picture's data couldn't be read, the answer now goes without it instead of with an empty card.

    The whole night's card: a row with Vashnik the Malignant, 2 pulls, killed, and Sszorak, 33 pulls, best 62.6%, then Sszorak's sentence, two numbers and its 33 pulls as bars coloured by what ended them

    A pull's card while it loads: grey blocks where its title, its sentence, its four numbers, its chart and its two buttons will be, and "Loading…" in the middle

  • Agent Raid plans are saved by their link, and the raidstrats.gg login is gone. An officer can now paste a raidstrats.gg plan's link instead of its export, and Wipebot puts the night's raiders on their spots with their full names, on a Wipebot set up with a raidstrats.gg key. In Viserio's assignment note, right-click the raidstrats.gg badge on a section's raid plan and Copy Link; Viserio's default plans are included. The login couldn't read those default plans, and a guild's own plan is still saved by its export. For those who run the bot: wipebot raidstrats-login, RAIDSTRATS_CLIENT_ID and RAIDSTRATS_CLIENT_SECRET are gone and the stored logins deleted; saved plans stay.

Fixed

  • Agent How a pull ended reads one way, and right. A pull that ended with the raid alive is no longer "called off": Wipebot names the boss's cast that landed on most of the living as it ended, where none had at any earlier moment or pull, or else says how many were alive and that no death decided it. A hit that kills many counts whole: "Viscous Cyst killed 5" on a pull where it killed 10 is gone, the wipe is decided at the hit's last death, and two abilities killing at once are both named. Every answer and the wipe post read one result, such as "deaths leading into Mutilate killing many". A wipe's summary no longer says the pull got past the enrage that ended most earlier pulls where the boss gained it on this pull too, after the wipe was decided: it says it came on this pull too, and when. A buff the boss carried through earlier wipes is no longer taken for the enrage that decided one, and a night counts apart the pulls on which the boss kept a buff: how many it ended, how many something else ended first, and how many it came too late on.

  • Agent A reset no longer counts as a death, and a battle res counts once it is taken. A player's night said "died on 8 of 33 pulls" above a trend that added up to 7: a reset's row stays, marked, and the counts leave it out and say so: "32 pulls (1 reset left out)". That goes for the deaths that count, the time dead, cooldown sums, the night's defensives (twelve deaths on a reset had counted as defensives unused) and who a mechanic hit. A res counts once the player dies again or casts, so alive counts are no longer one too many. The night's killer splits its deaths ("57 deaths, 40 of them in hits killing many") and names players only for the rest.

  • Agent Raid notes are checked more carefully for cooldowns, personals and kicks. A planned cooldown pressed under 3 s from its time in the note is now on time, where only under a second was: over four nights, 30% of presses were within a second and 64% within three. A raider who pressed a long defensive just before a "Big Personals" callout no longer reads as having pressed none: one still running counts, by the duration Lorrgs gives it, and the picture draws it as a green outline. A shaman's Reincarnation is no longer an answer, and "Ready" lists only the defensives the raider cast that night. A planned cooldown not cast says when it was still on cooldown, or was planned in the last 10 s before the wipe was decided. A raider who joined for the last six pulls of a night read "64 planned uses; late 2, not cast 18, dead 2": the 42 on pulls they weren't in are now counted apart. A planned external ("Guardian Spirit" and the tank's name) prints who it was meant for and whom the log says it went on. A kick on another cast of the wave is named, not "no kick", and over a night a kick that went through while its kicker was dead is counted apart from one they missed ("1 missed, 3 while dead"). The interrupt order between intstart and intend is printed, numbered, and said not to be checked.

    Planned cooldowns on Sszorak over 42 pulls: a row per planned use and a square per pull, green on time, gold early or late, a red cross not cast, grey dead by then, and on the right how many pulls it was on time; the key reads "on time (under 3 s from the note's time)", "early or late", "not cast, alive", "dead by then"

    Big Personals on Sszorak over 42 pulls, a row per raider and a square per pull: green where they pressed a defensive, a red cross where they pressed none, a green outline where a defensive was already running, blue where they pressed the note's cooldown for them

  • Agent Soaks in a raid note are counted for the right group. Where groups soak in turn, as on The Twin Fangs, each landing is now its own soak checked against its own group, where a night's check said almost nobody missed a soak. A hit counts for a group only when the note calls that group within 20 seconds and enough of its players were hit; stray hits, and the whole raid in one soak as a pull falls apart, are counted for no one. A player in several groups counts in each, and the night's list leads with who missed. A raider hit by another group's soaks is no longer called likely not soaking: hit by 1 of their own group's 57 soaks and 55 of Left's, Wutroll reads as soaking with another group than the note puts them in. A list of players for another job, such as orb carriers with their helpers, is no longer read as soak groups: a list is soak groups only where its heading names an ability. Raiders immune to a soak no longer make it "0 each": they are named and still count as having soaked. A kick callout at a time when no add was casting is now listed as a kick with nothing to kick.

  • Agent A raid note is read as it was written. On The Coiled Altar every line of the third stage was checked 38 seconds early: each phase of the note is now laid on the log's phase of that name, and the check says where each began. A line timed after the note's next phase began is no longer checked, so a push 20 seconds early no longer reads as five cooldowns pressed early and three not cast. A note for another difficulty says so. Lines that couldn't be read are counted, with the first shown, and a job written twice is kept. A line to "everyone" is no longer a cooldown a player called "everyone" never cast (seven times a pull on some notes), a role or a group no longer reads "not in this pull", and a name with its realm is that raider.

  • Agent A player who died early is no longer judged as if they had lived. A rogue alive for 53 s no longer "never cast" Sprint: a spell the top players press less than once in that time reads "not due", and only one they would have pressed, such as a damage cooldown, is still "never cast". A player alive under a minute, or under a third of the pull, is no longer placed among full kills, and a healer who died right after a cast no longer has their time dead counted as time with no cast begun. The comparison with top players has a key for its marks, shows the flagged spells first, and marks nothing the comparison doesn't.

    Draiman's casts against top Assassination Rogues, in the opened card: a key over the rows for their dot, the top players' median, their range, a spell never cast or far off, and one that is no fault, with Mutilate at 27.1 against 23.9 and Ambush, never cast, in red

  • Agent A cooldown pressed at the same moment each pull counts only on the pulls that got there. A healer's raid cooldown used at the same boss cast each pull no longer reads as half its uses missed: "Spirit Link Totem used on 16 of the 18 pulls that got to 1:11". Which cooldowns those are is told from the player's own first uses, and one pressed at the pull keeps its uses against possible uses. The night's card and Discord's picture count the same way, where the card said 16/32 and "37 of 64 uses", and a death on a reset is grey there. That moment is no longer called the right one: told a Holy Priest's Apotheosis was "held for" 1:03, answers praised the timing, though top Holy Priests press it at 0:18-0:26; it now reads "first pressed about then pull after pull", and when top players press it is in the comparison with them. Where healing names who left a cooldown ready and unused, it now says once that who was meant to press it isn't in the log, and whether a raid note is saved for that boss that night.

    Enfo's night on Sszorak as Discord's picture: under the pulls, "Major cooldowns over the night: Spirit Link Totem used on 16 of the 18 pulls that got to 1:11; Ascendance used on 18 of the 18 pulls that got to 1:07 (22 uses over the night)", and pull 9, a reset, with a grey dot under it

  • Agent A steady, heavy fight shows where its healing was tested most. On a Twin Fangs kill whose damage stayed high all fight, the healing answer was only "No spikes", though no healing cooldown went into its worst stretch, 6:25-6:44. A pull with no spike now shows its three busiest stretches, at 1.25 times its median or more, each with its damage, its healing, the cooldowns used and those left ready, and its deaths; a spike or stretch is measured on its own seconds. A healing cooldown pressed before one now counts for it while it lasts through half of it: Avenging Wrath at 3:32 read as missing from 3:38-3:44, and Sszorak's first wave as getting almost no cooldowns, though Apotheosis was up in most of them.

  • Agent A ranking's picture states the total and the shares its answer states. For "who did the least damage?", the meter showed 13.39M, the total of the bars it drew, under an answer that said 14.83M: the total and every share are now the answer's own, and a ranking the answer gives no total for shows none. The picture of the damage on adds states what those adds took, as the answer has it ("175.13M"). A raider who sat out pulls is marked as their row is ("in 11 of 33 pulls").

    Damage done in ten seconds of a Vashnik pull, least first, as a card in the light theme: "Dragepie is last with 362.25k, 42% of the median of the 13 players ranked.", the raid total 14.83M at 1.48M/s over 0:10 as the answer states it, and the damage dealers' bars with shares of that total, 2% for Dragepie

    The damage on Shrouded Venom in a Vashnik pull as the picture Discord gets: "Pomaa is first with 20.60M, 2.0 times the median of the 16 players ranked.", the total of 175.13M that the adds took and the median of 10M as numbers above the bars of the ten raiders who did the most, Pomaa at 21M first, and the other six in a line under them

  • Agent The same thing has the same number wherever you ask. A Rogue's Mutilate counted once per hand, about twice the casts per minute the comparison with top players showed: an ability's damage and a player's casts are now counted one way. An ability the log records under several spell ids is one row. A player's night and the replay of their deaths count the same deaths in a hit killing many, where one said 8 and the other 9. A death only an immunity that held for all 5 s would have saved, or one where a ready spell's tooltip gives no amount, is "can't tell" in every count, where the night's defensives counted it as one a defensive would have saved, and a player's night card draws that death's chip dashed. A night's card writes how far a wipe got as the answer does, to one decimal: "best 62.6%" where it rounded to "63%". Phases are P1, P2, P3 and I1, I2 wherever one is named, so "P3" no longer means two things. A wipe next to a kill reads the same boss at every moment, with health compared inside each phase (no more "-52 points behind"), and a pull that caught up says since when it was behind.

    Enfo's night on Sszorak as a card: what killed them with a chip per pull, pulls 19 and 28 in the colour of a death a ready defensive or a healthstone would have stopped, pulls 8, 12, 20 and 32 dashed, and under them the key: chip 19 for "a pull where a ready defensive or a healthstone would have kept them alive" and a dashed 8 for "a pull where the log can't tell"

  • Agent Lists of logs and kills keep difficulties apart. A log with a boss killed on Heroic and wiped on all night on Mythic no longer shows that boss as "killed": each difficulty lists its own bosses with their pulls and kills. A player's ranked kills are listed on the hardest difficulty and counted on the easier ones, where Normal and Heroic farm made 60 rows. Each boss gives its first kill's parse and its newest beside the best and the median ("best 83%, median 77%, first 83%, newest 77%"), where answers read the rows, newest first, upwards and said every boss had gone up. Two All Stars scores for one spec name their partition, and a standing reads "18th percentile of the spec", not "top 82%".

  • Agent Discord A Warcraft Logs link to one fight is read as that pull. Paste a link with #fight=21 or ?fight=4&type=healing and, when no other pull is named, the answer is about that pull, saying which it is ("Fight 21 in the link is Sszorak pull 13"), where it was about the latest pull. A link to several fights says so. A link to trash is refused where its pull was the one to read; a question about the whole night, or one that names its own pull, is answered, with a first line saying the link named no pull. A name that fits no player gives the closest names and the report's players, and a boss not pulled in this report says where the guild's other nights are found. A boss name that fits several bosses is read as the boss it names whole, else the one pulled last, and the first line says which.

  • Agent A boss's guide for one mechanic answers in seconds, also when no guide names it. Asking about an ability by its name in the log, when the guides call it something else, could run past a minute: the search now goes by the ability names on each boss's guide page, within a time limit. A rule Method gives as a short list, one line for each group of players, is kept whole, where the third of three such lines was lost. An ability no guide names is answered from its tooltip, and a page a site doesn't have is remembered. Wowhead's unscaled journal amounts ("5 Shadow damage every 2 sec" where the tooltip says 192,517) are left out, with a line saying the tooltips have them.

  • Agent A question that takes too long gets an answer saying what was slow. A slow Warcraft Logs or guide site could keep an answer waiting with nothing said, and in Discord it hung: a step now has a time limit, then says which source it was still waiting for. What was read until then is kept, so asking again is quicker. Saved raid notes that can't be read are said to be unreadable right now, no longer reported as none saved.

  • Agent Discord A chart's labels and marks no longer print over each other. On a phone the moment the wipe was decided and a damage peak's height each take the free place nearest them, and the boss's health runs from 100% to 0 on every pull, so two pulls compare. The health scale is on the right in the line's gold, and the cooldowns are one row over the chart. "5.0M/s" is no longer cut to ".0M/s". In Discord's meter the mark for another night is a notch clear of the amounts, and a second or third healer of one class in the mana lines is dashed or dotted.

    Vashnik pull 16 at a phone's width: a row of dots and pluses for the cooldowns over the chart, "decided 6:28" above the health line beside its dashed line, 2.5M/s whole on the left, and 100% and 9.43% in gold on the right

    Axegrinder's damage per player on two nights: each bar ends before the column of amounts, and the other night's amount is a small notch above and below each row

  • Agent Small slips in the wording are gone. A night of nearly three hours reads "2:54:43", not "174:43 long", and a parse reads "81st percentile", not "81th". No more "(Mythic) (Mythic)", and the night's first wipe no longer carries a best mark. An enemy nobody hit "took no damage". Counts read "×2" and seconds "3 s". A dungeon run is read as one boss pull. A death with no killing blow reads "no killing blow recorded". Healers in a damage spike and before a death are named "Holy Paladin", not "Providence (Holy)". A date before 10:00 UTC, still the evening before in the Americas, now carries its time and "UTC".

  • Agent Discord Your Warcraft Logs sign-in and your private reports stay yours. Everything read for an answer is read as its asker, and its buttons as whoever clicks them, no longer with the sign-in of whoever asked first since the bot started. Signed in with /login private:True, you can ask about a private report by its link in a server that isn't set up, and the answers work in full, buttons included. A link Warcraft Logs won't show says so, with how to let Wipebot read a private one. Nothing a private report showed is recorded, and a report made private or deleted after it was read is dropped within a day, where it kept answering for up to 30 days.

  • Discord An answer that reads as one message is sent as one. Discord counts the address behind every linked ability, so answers just over its limit went out as two messages: such an answer now drops its last links until it fits. A long answer cut inside a code block opens the block again in the next message. After a restart, the next question starts a new conversation on every bot, read with the messages before it as after a quiet quarter of an hour.

  • Discord A bot many servers share keeps up with each of them. Two servers that follow the same report each get their posts after wipes, where only the first did, and many questions at once no longer slow the bot down for every server. At most eight questions are answered at once, and one raider gets three at once and thirty an hour. On a bot where each server brings its own AI key, /help opens by saying an admin adds one with /wipebot setup, and What's new posts the changelog's own lines.

  • MCP Charts work with the keyboard and a finger, and the replay fits in fullscreen. Tab stops on each chart, the arrow keys step through its marks and Enter opens a pull; on a phone a tap on a night's thin bar says which pull it is, and a second tap opens it. A screen reader hears each mark, and buttons are a finger's size. The replay opens in fullscreen from its own button with play and the timeline in sight.

    Sszorak's night at a phone's width with pull 13's bar tapped: its tooltip with how far the pull got, what ended it and the first death, ending "Tap again for this pull"

    The replay of Sszorak pull 13 in fullscreen: the room with everyone's position, and under it, in the same window, play, the timeline with its deaths and the speed

  • MCP Claude offers to send a report when you say an answer was wrong. In Claude, which may load a connector's tools only when it searches for them, the way to send a report on an answer to Wipebot's maintainers now loads first, so the offer is made. Past the hourly limit per user, the refusal says what was asked for and what the limit is, and how long to wait until enough of it is over an hour old. A spell's tooltip or a spec's guide still answers once Wipebot has used up its Warcraft Logs reads for the hour.