Diablo 4 Player Says Lord of Hatred Campaign Is Blocked by a Solo Party-Step Bug

 

Diablo 4: Lord of Hatred has a new bug-watch entry, and this one has the special launch-day stink of a quest system arguing with itself.

A fresh Diablo IV console bug report claims that a player was disconnected during the Lord of Hatred campaign and then could no longer progress. The strange part? The game reportedly says not all party members are on the same quest step — while the player says they are playing solo.

The party problem with no party

That is the kind of bug that sounds almost funny until it happens to your campaign. Being blocked because a party member is out of sync makes sense in a multiplayer ARPG. Being blocked because an invisible imaginary party member disagrees with your quest progress is much less charming.

The report comes from the Xbox section of Blizzard’s console bug forum and, at the time of writing, appears to be a single-player-submitted issue rather than a confirmed widespread problem. So no, this is not yet “everyone’s campaign is broken.” It is more specific than that — and honestly, more irritating because of it.

Disconnects make campaign bugs extra ugly

Disconnects are already annoying in Diablo. They interrupt flow, reset momentum, and usually happen at the exact moment you were starting to feel like the game respected your evening.

But when a disconnect appears to leave the campaign state confused afterward, that is a different level of trouble. A quest step mismatch can potentially strand a player between “I did the thing” and “the game refuses to believe I did the thing,” which is basically the digital equivalent of being trapped in a cursed DMV.

Lord of Hatred already has progression warnings

This report lands alongside other early Lord of Hatred launch issues. Diabloz already covered Blizzard’s official Lord of Hatred known issues, including the “She Sleeps Within You” quest blocker and the missing Talisman Tab problem.

That does not mean this solo party-step report is officially confirmed in the same way. It does mean campaign progression is already one of the areas players are watching closely. When the expansion is new, anything that blocks forward movement feels ten times worse, because nobody wants to spend launch week negotiating with a broken quest flag.

A small report worth watching

For now, this is best treated as a bug-watch story: one clear report, a nasty-sounding progression block, and no visible Blizzard reply in the thread yet.

If you are playing Lord of Hatred solo and get disconnected mid-campaign, it may be worth checking your quest state carefully before pushing on. If the game suddenly insists that your non-existent party is out of sync, congratulations: you may have discovered the loneliest multiplayer bug in Sanctuary.

Launch day bugs are one thing. Being ghosted by your own solo campaign progress is another.

Read More

Diablo Immortal Bug May Let Locked Items Get Salvaged Anyway

 

Diablo Immortal has a fresh bug report that hits one of the scariest little corners of any loot game: the moment you trust the lock icon to protect something important.

A new official Diablo Immortal bug report claims that locked items can still be salvaged under a very specific bulk-salvage scenario. That is not a world-ending bug. It is worse in the small, personal way only loot games understand. Nobody wants their carefully saved gear turned into materials because the safety switch decided to take the afternoon off.

The bug appears tied to bulk salvage

According to the report, the issue happens when an item has already been selected for bulk salvage. The player says they long-pressed the item to open its stats window, tapped the lock icon, and expected that to protect it from being destroyed.

Instead, they say the item stayed in the salvage list and was still salvaged. Beautiful. Terrible. The kind of thing that makes players start treating every button in town like it might be a cursed altar.

The report is specific, but not universal

This is not currently framed as a confirmed widespread issue by Blizzard. It is a player-submitted bug report in the iOS section, and the original poster lists an iPhone 14 Pro Max running Diablo Immortal app version 4.3.0.

Another player in the thread says they normally use the lock function on PC without trouble, and that locking an item removes it from the salvage list for them. A later comment suggests the issue may no longer be happening on PC, while the original poster adds that they included a screen recording showing the locked item still being salvaged.

So for now, this looks like a very specific bug-watch item rather than a blanket “all locked gear is unsafe” panic. Still, it is exactly the sort of report Diablo Immortal players should notice before doing a tired late-night salvage sweep.

Locked should mean locked

The reason this matters is simple: item locking exists to create trust. Players use it because Diablo throws loot at them constantly, and without protection, one careless cleanup session can become a tiny personal tragedy with gem slots.

Diabloz recently covered how Fierce Pursuit reward math has players worried, and this new report sits in the same uncomfortable category: not necessarily huge on paper, but very irritating if it hits your account.

Double-check before you press salvage

Until Blizzard comments or the issue is patched, the safest move is boring but sensible: if you decide to keep something during bulk salvage, remove it from the salvage list entirely instead of relying only on locking it from the item details window.

Loot games live and die on tiny rituals. Lock the good stuff. Salvage the trash. Keep the upgrades. Move on. When that ritual gets weird, even briefly, players are right to get suspicious. In Diablo Immortal, losing a fight is annoying. Losing gear to a confused lock icon is pure psychological damage.

Read More

Lord of Hatred Reviews Are Strong, But Launch Day Is Already Messy

 

Diablo 4: Lord of Hatred has landed in that very Blizzard-shaped sweet spot where critics are praising the expansion and players are already sharpening pitchforks over launch bugs. In other words: Sanctuary is healing, but the furniture is still on fire.

On Metacritic, Lord of Hatred is currently sitting at an 84 Metascore, based on 42 critic reviews, with the site classifying it as “generally favorable.” That is a strong start for Diablo IV’s latest expansion, especially after years of Blizzard rebuilding the game’s reputation one systems overhaul, loot pass, and seasonal argument at a time.

The critics are mostly buying what Blizzard is selling

The critical consensus is fairly clear: Lord of Hatred is being treated as a substantial expansion, not a limp content drop wearing expensive armor. Reviews are praising the campaign, the new Skovos setting, the returning Paladin, the new Warlock, and the broader system changes around progression and endgame planning.

Several reviews highlighted by Metacritic frame the expansion as one of Diablo IV’s strongest moments so far. That matters because Diablo IV has spent much of its life in repair mode. Launch hype gave way to loot complaints, seasonal friction, endgame fatigue, and enough balance drama to power a small cursed village.

But launch day is already biting back

The awkward part is that strong reviews do not magically stop launch-day bugs from crawling out of the walls. Blizzard has already acknowledged several Lord of Hatred known issues, including a campaign progression blocker in “She Sleeps Within You” and a missing Talisman Tab problem for some players.

There are also player reports of technical trouble, including Lord of Hatred crashes and memory errors on high-end PCs. That does not mean the expansion is collapsing. It does mean launch day is already doing the usual live-service routine: big scores on one screen, bug reports glowing ominously on another.

A good expansion can still have an ugly first day

This is the part Diablo players know too well. A game can review well and still make people furious when a quest object fails to appear, a new system tab goes missing, or opening a menu causes a machine to wheeze like it has been cursed by a bargain-bin necromancer.

Lord of Hatred’s early score suggests Blizzard has delivered something critics genuinely like. The bug reports suggest players are about to spend the next few days separating the great new content from the annoying launch grit stuck between its teeth.

The real score starts after the patch cycle

Critic reviews are useful, but Diablo expansions live or die in the weeks after launch. That is when builds settle, bugs get fixed or become memes, endgame systems either sing or sag, and players decide whether the grind feels delicious or like unpaid labor in a haunted quarry.

For now, Lord of Hatred has the kind of critical momentum Blizzard wanted. It also has the kind of launch mess Diablo players expected. That combination is not shocking, but it is very Diablo: impressive, bloody, promising, and already asking for a hotfix.

Read More

Diablo 4 Players Say Lord of Hatred Is Melting High-End PCs

 

