Matt’s Notebook: The One Armed Bandit

by

Another week of farm for DJs and another week of progression for Last Call.

  • We managed to fully clear the raid again within two days. It was the first time I had seen any serious raid action in a long time. I did sit out on One Armed Bandit, but since the boss man wasn’t back yet, I got the call up to come in for Mug’zee, and we spent some time in there configuring with one less immunity. We did end up 4 healing it and executed a nice push early on. I did get a few pulls into Gallywix, and although I didn’t get into the last phase, I did see a good part of phase 1.
  • Over in Last Call, we started working on One Armed Bandit. I didn’t realize how finicky and exacting this boss can be. I guess we’re getting close to the end, and this is one of those pinnacle bosses (along with Mug’zee). We spent most of our progress just working on the fundamentals, including dispel placements, Big Hit placements, interrupts, and DPS prioritization. Our best was around 45% or so, which is solid for a first night of progression. Our second night was much better, as we did end up getting two good looks at the last phase. We ended with a 1% wipe with around 150 million health remaining. It was extremely close, but there was some general confusion towards the end. We had a few players get roasted by beams or get too close to pylons. Not only that, five coins were lying around at the end that weren’t picked up, which meant the boss was hitting quite hard. It was a solid week of progression for the team, and getting this much learning time in within two days overshot my expectations significantly.
  • Our new tank in Last Call is working well with us. Actually, our latest group of recruits have been meshing nicely (a DPS Monk, and Prot Warrior). Unfortunately, we don’t have a Ret or Prot Paladin available for Mug’zee, which makes mine popping that much more dangerous. There is a world where I bring back Diplomattic (my Ret Paladin) back in, though, but that’s not an option I want to consider just yet. I’m already thinking long-term about what the roster will look like entering Season 3. I do want to shore up our healers some more, even after adding a DJs healer into the team. At the rate we’re going, Gallywix is achievable. Mug’zee would be the final hump.
  • Bored of visions already? Yeah, me too. I got all of the currency and the helm enchants required for my main raiding characters. I’m just annoyed that the greater helm enchants are also time-gated.
  • My Shaman just needs two more 12 keys for full resilience. My Priest isn’t too far off from that either. Hopefully soon!

Those’re the updates for the week!

One Button to Rule Them All

by

Blizzard recently announced a new feature that’s got the community riled up. A one-button rotation option will be introduced that automates the next optimal spell cast. On paper, it sounds like a dream come true for players who struggle with complex rotations or for those who want a more relaxed gameplay experience.

But there’s a catch.

The one-button option comes with a longer global cooldown (the gcd), meaning that while you gain simplicity, you lose speed. Blizzard says the intent is to provide an alternative for players who use addons like Hekili to guide their rotations. The idea is to give players a built-in option rather than relying on third-party solutions.

But is it really going to change the game? Let’s break it down.

Why It Won’t Matter at the Mythic Level

At the Mythic raiding level, this one-button option is not going to see much use. The problem is that gcd penalty. When you’re pushing hard content, every millisecond counts. Adding even a slight delay between abilities can make the difference between a kill and a wipe.

Mythic raiders are already primed to think on their feet. They’re analyzing cooldown windows, juggling procs, and reacting to boss mechanics while weaving in their DPS sequence. This one-button system can’t keep up with the speed and precision required at this level.

One potential use that I could see, though, is the highlighter feature that comes with it. Even for skilled players, having a quick visual cue as a reminder could be handy. Think of it as a built-in priority helper. You’re still pressing your own keys, but the highlighter points out your next best option.

That said, I can’t see anyone who is seriously aiming for Cutting Edge relying on the full one-button rotation setup. It’s just too clunky for high-end content. Not saying that it’s impossible, because I suspect there will be a group that manages to do so but it’ll be towards the end of the tier with massive nerfs to the raid and equally large buffs to the characters.

Who Will Actually Use This Feature?

I see this being most useful for newer players or those picking up a new class or spec. If you’re learning how to be a Shadow Priest after maining a Warrior, you’re probably overwhelmed by the number of spells. I’ve been a Priest main forever, and I still get overwhelmed. The one-button option lets you get your feet wet without feeling like you’re drowning in keybinds.

Start off pressing one button, get a feel for what abilities trigger when, and eventually transition to pressing individual keys as you get more comfortable. It’s a teaching tool, not a crutch, and that distinction matters.

Another group that might benefit is the casual players who aren’t pushing Mythic+ or raiding at a high level. For them, the convenience might outweigh the GCD penalty. The same goes for players with accessibility challenges who might find a one-button rotation genuinely helpful for maintaining steady performance.

The Real Impact: A Wake-Up Call?

There’s one aspect of this feature that might catch some players off guard: the reality check.

