Click here to pre-order the latest issue of NAG Magazine

Diablo IV: Lord Of Hatred, Season Of Regret

For almost two weeks, Diablo IV: Lord of Hatred had me. Not politely. Not casually. Not in the “I’ll play for an hour after work” way. It had me in the old Diablo way, the dangerous way, the way where the game crawls under your skin and starts replacing normal thoughts with loot tables, boss attempts, affix rolls, and that one stupid missing upgrade that will definitely fix everything once it finally drops.

Miachu and I went in together, and for a while, it was everything I wanted it to be. The campaign worked. The mood worked. Sanctuary felt alive in that horrible Diablo way, full of rot, blood, old gods, bad decisions, and doors that should absolutely not be opened but obviously will be.

We pushed through it together, and the whole thing had that proper expansion energy. Not just more content, but a reason to come back. A reason to care. We finished the campaign. We kept going. We reached Lilith. And Lilith died.

No crisis. No endless wall. No moment where we had to sit in silence and question every choice we had made since character creation. We killed her and moved on, feeling like the game had accepted us. Like we had crossed the threshold. Like the real endgame had opened its mouth and invited us in. Then we reached Mephisto.

That is where the spell started to sour. Mephisto was not just “hard”. Hard is fine. Hard belongs here. I do not want the big bad of an expansion to fold like a wet napkin because someone on YouTube found a way to turn a left boot and two passive nodes into a nuclear weapon. I want resistance. I want the wall. I want the game to say, “Not yet.”

But Mephisto was not just a wall. He was a toll gate built in front of a swamp. His damage intake was being controlled through phases. You were not just walking in and burning him from 100 to 0. The fight had brakes. The game decided when enough damage was enough, and suddenly the answer was not “play better”, it was “go back and grind harder.” Fine.

That is Diablo. That is the altar. You take your weak little build, drag it back through the mud, and feed it better gear until it stops crying. So I went back to the grind.

I started chasing GAs. I started looking at my build properly. I started trying to roll the +skill mods I needed. And when things did not make sense, I did what most of us do before we blame the game. I blamed myself.

Maybe I misunderstood the system. Maybe I was using the wrong prism. Maybe there was some hidden restriction. Maybe I was being stupid. Maybe the build was not ready. Maybe, maybe, maybe. That is the poison.

Because two weeks later, Blizzard’s 3.0.2 patch notes finally said the quiet part out loud: there were “many +Skill Rank affixes that could not be rolled when using a skill rank tuning prism.” That is not flavour text. That is not a small inconvenience. That is the game admitting that one of the core things I was trying to fix my character with was broken under my feet. And it was not alone.

That same patch is a graveyard of broken systems. Warlock fixes. Talisman fixes. Horadric Cube fixes. Dungeon fixes. Boss fixes. Loot fixes. Tooltip fixes. Seasonal objective fixes. Class interaction fixes. Things not stacking. Things falling off. Things not rolling. Things not dropping. Things not applying. Things not doing what the game said they did. Blizzard’s own notes list a mountain of “Fixed an issue where…” entries across almost every major part of the expansion’s machinery.

This was not a rough edge. This was the engine coughing up blood. And this is where I lose patience, because Diablo is not just about killing demons. Diablo is about trust. The entire genre runs on trust.

When an item drops, I need to trust that it works. When a tooltip says something, I need to trust that it is at least trying to tell the truth. When a crafting system offers me a path, I need to trust that the path is real. When a boss blocks me and sends me back into the grind, I need to trust that the grind is not bugged. Because otherwise the whole thing collapses.

It collapses in that slow, awful way where every decision becomes suspect. Every failed roll becomes suspicious. Every weak damage number becomes a question mark. Every build problem becomes a murder mystery where the killer might be me, the game, the tooltip, the class, the item, the boss, or some half-dead system quietly bleeding behind the UI. That is not endgame. That is unpaid QA with extra steps.