Diablo 4: Lord of Hatred has not just opened the gates of Hell. For some PC players, it may also have opened Task Manager, a crash popup, and that very specific kind of launch-week despair usually reserved for broken drivers and cursed menu screens.

A fresh Diablo IV Technical Support thread has players reporting crashes, freezes, and out-of-memory errors on machines that should be chewing through Sanctuary without breaking a sweat. We are not talking about ancient potato rigs running on dust and hope. Several posts mention high-end CPUs, modern GPUs, and 32GB or more of RAM.

Menus are becoming the boss fight

The original report says Diablo 4 starts eating memory, freezing when basic panels are opened, and eventually crashes with an insufficient memory error. The player specifically mentions the map, stash, character panel, and other interface screens causing massive freezes, sometimes lasting long enough to make the whole game feel like it has been dragged into a swamp.

That is the annoying part. Combat problems are one thing. A boss fight going sideways is at least thematically correct. But when opening the map feels like summoning a system-level demon, the vibe changes quickly.

High-end hardware is not escaping it

Multiple replies claim similar behavior on strong systems, including PCs with modern Ryzen processors, RTX 4070 Super-class hardware, RX 7900 XT cards, RTX 5070 Ti setups, and even one machine listed with 96GB of RAM. Players describe crashes after a few minutes, freezes when entering dungeons, and stutters tied to opening maps or character screens.

One player says scanning and repairing the game did not fix it. Another says lowering texture quality helped a little but did not solve the problem. Others point out that both AMD and Nvidia cards are being mentioned, which makes the usual “it’s just one driver setting” explanation feel a bit too neat.

This echoes an older Diablo 4 problem

The timing is what makes this worth watching. Diabloz recently covered a Diablo 4 UI freeze bug forcing full restarts, but this newer thread has a sharper Lord of Hatred launch-week edge. Players are not just reporting menu weirdness. They are connecting it to memory errors, crashes, and instability right as the expansion lands.

That does not mean the issue is universal. Plenty of players are getting in, leveling, testing builds, and committing the usual crimes against monster populations. But for the affected crowd, this is exactly the kind of technical mess that turns launch excitement into hardware troubleshooting theatre.

Launch day should not feel like a RAM sacrifice

Blizzard has already confirmed some Lord of Hatred known issues, including quest blockers and a missing Talisman Tab problem. This crash thread is separate, and at the time of writing it looks like player-reported technical support chatter rather than an official confirmed known issue.

Still, it is the sort of chatter worth taking seriously. When players with serious hardware say Diablo 4 is freezing after opening basic menus, crashing after a few minutes, or throwing memory errors on systems that should have room to spare, that is not just launch-day whining. That is Hell trying to install itself directly into your RAM.

Read More

Diablo 4 Lord of Hatred Already Has Official Known Issues

 

Diablo 4: Lord of Hatred has arrived, which means the gates of Hell are open, players are charging into new content, and Blizzard’s bug-report forum has immediately started glowing like a cursed shrine.

The good news: Blizzard is already acknowledging several Lord of Hatred problems officially. The less-good news: some of them are the kind of launch-day nonsense that can block progress, hide a new system tab, or make players wonder if Mephisto personally QA-tested the quest flow.

“She Sleeps Within You” can block progression

The biggest official warning so far concerns the “She Sleeps Within You” quest. In a Blizzard known-issue post, the team says some players may be unable to progress because the intended interactable does not appear.

That is the classic campaign-blocker flavor of bug: you know where the game wants you to go, the quest knows where it wants you to go, but the thing you need to click has apparently taken a smoke break in another dimension.

Blizzard’s workaround is to leave the game, reload the character from character select, and replay the quest. The studio says the interactable should then appear as intended, with a proper fix aimed for an upcoming update.

The Talisman Tab is also acting weird

Another official issue hits one of Lord of Hatred’s new systems. Blizzard says the Talisman Tab may not appear for all players when it is unlocked while in a party, according to the current PC bug-report listing on the official Diablo IV forums.

The suggested workaround is a little clunky: complete the quest solo on an alternate character. That is not exactly elegant. It is more “please walk around the haunted mansion through the basement window because the front door is cursed.”

Still, it is better than silence. A missing tab for a new expansion system is the kind of bug that makes players instantly suspicious, especially when everyone is trying to understand new mechanics, new progression paths, and new ways to accidentally ruin a build with confidence.

This is launch mess, not launch doom

To be fair, none of this means Lord of Hatred is collapsing into a pile of bones. Big Diablo launches usually come with technical smoke. Some of it clears quickly. Some of it gets patched. Some of it becomes a forum meme with a longer lifespan than several seasonal mechanics.

But campaign progression bugs matter because they hit the one part of launch players expect to work cleanly: moving forward. Diabloz has already covered the broader Lord of Hatred launch timing, and now we are in the less glamorous phase: finding out which doors open, which tabs appear, and which quest objects have decided to become ghosts.

Check the workarounds before you rage-delete your evening

If you get stuck in “She Sleeps Within You,” Blizzard’s advice is to reload from character select and replay the quest. If the Talisman Tab is missing after unlocking it in a party, the current workaround points toward completing the related quest solo on another character.

It is not pretty, but it is useful. Lord of Hatred may be about Mephisto, corruption, and the slow poisoning of Sanctuary, but launch day still has an older villain: the interactable that refuses to show up.

Read More

Diablo Is Invading Overwatch Again, Because Hell Apparently Has a Skins Department

 

Diablo’s Lord of Hatred marketing campaign has now reached the “cross the streams and sell the cosmetics” phase, which is either corporate synergy or Mephisto discovering brand management.

Blizzard’s Overwatch x Hatred’s Reckoning event begins on April 28 and runs until May 18, bringing Diablo-themed skins back into Overwatch just as Diablo IV’s Lord of Hatred expansion kicks open the cathedral doors.

Mephisto has entered the hero shooter

The headline skin is the obvious one: Ramattra as Mephisto. That pairing makes a certain amount of cursed sense. Ramattra already has the presence of someone who would monologue beautifully in a ruined temple, so giving him the Lord of Hatred treatment is less a costume and more a career pivot.

The new lineup also includes Diablo-inspired looks for Brigitte, Freja, Lifeweaver, and Mauga, with the event leaning heavily into the Lord of Hatred mood. It is not subtle. Diablo rarely is. This is a franchise where even the furniture looks like it has unresolved trauma.

The old Diablo skins are coming back too

The event also brings back previous Trials of Sanctuary cosmetics, including Diablo-themed skins such as Lilith Moira, Inarius Pharah, Imperius Reinhardt, and Gilded Hunter Sombra. That is good news for players who missed the earlier crossover and bad news for anyone trying to pretend they will not check the shop “just to look.”

There are returning event challenges too, plus a very stupidly perfect weapon charm: Crab with a Knife. Is that Diablo? Not really. Is it the kind of tiny nonsense item that somehow becomes the thing people remember? Absolutely.

Diablo and Overwatch have done this dance before

This is not Blizzard’s first attempt to let its franchises raid each other’s closets. Long-time players may remember earlier cross-promotions like Mercy’s Wings for Diablo III, which turned an Overwatch purchase into a cosmetic reward inside Diablo.

The difference now is timing. This crossover is arriving right alongside Diablo IV’s biggest current push, with Lord of Hatred selling the endgame hard, Mephisto front and center, and Blizzard clearly trying to make the expansion feel like a full-company event rather than just another release on the calendar.

Hell looks weirdly good in team colors

For Diablo-only players, Hatred’s Reckoning may not be essential. It does not change your build, fix your drops, or make your stash magically less embarrassing.