If you’ve been using addons like Hekili for a long time and suddenly find that your damage drops when using Blizzard’s built-in version, it might make you question just how much of your rotation was actually instinct versus following visual cues.

I’m not saying everyone who uses rotation guides is a bad player, but there’s a difference between knowing why you’re pressing a button and just pressing it because it lit up. This new system might be a bit of a rude awakening for some players who thought they were more skilled than they actually are.

Ultimately, this feature is less about helping high-end players and more about making the game approachable for those who struggle with complex rotations. As long as it’s framed as a stepping stone rather than a solution, it’s not inherently bad.

The real key will be community perception. If players start using it as a crutch rather than a training tool, it could lead to some awkward encounters where one-button users find themselves vastly underperforming compared to their peers.

As always, the key to mastering your class is understanding why you’re making certain choices, not just following an automated sequence. If this feature helps players transition from basic to advanced play, great. But if it becomes a band-aid for bad habits, then it will end up being another unused option in the settings.

Matt’s Notebook: Gallywix Cleared!

by

Good season, everybody! Gallywix was a kill that we just stumbled into. It took us a total of 60 pulls. Most of our efforts were spent working on smoothing out the first pull. We wiped once we entered the final phase for the first time, and then we killed it on the subsequent pull. It was completely unexpected, as I thought it would’ve taken us longer to get a better understanding of it, but I gotta give flowers to the team for a job well done. Now our off-season starts as we slowly work our way back there and begin farming. We’ll have a pair of healers away this weekend, which means I get to come in. I’ve been on the sidelines, and I haven’t fully raided on my Priest since March.

  • We did add another healer to the DJs, and that brings us up to a healthy six-healer unit. This will be important as we enter the Summer months. We’re closing recruiting otherwise as we have a full slate right now.
  • Over in Last Call, we ended a few trials and some of our rostered players, as it was just no longer a good fit for us in the direction and approach we’re planning to push towards. Our healer count is at exactly 4, which is a perilous number for me as it means I have almost no buffer. The fallback healer I have would be me playing one of my other Priests.
  • Speaking of Last Call, we successfully defeated Sprocket! It took us 111 pulls, which is about on par with the average. Unfortunately, we struggled on going backwards with the reclear on Stix. There’s just something about it that makes farm kills that much harder. I know that we’re a solid team and we’re capable of it. I was so frustrated because we crushed Sprocket with an hour left. I wanted to push forward and go on to One Armed Bandit, but the rest of the senior team felt it more efficient to reclear Rik Reverb and Stix. We have about 10 weeks left in our season, and I really want to get to Gallywix and try to get a clear on it. The two hardest bosses are coming with Bandit and Mug’zee, both of which will take some serious time to learn.
  • Corruptions have come out this week, and much to my chagrin, it has also been time-gated. I can’t believe seven-year-old content is being drip-fed like this. The main content patches have been so much fun so far with Liberation of Undermine, but these other secondary patches don’t feel good right now, and we’re being forced to wait.
  • On my Holy Priest, I’ve been told there’s a new raid spec that’s back in play (Oracle Holy). Prayer of Healing is on the menu again! Can’t wait to try it out and see how it plays.
  • It’s a long weekend coming up and I will be out a few key players. I hope we will still have enough to get some reps in.

Matt’s Notebook: We’re on to Gallywix!

by

This is it! We’re on the final door step now. Gallywix is all that’s left standing, which is great news since we’re on the verge of entering the summer months soon. This means we’ll be entering farm mode! In the first exciting news, I’ve ordered a new PC finally. It’s much needed considering my current PC has lasted me since just prior to Covid so it’s definitely aging and I’ve been running into some performance issues in raid (especially with a full 30). Anyway, let’s jump into the notes.

  • Death Jesters is now on Gallywix. Mug’zee reached a point where any pull could be the kill if everyone was able to stay alive and committed. Phase 1 is certainly a hot mess as we’re planning our bombs and getting a feel of the start of the encounter. We are looking to recruit another healer to add to our lineup such as Resto Druid, a Mistweaver, or a Preservation Evoker. Come check us out here!
  • Last Call is now on Sprocketmonger, and we’re starting to consistently make it past the first intermission here with more players alive. I’m disappointed though as we lost one of our long time raiders. He was struggling with using Liquid’s Weak Auras pack and got so frustrated that he just decided to step down from the team altogether. One of our tanks, a Demon Hunter, has opted to switch to DPS due to inconsistent work schedules. We did recruit a new Protection Warrior, so I hope he will work out. Lastly, one of our Mistweavers has been occupied with things going on outside of the game that they also had to step away. On this team, we’re looking to add a hybrid healer (Windwalker/Mistweaver or Devastation/Preservation or Shadow/Holy Priest). Our application form can be found here.
  • Crest cap lifts this week! Rejoice! We’re going to need around 400 crests or so (assuming you’ve been capped out).
  • Our first set of Dinars become available this week! I have no idea what to buy! My Priest doesn’t need anything out of Heroic and I’m limited in what I can purchase from Mythic since I haven’t killed any of the bosses after the first two.

