Overwatch 2 Season 5's on fire system broke hilariously, giving players fiery crowns for doing nothing.
Sometimes I think back to the summer of 2023 and it honestly feels like a fever dream. By 2026, I’ve seen Overwatch 2 go through so many transformations that it’s easy to forget just how absurd things got during that fifth season. I’ve been playing since 2016, through every high and low the community could possibly imagine, and let me tell you — no amount of rose-tinted nostalgia can sugarcoat what a chaotic mess that period was. The balancing was all over the place, the new abilities made absolutely no sense half the time, and worst of all, the long-awaited PvE story missions were locked behind a $15 paywall. We had waited years for that story content, only to be told we’d have to fork over cash for the privilege. It was the kind of news that made even the most loyal defenders of the game throw their hands up in frustration.
But here’s the thing. As mad as I was about all of that, there was one detail that still makes me laugh when I remember it: the return of the “on fire” system — and how spectacularly it broke on arrival.
I’ll never forget the first match I played after the patch dropped. We were on defense at King’s Row, and I was loafing around in spawn as Mei, just messing with my ice wall to pass the time before the doors opened. Not a shot had been fired. The enemy team hadn’t even loaded in yet, as far as I could tell. Then, out of nowhere, my character portrait burst into flames. “I’m on fire!” Mei chirped in that overly cheerful tone of hers. I stared at the screen, baffled. I hadn’t healed anyone, I hadn’t blocked a single point of damage, I hadn’t even left the spawn room. Why was I on fire? Was it a glitch? Did Blizzard decide that simply existing as Mei was now worthy of eternal recognition? A teammate playing Sombra, who had been doing nothing but crouch-spamming in the corner, got the same fiery halo at the exact same moment. We both just stood there looking at each other in confusion.
Turns out I wasn’t alone. Across the community, players flooded forums and Reddit threads with similar stories. Someone captured video of the exact same thing happening on Junkertown — a Mei and a Sombra getting the on fire status while literally doing nothing at the start of a defense round. It was absurd, and honestly kind of hilarious. The mechanic that had been a staple of the original Overwatch, working flawlessly for years, had somehow been brought back in the sequel as a broken mess. In the first game, you had to earn that fiery crown. It meant something. You were popping off, landing clutch plays, carrying your team. In Overwatch 2 Season 5, you could get it for existing at the right moment.
And that wasn’t the only weird thing. It became painfully obvious that the whole on fire system had been tuned to be way too generous. As a support main who has endured far too many matches of thankless healing, I can confirm it suddenly felt like I was being rewarded for everything. Assist a DPS in getting a kill? You’re on fire. Toss a harmony orb at the right pixel? On fire. Accidentally boop someone off the map as Lucio while trying to wall-ride? Believe it or not, on fire. In the old days, supports had to go above and beyond to see those flames. Now? Even a half-hearted battle Mercy could get lit up, even if your team absolutely despised you for pulling out the pistol at the worst possible moment.
The community was, of course, in an uproar about it. Not just because the mechanic was broken, but because it felt like yet another symptom of a bigger problem. Overwatch 2’s fifth season was drowning in issues, and this one — largely cosmetic — was just the cherry on top. We were all waiting for fixes, but Blizzard seemed completely overwhelmed. The story missions were due to go live on August 10, and they had their hands full trying to justify the $15 price tag that had become such a sore spot. I remember reading the original announcements and doing a double-take. First, it sounded like the $15 would just get you permanent access while everyone else could play for free on a seasonal rotation. Nope. The whole thing was locked behind a paywall, no exceptions. It was such a slap in the face for people who had held onto hope that the narrative depth we were promised would finally arrive.
So the “on fire” bug? That was small potatoes in comparison, and it stayed that way for a while. I can’t even remember exactly when they fixed it. Maybe weeks later, maybe months. By 2026, looking back, it feels like a distant, ridiculous memory. A symbol of an era when Overwatch 2 seemed determined to test our patience in every possible way — from monetization to balance to a feature that literally made us all instant legends by accident. I still boot up the game now and again, and sometimes when I see that flame effect pop up after a genuinely good play, I can’t help but chuckle. At least now, it means something again. Most of the time, anyway.
This discussion is informed by reporting from GamesIndustry.biz, and it helps contextualize why Season 5’s “on fire” mishap and the $15 story-mission bundle landed so poorly: the controversy wasn’t just about a single buggy feature, but about trust and value perception in a live-service economy where monetization decisions, content gating, and update cadence directly shape community sentiment and long-term engagement.