But as a piece of launch-week noise, it works. Diablo invading Overwatch gives Blizzard another flashy way to put Mephisto everywhere, and the skins look dramatic enough to make the crossover feel less like filler and more like a properly dressed-up marketing ritual.

Besides, if Hell really is expanding into other games, at least it brought cosmetics instead of another 179GB install prompt.

Read More

Diablo 4 Sorcerer Players Are Already Fighting Over the New Uniques

 

Diablo 4’s Lord of Hatred launch is barely through the door, and Sorcerer players are already doing what Sorcerer players do best: staring at item text like it personally insulted their bloodline.

A fresh Diablo IV forum thread has started ranking the new Sorcerer uniques before the Season 13 meta has properly settled. That means this is not a final verdict. It is pre-launch theorycrafting, gut feeling, damage math, and class trauma blended into one very familiar Sanctuary cocktail.

Drognan’s Anguish is getting the loudest early attention

The headline item in the discussion is Drognan’s Anguish, a unique ring that pushes Pyromancy into dangerous territory by burning the player for a percentage of maximum life while increasing Burning damage. The item is also listed in the D4Builds Lord of Hatred update roundup, where it is shown as one of the new Sorcerer uniques arriving with the expansion.

That is exactly the kind of design Diablo players love and fear at the same time. Big damage number? Excellent. Hurting yourself to get there? Also excellent, but now everyone has to pretend they read the defensive layers section before faceplanting into an elite pack.

Fire builds may be the early winners

The early community read is that fire-focused Sorcerer setups could come out swinging, especially if Drognan’s Anguish lands as a build-defining piece rather than another “looks cool, lives in stash” unique. The same Lord of Hatred item roundup also lists Emberfury, a unique amulet tied to Pyromancy and Overpower scaling, giving fire Sorcs even more reason to start rubbing their hands together like suspicious wizards near dry wood.

Of course, theorycrafting before launch is always part science, part prophecy, and part “I really want this to be good because I already named the build.” Numbers that look outrageous on paper can collapse once cooldowns, survivability, boss uptime, and actual dungeon pacing get involved.

Not every new unique is getting royal treatment

The more interesting part of the discussion is not that one item looks strong. It is that Sorcerer players are already separating the new gear into “meta candidate,” “maybe useful,” and “please explain who this was for.” That is healthy, honestly. A class with several viable directions is more fun than one where everyone is shoved into the same lightning-shaped hallway.

Diabloz recently covered how Hydra Enchant changes were worrying Sorcerer players, so the class is entering Lord of Hatred with plenty of baggage. New uniques could soften that mood, or they could give players an entirely new set of complaints with better item art.

The real tier list starts after the corpses pile up

For now, these rankings are useful but not sacred. The proper test starts when players push Nightmare Dungeons, Tower runs, bosses, and whatever cursed endgame math Lord of Hatred throws into the grinder.

Still, the early fight over Sorcerer uniques is a good sign. It means the items are interesting enough to argue about. In Diablo, that is basically romance.

Read More

Diablo Immortal Players Say Fierce Pursuit Is Squeezing F2P Rewards

 

Diablo Immortal’s Fierce Pursuit event has gone from “limited-time reward track” to “spreadsheet boss fight,” and somehow that feels more dangerous than half the monsters in Sanctuary.

A new Diablo Immortal forum thread claims that free-to-play players may be pushed short of the full reward track because of the previously reported missing event tasks. The short version: if the math in the post is right, missing Skeletal Spoils could mean missing out on a legendary container and several legendary gems unless compensation arrives.

The complaint is about missing currency, not just missing tasks

This is tied to Fierce Pursuit’s week-one problem, where players reported that the expected Survivor’s Bane tasks were not showing up properly. Diabloz already covered that earlier issue in our article on missing Survivor’s Bane tasks in Fierce Pursuit, but the new complaint sharpens the blade.

The argument now is not simply “the event tracker is wrong.” It is “the event tracker being wrong may change what free players can realistically earn.” That is where Diablo Immortal discourse tends to get very spicy, very fast, and usually with at least one person yelling about orbs in the background.

Players want 70 Skeletal Spoils compensation

The forum post argues that players are short because week-one tasks did not appear as expected, and suggests a simple fix: give every player 70 Skeletal Spoils for the missing tasks. That number matters because Fierce Pursuit rewards are tied to event progress, and even a small missing chunk can become ugly if the premium booster gives paying players more room to breathe.

That is the heart of the backlash. Players are not just asking for a checkbox to light up. They are asking whether a bug has made the free reward path tighter than it was supposed to be. In a game already famous for monetization debates, that is basically tossing a cursed torch into dry hay.

This still needs careful reading

There is one important caveat: this is a player-side calculation and forum complaint, not a Blizzard-confirmed final outcome. At the time of writing, the thread is active, but this should still be treated as a developing player report rather than a confirmed official statement that all free-to-play players are locked out of the full track.

That said, the concern is not random. Fierce Pursuit has already had enough event-tracking weirdness to make players suspicious. Diabloz also covered an earlier Fierce Pursuit boss-kill counting bug, so this event has not exactly been gliding through Sanctuary like a polished angel with a clipboard.

Reward math is where patience dies

Live-service events can survive bugs. They can survive confusion. They can even survive players calling the reward structure stingy, because that is basically a seasonal weather pattern in Diablo Immortal.

What they struggle to survive is reward math that feels unfair. If free players believe a bug has made them miss legendary gems while paid options still smooth the path, the discussion stops being about event design and starts being about trust.

For now, Blizzard has an easy way to cool this down: clarify the reward math, confirm whether free players can still finish the track, and compensate the missing currency if the event launched short. Otherwise, Fierce Pursuit risks becoming exactly what every live-service event dreads — not a hunt, but an argument with numbers.

Read More

Diablo 4’s 179GB Install Size Has Players Clearing Their SSDs Like a Dungeon

 

Diablo 4 players were already preparing for Lord of Hatred. Some were farming, some were theorycrafting, and at least one player was apparently staring at their SSD like it had just been cursed by Mephisto himself.

A fresh Diablo IV forum thread has kicked off a familiar PC gaming complaint: Diablo 4 can look enormous when reinstalling with high-resolution assets. The original poster says they tried to make room for the game ahead of the expansion, only to be greeted by a 179GB install demand. That is not a file size. That is a landlord.

The high-res asset pack is the usual suspect

The thread quickly turned toward the likely culprit: Diablo 4’s high-resolution assets. One player asked whether the install included the high-res asset pack, while another said their own Diablo 4 folder was sitting at 164GB with those assets installed.

That tracks with long-running advice around Diablo 4’s optional texture pack. Guides like PC Gamer’s high-resolution assets explainer have pointed out that players can use Battle.net’s Modify Install option to toggle the high-resolution assets on or off. In plain English: if you are not playing at very high resolution, you may be hoarding a mountain of visual data you barely notice while being mauled by goatmen.

“Just install it on an external” is not always painless

The forum discussion also drifted into the usual emergency storage solutions. External drives came up. So did the warning that slower drives can mean long loading times and possible rubberbanding. Diablo 4 already has enough ways to make players feel trapped. Adding storage-related stutter to the list feels like seasoning the corpse.

To be fair, this does not look like a bug. It looks more like the ugly reality of a modern live-service ARPG with expansions, high-res textures, pre-loads, and enough environmental detail to make every dungeon wall look professionally miserable.

Lord of Hatred makes the timing worse