The worst part is that there was no proper warning before I wasted that time. No big communication saying, “Do not sink your resources into this because some +skill affixes are not rolling correctly.” No clear flag. No emergency flare. Just silence, then a patch note two weeks later confirming that the thing I had been wrestling with was not just confusing. It was broken. And in a seasonal game, two weeks is not nothing. Two weeks is the blood supply.

That is when the season is alive. That is when people are excited. That is when friends are still logging in. That is when couples like Miachu and me are still building the ritual. Still saying, “Okay, one more run.” Still pushing the next boss. Still checking gear. Still believing the next upgrade is just around the corner.

You do not get to waste those two weeks and call it a normal live-service hiccup. Not when the entire point of a season is momentum. Not when players are deciding whether this is their new obsession or another game they uninstall with a sigh. And for casual players, this kind of broken launch is even worse.

Mia is not sitting there trying to reverse-engineer Blizzard’s haunted maths cathedral. She is not reading every patch note with a miner’s helmet and a spreadsheet. She is playing the game in the way a normal person plays the game. Kill monsters. Get loot. Equip better things. Feel stronger. Push forward.

That is the promise. When that promise breaks, casual players do not go, “Interesting, perhaps this interaction is bugged and will be resolved in a future build.”

They think they are bad. They think they chose wrong. They think the game has already moved past them. They think the endgame is for someone else.

And once that happens, you have lost them. Not because Mephisto killed them. Not because the grind was long. Not because the game was hard. Because the game made them feel stupid for trusting it. That is the kind of damage a patch cannot fully fix.

You can fix the Tuning Prism. You can fix Warlock bugs. You can fix Talismans, Cube interactions, boss health, busted drops, and seasonal objectives.

But you cannot patch back the moment when someone stops believing the game is worth their time.

And that is what makes Lord of Hatred so frustrating. It is not garbage. If it were garbage, this would be easy. I would laugh, uninstall it, and move on. But it is not garbage.

There is a great expansion in here. I felt it in the campaign. I felt it when Miachu and I pushed through the story. I felt it when Lilith went down. I felt it when Mephisto stood there like the next great gate.

For a while, Lord of Hatred had the old fire. The proper fire. The kind that makes Diablo dangerous to start playing at night because suddenly the moon has moved and your real life is looking at you through the window like a disappointed parent.

Then the bugs started eating the altar. And once that happened, the whole experience changed shape. I was no longer asking, “How do I make my build better?” I was asking, “Is this even working?” That question is death.

That question kills buildcraft. It kills excitement. It kills experimentation. It turns every upgrade into an interrogation. It turns every boss attempt into a trial. It turns every tooltip into a suspect.

That is why this patch made me so angry. Not because Blizzard fixed things. Good. Fix them.

But because the notes read like a confession after the damage was already done. Because the game let players grind, roll, test, fail, doubt themselves, and only then admitted that major parts of the machine were not working properly.

That is not just buggy. That is disrespectful of time. And Diablo lives or dies by time.

Every dungeon is time. Every boss attempt is time. Every failed roll is time. Every GA chase is time. Every night you convince someone to log in with you instead of doing literally anything else is time.

When the game works, that time becomes obsession. When the game lies, that time becomes ash.

Lord of Hatred gave me one of the best Diablo weeks I have had in ages. Then it handed me a patch note and told me I had been fighting ghosts in the machinery. So no, I am not angry because Mephisto stopped us. Let him stop us. Let him break us. Let him force us back into the dark to earn the kill properly.

I am angry because the road back to him was broken. I am angry because the game made me question myself when the system was at fault. I am angry because casual players like Miachu do not survive this kind of launch damage. They do not sit around waiting for Blizzard to finish repairing the bridge after they have already fallen through it.

I am angry because Lord of Hatred had the bones of something brilliant, and then spent its most important opening weeks tripping over its own guts.

For two weeks, I thought we were grinding toward Mephisto. Turns out we were grinding against the patch notes. And right now, I do not want to calmly farm another dungeon. I do not want to politely wait for the next fix. I do not want to pretend this is just the normal cost of live-service gaming.

I want to drag the whole broken machine into the street, set it on fire, and see if the ashes finally roll +skills.