See who actually shows up, and whether loot is fair.
Attendance comes from real raid voice check-ins, left-early flags, and the raid lead's overrides, not a list of who said they would come. Post the Warcraft Logs link afterwards and he reads the fights as well, then shows you the names the two readings disagree about. Up and no-show rates per member and per raid, plus loot history that says whether it is always the same three players.
Who keeps no-showing, answered by a feeling.
Most guilds run attendance on memory and a hunch. Someone thinks the Ret has been flaky. Someone else swears the Resto Druid has won three trinkets while the Hunter has had nothing all tier. Nobody has the numbers, so the officer call goes in circles and the loot argument never settles.
Hootus keeps the receipts. Show-up rates come from real check-ins, loot comes in from the Gargul log your raid already keeps, and both sit where any officer can open them instead of in one officer's memory.
- I feel like the Ret has missed a lot lately.
- Has the Druid not won every trinket this tier?
- Who actually showed last Tuesday? Anyone remember?
- Did they leave before Prince, or was that the week before?
- We keep benching the same guy and nobody is tracking it.
Signups say they are coming. Voice says they showed.
Join the raid voice channel and Hootus checks you in, with the timestamp to prove it. The rest of the tier adds itself up from there.
- FjorvaltProtection Warriorjoined raid voice · 19:58Present
- BrightleafRestoration Druidjoined raid voice · 20:01Present
- ArrowsongMarksmanship Hunterjoined raid voice · 20:03Present
- MournhowlFeral Combat Druidleft before Prince · 21:30Left early
- SkarnCombat Roguemarked by the raid leadNo-show
He reads who joined raid voice, not your combat log. That is why the override is there, and why the lead sees the report before anyone else does.
- The mark starts from something realRaid voice, with a timestamp. Not a reaction, not a name on a list, not what anybody remembers on Thursday.
- Left early is its own thingA raider who stayed for the whole clear never gets lumped in with one who ghosted before the last pull.
- The lead has the last wordComms off, alt account, a call that needs a human eye. Any mark is editable, and the report waits for a confirm.
From a voice check-in to a number you trust.
Not your combat log, not your DPS. Just who was in the raid, when, and whether they stayed.
- On arrival
Voice check-in does the roll call
Hit the raid voice channel and Hootus checks you in with the time. Nobody counts reactions, nobody scrolls back through who swore they would be there.
- Mid-raid
Slipping out gets flagged
Leave before the last boss and he notes it. Showing up for the trash and vanishing before the kill reads differently, and the report keeps that difference.
- Any time
The raid lead overrides anything
Voice is the starting point, not the verdict. The alt-runner and the raider with comms off get fixed by hand, and the post-raid report waits for a confirm before it lands.
- Over the tier
It totals itself up
Up and no-show rates per member and per raid, plus bench rotation, so who has been sitting is a number instead of a feeling.
Voice proves they were in the room. The log proves they were in the pull.
Name a raid-log channel in Settings, Channels and Hootus reads every Warcraft Logs link dropped in it. Leave it unset and he never looks. What comes back is a second reading of who raided, taken from actual fight participation, and the interesting part is the handful of names where the two disagree.
- Fjorvalt
- Brightleaf
- Arrowsong
- Skarn
- Fjorvalt
- Brightleaf
- Arrowsong
- Vaelis
- VaelisIn the fights, never creditedMark presentLeave it
- SkarnCredited, in no fightMark absentLeave it
Bosses that died come out of the same report and feed guild progression, so the tier sheet keeps itself while the attendance argument gets settled.
- He works out the raid, or he asksA report carries a start time and a boss list, so most of them land on the right night by themselves. When two raids both fit, he stops and puts the choice in a dropdown. Guessing would file Tuesday under Thursday.
- Nobody types a commandIn the log channel the link is the whole interaction. He reacts to say he has taken it and only speaks up when something needs you: a private report, one already sitting on another raid, a night he cannot pin down. Run /raid log instead and he answers in full.
- The disagreements land on an officerTwo lists come out of it, and each row is a fix or a shrug: correct the attendance, or dismiss it and it stops asking. Anyone with the raid attendance permission can settle them from the raid page.
A log is better evidence than voice. It is still evidence.
The limits, said plainly, because an attendance number nobody trusts is worse than no number at all.
- No log, no second reading. Somebody has to upload the report and leave it readable. A private one gets a padlock and a note asking for it unlisted, and that is as far as he gets.
- He matches on names. Log names get lined up against your characters, so one he does not know goes into a list of its own instead of quietly counting as somebody.
- A pickup run is not your raid. Every report is weighed on how much of it was actually yours before the kills count for the guild. Five of your raiders and half the group, out of the box, and both numbers move in Settings, Raid automation.
- Credited with no fight is a question. A log that stopped recording early looks exactly like a raider who went home early. That row waits for a human and never marks anyone absent on its own.
Four things, and none of them is a spreadsheet.
Attendance stays cheap to keep because nobody has to keep it.
- Check-in from raid voice
- AutoCheck-in from raid voice
- Reactions to count
- 0Reactions to count
- Mark the lead can override
- AnyMark the lead can override
- Rates it keeps, up and no-show
- 2Rates it keeps, up and no-show
So it is not always the same three players.
Loot history shows who won what across the tier, and the fairness read tells you whether the drops spread around or piled onto a handful of mains. The Hunter who has not seen an upgrade in a month stops being a guess and starts being a line you can point at.
Items won line up against raids attended, which is the comparison officers actually argue about. Now the evidence is on the table when they do.
- Fjorvaltlast win 6 days ago4 items
- Mournhowllast win 20 days ago2 items
- Brightleaflast win 13 days ago3 items
- Pyreclawlast win 34 days ago1 item
- Arrowsongnothing this tier0 items
Built from the loot log your master looter already kept in raid, not from a spreadsheet somebody fills in on Wednesday.
Your master looter typed it once. That is enough.
Gargul records every award as the raid hands it out. Run /raid loot on the finished night, paste the export it gives you, and the items file themselves against that raid.
- Finished raids only. The command offers you raids that have closed, and checks again before it writes. A night still in progress has nowhere to put loot yet.
- Off spec stays off spec. Gargul's OS and soft-reserve flags cross over with the item level and the time of the award. Every item keeps the tag it was handed out under, and the tier totals hold main spec and off spec apart.
- It reads whichever shape your export comes in. Semicolons, tabs, or a CSV with named headers, header row or not. It works out the format instead of insisting on one.
- A line it cannot read tells you which line. Odd rows come back numbered with the reason and the rest still land. One mangled item name does not cost you the whole paste.
- You get a receipt. What landed, what got skipped, and the top looters of the night, back in Discord before you have closed the addon.
Reports route to officers, privately.
Attendance and loot numbers are not raid-channel material. They go where the call gets made.
- Officers, not the raid channel. The numbers land where the call gets made.
- Trends, not a wall of rows. Raid leads read the shape of the tier at a glance.
- Confirm before it posts. The post-raid report waits on a human.
- Attendance and loot together. One place, so the officer call has both halves.
Nobody remembers who showed on the 12th. The report does.
The point is not to catch anyone out. It is that the bench conversation, the trial call, and the loot argument all get easier when they start from something written down at the time instead of two people remembering different Tuesdays.
Walk into the officer call with the receipts.
Add HootusPlootus and the attendance and loot history start keeping themselves from your first raid. No spreadsheet to maintain, no reactions to count, just the trends ready when the officers sit down.