The frustration lands harder because it is happening right as players are getting ready for the expansion. Diabloz has already covered the Lord of Hatred pre-download and launch times, and this is the practical follow-up nobody enjoys: before you can fight Hell, you may have to fight your storage menu.

It also follows a small wave of pre-launch technical grumbling, including players reporting Lord of Hatred pre-load trouble. None of this means launch is doomed. It just means the road to Sanctuary still runs through Battle.net, disk space, and whatever forgotten game folder is eating 80GB in the shadows.

Check the checkbox before deleting half your library

If Diablo 4 is demanding a terrifying amount of space, the first stop should be Battle.net’s install settings. Open the Diablo 4 page, hit the gear icon, choose Modify Install, and check whether high-resolution assets are enabled. If they are, and you do not need them, removing them may spare your SSD from ritual sacrifice.

Diablo 4 being large is not new. Diablo 4 feeling like it wants to move into your PC and start receiving mail, however, is still worth calling out. Hell has many forms. Sometimes it is a 179GB install prompt.

Read More

Diablo 4 Wants 266.6 Million Paragon Points for a Crown

 

Diablo 4 has found a very Diablo way to celebrate Lord of Hatred: ask the entire playerbase to grind a number so weirdly evil it sounds like it was approved by a committee of accountants wearing skull masks.

Blizzard’s new Hatred’s Downfall Community Challenge tasks players with collectively earning 266,600,000 global Paragon Points. If the community hits that number, everyone gets the Crown of Hatred, a helm reward tied directly to Mephisto’s big Lord of Hatred moment.

A community grind with a suspiciously demonic number

The setup is simple: play Diablo 4, earn Paragon Points, and contribute to the global total. Blizzard says all players are eligible across all realms, whether they are sticking to the base game zones or heading into Skovos with the expansion.

That makes the challenge less of a special event mode and more of a giant background meter attached to normal progression. If you are playing, you are helping. If you are no-lifing, you are helping a lot. If you are logging in after work and accidentally falling asleep in town, you are helping spiritually.

The reward is the Crown of Hatred

The reward itself is the Crown of Hatred, which Blizzard describes as a helm infused with hate from Mephisto. Very normal hat. Extremely chill headwear. Definitely something a responsible wanderer should place on their skull without asking questions.

The funny part is that the reward has already triggered the usual Diablo community split: some players like the idea of a shared global milestone, while others are side-eyeing whether a cosmetic helm is enough motivation for a grind this large. A Blizzard forum discussion is already debating whether the goal is wildly steep, easily crushed in days, or one of those “of course it’ll unlock eventually” community events.

Big number, bigger question

The real question is not whether Diablo players can grind. They can. They have been clinically proving that for decades. The question is whether this challenge will feel like a fun launch-week rally or just another marketing meter floating above the apocalypse.

There is a good version of this idea. A global challenge gives the community something to watch together while Lord of Hatred launches, and the Tuesday progress updates should create a little ritual around the grind. Diablo needs more reasons for players to feel like Sanctuary is being fought over by everyone, not just whatever build currently deletes the screen fastest.

Sanctuary gets a group project

Diabloz has already covered the wider Lord of Hatred pre-download and launch timing, but Hatred’s Downfall deserves its own spotlight because this is less about launch logistics and more about Blizzard turning the entire playerbase into one giant Paragon-farming machine.

Will 266.6 million Paragon Points fall quickly? Probably. Will players complain while doing exactly what the event asks? Absolutely. That is not a flaw in the system. That is just Diablo culture wearing the Crown of Hatred early.

Read More

Diablo IV’s Mephisto Guitar Is Already Collector Bait

 

Diablo IV has crossed the line from “dark fantasy action RPG” into “yes, apparently Hell has a merch department with a guitar budget.” Honestly? That feels painfully on-brand.

As part of the Lord of Hatred launch push, Blizzard and Jackson have revealed the Jackson Kelly Diablo IV - Lord of Hatred Limited Edition, a Diablo-themed electric guitar plastered with Mephisto artwork, blood-red details, and enough sharp angles to look mildly illegal in a peaceful room.

Mephisto, but make it metal

The guitar is built around Jackson’s Kelly body shape, which already looks like it was designed during a power outage in a haunted amplifier factory. Add Mephisto’s face across the front, Diablo IV artwork on the back, red binding, and Diablo-inspired inlays, and you end up with something that looks less like an instrument and more like a cursed boss drop with strings.

Jackson’s official listing prices it at $1,299.99, and at the time of writing, the page marks it as sold out. That is not exactly surprising. Limited Diablo merch has a habit of vanishing faster than a usable Unique after a bad balance patch.

This is not random merch noise

The timing is doing a lot of work here. Blizzard’s Lord of Hatred launch blog puts the guitar right alongside the expansion rollout, the KoЯn collaboration track “Reward the Scars,” Twitch Drops, and the broader Mephisto marketing machine.

That matters because this does not feel like a lazy logo slap. Diablo and metal have always shared the same wardrobe: skulls, misery, cathedral lighting, loud noises, and a suspicious amount of red. A Diablo guitar is not subtle, but subtlety was never really invited to this funeral.

A collector piece first, a player weapon second

Specs-wise, the guitar is not just wall decoration. Jackson lists a Nyatoh body, through-body maple neck with graphite reinforcement, 24 jumbo frets, a compound-radius amaranth fingerboard, high-output Jackson pickups, a hardtail bridge, and an included gig bag. In normal human terms: yes, it is meant to be played, not merely stared at while whispering “soon” in a dark room.

Still, let’s be honest. A lot of these will end up as collector pieces. That is not a criticism. If you buy a Mephisto guitar with blood-red inlays, you are either preparing for a gig, decorating a gaming cave, or making a financial decision that your spouse will discover by accident.

Sanctuary found its riff

Diablo IV’s Lord of Hatred campaign push has been all about scale, noise, and Mephisto looming over everything like the world’s angriest album cover. This guitar fits that mood perfectly.

It is expensive, dramatic, probably gone before most players even noticed it existed, and extremely Diablo. In other words: a little ridiculous, very metal, and exactly the kind of collector bait Hell would approve of.

Read More

Diablo 4 Rune Linguistics Bug May Be Blocking Seasonal Progress

 

Diablo 4 has another tiny-sounding bug report with the potential to be deeply irritating, which is basically the series’ favorite flavor of technical nonsense.

A fresh official Diablo IV bug report says the seasonal objective Rune Linguistics will not complete after socketing runes. The player says they tested it on both PC and Xbox, tried a second character, and still could not get the objective to pop. That is not the kind of language lesson anyone asked for.

The problem is not just the checkbox

On paper, “socket some runes” sounds like one of those harmless seasonal chores players knock out while half-watching something on another screen. Click item. Add rune. Receive progress. Feel briefly productive. Move on.

But the report claims the objective is tied to seasonal progression, and that the failure is blocking access into The Pit. That is where the tone changes from “annoying little bug” to “why is a checkbox guarding the dungeon door like a drunk skeleton bouncer?”

One report, but a very specific one

This is still bug-watch territory. At the time of writing, the thread is sitting in Blizzard’s PC Bug Report section without a visible Blizzard reply, and there is not yet a giant pile of matching reports behind it. So no, this is not proof that Rune Linguistics is broken for everyone.

But it is specific enough to watch. The player names the objective, describes the action required, says it fails across platforms, and says a second character did not fix it. That is a cleaner report than the usual “game broke, fix please” graveyard poetry.

Season progression bugs always punch above their weight

