What's new

12 October 2026

The site

• Raid night pages the same night. When a raid ends shortly before the guild's nightly run, its log still counts as being written, so the night's pages (the raid night, the gear check, consumables, performance and the rest) used to wait a whole day for the next run. Now the night is read again about an hour after the nightly, so they are there the same night.
• Effort counts every kill, even mid-raid. If the nightly read a raid's log while the raid was still going, the kills after that never counted toward effort in the standings. Now a log is read again once it has grown.
• Players an accent apart are told apart. Reeroy and Rèeroy are two characters, and the site now treats them so: a log or a loot row naming one never counts for the other, the site never respells one into the other, and an officer can file each as their own raider's alt. A name typed without its accents, such as a Discord nickname, still finds its character.
• Who runs the uploader, by raider. Settings → Uploader names each uploader by its raider's main ("Cyllosis · as Employee"), and an uploader too old to update itself now shows there too, with what to do.
• Old uploaders are turned away. The site no longer takes anything from an uploader older than 1.15.1, the first that keeps each WoW game's loot history apart. Its window says to run /uploader in Discord for the new one, and Settings → Uploader and the health card mark it "refused". Loot files an officer drops on the Loot History page are taken as before.
• Changes show in seconds. A change made on the site (a setting, a roster or loot edit, an upload) shows on the pages within seconds, even while other guilds' nightly updates run. Settings says when they show it, and its Rebuild button is gone: nothing needs it any more.

11 October 2026

The site

• Forever names, two words. A Forever character's name is a first name and a last name, and the site now takes it that way wherever it checks a name: a re-roll asks for two words (and refuses one or three), long names are kept whole, a guild note that names a two-word main is understood, and on a Forever team a Discord nickname written without the space ("FuryTann") still counts as Fury Tann's signup.
• Forever groups for MRT. MRT's raid-group import splits names at spaces in the layout the comp tool uses, so a Forever team's "Copy for MRT" and /mrt now give one name per line, five lines a group: in MRT pick Raid Groups → Import and the layout with one name per line. /mrt's heading and the Commands page say so too. TBC teams keep theirs.
• Forever names in loot imports. A pasted or uploaded loot list recognises two-word names, with your roster's help, and never takes them for item names; realm names with spaces or hyphens ("Classic Beta PvE", "Azjol-Nerub") no longer keep a loot history out.
• The Forever demo speaks Forever. Every raider in the Forever demo guild now has a first name and a last name, so the demo shows what a Forever guild will see.
• Your guild's pages come first. A guild's front page now opens with its standings, then the wishlists, the loot history and the rest of the guild's own pages, from the most used down. The general pages (new here, the addon, the guides, the talent calculator, the commands) have a group of their own below.
• New guilds show raiders the standings. A guild set up from now on starts with its standings open to its raiders, on the site and in the addon's tooltips. A guild already set up keeps its own setting: Settings → People and access → Access → Standings page.

The bot

• Commands keep working while the bot updates. Discord now hands the bot's commands, buttons and forms to the site instead of the bot's own connection. While an update is handing over, a command gets a "thinking…" at once and its answer a moment later, so none fails.

10 October 2026

The site

• Updates without a gap. Most updates no longer take the site and the bot away for a spell: the new version starts beside the running one and takes over once it is ready, and a page opened in that moment waits a second instead of failing. A nightly update caught in the middle runs again on the new version.

9 October 2026

The site

• Each kill counts once. When two raiders log the same raid, every kill is in both logs, and a raider's parse for it went into their performance twice. Now the standings take each kill once: from the log that saw the most raiders in it, and from the other log only for a raider the first missed. The same goes for effort.
• Each log read once. With a Warcraft Logs client of your guild's own, the gear check, consumables, jobs, performance and avoidable damage pages each read the night's logs for themselves; now one read serves them all, about a quarter of the points. A second raider's log of the same pulls is read only for what it alone saw.
• The shared Warcraft Logs client, paced and said. A guild without a Warcraft Logs client of its own shares ours with every other guild, so it goes at a steady pace: the nightly runs at your guild's turn in the four hours after the time you set, during a raid a live log is looked for every 15 minutes, new reports are read six at a time, an hour apart, and only the standings' weeks. Settings → Integrations, the Health card and the setup say so, with your guild's time. A client of your guild's own (free, about two minutes) runs the nightly at the time you set, looks every 10 minutes, reads your whole log history and brings the deep log analysis.
• Your guild's data, in one file. Settings → Advanced → Your guild's data: a guildmaster downloads everything the site keeps for the guild (settings, roster, wishlists, requests, recipes, the loot history, raid nights, standings, the Warcraft Logs reads) as one JSON file. Sign-ins, tokens and links that work as keys are left out. Removing the guild is linked beside it.

8 October 2026

The site

