What He Actually Saw

Feedback gets asked twice, and neither one lands at 2am

Every ask Hootus has ever sent was a DM, fired between 01:10 and 03:01 local time straight after a four hour raid, and the DM was the only place the ask existed. Sixty-three people have been asked that way and two have ever answered. Two things happen now instead. A post goes up in the raid channel the moment the raid closes, button and all, while the night is still fresh and nobody's phone is buzzing at them. The DM holds until 10:00 the next morning in your guild's timezone, when there is somebody awake to read it. The channel post takes itself down when the 48 hour window shuts.

Benched raiders and the person running the raid get asked too

The ask went only to people credited as present, which quietly left out whoever sat the night out and whoever organised it. Both are asked now, in wording that knows which one they are, because there is no point asking a benched raider how the pace felt in fights they watched. The 48 hour sweep also names who has not answered rather than closing in silence, and Hootus no longer greets the raid leader by name in a message only the raid leader can see.

A report that puts your logs next to who you credited

Logs vs attendance, under Reports, lines up every raid holding a Warcraft Logs report against the attendance you recorded for it, at 30, 60, 90 days or all time. It is the surface that found the nine benched raiders in Serpentshrine, and an officer can re-check the logs and credit them from the page without overriding anybody's deliberate call. It also counts the log names that resolve to nobody, 96 names over 576 rows for the Night Owls, almost all of them genuine one-off outsiders rather than anything lost.

An activity page, and a record of who changed which setting

The guild activity feed has a page of its own, open to admins by default. Every settings change is written down as one row per field that moved, with what it was and what it became, so who turned the pug pings off has an answer rather than a shrug. Super admins get the same view across every server Hootus sits in.

The feedback ask is one post in the raid channel, and it calls the raiders in

Earlier today the ask went out twice, a post when the raid closed and a DM the next morning. The DM is gone. Every ask Hootus has ever sent was a DM and it could never be confirmed that a single one arrived, because Discord will not say. So there is one post now, in the channel the raid already lives in, mentioning the raider role so the people who raid see it without anybody being messaged privately. It carries the button, it says when it closes, and it deletes itself when it does. If your guild has no raider role set, the post still goes up, it just calls nobody in.

The feedback questions name the raid, and the scale can say the night was bad

The old three step scale ran from Ruffled feathers to Owls loved it, so its worst option was a mild grumble and its middle was already positive. There was no honest way to report a night that went badly, and the results page then printed that grumble as Rough night, in words the member was never offered. The scale has a bottom now. Question one says the word raid, because nothing after the DM embed did, and asking how keen you are for another run is replaced by asking how the group was to raid with, which a benched healer can answer as well as a tank.

A feedback night says how many replies it is built on

Four submissions, all time, were being rendered as confident averages with nothing on screen saying four. Every figure now carries the number of replies behind it, a night with one answer prints that answer instead of averaging it into a distribution of one, and the mood squares got a legend so a colour means something. A page that has never had a reply says so, and it opens on the night that has something to read.

The post-raid attendance message states what Hootus saw and asks only about the rest

Finishing a raid handed you the whole roster with everybody pre-ticked present, which is a form rather than a question, and the quickest way through a form is to save whatever the owl guessed. He now says in a sentence what he recorded when he is sure of it, and asks about people by name when he is not, and every one of those names can be settled from that one message. The form also works in a DM, which it never has: pressing a button there used to fail a permission check that went looking for the server it was already in.

Nothing recorded and nought recorded are two different sentences

A guild that has never entered a single item of loot was getting four tidy zeros and 0.0 per raid, which reads exactly like a broken page and is why the analytics were reported as showing placeholders. An empty tab now explains that nothing has been recorded yet. And when Discord refuses Hootus your role list, he says the rank breakdown is unavailable instead of drawing a number he cannot stand behind.

Attendance stops crediting a chat and stops benching a fight

Two errors in opposite directions. Someone who filed an absence before the raid and then dropped into voice for twenty minutes of chat was read as intent to raid and credited for the night; a declared absence is now an absence whatever voice does afterwards. And an officer's bench marking was outranking the fight list, which is how nine people who spent two and a half hours in Serpentshrine on 30 July are recorded as benched. A bench no longer survives a log that puts that person in the pulls.

Loot fairness was dividing by raids that had no loot in them

Per raid on the loot fairness card counted every raid you attended in the window but only the items from the two that had loot entered, so it came out wrong by up to eight times and put the ranking the card tells you to sort by in the wrong order. Three of the four raiders it named as overdue were not, and one sitting seventh from the top was joint most fed in the guild. The denominator is now the raids that actually had loot recorded, which is the only comparison that means anything.

The raiders table stops scoring almost everyone at 100% or nothing

Reliability was turnouts divided by turnouts plus no-shows, and a no-show only counted when an approved signup left no trace at all. Anyone who came got a row from voice capture and anyone who could not come filed an absence, which routes elsewhere, so the two numbers were nearly always the same: 102 of 113 rows read either 100% or a dash. Turnout is counted directly now, and declines, excused absences and benched players are three separate figures instead of one shrug.

Progression stops naming ten raiders as having never seen a kill

That tile is built entirely from Warcraft Logs, and only 35 of the Night Owls' 78 raids have a report attached, so a raider who has cleared Karazhan without anybody uploading it read as somebody who has downed nothing. Six of the ten it named had real attendance credits. Coverage is now measured against raiders who appear in a log at all, and a boss you have not killed is told apart from a night nobody logged, which is the difference between a bench decision and a shrug.

A server running two games stops piling them into one roster

Add retail next to MoP and your class card grew a Demon Hunter and your roster size went from 301 to 314 overnight, because the daily snapshot counted every character on every game link as one heap. Each link is measured on its own now, and the public guild directory counts your main one. While he was in there, the members tile split into raiding, lapsed and social, so it stops being a single number that answers nothing.

PUG pings only go out when the raid is taking pugs

On 28 August all 29 people in the pug pool were messaged about a Hyjal Summit run that was not open to pugs, because the manual notify button skipped the check the automatic path makes. Whether a raid takes pugs is now a switch the creator sets on the raid post, it is off unless you ask for it, and both the button and the scheduler obey it. Eight servers had never chosen and were carrying the old on-by-default, so they are off as of this release. Turn it back on in settings if you want it.