The reason this matters is simple: seasonal checklists are supposed to guide players through the game, not become a mini-boss made of bad tracking logic. When objectives fail to complete, players are not just losing a reward ping. They are losing confidence that the progression system knows what they have actually done.

Diabloz has already covered similar build-and-progression weirdness, including the recent missing skill point bug frustrating players. This Rune Linguistics report sits in the same ugly family: small on paper, potentially maddening in practice.

Check before you start blaming yourself

If you are working through seasonal objectives and Rune Linguistics does not complete after socketing runes, it may be worth checking the bug thread before tearing your stash apart like a cursed raccoon.

For now, this is not a confirmed widespread issue. It is, however, exactly the sort of Diablo 4 bug that can waste time, block momentum, and make a simple objective feel like it was written by a Horadrim intern on no sleep. With Lord of Hatred launch timing already pushing players into prep mode, Blizzard probably does not need another seasonal gate acting weird at the worst possible moment.

Read More

Diablo 4 Players Report Pre-Load Trouble Before Lord of Hatred Launch

 

Diablo 4’s Lord of Hatred pre-load is supposed to make launch night smoother. For some players, though, the ritual appears to have started with the ancient PC gaming curse: a download bar that refuses to move.

With the expansion almost here, a new Blizzard forum thread has players discussing cases where the pre-release download for Lord of Hatred is stuck at 0%. That is not exactly the kind of hell portal anyone wants to open before launch. Demons are one thing. A frozen Battle.net launcher is just rude.

The pre-load is live, but not everyone is gliding through

Blizzard officially made the Lord of Hatred pre-download available on April 23 for Battle.net, Xbox, and PlayStation. The same update also lets players pre-download patch 3.0.0 even if they have not purchased the expansion, which makes sense: nobody wants half the player base trying to eat a massive update at the exact moment Mephisto kicks the door in.

For many players, the download seems to have worked normally. Several replies in the forum thread say their pre-load completed days ago or installed in minutes. That makes this look less like a universal outage and more like a messy launcher-side issue hitting some users. Annoying, yes. Apocalyptic, not yet.

The 0% problem is the ugly part

The original report says the pre-LOH download had been stuck at 0% for hours, with other players chiming in about pre-update data throttling, disk checks, and the usual “try restarting everything before sacrificing a goat” troubleshooting dance.

One reply suggests checking whether Battle.net is actively using disk resources, because the launcher may be scanning existing files before downloading anything new. Another points toward download throttling settings. These are player suggestions, not an official Blizzard fix, so treat them as practical community troubleshooting rather than gospel carved into a cursed cathedral wall.

This is exactly why pre-loads exist

The good news is that these issues are appearing before launch, not after. That is the entire point of a pre-load window: let the problems crawl out of the cellar while there is still time to kick them back down.

Diabloz already covered the broader Lord of Hatred pre-download and launch times, but this is the less glamorous follow-up: yes, pre-loading is live, and yes, some players are already wrestling the launcher instead of demons.

Check it before launch night gets crowded

If you are planning to jump into Lord of Hatred the moment the gates open, now is the time to check your install, storage space, launcher settings, and update status. Not later. Not five minutes before launch. Not while staring at a 0% bar like it personally betrayed your bloodline.

For now, this does not look like a massive Diablo 4 meltdown. It does look like the usual pre-launch technical smoke rising from Sanctuary’s floorboards. Still, if your download is stuck, that smoke probably feels very real.

Read More

Diablo 4 Patch Confirms the Obducite Drought Wasn’t Just Player Paranoia

 

Diablo 4 players who felt like Obducite had been buried in a locked coffin under a second locked coffin may have just received the closest thing Sanctuary gets to validation.

Blizzard’s latest Diablo IV patch notes include one very small line with some very loud implications: the team has fixed an issue where Obducite “did not drop from all expected enemies in Nightmare Dungeons.” Translation: if your material grind felt strangely dry, you may not have been losing your mind. Well, not about this part.

The Obducite grind finally gets an official bug fix

Obducite matters because it sits right in the uncomfortable middle of Diablo 4’s endgame loop. Players need it for Masterworking, which means it directly affects how quickly a decent build becomes a properly dangerous one. When that material flow feels bad, the whole gear chase starts to feel like pushing a corpse wagon uphill.

For weeks, players have been arguing over whether the Obducite economy was too stingy, badly tuned, or simply bugged. A recent Reddit discussion about the lack of Obducite captured that mood pretty well, with players trading farming routes, frustration, and the usual endgame math that starts as theorycrafting and ends as mild self-harm.

Nightmare Dungeons were supposed to be the answer

The awkward part is that Nightmare Dungeons are meant to be one of the main places players go for this kind of progression fuel. When those dungeons do not reliably pay out from expected enemies, the whole loop starts to wobble. Players are not just complaining that they want more candy. They are asking why the candy machine sometimes accepts the coin and then coughs dust.

That is why this patch note lands harder than its size suggests. Blizzard is not saying “we increased Obducite because people complained.” It is saying something in the drop logic was not behaving as expected. That is a very different beast, and it gives the past few weeks of complaints a sharper edge.

The patch does more than fix one material problem

Patch 3.0.1 also improves Tower rewards, renames the activity to The Artificer’s Tower, and changes weapon-socketed gems so they now carry new multiplicative damage bonuses. That is a chunky little systems pass, especially with Lord of Hatred pre-download and launch timing already putting players into expansion-prep mode.

It also fits the broader picture Blizzard has been selling around Lord of Hatred’s endgame pitch: less dead weight, cleaner progression, and fewer systems that feel like they were assembled in the dark by a treasure goblin with a hangover.

Now players will test the fix the ugly way

The real verdict will not come from the patch notes. It will come from players running Nightmare Dungeons until their eyes turn into sigils and checking whether Obducite actually flows better.

For now, though, this is a good fix on paper and a slightly funny admission in practice. Diablo players spent weeks saying the grind felt wrong. Blizzard has now confirmed that, yes, at least part of the machine really was coughing dust.

Read More

Diablo 2 Resurrected PTR Herald Loot May Be Overtuned

 

Blizzard spent the last stretch of Diablo II: Resurrected feedback hearing that the new Herald system felt stingy, slow, and a bit like doing paperwork in a graveyard. Now the PTR may have pushed things hard in the other direction. A fresh Diablo II: Resurrected forum thread says testers farmed Heralds for about 12 combined hours and came away with a loot pile that included 32 Rainbow Facets, 2 Stones of Jordan, 7 Raven Frosts, a Mara’s Kaleidoscope, and more. That is not exactly “one nice drop if you behave.” That is PTR loot starting to look like it found the emergency wine cabinet.

Why players think Herald loot may be overtuned

The reaction is not coming out of nowhere. Blizzard’s official PTR 3.2 notes say Heralds now have a better shot at dropping Latent Sunder Charms starting from Tier 2 instead of Tier 4, that the drop chance is no longer heavily modified by player count, and that if a Herald fails to drop a Latent Sunder Charm, it now has an increased chance to drop “something desirable instead, like a charm or amulet.” Blizzard also says the goal is for players to have a very high chance of seeing both a Tier 1 and Tier 2 Herald in a single Terrorized Zone. That is a lot of pressure being added to one farming loop all at once. 

This is funny because the mood was the exact opposite a minute ago

That is what makes the story click. Diabloz already covered how players were tearing into the Herald system for wasting time and not paying out enough. The forum mood then was basically “why am I doing this?” Now the live PTR discussion has active threads like “Herald drops are……” sitting near the top of General Discussion while players debate whether Herald farming is suddenly too rewarding. Diablo II does love making the community choose between famine and absurdity, with very little polite middle ground. 