• More on each raid night's Performance page. With a Warcraft Logs client of your guild's own: each raider's casts a minute over the kills they cast in; a healer's crit rate, each spell's on hover; the debuffs each class keeps up on the bosses — the raid's own (Misery, Shadow Weaving, Winter's Chill, Improved Shadow Bolt, Expose Weakness, Blood Frenzy, Mangle) with who put them there, and each raider's own (Shadow Word: Pain, Vampiric Touch, a warlock's or druid's damage over time, a bear's Lacerate…); and every spell cast at a lower rank than the raider cast it at elsewhere that night — a heal cast low to spend less mana, or Earth Shock's or Frostbolt's rank 1, is said so, not flagged.
• Who stood in it. With a Warcraft Logs client of your guild's own, the night page links Avoidable damage: on every boss pull, wipes too, who took damage from what they can stay out of — fire on the ground, a boss's frontal attacks, each boss's own list (the RPB sheet's, and what it leaves out, such as Illidan's Blaze) — how often and how much, and the deaths it caused, the night's worst first, each raider's hits and damage boss by boss. A frontal attack's tanks are left out, and so are the soakers of a cleave your raid splits on purpose (Kaz'rogal's); what no one can stay out of altogether (Anetheron's Carrion Swarm) is shown boss by boss but counted in no total. Once a wipe is called and your raid runs into the fire to die, nothing counts: the call is read off the log, the moment your raiders stop casting, and each boss says when its wipes were called and what came after. For officers unless Settings → Access opens it to more.
• Every death on a long night. On a night of more than 200 deaths the night page showed none on its last pulls — Warcraft Logs hands them over 200 at a time. The rest are read now, for the nights already read too.
• Resistance at the fight. With a Warcraft Logs client of your guild's own, the night page shows what each raider had where a fight calls for it — shadow on Mother Shahraz for the whole raid, fire for Illidan's tanks and shadow for his warlock tank, frost and nature for Hydross's tanks: the gear they wore and the buffs on them at the pull, beside the resist set they keep and what your sheet asks. For whom the gear check is open.
• Engineering on the consumables page. With a Warcraft Logs client of your guild's own: every bomb, grenade, sapper, turret and Oil of Immolation each raider used, on the bosses and on the trash, and the damage it did — beside the boss pulls they bombed and drummed on, since a drum and an explosive share a two-minute cooldown.
• Trinkets and racials on the Performance page. With a Warcraft Logs client of your guild's own: each raider's on-use trinkets and racials on the night's kills — every use, of how many its cooldown allowed on the kills the trinket was worn, and Berserking and Blood Fury on the kills of whoever used them. A defensive trinket, or a racial used when needed, shows its uses alone; the wipes and the trash are on hover.
• What the Council sends back, and damage between raiders. The avoidable damage page counts Lady Malande's Reflective Shield — what raiders did to her while it was up, sent back at them — and lists the damage raiders did to each other through a mechanic they carried (Fatal Attraction, Shatter, Static Charge); pulls with a mind-controlled raider are left out of it.
• A night in two logs, whole. When two of your raiders log the same raid, or a night is split between logs (one raid, then the next), the consumables page, the gear check and the Performance page put the logs together pull by pull — each pull once, every raider in every pull they were in. Before, each raider came from one log, and a second logger who started halfway through could leave the night's first bosses out.

The bot

• A raid called off, in one press. The raid-time check-in has a "Raid cancelled" button for officers, and so does /checkin's answer: once pressed, the bot asks nothing more that night and posts no digest for it. A misclick is undone with "Not cancelled after all".

7 October 2026

Heads-up

• We are working on major updates, so expect some downtime. Over the coming days the site and the bot may be away for short spells while each update goes out. Nothing you have entered is lost, and everything is back as it was when they return.

The site

• A page for every raid night. On the Logs page, "the night →" opens the night: each pull in order with how long it ran, how it ended and who died to what, the idle time between pulls, and each boss's kill time — from the pull to the kill — against your fastest kill of that boss on any night. Nights fill in after the nightly update.
• A gear check for officers. With a Warcraft Logs client of your guild's own, the new Gear page lists what each raider should fix before the next raid — pieces not enchanted, empty sockets, gems under your minimum (blue by default), a meta gem whose colours are not worn — from each raider's newest raid night, so it clears itself once they fix it for the next raid, with everyone's gear by slot. Rocket Boots, worn for Mother Shahraz alone, are never asked for an enchant. PvP pieces are listed apart, only worth a look. The night page shows the night's gear to whoever may open the Gear page, and Settings → Gear check sets the gem minimum and which pieces must be enchanted.
• The night's assignment sheet beside its log. With a Warcraft Logs client of your guild's own, the night page links Jobs done: every boss pulled with the jobs its sheet handed out — curses, Expose Armor, Demoralizing Shout, kicks, misdirects, innervates — and what the log says each raider did: the debuff's time on the boss and whether it was theirs, their interrupts, onto whom they misdirected or innervated, and what the log has that the sheet did not ask for. For officers unless Settings → Access opens it to more.
• Every raid night's consumables, boss by boss. With a Warcraft Logs client of your guild's own, the night page links the night's consumables: who came to a boss without a flask or two elixirs, unfed, or with a weapon left bare — and the picks that do nothing for a raider's role — then a grid of everyone for the whole night or one pull: flasks, food, weapon oils, scrolls, jewelcrafted necks, potions, healthstones, runes, and every drum with how many it reached. For officers unless Settings → Access opens it to more.
• Each raid night, role by role. With a Warcraft Logs client of your guild's own, the night page links Performance: the tanks against the bosses' melee — swings taken, avoided, blocked, crushing blows and crits, over the night and on each kill — the healers' healing, overheal and active time, everyone's damage, damage per second and active time over the kills, and the night's interrupts. For officers unless Settings → Access opens it to more.
• Loot your guild's way. /whowants and /droplist rank who wants an item the way your guild hands out loot — the council's priority, a soft reserve's reservers, Gargul's fewest plus ones, DKP or EPGP — and each line says why. Your rules page is written for your loot system too.
• DKP and EPGP points beside the priority. Your addon's own points, read from its file or its export on the Loot History page, in a column on the standings.
• Decay for DKP and EPGP. Settings → Loot system: a share every few weeks (30 % every 4 weeks, say), a share when a new phase starts, or a decay now by hand — each can be taken back. DKP loses the share from positive balances; EPGP takes it off EP and GP alike, so your ratio stays and the gaps shrink. The site shows the points after the decay until your addon's next read, and the rules page says how your guild decays.
• Who Has Won What. A soft-reserve or roll guild can show who has won least lately instead of a priority score — Settings → Loot system.
• Shape your guild your way. Settings → Your guild's setup puts your teams on one page — each one's size, loot system, whose standings it counts on and how its raids split — and Settings → Modules switches off the parts your guild does not use. A new loot system can start a new season with nothing deleted, a raider can raid with more than one team, and a team's board can keep its own scoring weights and windows.
• Every client language prices the same. A German, French or Russian loot master's RCLootCouncil words and tier tokens count as the English ones.

Addon and uploader

• Addon 0.10.20 — update it to invite the raid from the sheet. With the night's sheet loaded, the raid leader presses Invite on the assignments tab and everyone in the comp who is not in the group yet is invited; past four, the party becomes a raid as soon as the first one joins. Once everybody is in, the same button sorts the raid into the comp's groups, out of combat. /vrt invite and /vrt groups do the same, and an assistant can do it too.
• Uploader 1.16.0 — nothing to do, it updates itself. It now sends LootReserve's won rolls, a DKP addon's points with its loot, and Gargul wins tagged with the raid they were reserved for.

6 October 2026

The site

• Deleted Raid-Helper events still count. Raid-Helper forgets an event once its post is deleted, so a guild that clears its raid posts after the raid lost those nights' signups — and raiders who came every week fell off the standings for "too few signups". The site now keeps the signups it read on the night, and a raid with no Raid-Helper event at all counts as a signup for everyone in its log.
• Every gate on the standings is yours to switch off. For a casual guild: Settings → Scoring's minimum signups, minimum attendance and weeks away before auto-inactive each take 0 for off, and one button turns all three off. The roster gate — how many roster members a log needs to count as your raid (Settings → Guild) — takes 0 too, and Settings → Integrations sets how much of a personal log must be your raiders (30–100%).
• Settings saves only what you change. A dropdown with no value of its own shows "default (…)" and stays that way when you save its section; before, a save wrote its first option, which on the Access section was "everyone" for the officer pages.
• Settings checks what you type. Times must be HH:MM, the three weights must add up to 100, names on the raid-role and comp lists that are not on the roster are named, and a roster rank with no multiplier is flagged. The attendance overrides file saves from Advanced as the bot wrote it, and an override that says "present" counts as attended.
• Guild masters hear when raids stop reaching the logs. When Raid-Helper shows raids and nothing reaches your guild's Warcraft Logs page — not even as personal logs the site counts — your guild masters get one DM saying since when and the two ways to fix it, instead of a warning only the standings page showed.
• Fewer warnings that do not apply. "Boss kills with no loot" waits until your guild's loot history has started, and no warning names a file on the server any more — each says where in Settings or on which page to fix it.
• Your guild's boss sheets carry no other guild's names. The Reliquary of Souls notes named a Vortex raider and the templates' header Vortex's tanks; both are gone from new guilds, existing guilds' sheets and the public guides.
• The Rules page keeps officer-only standings private. Its example table showed the top three of your live standings to everyone who could open the page; when your standings are for officers, it now shows three made-up raiders scored with your guild's numbers.
• Drop a loot file on the Loot History page. Officers drop the loot addon's saved file there — RCLootCouncil, Gargul, CEPGP, MonolithDKP or CommunityDKP — and its awards come in: no uploader needed, for a Mac or a one-off catch-up. It is read the way the uploader reads it, and an award an uploader also sent counts once.
• Tell your raiders in one post. Settings → Discord posts → Tell your raiders posts one message in the channel you pick: your guild's site, their wishlist, the in-game addon and /help. The health page says when it went out.
• Officers get a guide of their own. A new page beside the raiders' one — For officers, in the top bar — with the raid week from signups to the nightly update, what to check once a week, and where each job lives.
• A health page instead of the first-steps card. Officers open Health in the top bar: Warcraft Logs, the nightly update, Raid-Helper, the roster, the loot history, wishlists, Discord and the assignment sheets — each with what it is doing, the date it last worked and the one thing to do, and whose step that is. Your guild's front page shows the lines that need a hand, and the Discord message after setup links the page.
• Setup in three screens, with presets that say what they set. First the game and your team — its size, raid days, start time and time zone — then how your guild loots and how hard the standings are, then the connections, each of which can wait. Your realm comes from Warcraft Logs' own list, the guild's name is yours rather than your Discord server's, and each choice shows the values it sets. Settings → Raid nights and Scoring offer the same presets later.
• Settings sorted by job. Ten areas — raid nights and teams, signups, loot, assignments, bank and requests, people and access, Discord and site, connections — instead of a long "Guild" page and a "Bot & site" page that held a bit of everything. Home opens first: how your guild is doing, what is switched on with a button to change each, and what changed lately (dates only). The fields only a self-hosted bot reads are out of sight. A search box above the menu finds any setting by its words and opens it.
• Your team in one place. Settings → Raid nights and teams opens on your raid team: its game, its size and the raids that count, how it loots, when it raids, where the bot posts for it and how many raiders it has, each with a button to the section that sets it, and your guild's other games beside it. Name the team, or keep your guild's name. It is the first step to a guild running several teams; nothing changes for yours.
• Your guild can run several raid teams. Settings → Teams adds a team beside your main one — a second 25, a Karazhan group — with its own raid days, size, check-in, comp and channels, and its raiders on the Roster. Its logs and Raid-Helper events are filed under it; it has its own standings page, with a switch between the teams, or counts with the main team; its digest and check-in come after its own raid. A team on another game, Forever beside Anniversary, is one press from your guild's own answers. A team with a loot system of its own, such as a soft-reserve alt run that counts nowhere, is part of Pro.
• Actions instead of settings, each with an undo. Settings → Loot system has "A new phase started" — the debt from before it counts less, its raids count, the bosses two phases back stop counting for effort, in one press — and locks or unlocks the wishlists; the roster is marked as checked from Settings too. On the Loot History page an officer corrects any award's price with ✎, with a note. Home lists these actions, each with its undo, and an undo never overwrites a later change.
• See who moves before you save. As you change a value in Settings → Scoring, it shows whose priority changes and who changes places — worked out the way the nightly update does it, before anything is saved; the roster table and Advanced's editor have a Who moves? button. Recent changes says what each change did ("major: 30 → 45"), a section's Save is one change, and Home lists the earlier versions of each file, the last 30, any of which comes back after showing what it changes.
• Your own loot levels, and debt that runs out. Settings → Loot prices: name your levels your way — Major, Tier, Upgrade, a Best in slot of your own — set each one's price, add or remove them, and say which of your loot responses (read from your loot history, with real awards beside each) and which kinds of item land on each. An award can keep its full price for a while, then lose a set share of it each week until it is worth nothing, instead of halving forever. Major items and crafted pieces are picked by name, the bosses that no longer count for effort from a list. Your standings, Loot History, Rules page and Discord use your names.
• Loot prices and decay can change from today on. Settings → Loot prices asks when a change counts: from today on — the awards won before today keep the prices and the decay they had, and Major going from 30 to 40 costs 40 only for new awards — or for every award, the past too. The older awards' prices are listed there, and one press prices them as today; the Rules page and the standings say when older awards keep theirs.
• Each boss's worth for effort, from today on or for every raid. Settings → Loot → Effort per boss gives every boss a weight from 0 to 1 instead of the old "no longer counts" list: Gruul at 0.3 means the consumables on his kill count 0.3 of a current boss's, and a night of only old bosses weighs that much less. A change counts from today on — earlier raids keep what they had — or for every raid, the past too; who moves shows before you save, and "A new phase started" sets the old bosses to 0 from that day.
• The pages follow a change by themselves. A save in Settings, an action or a restore rebuilds your guild's pages a few seconds later — no Rebuild button to remember — and Settings says when they show it. A change made while the nightly update runs is built right after it, not the next night.
• Settings picks from lists instead of typed names. It takes Discord roles and channels from your server, raiders from your roster — the raid-role lists in their order, the comp builder's always-in and fill-last — raid days as chips and the realm from Warcraft Logs' list; times show your guild's time zone beside them. A name that is on neither the roster nor the server is marked, never dropped.
• Hand parts of Settings to your officers. Settings → Access gives Loot, Assignments, Signups and Bank and requests to Discord roles: a raid leader who is not guildmaster changes the raid roles and boss templates, a loot master the scoring — and nothing else. They open Settings with their Discord login and see Home and their areas.
• Guilds outside Europe run on their own clock. A US guild's raids, Raid-Helper events and loot are dated by its own clock — a Tuesday raid at 20:00 Eastern is Tuesday's, not the Wednesday it already is in Europe — and its lockout resets on Tuesday, the US region's day (an Oceanic guild on Sydney time: Wednesday). Settings → Requests sets another reset day if yours differs. Nothing changes for guilds in Europe.
• Smaller fixes across the site. A guild address with no page behind it shows a page with your menubar instead of a line of code; the standings header shows the date only; the demo's raiders have their own consumables, so its effort column is no longer 50% for everyone; Settings names the uploader and the Era Warcraft Logs host correctly; the Forever page has one disclaimer, not two.

Addon and uploader

• Addon 0.10.18 — update it: the window greets raiders, and the guild bank stays with the officers. It opens on the assignments on a raid night and on Professions in between, with words for raiders when no sheet is loaded; the status line and the minimap button say when a newer version is out. A guild bank read now reaches only the officers' addons — on the guild channel an officer's read put officer-only tabs into every raider's Professions tab.
• /uploader has a button for when Windows takes the uploader away. Under the download link, *Windows deleted it?* shows the raider who asked, and no one else, how to get the file back and keep it, step by step, in Windows Security or another protection program. The command's line in Discord's command list says so, so nobody has to ask an officer first.

5 October 2026

The site

• Setup asks nothing for Warcraft Logs. The site reads your guild's public reports with its own Warcraft Logs client, so a new guild skips the API client step; Check on Warcraft Logs still shows that the guild is found. A client of your guild's own stays optional in Settings → Integrations: with it the standings fill in at once and the all-time attendance reaches back to your first log; without it a new guild's reports come in over its first hours, newest first. Guilds that have a client keep it — nothing changes for them.
• Raids uploaded as personal logs count. When a raid night has no log on your guild's Warcraft Logs page, the site looks through your raiders' recent logs for who uploaded it and follows that logger. Their personal logs count as your raid nights when they are a raid you count, on one of your raid nights, with at least 60% of the players yours (the roster and that night's signups). Settings → Integrations shows who was found and how many nights, with a switch for each, and takes a log link to add a logger the site missed. Your guild's own log of a raid always wins.
• Add the bot and set up in one click. One Discord authorisation logs you in, adds the bot to the server you pick and opens its setup form.
• Whoever sets the guild up lands with Settings. The form shows your Discord roles and stops you before you lock yourself out of Settings. Logged-out raiders get your guild's own login page, and a member without the right role is told which role the page needs.
• Raid-Helper is optional now. Setup no longer asks for its key: a guild without Raid-Helper sets up and gets its standings, loot history, wishlists and requests. Signups, comps, check-ins and the assignment sheets come once a guildmaster adds the key in Settings → Integrations, and removing it no longer stops the nightly update.
• Restarting your guild's bot restarts only yours. The Settings button reloads your guild's bot in a few seconds; it used to restart every guild on the site, mid-raid included.
• A WoW: Forever guild sets up without Warcraft Logs. Warcraft Logs has no Forever realms yet, so setup no longer looks the guild up there — which stopped every Forever-only guild. Once Warcraft Logs logs Forever, the logs join the nightly by themselves.
• The live log looks less often — nothing to do. During a raid the Logs page still marks the log being written as "live now"; the check runs every ten minutes until a log turns up, then every fifteen instead of every five, and stops for the night once the log has ended.

Addon and uploader

• Uploader 1.15.1 — nothing to do, it updates itself: each game's loot history stays its own. Every World of Warcraft game keeps its own RCLootCouncil history, so a loot master who also plays Classic Era or retail on the same Battle.net account has one in each game's folder. The uploader sent them all and the site filed them per account only: the two games' histories could overwrite each other, and another game's awards on one of your raid nights could even count. Now each file says which game's folder it comes from, the site keeps each game apart and leaves out the games your guild does not play, and the uploader says once which file it set aside and why.

4 October 2026

Addon and uploader

• Addon 0.10.17 — update it: RCLootCouncil's loot history window opens again. Four awards the site held as filed by hand had been added to RCLootCouncil's own history on officers' PCs under ids its history window cannot sort, and /rc history stopped with an error. 0.10.17 takes them out at the next login or /reload and never adds such an award again; the site no longer hands them over, and they stay in the site's loot history.

The site

• Choose the raids you loot with RCLootCouncil. Settings → Guild has a box per raid, all ticked. Untick the ones you run without it — alt runs, older raids — and the site stops expecting loot history for them: no "boss killed with no loot" warning, and the digest says the raid was looted without RCLootCouncil instead of asking where the loot went. Their logs count for attendance as before.
• A request handed out in part stays open for the rest. Giving 1 of 2 gems — or 2 of 3, or two hearts of three — no longer closes the request: what was handed out goes into the log on its day, and the request stays in the queue with only what is still wanted, each line marked with what it already got ("got 1 of 2"). A line the guild will not give is closed with its own "no" tick, and undoing a hand-out puts it back into the request.

3 October 2026

The site

• The nightly digest comes at night, and only after a raid. It went out after the first page update of each day — often around noon, raid or not. Now it follows the nightly update (23:45 unless your guild set another time), on your raid days only; a guild without raid days set gets it on the days with a Raid-Helper event.
• Each guild runs on its own clock. A new Time zone setting, next to the nightly's time in Settings: the nightly update, the digest, the raid days, the raid start and the raid check-in all follow it. Left empty, it is your realm's region — Central European Time for EU realms, US Eastern for US, Sydney for Oceania.
• Move anyone into any stack on a boss. On the assignments page an officer's "move someone into this stack" now lists the whole raid, not just that section. Put your elemental shaman in the melee stack on the bosses they play enhancement and they play melee there — out of the ranged camps on that boss, marked on the sheet — and stay ranged everywhere else. Moving them back undoes it. Press "every week" on the mark and they play that role on that boss every raid night they are in the comp, with nobody moving them again; "stop every week" ends it, and a move back on the night still wins for that night.

2 October 2026

Addon and uploader

• Addon 0.10.16 — update it: no more stutter after a search. With the window closed, the professions list kept redrawing itself whenever the game answered an item or the guild list updated — after a search, across every profession, which made the game stutter now and then. It now draws only while you can see it, and closing the window clears the search.

The site

• A reminder before the trial ends. A guild on the 14-day Pro trial now gets a Discord message three days before it ends and again once it has: what stays free, what stops and where to subscribe. It goes to the guild masters who run the guild's site — by DM, or as a notice in the server when no DM gets through.
• A new guild's roster fills itself from its raid logs. Until an officer has checked it, everyone the guild's Warcraft Logs show on two or more nights of its latest eight weeks of raiding joins the roster on their own — with class, role and the Discord name from Raid-Helper — so the standings work from the first build, even when the newest log is months old. Officers fix mains, alts, ranks and roles, then press Mark as checked on the Roster page; from then on new faces wait on the Officers page's Roster tab as before. Nothing to run, and an empty roster no longer stops the nightly update.
• Raids that never reach the guild's logs are pointed out. When Raid-Helper shows raids but nothing has been logged to the guild on Warcraft Logs since, the standings page and the officers' digest say so and what to change: logs uploaded as personal logs never count, so whoever logs picks the guild in the Warcraft Logs uploader.

25 September 2026

The site

• Council mode's table lines up. On the loot history page the numbers sit under their headings, the table stays inside its panel, and "not on current board" goes on a small line under the name.
• The assignment sheets are free — Pro is now the automation around them. Everything the in-game addon shows is free: the assignment sheets (the page, /assign, the sheet in game), loot priority, loot history and the RCLootCouncil sync, wishlists and bank requests. Pro — $5 a month or $49 a year, 14 days free for a new guild — keeps the automation: pull cards in Discord that follow the comp, the comp builder sending to Raid-Helper, raid check-in, the nightly digest, wishlist reminders, loot-council mode, imports from other loot addons and the MRT export.

Addon and uploader

• Addon 0.10.15 — update it: it looks like WoW now, and every crafter's recipes show. The window is Blizzard's own framed window, with the addon's icon in the portrait, the tabs along the bottom edge like the character window, the game's search box and WoW's gold and white text. The professions show their own icons in action-button slots; the one you pick lights up, and hovering it says how many crafts the guild knows. A client without these frames keeps the old look.
• The professions tab lists everything the site knows a crafter has. A profession window read while filtered — one slot, or "Have Materials" ticked — counted as the crafter's whole list, and the addon then kept the site's fuller one out: one enchanter showed a single enchant of the 191 the site had. A filtered window can no longer shorten a list; recipes now go only when a crafter unlearns the profession or gives up a specialisation. The site fills in what a crafter's own report lacks (on every PC that runs the uploader), and enchants sit under their slot instead of as "Formula: …".
• Addon 0.10.14 — a tidy-up under the hood; update when convenient. Nothing changes in game. The addon now asks the game its current way for item counts, known spells, the gems in a piece and the consumables report to raid chat — calls TBC Anniversary and WoW: Forever both have — and the variables and code nothing used are gone. Checked against the WoW API definitions addon authors use: no stray globals, and the one older call left is the one the Anniversary client has no newer version of. The download itself now names its folders the standard way: the zips before this one wrote Windows' backslashes, which some unzip tools on macOS and Linux turn into loose files instead of the addon's folder.

24 September 2026

Addon and uploader

• Addon 0.10.13 — asking the guild for a craft names who is online first. Right-click a recipe in the Professions tab, "Ask in guild chat": the line named the first three crafters alphabetically, online or not, so the question often went to people who were not there. The online crafters come first now — in that line, in the menu's whispers, on the row and in its tooltip — read from the guild list at the moment you click.
• Addon 0.10.12 — update it: RCLootCouncil's loot history stays whole on every officer's PC. A raid you missed, or looted from another computer, used to leave a hole in your in-game RCLootCouncil history — its history window and the voting frame's "won before" counts only knew what your own PC had recorded. Now the awards the guild's history holds and yours lacks arrive with the uploader's inbox and go into RCLootCouncil's history at your next /reload or login, exactly as RCLootCouncil wrote them on the PC that recorded them, under their own ids — nothing is added twice, and an award you delete in game stays deleted. Needs uploader 1.15.0 (it updates itself within the hour).
• Uploader 1.15.0 — the loot history goes both ways. It still sends your RCLootCouncil history up; now it also sends each award whole (RCLootCouncil's own entry, so another PC gets it back as it was), asks the site which awards your history lacks, and writes those into the addon's inbox — at most 300 a pass, newest first, the rest once the game has saved them.

The site

• /request new: the amount counts, and several gems go in one request. amount:2 what:Crimson Spinel requested one: the gem suggestion put a "1" in front of the name, and a list took its numbers from what: alone. Now a line without a number of its own takes amount:, and what2: / amount2: and what3: / amount3: add more gems — or bank items — to the same request. A list typed into what: ("2 Crimson Spinel, 1 Lionseye") works too: a suggestion now sends exactly what it shows, so picking the second gem no longer loses the first.
• An officer's own request form sits above the log. On the Requests page an officer's own requests, and the form to ask for something, came after "Who got what, when" — a log that grows all season, so the form sat at the very bottom. It now comes straight after the walk-up, above the log, headed "Your requests".

22 September 2026

The site

• The comp builds itself — from the signups, with your rules, into Raid-Helper. On the assignments page, officers press "🧩 build the comp": a proposal from the raid's signups as they are this minute — tanks and healers to the numbers you set, your always-in list seated first (the main tank, the raid leader), your fill-last list only when the raid is short, class minimums ("Shaman 4"), and the seats left given out by the rule you choose — whoever sat most recently plays first, or the best attendance, or first signed first in — with rank ahead of all of it. Every seat and every bench line says why. "Send to Raid-Helper" puts it into the event's comp tool, where you drag as usual; "Post the bench list" tells the raid who sits and who is first in line. Set it up under Settings → Comp builder.
• Two editions on one Discord server each see their own raids. A Raid-Helper event says which game it is for — the template it was posted from (TBC's, the vanilla one Forever's raids will use) — and until now an edition took every event on the shared server: the Forever edition's first good night pulled the Anniversary guild's raids as its own. Now an edition takes the events of its game's template only; a guild alone on its server still takes everything, since it may post raids from whatever template it likes. Settings → Guild → "Raid-Helper templates" names the templates yourself — a custom one, or "all" — when the default is not what you post from; pinned event ids count whatever their template.
• A guild Warcraft Logs does not know no longer stops its night. A Forever guild's realm is not on Warcraft Logs yet, and the nightly pipeline died at that first step every night since the guild was set up — so its Raid-Helper signups, loot history and pages never refreshed either, and nothing said so until the alerts arrived. Now that guild is one integration skipped: the night goes on with Raid-Helper, the loot import and the pages, and a line in the pipeline's output says why. A wrong realm slug on a guild whose game does have logs is named in a message to the owner once a day, with the setting to fix.
• A failed night says why in the message. The alert pointed at "the log under hub/logs" — a file on the server. It now carries the failure's own first line, and the instance's row on the admin page shows the same reason under the red "failed".

21 September 2026

Addon and uploader

• Addon 0.10.11 — the council column says why a raider is off the board. A raider under the guild's attendance bar, auto-inactive or short of signups showed "—" in the RCLootCouncil voting frame, as if unknown. Now the cell says "47% bar", "inactive" or "unsigned", sorts below the ranked, and the tooltip says what the bar is and when they are back on it. Uploader 1.14.1 carries the reason into the inbox.
• Addon 0.10.10 — /vrt pull <guildmate>, and the guild's recipes arrive with the inbox. Two ways to fill in the professions of guildmates you were never online with. The site's way: the uploader's inbox now carries the guild's recipes as the site knows them — the union of what every uploader has carried — and the addon files them where it holds nothing first-hand (never over your own readings or a package heard from the character itself). The in-game way, for anyone without an uploader: /vrt pull Diskomus whispers him the tags you hold, and his addon whispers back every recipes package he holds that you lack — his own account's first-hand and the ones he heard from others, marked as passed on. Second-hand ranks below first-hand and below the site, so it fills holes and is replaced the moment the owner or the site speaks; a relayed record is never sent to the site. A first pull of a big guild is a few hundred messages, which the game paces over a few minutes.
• Uploader 1.14.0 — the guild's recipes ride into the addon's inbox. Every two minutes, beside the wishlists, bank requests and standings: the recipes of every character in the guild as the site knows them, so a client shows who can craft what without having been online with them. A record the addon took from the site, or from a guildmate passing it on, is second-hand and is never sent back. The exe is the launcher and does not change; the program updates itself within the hour.

The site

• Settings works again — its page script had a stray apostrophe. The Settings page shipped on 2026-09-21 with "raider's" inside a quoted string of its own script, which stopped the whole script: the page loaded but nothing on it read or saved. The test that parses every page's scripts caught it the next time it ran; it runs before every commit from here.
• The rules page speaks the game's language. The sentences that are the game's, not the guild's — the legendary example, what a tier token is, which potions and flasks count, the two-tiers-old bosses, the non-unique rings, the chase items — were Anniversary's on every page: a Forever guild's rules named Warglaives and Shattrath flasks. Each game has its own now (Forever's: the Hyjal Summit questline and sets, its four new flasks beside vanilla's, two elixirs instead of a battle/guardian pair, no tiers-old rule yet), and existing pages move over by themselves.
• The "for?" box on a request suggests every item, with links. On a guild-bank request the box for what the lines are for suggested nothing; on a gem or enchant request it suggested gear only, as plain names. It now suggests from every item — the shard as readily as the bracers, the formula, the pattern — each with its icon and colour, and what you pick links on the request. Settings → Requests calls the lookup "every item", which is what it always did on the lines.
• Posted pull cards follow the comp with nobody on the page. The comp watcher reads Raid-Helper only while someone has the assignments page open; a comp edit on a raid night with the page closed left the pull cards in Discord saying the old comp. While cards are posted for a night that is on, the watcher reads every five minutes on its own (some 260 calls over the night, well inside the allowance) and re-edits the cards when the comp changed.
• A Raid-Helper read that never answers is over in fifteen seconds. Until now a request Raid-Helper took and never finished held the assignments page — and every page and job waiting behind it — for as long as the connection lasted. It is a failure like any other after fifteen seconds: the sheet keeps the comp as last read and says so, the Health card counts the timeouts.
• The rules page now says what your settings say. It was a copy of one text with the guild's name pasted in — the weights, windows, half-life, debt tiers, effort split and rank multipliers were prose, and the example rows were one guild's raiders on every guild's page. Now every number comes from Settings → Scoring at each build, the sentences that depend on a setting (the signup gate, the attendance bar, tentative credit, how tanks and healers are scored, the phase rule, the alt rule) appear or change with it, and the example rows are your own top three. A page a guild wrote itself is left as written.
• The owner is told when something breaks — before a raider is. Raid-Helper refusing calls, the soft brake, a nightly that failed: the hub sends it to the alerts channel the owner names, or as a DM to each owner, once per kind per six hours. /hub/admin has a Health card: Raid-Helper's calls today and whether it is answering, the newest backup and its age, the last error, the recent alerts and where they went.
• The hub's nightly archives are pulled to a second machine. A daily task on the owner's own PC fetches every archive the hub keeps (fourteen nights plus one a month) and verifies the newest. Off the server, nothing is lost with it.
• Officers can file an award the loot addon never recorded. On the loot history page: character, item (picked from the suggestions, so it links), date, boss, response, note. The row goes into the manual file beside the uploads, the standings rebuild, and the officer gets the RCLootCouncil entry to paste into the loot master's history if the game should show it too — same id, so the site counts one award whichever way it arrives. Each row can be taken back out.
• Raid-Helper key: one for all editions, or one per edition. Settings → Guild → "Raid-Helper key — one for all editions, or one per edition". Shared (the default) copies the original edition's key to every sibling, one allowance of 5,000 calls a day between them; per edition, each keeps the key its own Integrations page was given, each with its own allowance.
• A raid past midnight keeps its sheet. The assignments looked for tonight's raid by today's date; at 00:01 the night became "no Raid-Helper event found". A night is still on until five hours after its start, whatever the date says.
• An attendance bar for the standings — each guild sets its own. Settings → Scoring → "Standings gate — min attendance (%)": a raider under that share of the attendance window's raids is off the board (and off the addon's Priority column) until they are over it, named under the table with their share — "Off the board — under the guild's attendance bar of 60% over the last 8 weeks: Halfway (50%)". 0 means no bar, which is the default; Vortex runs 60.
• "Names missing from the roster" means names from this window, and says when each was seen. The nightly digest named a character nobody had raided with — an alt's award from June that had arrived the day before in an officer's first upload of their loot history. Loot older than the attendance window no longer puts a name on that line or on the officers' link panel, and every name now carries when it was last seen and where: "Pugmage (1x, loot 2026-09-06)", "Stranger (2x, in the log 2026-09-20)".
• Asking the guild bank: the items you type are linked. On a bank request, each line's box now suggests as you type — what the bank holds first, with the count, then any item by that name — every suggestion with its icon and colour, and the one you pick becomes a linked chip in the box (click it to change), the way the gem tab picks. The request then carries the item itself: the officers' table and your own list show it with its icon, colour and tooltip. (The suggestion menu also sits under the box it belongs to now, not at the bottom of the card.)

20 September 2026

The site

• The assignments sheet stays tonight's when Raid-Helper stops answering. On 2026-09-20 Raid-Helper's daily allowance (5,000 calls a key) ran out during the raid, and the sheet built that afternoon came back labelled "the last raid's sheet — no comp posted yet". Now the comp Raid-Helper last gave is kept on file, so an outage or a restart mid-raid leaves the sheet whole — pins and edits work, a bar says Raid-Helper is not answering — and a sheet is "an old raid's" only from five hours after the raid's start. The bot also asks Raid-Helper only while somebody is looking — a page open, or a request in the last ten minutes — once a minute around a raid (six hours before to five after), every five minutes otherwise; one answer is shared between a guild's editions and a raid full of page loads, and nothing is asked while Raid-Helper says to wait or while nobody has the page open.

18 September 2026

Addon and uploader

• Uploader 1.13.0 — the exe is a launcher that never changes; the program is a file beside it. An officer's antivirus called the 1.12 exe a trojan on first sight: an unsigned program that starts at logon, runs without a window and downloads and swaps its own executable is what those classifiers are built to catch. Now vrt-uploader.exe does one thing — run vrt-uploader.cjs from beside itself, fetching it once (hash-checked) when it is not there — and an update replaces that file; no executable is ever downloaded or swapped again. Every copy from 1.12.0 updates itself into it within the hour. Officers: put the exe in a folder of its own and keep the folder — those two files are what runs after every logon.
• Vortex Raid Tool Forever 0.1.1 — the first login on the beta, and its fixes. The Forever client is the modern engine: the item, spell and buff reads the Anniversary client answers as plain functions live in C_Item, C_Spell and C_UnitAuras there, and the tooltip has no OnTooltipSetItem. 0.1.0 threw on every item in the bags and on the Professions tab, and its wishlist file stopped loading half way. 0.1.1 asks the client which of the two it has, on every such call, and the same code serves both games. Not on CurseForge yet; on the beta.
• Uploader 1.12.5 — your uploads are filed under your character, not your Windows account name. Until now the name on the loot import list and on Settings → Uploader "Who runs it" was whatever Windows calls you — a first name for many, "Gebruiker" for one. The uploader now takes the character the in-game addon reads for on that PC, chooses it once and keeps it; --by <name> still picks any name. Every copy from 1.12.0 fetches it by itself within the hour; a copy not heard from for two weeks drops off the list.
• The Forever addon's consumables checklist plays by vanilla's rules. No battle/guardian split: any two elixirs fill the two slots, the jujus, Winterfall Firewater and the like count as elixirs, the four Hyjal flasks are flasks, and the strip and the raid report say "elixir" and "2nd elixir" instead of battle and guardian. The Anniversary addon is unchanged.
• Vortex Raid Tool Forever — the addon for World of Warcraft: Forever, built. A second addon, "Vortex Raid Tool Forever", from the same code as the Anniversary one: its own name, its own version, /vrtf beside /vrt, no room pictures until the raids are seen (0.1 MB), and a recipe scan that reads Forever's new profession window — the old one does not exist on that client. Every function and event it uses is checked against the beta client's own list before a build can ship, the way the Anniversary addon is checked against its client. It goes to the beta first; a CurseForge listing follows when it has been seen working. The uploader (1.12.4, fetched by itself) reads the Forever addon's file and writes its inbox into that addon's folder — one uploader for both games.
• Addon 0.10.9 — update it: on an alt, your assignments find you. Rxtinct raided as a hunter; his main is on the sheet as Rxshameman, and the tab showed him nothing unless he ticked *everyone*, because the sheet names mains and the game names characters. Now the sheet carries each main's characters as the roster links them, and the addon matches the character it runs on to the sheet's name by itself: a linked alt straight away; an unlinked one through the inbox's names when the uploader runs on that PC, and otherwise — once you are in the group — as the one person of your class on the sheet who is not in the raid. It tells you once which name it is showing; /vrt as <name> still overrides. Two of your class missing, or none, and it guesses nothing. And a row an officer writes your character's own name into on the night is yours too. For officers, the row picker now knows who is actually in the raid: somebody you invited to fill who is not on the sheet is listed first, marked *in the raid, not on the sheet*, in the class the game says — one click puts them on the row — and a sheet name that is not in the raid is marked *not in the raid*, so you see whose rows need a new name.
• Who runs the uploader, on which build — on Settings → Uploader. A guildmate said he had pressed Y hours earlier and nobody could tell whether his copy was alive, and the download is named for the guild, not the version, so nobody could say who was on an old build either. From 1.12.3 every request the uploader makes says its version and its by-line, and the site keeps a note per person: version, when it was last heard from, what it last did — with *behind* when a copy is older than the current build and *silent* when it has not been heard from for three hours (a running copy checks in every couple of minutes). Copies before 1.12.3 say nothing until they are updated: from 1.12.0 they fetch it by themselves, older ones need /uploader once more. The uploader also says its version at the top of every run, in the window and in its log; and its file's Properties → Details carries it too.

The site

• Refer a guild: a month free for you, half a month off for them. Every guild has a referral link — on Your servers and on its billing page, vortexraidtool.com/hub/?ref=<your slug>. When a guild sets up through it and pays its first month, one month of Pro is credited to your subscription (Stripe takes it off your next invoice), and their first invoice is 50% of a month cheaper — the discount is on their checkout by itself. The new guild's setup form says who referred them and what both sides get; a server cannot refer itself; one month per referred guild, for any number of guilds. Partner codes (a streamer's, a community's) work the same way and can be typed at checkout too.
• The tool on WoW: Forever, on one page. For the guild leaders choosing their tools between name reservation and launch: what works from the first login (roster and re-rolls, professions and recipes with Forever's own, guild bank requests, Discord, the Forever addon on the beta), what comes with the raids on 9 December (assignments, loot priority, guides), and how a guild raids both games from one setup — the Forever demo, the profession bonuses and the calculator a click away. "WoW: Forever" sits in the product bar on every public page, the front page names both games, the downloads page lists both addons.
• Forever guilds know Forever's items and recipes. The beta client's own tables — read through the community's build mirror, not guessed — give a Forever guild its item database (19,171 items, 6,497 of them new) and its recipe catalogue (2,207 crafts, 1,158 new) from the day it is set up: the recipes page, the wishlist and request lookups and the professions tab in the Forever addon name vanilla's things and Forever's, not TBC's. The Forever professions page gained what the tables confirm, in the tooltips' words: the four Hyjal flasks (Stamina plus hit, crit, expertise or haste inside Mount Hyjal, Hyjal Summit and the Barrow Deeps), the Revealing Draught, First Aid's poultices, tourniquets and anti-venom, the herbalists' Seed of Renewal and Death Lotus, the skinners' Camp Chair and Tanning Rack, the fishers' lures, the engineers' Repair Bot, the enchanters' Lute, the cooks' campfire tiers. The raids' bosses and loot are not in the open tables yet.
• Forever sites: readable cards, and the assignments behind a lock until the raids. The Forever theme's cards were panes of glass over the key art and could not be read; they are dark glass now. And a Forever guild's Assignments item sits locked in the menubar with a note — the first raids open on 9 December — instead of an empty sheet: the landing card says it, the page says it, and /assign in Discord answers it. A guild testing on the PTR can lift the lock in its settings file.
• The hub owner's overview. The admin page opens with the numbers a seller needs: guilds on the hub (by game, and any whose server the bot has left), Discord servers with the bot and how many of them never set a guild up — the leads, each with when the bot was added and who from that server has been at the hub — paying, comped and free guilds, trials with the days left (red within a week) and trials that ran out without a purchase, guilds active this week, raiders in all, people at the hub in 30 days. Then every guild with its plan state, use and contact (the server's owner, the admins seen at the hub), and the instance table as before.
• Paladins are the tank healers. With two or more holy paladins in the raid, the sheet used to put one on a tank and a druid or priest on the other — the mix rule that keeps two priests off the raid slots was keeping the second paladin off the second tank. A class can now stack on a job (Settings → Assignments, "Healer classes that stack on a job": Paladin on tank, by default), so every holy paladin heals a tank before any other class is asked; the mix rule still applies to the rest.

17 September 2026

Addon and uploader

• Uploader 1.12.2 — an updated uploader runs under its own name. After 1.12.0's first self-update the new copy kept the name it was downloaded under in Task Manager (vrt-uploader.new.exe) until the next logon, though the file had been renamed; now it starts itself again from the file's proper name and the copy it replaced is cleared away within the minute. A copy still running under the download name updates cleanly too.
• The bot answers Discord again; uploader 1.12.1 comes by itself. This evening /uploader got "the application did not respond": the hub was filing the addon's recipe reports — a few uploaders, every half minute — and read the guild's whole recipe ledger (3 MB by now) once per recipe name, 128 times per report, so the bot missed Discord's three-second window. The ledger is read once per report now. The reports were coming that often because a PC with two accounts holds a character's own reading on one and a copy heard over the guild channel on the other, and the uploader sent whichever it read second, turn and turn about, every look; 1.12.1 sends one reading per character — its own, else the newest. Nobody installs it: every 1.12.0 fetches it within the hour.
• Addon 0.10.8 — update it now: 0.10.6 and 0.10.7 came up with every tab empty. Not lost — your saved data was untouched — but the addon stopped loading half way: 0.10.6's specialisation read listened for an event under a name the Anniversary client does not know, the client refused it, and everything defined after that line (the guild's crafts, the packages, the bank and roster readers) never existed. The event is now asked for under a guard, with both its old and its modern name, and a new check in the build verifies every function and event the addon uses against the client's own list before a version can ship. Uploader 1.11.1 writes the inbox again when an addon update has replaced it with the empty file the addon ships — until now the wishlists, requests and standings went missing after every update until the site changed.
• Uploader 1.12.0 — the last one you install by hand: from now on it updates itself. Once an hour it asks the site whether a newer build is out; if so it fetches it beside itself, checks it against the published hash, starts it with the same settings and stops — the new copy takes the old file's name and its logon entry, so nothing changes for you, and the log says "updated to …". A download that fails or does not match its hash is not installed. Officers on an earlier uploader run /uploader once more; after that, never again.
• Addon 0.10.7 and uploader 1.11.0 — update both: the loot decision, in the loot council frame, and its reasons posted for the guild. The one moment every guild argues about is the minute after a drop, and until now the tool was not in the room for it. Now the RCLootCouncil voting frame has a VRT column: for each candidate their place on the standings and where this item sits on their own wishlist ("#3 · w1"), and a tooltip with the rest — Priority, rank, attendance, last item and when. The council sees the guild's own rules applied before anyone votes, and the decision comes out the same whoever is voting that night. The numbers come in with the uploader every couple of minutes, behind the same switch as the Priority on tooltips, so council members want the uploader on their PC. And the loop closes: every award the council sees is recorded — the candidates, what each said, the votes — the uploader carries it out, and the bot keeps one message per raid night in the channel you pick under Settings → Bot & site → Loot awards — a line per item, edited as the awards come in, never a post per drop: "Warglaive of Azzinoth → Ingy (Mainspec) — priority #1 of 3 (52.4), wishlist #1, attendance 96%, last item 12 Aug, votes 4/5 · over Natron #2, Zap #3". The rationale is public before anyone asks. Nothing is posted until you pick a channel; /vrt council in game says what your client has.
• Addon 0.10.6 — update it: the professions tab says who went which way, and the slots are a dropdown. Which specialisation a crafter took — Armorsmith or Weaponsmith and which Master, Dragonscale, Elemental or Tribal, Mooncloth, Shadoweave or Spellfire, Gnomish or Goblin, Elixir, Potion or Transmutation — is a passive spell in their spellbook, so each raider's addon reads it there at login and tells the guild the way it tells recipes; nobody has to say. A profession's list now opens with a Specialisations section — each way and who in the guild went it, class-coloured, a dot when online, right-click to whisper — a craft's tooltip names each crafter's specialisation beside them, a search for a name finds theirs, and /vrt specs prints the whole guild's. The site gets them too: the uploader carries them with the recipes, and the recipes page pins them at the top of each profession as it always did for ones typed by hand. And the row of slot buttons under the search is gone: one dropdown on the count line lists the slots the list has, a count beside each, the specialisations first — one click, one slot, and the list starts at the same height whatever the window's width.

The site

• Requests: one question, one column. A free-text request type — Hearts of Darkness — asked "what for" and then "for?", the same question twice, and the ledger put the piece in one column or the other depending on which box the raider had typed it into. It asks once now; the ledger has one What for column with the item on the left every time, in the item's own spelling, and a request from before that filled both boxes shows the second as a note beside it. A pick-list (the gem, and the item it goes into) and a bank list (the lines, and the reason) keep both.
• WoW: Forever profession bonuses, on one page. Every profession's bonus in World of Warcraft: Forever — Mining's Stamina, Herbalism's magic resistance, Enchanting's ring enchants, Alchemy's longer flasks, Tailoring's embroidery, the campsite objects each one crafts — profession by profession beside the Forever talent calculator, with how each is known (Blizzard said it, the beta shows it, or it was read off the demo and is provisional) and what it means on a raid night: the tank's profession, the caster's, the Onyxia bonus. Dated to the beta's first day and kept current as the datamining lands.

16 September 2026

Addon and uploader

• Addon 0.10.5 — update it: the consumables report stops lying. On the first raid night with the checklist it named fourteen raiders as missing elixirs who had them up. A buff carries the effect's name, not the item's — Mighty Agility, Fel Strength, Healing Power — so the report now matches elixirs on those words with or without "Elixir of" in front, counts Healing Power as the battle elixir it is (it was filed as guardian, so every healer read as missing their battle elixir), and knows Shattrath and Unstable flasks. The verdict shows what was recognised beside what is missing, and every buff a flagged raider carries goes to /vrt log, so a name it still does not know is one paste away from being added.
• The site's data reaches the addon through its own inbox now, every two minutes — and the uploader (1.10.0) never writes the game's saved file again. The wishlists and the bank's request queue used to be written into the addon's saved variables while the game was closed; this evening one such write landed in the middle of a /reload, the file came out unreadable and the game loaded nothing (the data was put back from the game's own backup). The uploader now writes a small Inbox.lua inside the addon's folder, a file the game reads at every /reload and never writes itself, and refreshes it whenever the site's answer changes, game open or not. A /reload takes it; nothing else can, that is the game. The Requests tab and the wishlist tooltip say when the inbox was written.
• Addon 0.10.4 — the profession window is left as you had it. Every update of the trade skill window re-expanded all its headers, which fires another update, so the list redrew under the mouse without end — a guildie could not scroll it with the addon on. A scan now remembers which headers were collapsed, expands, reads, and collapses them again, and ignores the update its own expanding causes.
• Addon 0.10.4 — update it: a Given press is unmistakable, and every officer in game sees it at once. And the button works at all now: since the Requests tab arrived in 0.10.0 its click looked for the request on the wrong frame and did nothing — no mark, no green, nothing for the uploader to carry. Pressing Given on the Requests tab turns the row green with who handed it out and when, turns the button into Undo, counts it in the header, and puts a line in the middle of the screen — the game's notice frame, never chat — so nobody presses it twice. The mark is told to the guild at once: every client running the addon keeps it and every officer's tab shows the row handed out, so the first of them to /reload or log out carries it to the site, or the new Send now button reloads on the spot. A press by somebody else cannot be undone from your tab.
• Addon 0.10.3 — update it: the status line opens on a click, not on hovering. The comms report behind the header's status line opened the moment the mouse crossed it, its frame covered the whole right of the header so the window could not be dragged there, and the report itself hid the window. Now it opens on a click on the text alone, sits above the header, and closes when the mouse leaves.
• Addon 0.10.2 — update it: the room picture keeps its shape in a wide window. The panel used to be the window's width and a fixed height, so a wide window showed a thin band off the top of the drawing and the rest was cut off. The panel is now as large as the drawing's own proportions allow — the window's width or half its height, whichever binds — centred, so the whole drawing is on screen and a wider window only makes it bigger. Zoom and drag work as before.
• The /uploader reply and the Settings page say what the uploader does now : after the loot history, gear, recipes and bank, that it brings the guild's wishlists and bank requests into the addon while the game is closed and carries a Given pressed in game back to the site.
• Addon 0.10.1 — update it: the raider's Priority on the wishlist line. Hover an item and each name under "Wishlisted by" carries that raider's Priority — Ingy #1 (52.4) — in Priority order, the order the council reads. A T6 class piece shows under its token and a crafted piece under its recipe too, naming what was wishlisted, since the token or the pattern is what drops; and an item already won no longer shows. The numbers travel with the wishlists through the uploader (1.9.0), so they go out only when the guild lets them: raiders may see the standings page anyway, or the new switch on Settings — which says plainly that anyone holding the guild's upload code can fetch them.
• Addon 0.10.0 — update it: who has it wishlisted, on every item's tooltip. For a rank that can promote, hovering any item — a drop in the loot window, a link in chat, a row on the professions tab — adds "Wishlisted by" with each raider's name and the rank the item holds on their list. The guild's wishlists reach the game the one way anything can: the uploader (1.7.0) writes them into the addon while the game is closed, so they are as of your last login, and the line says the date. /vrt wishlists says what is loaded. Also in 0.10.0: a status line in the window's header — the version, how many guildmates this client holds, when the guild was last asked, whether anything is waiting to send; hover it for the full comms report. A send preview: Send to raid now shows what goes out, to how many, and who in the group is known to have the addon, with a Send or Cancel. A resist-set reminder: on a boss where your job carries a (FR), (SR), (NR), (AR) or (FrR) tag, one line at the top of your list says how much of that set is on against the best you own — silent, in the window, never in chat. A consumables checklist: above your list, your own flask (or battle and guardian elixir), food and weapon oil, green or orange, read off your buffs the way the site's effort score reads them off the logs; on a Demon, Elixir of Demonslaying counts as the flask and the battle elixir. And for the raid leader or an assistant, /vrt consumes shows who in the raid is missing what, and /vrt consumes raid prints it to raid chat — the one thing the addon says in chat, and only because a leader typed it. The guild bank's requests, in game: a Requests tab, for a rank that can promote, lists everything waiting — who, which character, the lines with what the bank holds, what it is for — and a Given button; a hand-out marked there reaches the site after your next /reload or logout, through the same rules as the tracker's Given, in your character's name, and the row leaves the tab the next time the uploader brings the queue in. And a gentler guild sync — the game's own message throttle refused the first packages after login and they went round again; the addon now finds the pace the game allows and keeps to it — a refusal slows the pace, a long clean run speeds it up again — so the transfer settles instead of bouncing off the limit every few messages. And a login wave strands nobody: every ask is answered — a minute's asks together, once — where before a second ask within twenty seconds was dropped and that person waited half an hour; a package that only half arrived is asked for again within two minutes.
• Every guild member's resist gear counts. A character on nobody's roster entry but in the guild — a social, an unlinked alt — has their resistance gear filed under their own name now, the way recipes already were, instead of being turned away; it moves to the raider's entry the moment an officer links the alt. The uploader (1.6.1) says so instead of printing a "not on the roster" line for each of them.
• Addon 0.9.0 — update it: raid and boss buttons, and the professions tab knows what you have. The assignments tab has a row of buttons per raid, in the site's colours, and under it the bosses of that raid — one click instead of arrowing through the whole night. On the professions tab each material says how many you have (bags, and your bank once it has been opened) and how many the guild bank holds; a "usable by me" switch keeps to armour and weapons your class can use; right-click has "Ask in guild chat", which fills the chat line with the item and its crafters, says you have the mats when you do, and sends nothing until you press Enter. And the list no longer jumps about or dawdles while a search loads: every row draws with its icon at once, the order of a search holds still until the game has described every item in it, the addon remembers every item the game has described so the next session draws the list complete without asking, the first opening reads the rest of the catalogue in the background and steps aside while you are looking at a list, and the list stays where you scrolled it.
• Addon 0.8.4 — update it: crafters no longer vanish from the professions tab. In 0.8.3 the tab trusted a guild roster the game had refreshed with offline members hidden, so whenever someone logged in, every offline crafter dropped out of the tab — your own alts included — until the next full read. A roster is only kept when it lists everyone now, and your own characters are listed on their own account. Right-click on a row works again too: the crafters, one click whispers, and a "Link in chat" line — the old menu quietly did nothing on this client.
• Addon 0.8.3 — update it: the professions tab keeps to your guild, and the version shows. The tab lists a crafter only while they are in the guild you are standing in: someone who leaves drops out of it, an alt in another guild sees that guild's crafters and nobody else's, and what a client heard in one guild stays out of the other's tab. The minimap button's tooltip now says which version you run.

The site

• Only the guild's own loot addon counts. An officer's Gargul, running beside RCLootCouncil, had logged a year of awards of its own, and this evening the uploader carried them in: 1,096 awards, 649 of them to roster characters, every one counted as debt. The site now files only the loot system the guild runs (Settings → Loot system); another addon's file is answered with why and not stored, the uploader (1.9.2) says so once and leaves it alone, and the Gargul awards are out of the standings again. Which addons count is the guild's to choose now — Settings → Uploader, "Loot addons the uploader may send", tick boxes for the five the uploader reads; until something is ticked the list follows the Loot system setting.
• Uploader 1.9.2, the first run and the next one. A file it cannot read no longer stops the files after it; when you say yes to starting with Windows it goes to the background at once, so the window can be closed and nothing stops; and a newer download run by hand takes over the logon entry from the old file, stops the old copy and says it can be deleted.
• The uploader (1.9.1) no longer asks "which ones?" on the first run. Every loot addon file written in the last half-year is taken, each account kept apart on the site and a raid that is not the guild's left out there; a file untouched for six months is an old client's and is left alone. The first officers to install were stopped at that question and had to be told what to type.
• A guild-named uploader claims its guild again, and cannot take the hub down. The first officer to run one this evening got "paste the upload code" instead: the claim route hit an error on the hub's side, the hub restarted, and the uploader fell back to asking. The route is fixed, and every uploader route now answers an error instead of ending the process.
• The "Uploads need the code" tick on Settings works. It answered "unknown setting" since it was added — its field was filed under no file — and a test now checks every setting the page posts against what the server accepts.
• One address for the site. A page asked for under www.vortexraidtool.com is sent to vortexraidtool.com with a permanent redirect. Search Console had crawled four www copies of the talent calculators and filed four more as alternates of the canonical page; the proxy forwarded both names and the site answered both.
• The /uploader command answers again instead of breaking. Since the unsigned-file warning went into its reply earlier today, the command answered "Something broke" to everyone who typed it; the reply is fixed, and a test now runs the bot's simple commands through the real handler so a reply that breaks fails the suite instead of the first raider.
• Two of a one-handed weapon on a wishlist. A non-unique one-hander can be listed twice, the way non-unique rings always could — a hunter, rogue, warrior or shaman with two Blades of Infamy in mind lists both. On the site, in Discord with /wish add, and in the page's picker; a win crosses off one copy.
• The recipes page links the craft, not the scroll. Hover a recipe and the tooltip is the spell's — what it makes and what it costs — instead of the pattern's "teaches you". Same on every crafter list.
• The uploader says it is unsigned when it is handed to you. The bot's /uploader reply and the Settings page say the same thing: the file is not code-signed, so Windows SmartScreen will call it an unrecognized app the first time (More info → Run anyway) and an antivirus may hold it for a moment. That is the missing signature, not the file — its source is public, and every release is built there in the open.
• A page for raiders. Your guild runs the tool and you just joined: vortexraidtool.com/hub/raiders is the three things to do once — the addon from CurseForge, your profession windows, the Discord login — with what you get in game and on the site, the /vrt commands and the questions people ask. Officers link it instead of typing it; it is in the product bar, on the front page, on the addon page and on every guild's front door.
• The addon card on the front page is a real screenshot — the assignments tab with Shade of Akama's picture and the raid and boss buttons — instead of a mock-up.
• The addon is on every page now, sold on what it does by itself. The front page, the addon page, the guides, the talent calculators, the comparison pages, the trial and every guild's front door say what the free addon gives a guild with nothing else set up: a Professions tab — every craft, who in the guild can make it, what it needs — kept current by the guild itself. The addon page shows it, and the product bar calls the page what it is.
• Tidier for search engines. Every page has a description and a title under 65 characters, every picture a name, the front page one address, the demo's commands page no longer links a settings page it does not have, and the privacy policy says what the addon collects and how it reaches the site.

15 September 2026

Addon and uploader

• Addon 0.8.2 — highest skill first. Within a slot the crafts are ordered by the skill they are learned at, highest at the top, and each row shows that number; the name only breaks ties.
• Addon 0.8.1 — pick a slot. On the professions tab, the slots a profession has are buttons under the search: one click shows that slot alone — Cloak enchants, say — another shows the whole profession again. Names get more of the row.
• Addon 0.8.0 — update it: the professions tab. The window has two tabs now. Professions lists every craft of a profession by slot — head to trinket, weapons, enchants, then consumables and materials — with who in the guild can make it, a green dot when they are online, and what it needs, exactly as the crafter's own window says it. Search a recipe, a material or a crafter across every profession. Shift-click links the item; right-click whispers a crafter. /vrt who mongoose opens it searching.
• Addon 0.7.0 — update it: the guild keeps itself up to date. Your gear, your characters' recipes and a guild bank read are announced to the guild channel when they change, and a client asks the guild for what it lacks after login and every half hour — only the differences answer. Everyone with the addon holds the whole guild, so any uploader carries it to the site; no officer has to ask. /vrt sync asks now; /vrt share off keeps a character out of it.
• Addon 0.6.1 — update it: Enchanting recipes are read now. On this client Enchanting opens in the old Craft window, not the trade-skill window, and the addon only ever read the latter — so nobody's enchants reached the site. Open the Enchanting window once and they are in the next ask.
• Addon 0.6.0 — update it: recipes for every character of yours, asked of the guild. An officer types /vrt ask recipes and the whole guild answers — and each answer covers every character of the raider's in the guild, alts included, from the professions the addon has read on that account. So the alt you craft on no longer has to be in the raid, or even logged in: open its profession window once, and the next ask on any of your characters carries it. The raid ask (/vrt ask) stays what it was: resistance gear. Uploader 1.5.4 carries which character sent a package, and the site checks the two are the same raider.
• Addon 0.5.6 — update it: the Illidari Council and Mother Shahraz pictures are the new ones. The same two pictures the assignments page shows since today — the council with its ability column, Mother Shahraz as the guild had her: melee on Star, the tanks pixel-stacked in her cone, ranged and healers on Triangle. Nothing else changed in the addon.
• Addon 0.5.6 is the Release build on CurseForge. The CurseForge app installs and updates it by default now — nobody needs the site's zip unless they prefer it.

Site

• The Officers page has a Roster tab. Every main with class, role, rank, alts (in their own class colours), the in-game rank and level, Discord name and join date — and below it the two filing panels: every guild character on nobody's entry, and the log names that match nobody, each with a one-click "alt of…". The standings page is standings again, nothing above the table; the Roster page stays the guild's roster list.
• Officer sections open for officers who are already logged in. The menubar unlocked officer-only parts of a page the instant it loaded, before the rest of the page existed, so the roster panels, the loot council card and the import cards only ever appeared right after logging in on that page. They open on every page now.
• The Roster page shows the whole guild, for officers. Below the roster: every character the game's guild list has that is on nobody's entry — level, rank, last seen, the note, the main it points at — with a one-click "alt of…" beside each, and the log names that match nobody. All of them, not only the level-capped and recently online; names in class colours. This used to sit on the standings page only, and only opened with the officer passphrase; a Discord login as officer is enough now.
• Every guild member's recipes count. A character in the guild list the addon reads, but on nobody's roster entry yet, used to have its recipes refused. Now they are filed on the character's own name and listed with a "in the guild, not on the roster" tag, in the character's class colour. The moment an officer files the character as somebody's alt on the standings page, the recipes become that raider's.
• Names are spelled the way the game spells them. A main that was typed from a Discord name without its accents — Repent for Repènt — made the real character look like an alt of a phantom main. The site now takes the spelling from the guild list the addon reads (or from the logs), for mains and alts alike, and every list that names people follows. Nothing else about a raider changes.
• An alt's recipes wear the alt's colour. On the recipes page a crafter's name is in that character's own class colour, with the main's name after it, smaller, in the main's — a druid alt of a rogue reads as a druid, not as a rogue with a note. The alt's class comes from the guild list the addon reads.
• Try it on your own raid, no account. Paste a Raid-Helper event link on the front page (or at vortexraidtool.com/hub/try) and get that raid's assignment sheet — every Black Temple, Hyjal and Sunwell boss, your raiders' names, filled from class and spec — and the pull card the way the bot posts it. It reads Raid-Helper's public event data when you ask and stores nothing; a set-up guild's roster, standing rules and resist sets fill in the rows the trial leaves open. Three looks per Discord server every 30 days; opening the same event again is free.
• The Commands page lists everything now. The addon's own commands (/vrt), the roster tools (/roster reroll, /uploader, /edition, /support), /resist list, the roster page, and the endpoints the uploader and the addon use. The /prio command's description in Discord no longer says it is disabled for everyone.
• Titles that say what a page is. The front page, downloads, compare, talent calculators and the trial name the game and the job in their search titles; the downloads page tells search engines about the addon — free, on CurseForge, which version. The compare and guide pages link the trial.
• Talent calculators: the tooltip sits beside its talent, and the description panel keeps one height. The tooltip used to land far to the right of the talent you were on; the panel under the trees grew and shrank with every hover. The logo in the top bar goes to the hub, on the product pages and on a guild's pages alike.
• Talent calculators: the Classic texts read cleanly. Wowhead's own tooltip markup — Season of Discovery tuning notes, level-scaled numbers, spell-dependent phrases, line breaks — showed raw in some "Changed from Classic" lines on the Forever pages. Every talent of every class was swept; the Classic-era wording stays, the rest is gone, and the build keeps it that way.
• WoW: Forever talents, ready for the beta crowd. A page of every talent Forever adds, changes or drops compared with Classic, class by class, with the text of each new one (vortexraidtool.com/talents/forever/changes); each Forever class page says what changed for that class; the Forever calculator page answers the questions people ask — points, Legacy perks, the dates — and the pages carry their own link picture when shared. Titles name the game and the class the way people search for them.
• The uploader is handed out inside the tool, and every page says what the tool is. The loot master's uploader is no longer a plain download on the public downloads page: an officer gets a link made for the guild from the Settings page or with /uploader in Discord, as before. Every page now carries the line that Vortex Raid Tool is an independent fan-made tool, not affiliated with or endorsed by Blizzard, and every passphrase prompt says whose passphrase it is. Google's Safe Browsing had listed the site for "deceptive pages" without naming one; these are the plausible causes, removed.
• Marks of the Illidari: ask for one or two. The amount is yours to choose, up to the guild's limit — one if you only need one — and asking for more than the limit is refused with the limit, not quietly cut down. /mark request and /request new take amount:; the requests page caps the field.
• The addon comes from CurseForge, and only from there. The downloads page no longer offers the zip; every old download address on the site sends you to the CurseForge page. CurseForge checks every file before it goes up, and its app keeps a whole raid on the same version — that is where addons should come from.
• The Illidari Council's picture now has the ability list. The same column every other room picture carries — Gathios, Veras, Malande and Zerevor each with what to watch for, and the one health pool they share — on the layout the picture already had: the two zones, Gathios and Veras tanked together with the melee on Gathios, Malande at the top of the stairs for the kick rotation, Zerevor kited across the dais and up the ramp by the mage tank. The addon's copy of the picture follows with its next version.
• Mother Shahraz: the guild's original picture, rebuilt. The room as you walk in — the melee pixel-stacked on Star at the left statue, Mother directly to their right facing Triangle, the three tanks pixel-stacked between her and Triangle and alone in her cone (Saber Lash splits over them, one-shots anyone else, and one tank out of melee range is a wipe), the ranged and healers pixel-stacked on Triangle at the right statue, and the Fatal Attraction indicator: the linked three run apart left, right and down — with the ability column, Prismatic Aura included. The sheet and the pull cards show her picture again; they had been without one since 4 September.

14 September 2026

Addon and uploader

• Addon 0.5.5 — update it: Illidan's room pictures are the new ones. The four phases in order — the three stacks on the grate, the flames on their sides, the half moon when he lands, the demon form — the same pictures the assignments page shows. Nothing else changed in the addon; a raid where someone is on 0.5.4 is a raid where that person still sees last week's Illidan. CurseForge's app fetches only the changed files.

Site

• Illidan: new pictures, and one set of marks for the whole fight. Ranged and healers go to three stacks on the grate in phase 1 — Triangle, Square, Star — and keep them: the same stacks in phase 2 while each Flame of Azzinoth is walked up and down its own side; when he lands for phase 3 everyone spreads in a half moon on the far side, each group straight out from its grate spot, 5 yards apart for Agonizing Flames, and stays there through the demon form, where only the warlock tank steps in. The melee stand at his rear, where the parasites are dropped and cleaved, and the tank walks him along the platform's edge on Flame Crash. Four pictures now, one per phase; the sheet has one ranged-stacks section for every phase instead of three, and the mages' shadowfiend team is gone.
• The front page's own backdrop. Illidan on the left, the Forever paladin with the lit hammer on the right, each game's logo at the foot of its half — one picture, so nothing drifts with the size of the window; a phone held upright gets the same two stacked.
• New looks, one per game. TBC pages wear Illidan's Temple: the same violet, with Blizzard's Burning Crusade key art — Illidan, glaives out — behind the page. Forever pages sit behind glass: Blizzard's Forever key art with frosted, see-through panels over it. The content column rests on a translucent block so tables read over the art; on a phone the art stays put while the page scrolls over it. Every hub page carries one bar — the hub, Guides, Talent calculators, Downloads, and "← Back to your guild" when you came from one.
• Assignments: the last raid's sheet stays up until the next comp is ready. No comp posted yet, or one too small for a sheet, and the page shows the previous raid's assignments, read-only, with the reason on top — it swaps to tonight's the moment the comp is ready. And a 25-man sheet no longer fills itself from ten or fewer signups; a comp counts once it has eleven (Forever's 10-mans count as they are).
• The games' own logos wherever a page names or picks a game. The talent calculators' game switch and pills, the front page's button and Forever banner, the edition pills in a guild's menubar, the guild's home page, the guides' Forever section — Blizzard's Burning Crusade Classic Anniversary and World of Warcraft: Forever marks, from Blizzard's own servers.
• Talent calculators, for both games, free — vortexraidtool.com/talents. Every class for TBC Anniversary (61 points, nine rows) and for WoW: Forever (51 points — the reworked trees Blizzard showed at BlizzCon, not Classic Era's). Each tree on its own art, the class icons on the class picker. Click a talent for a point, right-click to take one back, the rows open at five points a row and prerequisites hold as in the game; the link in the address bar is the build — Copy link and send it. Hover or tap a talent for its text at every rank — 3/5 Anticipation shows rank 3's numbers; on Forever, a rank nobody has seen in the game yet says so, and each talent says whether it is new, changed or moved from Classic. No login. On Forever, the Legacy perks sit under every class's trees and on their own page — three account-wide trees with the medallions the demo showed, one point per challenge, 16 spendable per character at launch, 65 earnable, every rank's numbers — in the same share link. The big button on the front page, a Talents item in every guild's menubar and a card on the guild's home page take you there, to your own game. TBC layouts after the wowsims project, texts from Wowhead; Forever from Wowhead's Forever calculator (every rank) and talentsforever.com (CC BY 4.0), both of which follow the beta.
• Roster page: the officer button reads right on every row. The first raider showed Remove and everyone after it showed Restore, whatever their state — a rendering slip, nobody was moved. Active raiders show Remove; former members show Restore.

13 September 2026

Addon and uploader

• Addon 0.5.4 — update it: the addon reads the guild roster, and every read says which game it came from. Every character in the guild as the game lists it — rank, level, class, the notes, how long since it was online — is written down when the roster arrives after login and then at most once in ten minutes; /vrt guild asks for a fresh one. The uploader (1.5.3, it updates itself) carries it to the site. Nothing is said in chat, nothing goes to other players — the guildmaster's read is enough. Every read now carries the client it came from (2.5.x on the Anniversary realms, the 1.x line on Forever) and the realm: a guild running two editions has both clients on one PC, and the uploader sends each read to the edition that plays that game — while every site refuses a read from the wrong game or realm rather than overwrite its own roster or bank.
• Officers: "In the guild, not on the roster." A new panel on the Standings page lists the characters the game knows and the site does not, each with the main its note points at ("Cyllosis bank", "alt of Nimue") — one click files it as that main's alt, or one click files all of them. Characters below the level cap or offline for two months are folded away. Nobody is put into the standings from here: a character that is not somebody's alt waits until it turns up in a log. Where a main's in-game rank differs from the roster's, the panel shows both and lets you adopt the game's.

Site

• A Roster page, for the guild. Who raids with the guild — every main with class, role, rank, alts, when they joined and what they raided as before a re-roll, the game's own rank and level beside it once the addon has read the guild list, and a class bar at the top. Members see it after logging in (a setting decides who); officers also see Discord names and the former members, and can Remove a raider — which marks them inactive so their nights and loot stay in the books — or bring one back. Someone removed also disappears from the Recipes lists and /recipe who, and from the resist-set holders (their records stay, and come back with a restore). It is in the menu next to Recipes, and open to anyone on both demos.
• The demo guild now plays two games. Next to the TBC demo there is a Forever one — the same made-up raiders, five of them re-rolled for the new game, raiding Barrow Deeps at 10, Hyjal Summit at 20 and Onyxia at 40, the bank handing out flasks and enchanting materials — in Forever's colours, with the Anniversary · Forever switch in the menubar of both. Nothing on it can be changed, as before.
• A raider re-rolled? One action. /roster reroll main:<who> to:<new character> in Discord, or ↻ Re-rolled on the Settings roster: the new character becomes their main, the old one stays on the entry as an alt — so every night and every drop under the old name still counts for the same person — the class follows the new character (from the guild list or the logs, or you say it), and the assignment preferences and any waiting request follow along. The roster remembers the names a person has raided under. Built for the week everyone hits the cap on Forever.
• One subscription for the whole Discord server. A guild running two editions pays once: the plan lives with the first edition and every other edition mirrors it, and removing one edition never cancels the subscription while another is still running. Each edition keeps its own Discord roles — "Anniversary member" and "Forever member" can be two roles with their own channels, set in each edition's Settings.
• Assignments: the picker no longer runs off the bottom of the screen, an Innervate can only go to someone with mana, and the label column takes only the room it needs. The officers' dropdown on a long list (thirty raiders for an innervate) used to open below the fold and close itself the moment you tried to scroll it; it now opens upward when there is more room above, sizes itself to the screen and scrolls inside. Warriors and rogues are gone from the Innervate and Power Infusion target lists — a template can name the receiving classes itself with targetClasses. And a card's left column is now as wide as its widest label instead of always half the card — the misdirects' "1" and "2" no longer push the names into a cramped right half.
• The demo guild's Requests page opens for anyone. It used to ask for a login it could never give. It now shows the officers' view straight away — every request type, a queue and a log: gems for a new chest with the bank's count on each line, a bank list for an enchant, marks, a heart for a pattern, one hand-out given short with the officer's note. Nothing there can be changed, as before.
• Coming to WoW: Forever. Vortex Raid Tool will be ready for World of Warcraft: Forever on launch day, 4 November — roster, recipes, guild bank requests and Discord from the first login; assignment sheets and loot priority when the raids open on 9 December. The front page says so, in Forever's own colours, and a new card there shows the crafter registry the way the Recipes page does.
• One guild, two games — side by side. A guild can now run TBC Anniversary and World of Warcraft: Forever at the same time: a second site and bot setup for the same Discord server, with its own roster, ledgers, pages and colours. Every page gets a switch between the editions ("Anniversary · Forever") that keeps you logged in, and a guildmaster says which edition answers Discord commands — everywhere with /edition primary, or per channel with /edition here. Add one from the hub's servers page ("+ Forever edition"); the form is filled in from the guild you already have. Nothing changes for a guild on one game.
• Settings knows which game the guild plays. A new Game field (TBC Anniversary today; World of Warcraft: Forever from 4 November) sets which raids count as raid nights, the raid sizes, what the guild bank offers as request types and which Wowhead database the item links use. Every guild is on TBC Anniversary and nothing changes for them; a guild set up for Forever starts with the three December raids, a bar for "our raid" that fits 10-, 20- and 40-player logs, flasks and enchanting materials instead of gems and marks, and vanilla's consumables in the Effort score. Setting up a new guild asks the game.
• The site can wear a second set of colours. Every page takes its colours from one table now, so a guild playing Forever gets a look drawn from the game's own palette while a guild on TBC Anniversary sees exactly what it saw before — nothing changed on screen today.

12 September 2026

In game

• Addon 0.5.2 — update it: the addon no longer writes in chat. The bank read, the gear and recipe sync, an old-version notice — all of it used to land in the chat frame, and raiders hate an addon that talks. Now the addon keeps a log instead: /vrt log opens it (the last 150 lines, kept across a /reload and a logout), /vrt bank, /vrt gear and /vrt comms open their page without an echo in chat, and /vrt on its own lists the commands on a page. The one thing still said in chat is the one worth hearing: the raid leader sent the assignments, or changed a row. Typed commands still get their one-line answer.
• Addon 0.5.1 — update it: the guild bank read now works on the Anniversary client. 0.5.0 listened for the bank the way older clients announce it, and the engine the Anniversary realms run on says it another way — so a visit to the bank was never noticed, and nothing was written for the uploader to carry. Both ways are heard now. /vrt bank says what the reader knows: the last read (when, by whom, how many items and tabs), whether the bank is open, and what it has been doing — and reads again if the bank is open. On CurseForge and at vortexraidtool.com/downloads.
• Uploader 1.5.1 updates itself; a scan the bot says no to is offered once. A character the addon read who is not on the roster (a bank alt, a friend's character on the same PC) was offered again at every look — four times a minute for as long as the uploader ran. Now once, until the addon has a newer scan or the uploader starts again; a raider added to the roster is filed at the next start. And one look finishes before the next begins, so a logout with twenty-five raiders' scans is filed once, not twice. The installed uploader updates itself on its next run.

Site

• The site on a phone, and the officers' log in any browser. No page scrolls sideways any more: a table wider than the screen scrolls in its own box, the menubar and the standings' formula wrap, the rules page stops rendering zoomed out. The Requests page's "Who got what, when" had a column that could shrink to one letter a line once the undo button was added — on a phone, and in a Firefox window that was not wide — it now sizes by content, and on a phone it becomes a list of labelled cards; the officer's per-line grid folds each line's note under its numbers.
• Undo from the log, and a form that stays put. Every row of the officers' "Who got what, when" has an undo: a request goes back to waiting with nothing given, a walk-up disappears from the log. The page used to refresh itself every 25 seconds and wipe whatever an officer was halfway through typing — picking the item from the suggestions was often the moment it landed; it now waits while a form has anything in it. And an officer on the roster gets their own Your requests card under the officer cards, so asking for gems for yourself is a request, not a walk-up that hands them out at once.
• No request without saying what it is for. Every request type that has a "for" asks for it and refuses a request without one — the gems' piece, the bank mats' enchant or flask batch. The guild bank asks now too; a guild that would rather not can untick "For?" on the type.
• Several requests open at once. A raider may have more than one request of a type waiting — the chest's gems and the gloves' gem, a bank list on Wednesday and another on Sunday — and cancel whichever one they mean. Marks of the Illidari stay once per lockout, as before. A guild that wants a type back to one-at-a-time has a switch for it (Settings → Request types → "One at a time"). Officers confirm each request on its own; /request given in Discord serves a raider's oldest one first and says how many more are waiting.
• The home page's list is in the menubar's order. The raid's pages first (Assignments, Wishlist, Recipes, Requests, Logs, Loot History), then the reading (Commands, Guides, Rules), then what a login unlocks — the same order the bar teaches, so a page is where you learned to look.
• The menubar is centred — properly this time. The middle group is centred on the page, not in whatever the two side groups left over. On a laptop window or a tablet the outer groups share the first row and the raid's pages take a centred row of their own; on a phone every group has its own centred row and a group that does not fit wraps instead of running off the edge.
• Several gems in one request — a three-socket chest is one ask, not three. The Epic gems type is a list now: a line per gem, any of the six, how many of each, and what they go into; the menu shows how many of each the bank holds. An officer confirms it line by line like a bank request — gives fewer, declines one, adds a note — and the raider sees given against asked. In Discord, /request new type:gems what:2 Crimson Spinel, 1 Lionseye for:Cataclysm Chestpiece — the autocomplete completes the gem you are typing and keeps the ones before it. Requests filed before the change are confirmed the same way. Any request type with a fixed list can be a list of them now (Settings → Request types: the "open — a list of items" period with choices filled in).
• A character the game spells with an accent is the roster's plain one, everywhere. Íngy and Repènt are Ingy and Repent on the roster. The standings always folded the accents away, but the addon's gear and recipe reports, the officers' Attendance tab, the check that decides whether a raid was ours, and the uploader's guild finder compared the letters as written — so those two raiders were "not on the roster" to the uploader and absent from every week on the Attendance tab. All of them fold the accents away now, and the Attendance rows are right.

11 September 2026

Loot pricing

• A pattern taken offspec is free, whatever it makes. The guild gains a crafter either way, which is the point of the drop. Only a pattern for a piece that binds on pickup, taken for mainspec, prices like an item — minor, 6 points.
• Crafted bracers, gloves and rings are BoE, so their patterns are free — past charges refunded. The list of binds-on-pickup crafts was checked against the game item by item: every crafted bracer, glove and ring of this tier binds when equipped, and only the shoulders, chests and necks bind on pickup. Sixteen names were wrong. Anyone charged for a bracer, glove or ring pattern has the points back.
• The crafted boots and mantles bind on pickup, so their patterns now cost — past wins included. Boots of Blasting, of the Long Road, of Natural Grace, of Utter Darkness, of the Crimson Hawk, of the Protector, Hurricane Boots, Red Havoc Boots, Swiftheal Mantle and Mantle of Nimble Thought were missing from the list and had been free. Taken for mainspec they are 6 points, and standings recompute from the whole history, so this reaches wins already handed out.
• An award logged twice after a reload counts once. RCLootCouncil sometimes has to be reloaded mid-award and logs it again a few seconds later. The same raider winning the same item within thirty seconds is one drop. Not for anything disenchanted or banked — the banker really does receive every copy nobody wanted. Sixteen past awards corrected, 57 points given back across ten raiders.

In game

• Only our own raids enter the loot history. A raider who also raids elsewhere has one RCLootCouncil history holding both guilds' awards, and it all used to arrive. Now a night counts only if it was ours: five or more guild members in the Warcraft Logs report of that night, or — with no log — five or more distinct guild members among the night's awards. Anything else stays out, whole, of the loot history and the standings; the build log says which nights and why. The number is on Settings → Scoring ("Guild members awarded on a night, at least"; 0 keeps everything). Judged when the files are read, so a raider added to the roster later brings their nights in without a re-upload. Vortex's own history: nothing changed, all 35 nights are ours.
• /uploader in Discord — a download that already knows your guild. Anyone on the roster runs it and gets a private link to vrt-uploader-<guild>-<id>.exe; the file reads its own name on the first run and sets itself up — nothing to paste, no roster match needed. The link lasts 14 days and is as good as the code, so it is yours alone; a new upload code voids every link.
• The uploader needs no code any more. Run it, and on the first run it reads the names in your loot history and asks the hub which guild those raiders belong to — the guild whose roster they clearly fit (three names or more, and clearly more than any other guild's). It files under that guild from then on; if no guild fits, or two do, nothing is uploaded and it asks for the guild's code instead. Uploader 1.5.0.
• The uploader is for any raider, not only the loot master. RCLootCouncil sends every award to everyone in the raid, so any raider's history file fills the same ledger; and whoever opens the guild bank or a profession window with the addon on is the one whose uploader has that to send. So: any raider installs it, runs it once, done — more PCs, more complete. A guild that would rather every upload carried its code switches that on in Settings → Uploader (Uploads need the code); the code is also the way in for a brand-new guild with an empty roster, or a raider in two guilds here.
• Addon 0.5.0 reads the guild bank. Open it and the addon reads every tab it may see and hands the snapshot to the uploader; nothing is said in chat but one line when the read completes. Uploader 1.3.0 carries it (the installed one updates itself on the next run — or take it from Downloads). On CurseForge and at vortexraidtool.com/downloads.
• Update the addon to 0.4.1 — every /vrt ask was throwing an error. Version, gear and recipes alike, since 0.3.0. The small update is enough; the pictures have not changed.

Requests

• Officers are told when a bank request comes in. Settings → Request types → "Officers are told in" picks a channel; the bot posts one line there — who, the lines, the note, a link to the page — for every type with "Tell officers" ticked (the Guild bank has it on; marks and the like are off, so the channel is not flooded).
• The request table knows what the bank holds. Open the guild bank in game with addon 0.5.0 on, on the PC that runs the uploader, and the site gets a snapshot — every tab, every item, the gold. From then on each line of a bank request says "in bank 14" beside "asked 5", the Give box starts at what the bank has when that is less, and raiders typing a line get the bank's own items suggested with their counts. The Requests page says when it was last read and by whom.
• Guild bank requests: several items in one, confirmed line by line. A new request type, ＋ Guild bank on Settings → Request types: a raider lists what they want from the bank and how many of each — enchanting mats, gems, flasks, up to twelve lines — on the Requests page or with /request new type:Guild bank what:5 Large Prismatic Shard, 2 Void Crystal. An officer goes through it line by line: gives what was asked, fewer ("only had 2"), or declines a line, with a note the raider sees; decline all answers a request the bank cannot fill instead of leaving it hanging. The raider's page shows given against asked; the ledger counts what was given.

Officers

• An Attendance tab on the officer page — all-time, and per phase. Every 25-man raid week the guild has logged since its first, and each raider's weeks of it: total, then P1 Gruul / Magtheridon, P2 SSC / TK, P3 BT / Hyjal, P4 Sunwell when it comes (Zul'Aman is 3.5 and a 10-man, so it never appears). Counted in lockouts, not nights — a raid week counts once however many groups or nights it took, and a raider in any of that week's logs was there — because in P2 the guild often ran two groups, and per-night counting would have called half the raid absent every week. A nights column beside it, a first and last night, so who has been with the guild the longest is a column rather than a memory. Alts count for their main; inactive members stay listed; a raider who signed up and was benched gets a small +1b beside the count on the nights the signups cover — not added to it, since the table is who was in the raid. It is a record, not a score: the standings keep their own window and their own rules, untouched. The nightly pull now keeps every report the guild ever logged for this (asked for by an officer).

Hub

• Stuck on the setup? Let us do it for you. /support allow in your Discord (server admins and delegates), or Allow support access under your guild on vortexraidtool.com/hub/servers: for a week, the person running Vortex Raid Tool can open your guild's site as guildmaster and set it up or fix it with you. Nothing happens unless you click it, the page shows every time it was used, and Revoke ends it on the spot. The privacy policy says the same.

Downloads

• The addon is one download, and it is the CurseForge file. vortexraidtool.com/downloads now sends you to CurseForge first — the app installs it and keeps the whole raid on the same version — and offers the same file beside it, byte for byte, for anyone not using the app. There is no longer a separate "update without the pictures": one file, named for its version, and the old links land on it.

Site

• The menubar centres on a phone. On a narrow screen the three groups of the menu each take a row of their own, centred, instead of the second row sitting against the left edge.

Scoring

• An alt in the same night's log is no longer a second night at 0%. An alt parked in the raid for some trash, with a buff up and never at a boss, was being read as present for every kill and using nothing — and it counted as its owner's night alongside the real one, pulling the effort score down. A name that was in no kill is not scored, and a raider has one effort record a night: their own character's when it is in the log, else the alt they raided on. Every past night has been re-read with that rule.

10 September 2026

Update the addon before the next raid

• Download the addon again, and delete your old VortexRaidTool_Pictures folder. vortexraidtool.com/downloads — take the whole thing, not the small update. It is one folder now, with the room pictures inside it, so there is nothing second to copy. Delete the old VortexRaidTool_Pictures folder or the game keeps drawing the diagrams that were in it — including the Azgalor below.
• Azgalor: Star, Triangle and Square are ranged camps, and every melee stacks on one mark behind him. It used to split the melee across two of the marks and crowd every ranged onto the third. The camps are filled the same way as the rest of Hyjal, so a party group keeps its totems together. The room picture says the same thing now. Anyone still on an old copy is looking at the old drawing.

In game

• It stopped talking in your chat. Gear and recipes arrive all night, on every client, and none of it was worth a line of anybody's chat — several of you asked what "sent gear" even was. Nothing about it is printed any more. Whoever asks gets a window once the answers are in; everybody else hears nothing.
• Resistance gear stopped going missing. Anyone with a bank full of it was the one whose set arrived half-sent, because everyone answered at the same moment and what gets lost is whoever had the most to send. The raid spreads its answers out now, and a whole raid of them can be put back together at once.
• Your recipes keep themselves, alongside the gear. They travel together, so the guild's crafter list stays current without anyone being asked for it — and on a night when nobody learned anything it costs nothing to check.

Everywhere

• The addon is on CurseForge. curseforge.com/wow/addons/vortex-raid-tool — install it with the CurseForge app and it updates itself, which is the real fix for a raid where one person is still on last week's copy.
• Downloads have a page of their own. vortexraidtool.com/downloads has the addon with the room pictures, the small update for people who already have it, and the loot master's uploader, with where to put each one.

9 September 2026

In game

• The assignments now run inside the game. A free addon shows your own lines for the boss you are on, or the whole raid, with the room picture beside them and every name in its class colour. The download is on the assignments page and the pictures are in it.
• Your raid leader hands the sheet to everyone. One officer sends it to the raid and nobody else copies anything. A row changed at the pull reaches the raid the moment it is decided, marked as changed, and can be put back.
• Resistance sets fill themselves in. The addon reads what you actually own off your own gear, counting gems and enchants, and it reaches the site without anyone typing a number. Open your bank once and what is in there counts from then on, wherever you are.
• So do known recipes. Open a profession window and the guild's recipe list keeps itself; an officer can ask the whole guild for everyone's with one command.
• A minimap button opens it, and one command tells you who in the raid is running which version.
• Get the addon here: https://vortexraidtool.com/downloads/VortexRaidTool.zip — 28 MB with the room pictures inside. Extract both folders into World of Warcraft/_anniversary_/Interface/AddOns, then restart the game.

Requests

• A request made after the week's last raid counts toward the next lockout. Once the last raid of a lockout has started there is no raid left to hand anything over in, so the request used to sit in a queue that emptied at the Wednesday reset with nobody served. It now waits in the lockout where it can actually be given out, and the Requests page says that is what it is doing. Which night counts as the last raid comes from your raid days on the Check-in settings, and a guildmaster can switch the whole thing off next to the reset hour.
• Nothing still waiting disappears when the week rolls over. Whatever was left unserved in the lockout that ended stays in the officer's queue, marked as asked for the week before, until it is handed over. A raider who is still waiting cannot ask a second time for the same hand-out.
• A hand-out counts in the lockout it was given in. Ticking one off records it in the week the marks left the bank, so marks given on the Monday after the raid are that reset's rather than the ending one's. Undoing a tick puts the request back exactly where it was.

8 September 2026

Assignments

• Every sheet row carries the diagram's raid mark. Wherever a picture puts a group on Star, Triangle, Square, Circle, Diamond or Moon, the sheet's row starts with that mark: Kaz'rogal's ranged groups, Gurtogg's soak groups, Brutallus's sides, Felmyst's three camps, Sacrolash's ramp stack, M'uru phase 1, Mother Shahraz's stacks, Illidan phase 1, Azgalor's melee groups, Shade of Akama's sides.
• Kalecgos portal groups are built by rule. Four groups on the marks, five people at most, one or two healers and a druid or mage in each; a decurse slot per group, filled from inside it. When the roster cannot give every group a healer and a decurser the sheet builds three larger groups instead and says why. Short of decursers, a resto druid heals a portal group rather than the tank. The Sathrovarr tanks take portals 1+3 and 2+4.
• Archimonde stacks follow the tank healers. H1's party group stands on Square, H2's on Star, the rest on Triangle; the tank healers stand with the tank, not in a stack. Square's and Star's decurser may be that healer, Triangle's never; the tank's decurser is a resto druid, else a mage, and never from Triangle. The group swap makes sure every stack has a decurser.
• M'uru phase 2 and Kil'jaeden number every spot. R1… for the ranged, H1… for the healers, on the diagram and on the sheet, one raider per number; Kil'jaeden's H1 and H2 are the tank healers at the Sunwell.
• The sheet refreshes every minute for everyone , officers' drafts included, on top of the live stream.
• Officers can open the draft to raiders by hand with /assign announce:true, or hide it again with announce:false.

Room diagrams

• 27 new diagrams , drawn by our own studio on raidplan.io's maps, replace the third-party pictures (the council's stay). Corrections from the raid leader on Illidan phase 1, 2 and 4, Teron, Kaz'rogal, Gurtogg, Kalecgos, Felmyst's breath lanes, the Eredar Twins, M'uru and Kil'jaeden.
• Guides opened from a guild's site keep a way back to that guild (or to the demo).

Nightly digest

• The digest's channel and contents are settings. Settings → Bot & site: pick the channel from the server's list and switch each block on or off — loot recorded, top parses of the night, movers, top 5, new faces in the log, warnings. /wishadmin digest on now takes an optional channel.
• Top parses of the night : the three best kill parses of the last raid, dps for dps and tanks, hps for healers.

Scoring

• Performance statistic : median (as before) or mean over the window's kill parses — Settings → Scoring. Wipes never count; Warcraft Logs ranks kills only.

Recipes

• A craft added from a "Schematic: …" / "Pattern: …" post now files under the craft and links the crafted item, not the scroll; older records were corrected.

Site

• Front page: the demo guild is the first thing to click, right under the headline; the top bar stays put while scrolling.
• The demo guild's menubar has a "Back to hub" tab.
• The menubar is in three zones: Home and the reading (Commands · Guides · Rules) on the left, the raid's pages (Assignments · Wishlist · Recipes · Requests · Logs · Loot History) in the middle, the logged-in pages on the right.
• The Commands page lists every slash command, including /recipe remove, /mark, /assign announce, /attendance list, /resist update … player: and /delegate.
• /help opens with the help Discord's invite.

Product

• Logo : the silver V on the violet vortex — favicon, hub pages, social card, the help server, the bot's avatar.
• Public demo guild at /demo/: made-up raiders, real pages, refreshed once its raid night passes.
• Comparison pages (/hub/compare): coming from ThatsMyBis, wowaudit or a spreadsheet.
• Pull cards, check-ins, printable sheets and guild pages carry a quiet "made with" line.
• Help Discord : a Subscriber role that follows the paid plans (the admins and delegates of a guild on Pro get it, and lose it when the plan lapses) and a subscribers-only channel; a Team category with the team's chat and the moderators' alerts.

7 September 2026

• Recipes : who can craft what, by profession — every craft of every profession in the pickers, specialisations pinned on top, a guild's recipe sheet importable, recipe claims in chat (the bot asks, a ✅ files), inactive members stay on the list.
• Requests : marks, Hearts of Darkness, epic gems and more in one ledger — request types with lockouts, amounts, a "For?" note, item lookups with Wowhead links, real gem icons; a members' page for their own requests.
• Assignments follow Raid-Helper's Announce : raiders see the sheet once the comp is announced, officers see the draft; the sheet says when it opens; live updates patch the page in place.
• Hub : /delegate hands setup, billing and settings to a member; a guide for members who are not the server admin; the help Discord link on the pages, in /help and in the bot's notices; setup lands on the new site logged in with a first-steps card.
• Loot : a shared RCLootCouncil id is one drop re-awarded and counts once; two awards in one second no longer collapse; the uploader (1.1.0) reads Gargul, CEPGP, MonolithDKP and CommunityDKP too.
• Standings and pages : class colours on names everywhere, item icons and rarity colours on the loot history, an editable signup cross-check for officers, hub logs on disk with crash context.