Ugh, back to work. Have a good week!

The Art of the Post-Raid Debrief

by
The other day, I was chatting with one of the other raid leaders from a different team in our community. We got onto the topic of raid feedback after the raid ends.

Their team uses a system where they post individual debrief threads in Discord sorted by date. People dig into logs, break down their performance, and share what they’ve learned or where they messed up. It’s super detailed, and honestly, it works for them. Especially for the log-savvy folks who live in Warcraft Logs and can extract key information from a night.

Our approach in Last Call is a little different.

We keep it mostly team-focused. When we review fights, we share insights with the whole squad. Once in a while, if there’s something that needs to be addressed, such as a key mechanic someone consistently missed, we’ll mention it if it’s a learning point for everyone. We don’t want to turn our review into a firing squad. The point isn’t to shame people on their class rotation or anything. If I missed one Ancestral Swiftness, that’s not really going to move the needle (but I’m still going to file that information away because I could’ve played that Shaman better).

It’s to improve as a group.

Debriefing After Stix: A Real Example

Let me give you a recent case. We were working on Stix, and during our post-raid breakdown, we pulled a bunch of things out of the logs:

  • Defensive cooldown usage: Who popped a defensive when they were supposed to? Who forgot? Who panicked and overlapped three cooldowns on the same hit?
  • Trash ball behaviour: Did players avoid the crab shells? Did they accidentally miss a Scrapmaster and turn into a small ball instead of a medium or large one? Every little bit of damage helps on Stix, and that includes how well you manage those ball mechanics.
  • Interrupts: This is huge. Did we have full coverage on Scrapmasters?

Even on wipes, every pull gives you data. And the more you learn from that data, the faster you kill the boss. We shared a table with player information that showed who missed Scrapmasters or rolled into Bombshells. In this situation, we had to spotlight players who were making errors. Either they weren’t seeing information, or they weren’t responding to it and these are both things we have to correct one by one. Over time, the team did improve as a whole, and the number of mistakes went down as everyone became more familiar with what to look for and what to avoid. Without having waded into the weeds of the information, we would not have realized that the Scrapmaster in the Purple Diamond section (the one near the wall) was the one that frequently got overlooked.

Our coaching point then was if you are assigned diamond, specifically look for the Scrapmaster that’s near the wall because chances are you balled right by it or it happens to blend in with the wall that it’s just missed.

The Debrief Toolkit: What We Look For

Here’s what we usually include in our team debriefs:

  • Positioning: Anyone consistently getting hit by frontals or mechanics they should’ve dodged?
  • Cooldown assignments: Were healing CDs used where they were planned? Were any wasted? Was anyone holding a CD too long out of fear? The flipside holds true as maybe we used a raid wide ability somewhere that didn’t warrant it.
  • DPS optimization: Were people using potions and cooldowns on time? Did they get value out of their major windows? Are they targeting the right ads including Scrapmasters?
  • Death analysis: Were deaths avoidable? Did they come from mechanics, poor healing coverage, or missed externals?

You don’t have to go full detective mode. Even picking two or three key points per night can make a big difference.

Tools We Use

  • Warcraft Logs: The core of any good debrief. Parses, cooldown usage, deaths, damage taken—you name it.
  • Viscerio’s Combat Replay: Great for showing positional data and understanding how the raid moved during a fight.
  • Method Raid Tools Logs: Super helpful for tracking planned cooldowns vs. actual usage.
  • Warcraft Recorder: This one’s a game-changer if you’re not already using it. It captures in-game footage automatically, making it easy to review exact moments, callouts, and spatial awareness issues. Bonus: It’s great for training, clip sharing, or spotting issues that don’t show up in logs.

Tone Matters More Than You Think

If there’s one thing I’ve learned as a raid leader, it’s that tone makes or breaks your debriefs.

You could have the most accurate breakdown in the world, but if it comes across like a scolding session, no one’s going to internalize it. Worse, they’ll tune out or even resent it.

We try to keep things constructive. We highlight the good stuff. “Great use of Pain Suppression on that 2nd phase soak.” “We handled the adds way better this pull.” Stuff like that. Wins get celebrated just as much as fails get analyzed.

Final Thoughts

A raid doesn’t end when the boss dies or wipes your raid group. It ends when you understand why it went the way it did.

Debriefs help bridge the gap between one raid night and the next. They’re how you carry lessons forward. And the better your team reviews together, the stronger you’ll be on the next pull.

Start small. Pick one fight. Pick one thing. Talk about it. You might be surprised how much smoother your next raid night goes.