To be fair, this is PTR territory

That disclaimer matters. PTR loot is not the same thing as final live balance, and Blizzard often uses these windows to test systems while players stress them in ways no sane human being would normally schedule. There is also disagreement in the thread itself, with some players arguing Heralds already had good elite-unique loot and that the real difference now is simply that Heralds are spawning more often and getting farmed more aggressively. So no, this is not proof Diablo II: Resurrected has permanently turned Heralds into jackpot vending machines. But it is a very fair sign that Blizzard’s fix for “Heralds feel bad” may currently be landing closer to “Heralds feel drunk.”

Read More

Diablo 4 Barbarian Dagger Drops Look Bugged

 

Diablo 4 has another fresh loot-table headache on the board, and this one is almost funny until you remember it is happening in a game built around showering players with gear. A new official PC bug report says Barbarians are getting dagger drops during Season 12, even though the player says those daggers are unusable on the class and appear in red. The stranger part is that these are not just random daggers falling out of the sky for no reason. The report says they are rolling with Barbarian-specific affixes, which makes the whole thing feel less like bad luck and more like the loot system wandering into the wrong class room with a clipboard and no supervision.

What the report actually claims

The April 24 thread is very direct. The player says they have been getting dagger drops “quite often” on Barbarian this season, that the daggers show up with Barbarian-specific affixes, and that they do not have another character who can use daggers. They also point out something important: other incompatible item types do not seem to be dropping the same way. That is what gives the complaint some teeth. If it were one weird item in isolation, you could shrug and move on. If one specific weapon type keeps slipping through with class-specific rolls attached, that starts to look like an actual loot-pool problem.

Why this is a bad look for Barbarian loot

Blizzard’s own Diablo IV material frames the Barbarian around its Arsenal identity, built on wielding multiple weapon types in close combat, with examples centered on things like two-handed maces and hand axes rather than daggers. So when a Barbarian is apparently receiving dagger drops with Barbarian affixes attached, the complaint is not just “I found vendor trash.” It is “the game seems confused about what my class is supposed to be using.” In a loot game, that distinction matters a lot.

It also fits the current Diablo 4 itemization mood

This lands at a time when Diabloz has already been tracking other item and reward weirdness, including the recent Mythic level-requirement confusion for alt characters. Different issue, same rotten smell: players trying to make sense of gear systems that do not feel as clean as they should. Diablo can survive harsh drop rates. What it handles less gracefully is loot that looks like it was generated by a treasure goblin with a concussion.

For now, this stays in bug-watch territory

At the time of writing, the thread is live in Blizzard’s PC Bug Report section and does not show a visible Blizzard reply yet. So no, this is not proof that every Barbarian in Sanctuary is drowning in unusable daggers. But it is a clean enough report to watch, because the complaint is specific, class-bound, and easy to understand: if a Barbarian is getting repeated dagger drops with Barbarian affixes on them, the loot table is doing something it probably should not be doing. And in Diablo 4, players usually notice that kind of nonsense fast.

Read More

Diablo 4 Grandfather Drop Vanished After Disconnect

 

Diablo 4 has another ugly bug-watch story on the board, and this one hits the exact part of the game that is supposed to feel euphoric. A fresh official PC bug report says a player got The Grandfather from Andariel, got disconnected immediately after the drop, then logged back in to find the Mythic gone. Worse, the player says the rollback did not return the boss keys either. That is not just bad luck. That is the kind of story that makes a loot game feel like it pickpocketed its own jackpot moment.

A brutal story, even if it is only one report so far

According to the thread, this happened on the player’s 12th Andariel run. They say the Grandfather dropped, the game disconnected, and when they got back in, the item was gone from the ground and not sitting in stash either. The player also says the rollback did not refund the keys used for the run. At the time of writing, the thread is live in Blizzard’s PC Bug Report section and does not show a visible Blizzard reply yet, so this is still best treated as a single-report bug watch rather than proof of a widespread issue. But for a Mythic drop, one report is enough to make people nervous fast.

Why this one stings harder than a normal disconnect

Because this is not some random trash loot from a forgettable dungeon clear. This is The Grandfather, one of Diablo 4’s Mythic Uniques, dropping from one of the game’s marquee boss-farming targets. If you are running Andariel, you are already deep in the grind loop and burning resources for a shot at exactly this kind of payoff. Diabloz has covered how the Ritual of Anguish works for Andariel farming, and that context matters here: these runs are not free, and Mythic jackpots are the whole reason players put up with the ritual in the first place.

This is exactly the sort of rollback horror story players hate

Loot games can survive bad RNG. They can survive long dry spells. What they do not survive gracefully is a moment where the rare item actually appears, then the server yanks the floorboards out and pretends it never happened. That is a very different kind of frustration because it does not feel unlucky. It feels invalidating. And right now, with players already arguing over Mythic rules and requirements, Diablo 4 really did not need a fresh story about the loot disappearing after it finally showed up.

For now, this stays in rollback-watch territory

There is no visible Blizzard acknowledgment on the thread yet, and no pile of matching reports behind it at the moment. So no, this is not enough to claim Andariel is broadly eating Mythics. But it is exactly the kind of report worth watching, because when a rare drop vanishes on disconnect and the keys vanish with it, players do not just lose an item. They lose trust in the whole boss-farm loop. In Diablo, that is a much nastier loss.

Read More

Diablo 4 Mythic Level Rules Are Confusing Alt Players

 

Diablo 4 has stumbled into another itemization mess, and this one is especially good at irritating anyone who likes gearing alts. A fresh General Discussion thread asks whether Mythic Uniques are now level 60 only after a player tried to equip one on a level 35 character and found it locked at 60 instead. That would be annoying enough on its own. The more classic Diablo 4 twist is that other players immediately replied saying some Mythics still show level 35 while others show level 60, which makes the whole thing feel less like a clean rule change and more like item logic wandering around unsupervised.

Players do not even agree on what the rule is

That is what makes this story work. In the new April 24 thread, one reply says “some pieces are Lv.60, some pieces are 35,” while older April discussion around the same issue says natural drops seem to be showing up at level 60, crafted Mythics can still appear at 35, and lower-level characters opening certain caches may still get level 35 versions. Another player even claims Mythics can jump from 35 to 60 when they are modified. None of that adds up to a clean, player-friendly system. It adds up to people trying to reverse-engineer loot rules from a pile of contradictory item tooltips.

Why alt players are the ones getting punched here

The loudest frustration is not really about one number on an item. It is about what that number does to alt progression. In the early-April discussion, multiple players say level 60 requirements “suck the joy out of leveling alts” because Mythics used to be one of the funniest ways to turn a fresh character into a temporary monster at level 35. That is not some fringe complaint either. Diablo players love hand-me-down power. Taking that away, or making it inconsistent enough that nobody knows what will happen, kills a very specific kind of fun fast.

The weird part is that Blizzard does not appear to have clearly announced this

That is where the irritation gets sharper. Blizzard’s Patch 2.6 notes do mention Mythic-related changes and bug fixes, including a fix for Mythic Uniques not dropping with Greater Affixes, but there is no obvious note in that patch summary saying Mythic equip requirements were deliberately changed from 35 to 60 across the board. That does not prove the current behavior is a bug. But when players are actively reporting mixed results and the official notes do not clearly explain the new rule, Blizzard is basically outsourcing item clarity to rumor and forum archaeology.

Right now, this looks messy more than settled

So no, this does not read like a simple “Blizzard nerfed alt fun” story with a neat little bow on it. It reads like Diablo 4 has Mythics in two or three different states depending on how they dropped, who opened what, or what got done to the item afterward. That is a bad look this close to Lord of Hatred launch prep, especially when players are already trying to sort characters, gear plans, and stash clutter before the expansion lands. Diablo can survive brutal systems. What it keeps struggling with is systems that feel like they were explained by a drunk treasure goblin.

Read More

Diablo 4 Lord of Hatred Pre-Download and Launch Times

 

If you have spent the last day asking when you can finally preload Lord of Hatred, you are not alone. Blizzard has now posted the full “Prepare for the Reckoning” launch guide, and it answers the stuff players actually care about: when pre-download starts, when the rollout begins, what is free for everyone, and what extra launch-week bait Blizzard is hanging in front of the player base. The timing matters too, because players were already asking “Where is the pre-download?” on the official forums today. 

Pre-download is up now for the platforms that matter

Blizzard says pre-download for Lord of Hatred and patch 3.0.0 began on April 23 at 4:00 p.m. PDT for Battle.net, Xbox, and PlayStation. More importantly, Blizzard also says you can pre-download the 3.0.0 patch whether or not you bought the expansion, which is useful because not everyone wants to make a purchase decision while half-awake and staring at a progress bar. If you play Diablo IV at all, you may as well get the patch loaded now instead of pretending Future You is going to handle it gracefully.

Launch starts rolling out on April 27

The actual Lord of Hatred rollout begins on April 27 at 4:00 p.m. PDT, according to Blizzard’s global launch schedule. Then, half an hour later, the Season of Reckoning kicks off at 4:30 p.m. PDT. That season is a bit of an odd duck, because Blizzard says it does not introduce a new seasonal story, theme, or gameplay gimmick. Instead, it leans on the expansion’s major system changes, including the reworked progression and broader gameplay updates, to carry the season. That is either refreshingly clean or slightly lazy, depending on how charitable you are feeling today.

There is also the usual launch-week sugar pile

Blizzard is padding launch week with a few extras. The Hatred’s Downfall Community Challenge promises the Crown of Hatred to all Diablo IV players if the community reaches 266,600,000 global Paragon Points. On top of that, Blizzard has lined up Lord of Hatred launch Twitch Drops beginning April 27 at 4:00 p.m. PDT, with additional weekly rewards following into May. So yes, the expansion is the headline, but Blizzard is also very clearly doing that live-service thing where every doorway into launch has another shiny object hanging over it. 

The useful version

Here is the clean takeaway: if you plan to play Diablo IV next week, preload now, check Blizzard’s launch map, and stop guessing. The official information is finally live, and this is one of those rare cases where the boring logistics story is actually the most useful one on the board. Sanctuary will still be full of arguments in a few days. At least your install does not have to be one of them. 

Read More

Diablo 4 Lord of Hatred Trailer Pushes the Endgame Hard

The new official Lord of Hatred launch trailer has finally landed, and the interesting thing is not that Blizzard made another expensive-looking Diablo video. Of course it did. The more useful takeaway is that the trailer phase now feels less like mystery-building and more like a blunt sales pitch for what Blizzard thinks actually matters six days before launch: Mephisto, Skovos, two new classes, and a much bigger systems reset than the average expansion usually dares to promise.

This is no longer just a story expansion pitch

Blizzard’s official Lord of Hatred page makes that crystal clear. Yes, the campaign centers on Neyrelle, Mephisto, and the corruption spreading into the sacred isles of Skovos. But the real weight of the marketing is sitting on the systems side: major skill tree reworks for every class, level-cap increases, a new loot filter, skill variants, the Horadric Cube, the new Talisman system, War Plans for endgame progression, and Echoing Hatred as a new horde-style test. That is not small-print support material. That is Blizzard telling players the expansion needs to feel like a structural shake-up, not just more cutscenes and another haunted coastline.

The trailer is really selling three things

First, it is selling Mephisto as the obvious center of gravity. Second, it is selling class fantasy hard. Blizzard is already letting players access the Paladin immediately through pre-purchase, while the Warlock is positioned as the darker counterweight and gets its own full feature spotlight in Blizzard’s Warlock class overview. Third, it is selling the idea that Lord of Hatred is where Diablo 4 finally stops tiptoeing around its broader progression problems and starts rearranging the furniture properly.

That last part is the real hook

Because honestly, Diablo 4 does not need another trailer that only says “evil is back” in a dramatic voice. It needs a reason for players to believe this expansion changes how the game feels after the credits roll. That is why the launch marketing keeps hammering endgame, customization, and class identity. Even Xbox’s store copy frames Lord of Hatred around the new campaign, Skovos, two new classes, and “major updates like an overhauled endgame, transmutation, and set bonuses.” Blizzard knows where the pressure is.

The real test starts after the trailer glow wears off

That is where Diabloz readers should probably keep their eyebrows raised. We already looked at the pre-launch prep side, and we have been tracking how skill tree overhaul talk keeps surfacing around this expansion. The launch trailer does its job well enough: it makes Lord of Hatred look big, costly, and confident. But six days from release, Blizzard is no longer being judged on vibes. It is being judged on whether all those promised systems actually land without turning Sanctuary into another bug diary with prettier lighting.

Read More

Diablo 2 Resurrected Chronicle Still Feels Unfinished

 

When Reign of the Warlock first hit Diablo II: Resurrected, the Chronicle system looked like one of the smartest additions in the whole package. On paper, it is exactly the kind of thing long-time loot goblins want: an in-game way to track uniques, sets, and runewords, plus where and when they dropped. In practice, though, Chronicle keeps showing up on Blizzard’s bug boards for all the wrong reasons. And at this point, that is starting to feel less like launch dust and more like a feature that still is not fully settled in its own skin.

The promise was great

Blizzard pitched Chronicle as a clean way to track “every item you’ve ever collected” in-game, including uniques, sets, and runewords. That is a genuinely strong idea for Diablo II, especially in a game where players have spent years building mule armies and homemade checklists like medieval tax records. The problem is that Chronicle has kept colliding with reality. Blizzard’s own known issues thread at launch already listed Chronicle bugs, including crashes, incorrect runeword labeling, and “eligible” text appearing when it should not. So yes, the warning signs were there early.

The ugly part is that the bug list did not really stop

Fast forward to April, and Blizzard’s Diablo II: Resurrected bug board is still littered with Chronicle complaints. Recent reports include found items not registering correctly, Chronicle rewards not staying selected between games, Town Portal reward issues, and players saying they have to re-enable cosmetic rewards every single session. One of the roughest reports came in March, when an offline player said their Chronicle progress dropped all the way back to 0% after previously reaching nearly 50% on uniques and 58% on sets. That is not a cosmetic annoyance. That is the kind of bug that makes collectors stare at the screen like the game just stole their weekend.

To Blizzard’s credit, some fixes have landed

This is not a case of Blizzard doing absolutely nothing. Patch 3.1.1 in February fixed several Chronicle-related issues, including the wrong runeword name showing up, the false “eligible” text, and a Nintendo Switch Chronicle crash. That matters. But it also makes the current situation more frustrating, because Chronicle is now in that awkward zone where it is clearly live, clearly useful, and still clearly unreliable for a chunk of players. That is almost worse than a feature being obviously broken, because it keeps tempting people to trust it.

Right now, Chronicle feels like a great idea with loose bolts

That is the real headline. Chronicle is still one of the best ideas in Reign of the Warlock, but the April bug traffic makes it hard to call the feature fully locked down. Some of the issues may be platform-specific. Some may hit offline harder than online. Some are clearly quality-of-life annoyances rather than total feature killers. Even so, when your item-history system forgets items, forgets cosmetics, or in the worst case seems to forget progress, players are going to stop treating it like a trophy case and start treating it like a haunted filing cabinet. For Diablo II, that is a very on-brand problem. It is also one Blizzard still needs to finish cleaning up.

Read More

Diablo 4 Missing Skill Point Bug Still Frustrates Players

 

Diablo 4 has another bug report making the rounds, and this one is not flashy enough to dominate a trailer breakdown or set Reddit on fire. It is worse in a quieter way. A fresh official PC bug report says a level 60 Eternal Druid with every renown tier completed, including Nahantu, is still stuck at 70 skill points instead of 71. After refunding everything in respec mode, the player says the game still only gives back 70 points to spend. That is the kind of bug that does not scream. It just sits there and ruins your build by one stupid little notch.

What the player is actually reporting

The new April 23 thread is pretty direct. The player says they finished every renown tier for every zone, claimed all of them, and still cannot reach the expected cap. They also note that the usual forum folklore about “level up a bit more and the points come back” is not much help here, because this character is already level 60 and sitting at cap. So this is not just a UI hiccup during leveling. It looks more like the game deciding one of the most basic build resources in Diablo 4 is optional.

This is not a new complaint crawling out of the swamp

That is what gives the story teeth. Diablo 4 players were already posting about missing skill points back in June 2023, including reports of renown rewards not properly counting and respec behavior making points seem to vanish. More recently, players were still reporting the same broader issue in January 2026 and March 2026, with max-level characters saying they were stuck on 69 instead of 71 even after hitting full renown progress. So no, this does not look like some charming new one-day glitch. It looks like one of those bugs that keeps getting dragged behind the game like a tin can tied to a hearse.

Why one missing point matters more than it sounds

In a game like Diablo 4, one missing skill point is not just a cosmetic accounting error. It can break a build path, force compromises, or lock players out of the exact setup they are trying to run. That gets even more annoying with Lord of Hatred this close, because players are already thinking harder about skill allocation, respecs, and future build planning. We have already touched on that broader pressure in our Lord of Hatred prep guide and earlier speculation around possible skill system changes. This is exactly the wrong time for the live game to be casually eating part of a character sheet.

Still a bug-watch, but an ugly one

At the time of writing, the new thread is live in Blizzard’s PC Bug Report section and does not show a visible Blizzard reply. So this is still bug-watch territory, not proof that every max-level character in Sanctuary is secretly underfunded. But when the same type of complaint keeps resurfacing across multiple years, it stops sounding like isolated player confusion and starts sounding like one of Diablo 4’s favorite bad habits. A missing skill point may be small on paper. In practice, it is the kind of bug that makes a finished character feel unfinished.

Read More

Diablo 4 Hydra Enchant Bug May Cut Sorcerer Damage

 

Diablo 4 has another fresh bug report on the board, and this one lands right on a build interaction that should feel clever, not self-destructive. A new official PC bug report says Hydra Sorcerer damage drops hard when the Hydra Enchantment effect kicks in. According to the player, normal Hydra burn ticks usually climb to roughly 110–130 million, but once the enchant-spawned Hydra appears after crossing the 200 Mana threshold, both Hydras fall to around 50 million burn ticks instead. That is not a cute little edge-case. That is your “bonus” mechanic apparently showing up with a crowbar and kneecapping the build.

What the report is actually claiming

The player says this happens specifically on a burn-focused Hydra setup that also stacks extra heads through passives and gear. Their theory is that the enchant-spawned Hydra is not being treated as a separate entity, and that its fixed head count may be overwriting the extra-head scaling on the regular Hydra as well. In plain English: instead of getting a free extra summon, the whole setup may be collapsing into a worse version of itself the moment the enchant effect procs. For a Sorcerer build built around sustained burn pressure, that is brutal.

Why Sorcerer players will care about this one fast

This is not some obscure cosmetic annoyance buried in a menu. It is a build-performance complaint, and those travel fast because players notice them immediately in boss fights, pit runs, and any content where damage consistency matters. It is also the kind of bug that feels especially dirty because the enchantment system is supposed to add power or utility, not quietly shave huge chunks off your output. If the report is accurate, Hydra Enchant is not just underperforming. It is acting like a trap option for a build that should want it.

For now, this stays in build-specific bug-watch territory

There is an important caveat here: at the time of writing, the thread is very new, sitting in Blizzard’s PC Bug Report section with no visible Blizzard reply yet. So no, this is not proof that every Hydra Sorcerer in Sanctuary is broken in exactly the same way. But it is a very clean technical complaint with clear numbers, a clear trigger, and a very obvious “this should not work like this” logic behind it. Those are usually the bug reports worth watching.

Sorcerer does not need another hidden tax

That is really the whole problem. Diablo 4 already has enough weirdness this season without builds punishing players for slotting the mechanic that looks like it should help. Diabloz has recently covered how Season 12 bugs have been making party play rougher, and even yesterday’s Duriel instant-death report involved a Hydra Sorcerer setup in the mix. If Hydra Enchant is now quietly cutting Hydra damage in half, Sorc players have every right to be annoyed. A class mechanic should not feel like a sabotage button with nice branding.

Read More

Diablo Immortal Fierce Pursuit May Be Missing Tasks

 

Diablo Immortal has another Fierce Pursuit problem on the table, and this one looks nastier than a tracker counting one kill when it should count three. A fresh official bug report says the event launched without the expected Survivor’s Bane tasks for week one, even though Blizzard’s own event breakdown lists April 22 to April 29 as the Survivor’s Bane phase of the rotation. If that is accurate, this is not just a small UI hiccup. It is the kind of thing that makes the whole event reward ladder feel crooked from day one.

What players say is missing

According to the forum post, Fierce Pursuit currently shows only Weekly Tasks and Defense of Cyrangar-related objectives, with no Survivor’s Bane tasks available at all. One reply says they completed every available objective except the “level up five times” task and still only reached 202 points, while the first week should total 282 points. That leaves a gap of 70 points, which is a lot harder to shrug off than the usual “maybe I missed one checkbox” confusion.

Why this looks bigger than one annoyed forum post

The complaint lines up with Blizzard’s own official event details, which say each week of Fierce Pursuit is built around a featured gameplay mode and specifically list Survivor’s Bane as the first week’s focus. A matching Reddit bug post is also circulating with the same basic argument: week one is supposed to revolve around Survivor’s Bane, but the event tasks do not reflect that in-game. That does not prove the entire player base is blocked, but it does make this look less like one lonely player hallucinating at the reward screen.

That is bad timing for Fierce Pursuit

It is especially bad because Diabloz already covered one early Fierce Pursuit bug tied to Castle Cyrangar boss kills not counting properly. If the event is now also missing an entire set of week-one Survivor’s Bane objectives, then Fierce Pursuit is starting to feel less like a clean limited-time reward push and more like a haunted spreadsheet wearing DOOM armor. That is funny for about eight seconds, and then players start asking whether the reward path can actually be trusted.

Another bug-watch, but a stronger one

At the time of writing, the thread is live in Blizzard’s Bug Report section, has at least one direct confirmation reply, and does not show a visible Blizzard response yet. So this still sits in bug-watch territory, not full confirmed meltdown territory. But if Blizzard told players Survivor’s Bane would anchor week one and the live event launched without those tasks, that is a pretty ugly own goal. Live-service events can survive grind. What they do not survive gracefully is math that stops adding up on day one.

Read More