Diablo 4 Lord of Hatred May Be Muting ROG Ally Players

 

Diablo 4: Lord of Hatred has already served up quest bugs, hotfixes, loot arguments, and paid-content confusion. Now the expansion may be adding a new handheld-specific irritation to the pile: the sound just giving up and walking into the fog.

A fresh Diablo IV PC bug report says audio can suddenly stop on the ROG Ally Z1 Extreme while playing Lord of Hatred. The player says they are using the handheld optimized presets with 8GB VRAM, and that the issue did not happen before the expansion launched.

The sound cuts out and stays gone

According to the original report, the audio stops suddenly and does not come back until the game is restarted. That is the kind of bug that sounds small until you are actually playing with it. Diablo without sound is weird. Diablo without sound on a handheld is even weirder. Suddenly every demon ambush feels like a cursed mime performance.

Another player in the thread says they are seeing the same issue, with the game freezing for a couple of seconds before the audio drops out. They also suggest a possible workaround: go into options, change the audio output under sound settings, and save. Annoying? Yes. Better than restarting every time? Also yes.

Handheld bugs hit differently

This is not the same kind of problem as a full crash or a campaign blocker, but handheld players have less patience for ritual troubleshooting. The whole point of playing Diablo 4 on a device like the ROG Ally is convenience: sit down, grind, kill things, maybe question your loot decisions, then stop when real life starts yelling.

If audio cuts out mid-session and the fix requires menu-diving every time, that convenience gets stabbed in the ribs. It turns a portable session into a tiny tech-support pilgrimage.

Bug-watch, not a confirmed widespread issue

At the time of writing, this appears to be a small player-submitted report rather than an official Blizzard-confirmed known issue. So no, this is not “Lord of Hatred breaks all ROG Ally audio.” It is a bug-watch item from players using that hardware.

Still, it fits the wider launch-week pattern. Diabloz has already covered Hotfix 4 removing the Pit and Tower portal, early Lord of Hatred hotfixes, and a stack of other small-but-annoying post-launch issues.

Silence is not very metal

If you are playing Diablo 4 on a ROG Ally and the sound drops out, the reported workaround is to change the audio output in the sound settings and save, rather than restarting the whole game. That may not solve the root problem, but it could save a session from becoming a full reboot ceremony.

Lord of Hatred is supposed to sound like Hell clawing through Sanctuary. On ROG Ally, for some players, it apparently sounds like nothing at all. And somehow, that might be even more cursed.

Read More

Diablo 4 Wardrobe Bug Is Back, and It’s Eating the Whole Outfit

 

Diablo 4: Lord of Hatred has brought new systems, new bugs, new hotfixes, and now, apparently, a wardrobe that has decided fashion is no longer a player choice.

A fresh Diablo IV PC bug report says one player has been unable to properly use the Wardrobe since day one of Lord of Hatred. The player claims they cannot pick a pet, change a mount, select trophies, or adjust outfit pieces normally. In true Diablo fashion, even the closet has entered its villain era.

The helm slot allegedly grabs the whole outfit

The strangest part of the report is the outfit selection behavior. According to the player, clicking an item for the helm slot automatically selects the entire gear set instead.

That is not a wardrobe. That is a cursed mannequin with executive authority.

Cosmetic bugs are easy to laugh at until they hit the systems players actually use every day. Pets, mounts, trophies, transmogs, and saved looks are part of how players make their character feel like theirs. If the Wardrobe starts treating every small change like a full outfit takeover, it turns harmless customization into a tiny UI wrestling match.

Reinstalling did not fix it

The player says they tried uninstalling and reinstalling Diablo 4, but the problem remained. That detail matters because it suggests this may not be a simple local hiccup for the affected account or installation.

To be clear, this is still a player-submitted bug report, not a Blizzard-confirmed widespread issue. At the time of writing, it appears to be a small thread rather than a giant forum fire. But the report is specific enough to watch, especially because Wardrobe weirdness has already haunted Diablo 4 before.

Lord of Hatred has been noisy already

This lands during a busy launch window where Diabloz has already covered Hotfix 4 removing the Pit and Tower portal, early Lord of Hatred hotfixes, and several quest or entitlement issues.

The Wardrobe bug is smaller than a campaign blocker or paid-content access problem, obviously. Nobody is losing a class unlock because their helmet menu is possessed. But these smaller bugs still shape launch-week mood because they hit the everyday friction layer — the part of the game players touch between dungeons, builds, and loot arguments.

The closet should not be endgame content

If you are affected, there is no clear official workaround in the thread yet. The obvious first steps are still the boring ones: restart, check account state, avoid making major cosmetic changes if the interface behaves strangely, and document what happens before filing or adding to a bug report.

For everyone else, this is another one for the Lord of Hatred bug-watch board. Diablo 4 has bosses, dungeons, systems, and loot tables to fight. The Wardrobe really does not need to join the enemy roster.

Read More

Diablo 4’s Removed Elixirs May Have Broken an Old Vessel of Hatred Side Quest

 

Diablo 4: Lord of Hatred has been busy changing systems, cleaning up bugs, and generally rearranging Sanctuary’s furniture. Unfortunately, one old side quest may have been left standing in the room holding an item that no longer exists.

A fresh Diablo IV PC bug report says the Vessel of Hatred side quest The Scales of History can no longer be completed because it asks players to hand over an Elixir of Shadow Resistance. The problem? Lord of Hatred removed elixirs, meaning players who do not already have one sitting around may have no way to craft the required item.

An old quest meets a new system change

This is not the usual “monster stuck in a wall” bug. This is more interesting, and honestly more annoying in a design-archaeology sort of way.

The quest appears to belong to the previous Vessel of Hatred content, but Lord of Hatred has changed the surrounding systems. If the quest still checks for an old elixir while the game no longer lets players create that elixir, the quest becomes a little museum exhibit of outdated mechanics. Very educational. Completely useless if you want the quest finished.

The issue may only hit players without old elixirs

The report specifically says the quest is blocked unless the player already has an existing Elixir of Shadow Resistance from before the system change. That distinction matters. If someone kept old elixirs in their inventory or stash, they may be able to get through it. If not, the quest may be stuck asking for a ghost item.

That makes this a weird edge-case bug, but not a harmless one. Side quests are the sort of content players often clean up later, especially after big expansions pull them back into the game. Being punished because you did not hoard a now-removed consumable is peak RPG inventory comedy, except the joke is on your completion log.

Lord of Hatred’s cleanup list keeps growing

Diabloz has already covered Blizzard’s Hotfix 4 changes, including the removed Pit/Tower portal, the Nemesis exploit fix, and another progression blocker getting patched. This Scales of History report is a smaller issue, but it belongs to the same launch-week theme: one system changes, another system complains from the basement.

It also shows why old quest content can be tricky after major overhauls. Removing or replacing a system is one thing. Making sure no quest, NPC, cache, reward, or ancient fetch objective still depends on that system is the real dungeon.

The fix should be simple, at least on paper

If the report is accurate, Blizzard has a few obvious options. Replace the required item, auto-complete that step, make the NPC accept a modern equivalent, or bring back a limited quest-specific way to obtain the old elixir.

Until then, players trying to finish The Scales of History may want to check whether they already have an Elixir of Shadow Resistance before chasing the quest too far. If the game asks for one and your stash is empty, you may not be missing a vendor. You may be staring at a quest that forgot time moved on.

Read More

Diablo 4 Steam Buyer Says Ultimate Edition Didn’t Unlock Lord of Hatred

 

Diablo 4: Lord of Hatred has another launch-week problem report, and this one hits the most dangerous part of any live-service game: paid content not showing up where it should.

A fresh Diablo IV PC bug report says a Steam player bought the Ultimate Edition of Lord of Hatred through the in-game store, received some cosmetic rewards, but still cannot access the core expansion content. That is not the kind of deluxe experience anyone is hoping for. That is the premium version of standing outside the club holding a receipt.

Cosmetics arrived, but the expansion did not

According to the report, the purchase was made on April 22 while playing Diablo IV through Steam. The player says some cosmetic items were granted correctly, which makes the issue stranger: part of the purchase appears to have landed, while the actual expansion access did not.

The reported problems are blunt. The Paladin and Warlock classes remain locked, the game still loads as Vessel of Hatred, and the Steam library does not show ownership of the Ultimate Edition DLC. In other words, the shiny wrapper showed up, but the meal is still missing.

This sounds like an entitlement sync problem

The player describes it as a possible licensing or entitlement sync issue between Blizzard and Steam when purchasing through the in-game store. That makes sense as a working theory, because the report is not simply “my purchase vanished.” It is more awkward than that: cosmetics are there, expansion access is not, and Steam allegedly does not recognize the DLC ownership.

That is exactly the kind of platform-account weirdness that can make support feel like being bounced between two locked doors, both with very professional signage.

Support reportedly sent the player back to bug reports

The report says the player restarted the game and Steam, tried Steam refresh methods, verified game files, confirmed the transaction history, and contacted both Blizzard and Steam support.

According to the post, Blizzard support initially suggested generic Steam refresh troubleshooting. After the issue persisted, the player says they were told Blizzard could not resolve it and were redirected to submit a bug report instead. That may be technically correct from a support-routing perspective, but if you paid for Ultimate and cannot play the expansion, it probably feels about as helpful as a town portal painted on a wall.

Paid-content bugs always feel sharper

Diabloz recently covered how Ultimate buyers were confused by the Battle Pass token flow, but this report is a different beast. The Battle Pass issue looked partly like UI confusion. This one is a player saying the expansion itself is not being applied correctly through Steam.

For now, this should be treated as a single bug report, not proof of a widespread Steam problem. Still, the category is serious. When paid expansion access, locked classes, and account entitlements collide, players do not care whether the villain is Steam, Blizzard, a sync delay, or some gremlin in the transaction pipe. They care that the content they bought is not playable.

Check your Steam ownership before assuming it is fixed

If you bought Lord of Hatred Ultimate through Steam and something looks wrong, check the in-game entitlements, your Steam DLC ownership, and your transaction history before buying anything twice. Screenshots are your friend here, because launch-week support conversations have a nasty habit of turning into paperwork dungeons.

This may end up being a narrow account-sync case. But for the player affected, narrow does not matter. Paying for Ultimate and getting locked out of the expansion is not a minor inconvenience. It is Hell with a receipt.

Read More

Diablo 4 Hotfix 4 Deletes the Pit Portal Nobody Asked For

 

Diablo 4: Lord of Hatred has reached that magical launch-week stage where the fixes are coming fast, the forums are warm, and Blizzard is already removing a quality-of-life feature because, apparently, the quality forgot to bring the life.

Blizzard’s latest Hotfix 4 notes for patch 3.0.1 remove the portal that automatically spawned after finishing a Pit or Tower run. Blizzard says the portal was added with quality-of-life intentions, but “missed the mark.” Translation: the button was supposed to help, but instead wandered into the room wearing clown shoes.

The Pit portal has been sent back to Hell

On paper, an exit portal after a run sounds useful. Nobody hates convenience. Diablo players will happily accept shortcuts, stash improvements, cleaner menus, faster resets, and anything else that removes unnecessary friction from the grind.

The problem is that convenience has to land in the right place. If a portal pops up where players do not want it, interrupts flow, causes misclick anxiety, or generally feels like the game is shoving them toward the door, it stops being a quality-of-life feature and starts being a tiny haunted doorman.

The Nemesis farming exploit is dead too

Hotfix 4 also closes a nastier loophole: Blizzard fixed an issue where Nemesis boss lairs could be farmed infinitely by grouping up with other players and swapping difficulties.

That is the kind of exploit that never stays quiet for long. If there is a repeatable reward loop hiding behind party behavior and difficulty swapping, Diablo players will find it, test it, optimize it, name it something stupid, and then act surprised when Blizzard walks in with a hammer.

Another quest blocker gets patched

The hotfix also fixes another issue with The Soil, The Seed, The Fruit, where progression could be blocked if multiple players interacted with chains at the same time. That quest has already been part of Lord of Hatred’s early cleanup cycle, so seeing it appear again is not exactly comforting — but at least it is being addressed.

Diabloz previously covered Blizzard’s first Lord of Hatred hotfixes, and the pattern is clear now: Blizzard is moving quickly, but launch week still has plenty of bones rattling in the walls.

Fast fixes, messy signals

There is a good version of this story. Hotfix 4 shows Blizzard reacting quickly, removing a bad QoL experiment, closing an exploit, fixing a quest blocker, and adding more stability improvements.

There is also the less flattering version: Lord of Hatred’s first week is already a blur of quest blockers, reward fixes, balance corrections, exploit closures, and features being walked back because they annoyed players faster than expected.

Still, this is exactly what launch-week maintenance is supposed to look like. Keep what works. Kill what breaks. Delete the helpful portal that was somehow not helpful. Sanctuary has enough problems without the exit door becoming one of them.

Read More

Diablo Immortal Player Says Rift Talisman Platinum Never Arrived

 

Diablo Immortal has a new “where did my currency go?” bug-watch report, which is never the kind of phrase that makes mobile ARPG players feel calm and moisturized.

A fresh official Diablo Immortal bug report says leftover Rift Talismans were supposed to be automatically converted into Platinum after the recent update and sent through in-game mail. According to the player, that mail never arrived.

The missing conversion claim

The player says they had roughly 16–17 Rift Talismans before the update, then used eight of them to upgrade Leviathan Tomb to four stars. That should have left around 8–9 Talismans remaining for conversion.

Instead, they report checking their mailbox after logging in and finding no Platinum conversion mail at all. Worse, they say other players confirmed receiving their conversion mails, which makes this feel less like “maybe the conversion is delayed for everyone” and more like “why did my account get invited to the empty plate club?”

There may be a login wrinkle too

The same report mentions another odd detail: after the update, the player says they were initially stuck on the “Tap to Play” screen and had to uninstall and reinstall the game before accessing the account again.

That may or may not be connected to the missing Platinum. The thread includes a reply saying the login issue had been noted and documented, but there is no visible Blizzard confirmation in the thread that the Rift Talisman conversion issue is widespread or officially tied to that login problem.

Small report, annoying category

For now, this is a single bug report, not proof of a global currency problem. But it belongs to the category of Diablo Immortal issues that players watch closely because it involves account value, conversion rewards, and resources that should not quietly vanish into the fog.

Diabloz recently covered a legendary gem upgrade glitch report and reports of Legendary Crest runs giving no gems. This Rift Talisman report is different, but it scratches the same uncomfortable nerve: players did the thing, expected the payout, and now the reward appears to be missing.

Check the mail before moving on

If you had leftover Rift Talismans before the update, it is probably worth checking your in-game mail, Platinum balance, and screenshots if you have them. If the conversion never arrived, the bug report thread is the kind of place Blizzard can use to spot patterns.

Currency conversion is not glamorous content. Nobody logs in dreaming of mail accounting. But when the mail accounting fails, suddenly it becomes the most important dungeon in the game.

Read More

Diablo 4 Crown of Ash and Ember Quest May Be Blocked by One Stuck Enemy

 

Diablo 4: Lord of Hatred has another wonderfully specific bug-watch entry, and this one is almost elegant in how annoying it sounds: one enemy, one pillar, one quest that refuses to move on.

A new Diablo IV PC bug report says the Crown of Ash and Ember quest can become impossible to finish because a Corrupted Bowmaiden gets stuck inside the center pillar in the Chamber of Queen Antia. The player says the enemy cannot be killed, which blocks the quest from completing.

One stuck enemy, one blocked quest

That is the kind of bug that sounds tiny until it lands in your evening. Diablo players are used to fighting armies, bosses, elites, cursed rituals, and whatever the loot system has decided to emotionally do to them that day.

But an enemy trapped inside geometry? That is a different beast. You can theorycraft around bad damage. You can outgear a tough fight. You cannot meaningfully negotiate with a Bowmaiden who has apparently chosen pillar-based immortality.

Another player says waiting did not help

The report is still small, so this should not be treated as a confirmed widespread issue. At the time of writing, the thread has a matching reply from another player who says they hit the same problem and waited around 20 minutes for the enemy to come out, but nothing happened.

That detail matters because it makes the issue sound less like a momentary positioning hiccup and more like a proper quest blocker when it occurs. If the missing enemy were simply slow, stuck for a few seconds, or pathing weirdly, that would be one thing. Twenty minutes is not pathing. That is a hostage situation with extra candles.

Lord of Hatred already has quest-bug baggage

This lands after Blizzard has already acknowledged and patched several early expansion problems. Diabloz covered the first Lord of Hatred hotfixes, and Blizzard has continued pushing fixes for launch-week issues.

That does not mean Crown of Ash and Ember is officially confirmed as a major problem. It means players are now watching quest flow very closely, because launch-week campaign blockers are the fastest way to turn excitement into angry tab-switching.

Bug-watch, not panic mode

For now, this is a small but very clean bug-watch story: the quest name is clear, the location is clear, the enemy is named, and at least one other player says they saw the same thing.

If you are running Crown of Ash and Ember and the fight stalls in Chamber of Queen Antia, keep an eye out for a Corrupted Bowmaiden trapped in the central pillar. If that happens, you may not be missing some clever mechanic. You may just be staring at the dumbest kind of Diablo boss: the one the game forgot to let you hit.

Read More

Diablo Immortal Players Say Legendary Crest Runs Gave No Gems

 

Diablo Immortal has another fresh bug-watch story, and this one lands directly in the game’s most radioactive zone: Legendary Crests, Elder Rifts, and the expectation that expensive little tickets should probably produce rewards.

Two new reports on the official Diablo Immortal forums claim that players ran Elder Rifts with Legendary Crests and received no legendary gems afterward. One iOS bug report says a player used 10 Legendary Crests, killed the boss, and did not receive any gems. Another separate report claims two Elder Rift runs with 10 Legendary Crests each produced no gem chest and no gems.

That is not the kind of Rift surprise anyone wants

Legendary Crests are not background clutter. They are one of Diablo Immortal’s most sensitive resources because they sit right at the intersection of progression, builds, spending, and player trust. If someone burns 10 or 20 of them and walks away empty-handed, the reaction is not going to be mild curiosity. It is going to be “excuse me, where did my loot go?” but with more smoke coming out of the keyboard.

The first report says the player used the new legendary gem banner with Blood-Soaked Jade selected as the 50% drop option, but did not select any two-star gems. The second report also mentions an incomplete new gem selection, saying only the five-star option was selected and not the two-star selection.

The new gem selection may be part of the mystery

That repeated detail is the most interesting part. Both reports point toward the new gem selection/banner flow in some way, though that does not prove it caused the issue. It could be coincidence. It could be a weird edge case. It could be players bumping into unclear system behavior. Or it could be the sort of bug that makes everyone suddenly read every menu like it is a contract written by a demon accountant.

At the time of writing, this does not appear to be officially confirmed by Blizzard as a widespread issue. The threads are player-submitted bug reports, and one reply asks whether delayed rewards or mail delivery might explain the missing gems. In the 10-Crest thread, the original poster later says no mail arrived after almost two hours and that logging out, force closing, and relaunching did not fix it.

Immortal bugs feel worse when paid resources are involved

Diabloz recently covered a legendary gem upgrade glitch report where a player said materials vanished without progress. This new Crest issue sits in the same uncomfortable category: limited data, very high anxiety.

That is the problem with Diablo Immortal bug reports around gems and crests. Even if only a small number of players are affected, the subject matter is expensive enough that nobody shrugs it off. A missing cosmetic is annoying. A missing gem chest after Legendary Crests feels like the game reached into the reward machine and pulled out a receipt for pain.

Screenshot everything before running more Crests

Until Blizzard comments or more reports clarify the pattern, the boring advice is probably the best advice: if you are using the new gem selection flow, double-check every slot before running Legendary Crests. Screenshot your setup, your Crest count, and your reward history if you are worried.

This may turn out to be a narrow issue, a delayed delivery problem, or something tied to incomplete gem selection. But if players are spending Legendary Crests and reporting zero gems, Diablo Immortal has a problem worth watching very closely.

Read More

Diablo 4 Ultimate Buyers Are Confused by the Battle Pass Token

 

Diablo 4: Lord of Hatred has found another way to make launch week feel like a cursed accounting exam. This time, the question is simple: if someone bought the Ultimate edition, why does the Battle Pass screen still look like it wants more Platinum?

A new Diablo IV forum thread has players asking where their Battle Pass unlock token is after buying Lord of Hatred Ultimate. The original poster says the game showed a 2800 Platinum purchase prompt instead of an obvious unlock token, while another player says they also did not see theirs and accidentally spent Platinum.

The token may be hiding in the Reliquary flow

The important detail is that this may be more confusing UI than missing entitlement. One player in the thread shared what they said was a support response, explaining that the token is tied to the Reliquary menu and should appear as a special prompt when selecting the Battle Pass option.

Another reply says players need to click the Battle Pass first, at which point the game should tell them they have a token to use. That is useful information, but it also highlights the problem: if players are afraid to click because the button looks like it costs Platinum, the interface is already doing a tiny betrayal dance.

The 2800 Platinum prompt is causing panic

Part of the confusion appears to come from the difference between Battle Pass tiers. One reply says the token works for the mid-tier Battle Pass, not the highest one. That matters because the higher-tier option can still show a bigger Platinum price, which makes the whole thing feel less like a reward and more like a shop trap with candles around it.

To be clear, this does not currently look like Blizzard has officially confirmed a widespread missing-token bug. It is a player discussion with at least one shared support explanation and several confused buyers comparing notes. But when players have paid for the expensive edition, “maybe click the scary purchase-looking thing” is not exactly the most comforting ritual.

Launch week has enough friction already

This lands during a messy Lord of Hatred launch stretch. Diabloz has already covered Blizzard’s Hotfix 3 changes to War Plans rewards and the earlier Lord of Hatred known issues, so the last thing players need is another system that technically works but feels like it was designed by a treasure goblin with a legal department.

Battle Pass confusion is especially dangerous because it touches money, Platinum, and edition bonuses. Players can tolerate a bugged monster. They are much less forgiving when they think they might accidentally spend currency on something they already bought.

Check before feeding the Platinum machine

If you bought Lord of Hatred Ultimate and do not immediately see your Battle Pass token, do not panic-click your way into a purchase. Check the Reliquary tab, select the Battle Pass option carefully, and look for a prompt that offers to use the token instead.

If the prompt never appears, that is when support and bug reporting become the next stop. The token may be there. The problem is that Diablo 4’s UI is making some players feel like they need a dungeon guide just to redeem what they paid for.

Read More

Diablo 4 Hotfix 3 Makes War Plans Less Miserable in Parties

 

Diablo 4: Lord of Hatred is still fresh enough to smell like launch smoke, and Blizzard is already back with another hotfix. This one is not just “some numbers moved around in the basement.” It directly targets one of the expansion’s more annoying early party-play problems.

According to Blizzard’s Hotfix 3 notes for patch 3.0.1, War Plans were not properly rewarding players who jumped in to help friends complete a node. Helpers were supposed to receive a base loot cache and activity meta progression XP. Instead, the cache was bugged and not dropping. Very heroic. Very cooperative. Very “thanks for helping, enjoy this empty plate.”

War Plans helpers should now get paid

The biggest fix is simple: the missing helper cache should now drop properly. Blizzard is also sweetening the deal by increasing helper meta progression XP from the intended 80% to 100%.

That matters because group play lives or dies on whether helping actually feels worthwhile. If players join a friend’s activity and walk away feeling like unpaid dungeon interns, they will stop helping. Diablo is already full of monsters. It does not need social friction pretending to be game design.

The final cache gets better too

Blizzard also says Hotfix 3 improves final cache rewards for War Plans. That is a smart move, because reward feel has already become one of Lord of Hatred’s loudest early arguments.

Diabloz recently covered how players are already debating Lord of Hatred’s loot drought, with some claiming drops feel thin and others defending the new slower gear chase. Better War Plans cache rewards will not settle that whole fight, but at least it makes one part of the expansion’s reward loop look less stingy.

Balance outliers also got the axe

Hotfix 3 also fixes several high-profile balance issues ahead of the first Tower rotation. Sorcerer’s Blizzard was scaling far more than intended with skill point investment, while Druid’s Lightning Storm with the Omnibolt variant could scale infinitely. That is not “strong build energy.” That is “the math goblin escaped containment.”

The patch also fixes Cowl of the Nameless causing Poison Imbuement to deal far higher damage than intended, Heir of Perdition’s stolen buff sometimes lasting too long, and several Charm or Seal-related issues.

The patch hammer is still swinging

This follows Blizzard’s earlier Lord of Hatred hotfixes, which tackled quest blockers, Talisman Tab problems, overtuned Necromancer variants, and monsters with inflated health.

So yes, launch week is still messy. But Blizzard is moving quickly, and Hotfix 3 is the kind of patch players usually appreciate: less punishment for helping friends, better rewards, and fewer builds powered by cursed spreadsheet explosions.

War Plans may still need more tuning, but at least helping a friend should now feel less like charity work in Hell.

Read More

Diablo Immortal Player Says Legendary Gem Upgrade Ate Their Materials

 

Diablo Immortal has a fresh bug report aimed straight at the part of the game where players get very, very protective: legendary gems. When those materials vanish, nobody calmly says, “Ah well, the spreadsheet spirits were hungry.”

A new Diablo Immortal bug report claims that a progressive legendary gem upgrade consumed two purchased gems and gem power, but failed to increase the main gem’s progress as expected. That is the kind of sentence that makes Immortal players instinctively check their inventory twice.

The report involves a Void Spark upgrade

According to the player, they had a rank 6, 48% progressive, 4/5 quality Void Spark. They then purchased two 2/5 quality Void Spark gems from the platinum auction house and went to the jeweler to upgrade it.

The expected result, according to the report, was that the gem would move from 48% progress to 64%. Instead, the player says both gems and gem power were consumed, while the Void Spark stayed at 48%. In loot-game language, that is not a hiccup. That is the machine eating your offering and refusing to blink.

This is bug-watch, not a confirmed widespread issue

At the time of writing, the thread appears to be a single iOS bug report without a visible Blizzard response. So this should not be treated as proof that progressive legendary gem upgrades are broken for everyone.

But it is still worth watching because of what is involved. Legendary gems are not throwaway junk. They are one of Diablo Immortal’s most sensitive systems, tied to progression, builds, resonance, platinum, and the kind of resource investment that makes players suddenly become forensic accountants.

Immortal bugs feel worse when expensive systems are involved

Diabloz recently covered a separate Diablo Immortal issue where locked items may still get salvaged in a specific bulk-salvage scenario. This new gem report sits in the same panic cabinet: small sample size, but deeply unpleasant if it hits you.

There is a difference between a visual bug and a resource bug. A typo can be annoying. A missing animation can be funny. But when player-owned materials disappear during an upgrade, the mood changes instantly. That is not cosmetic weirdness. That is wallet-adjacent horror with a gem icon.

Check your upgrades before you click again

Until Blizzard comments or more reports appear, the safest advice is boring but practical: pay attention before and after upgrading progressive legendary gems. Screenshotting your gem progress, materials, and upgrade screen is not glamorous, but neither is trying to explain vanished resources after the fact.

For now, this is a single report, not a full-blown crisis. Still, Diablo Immortal players know the rule: when the jeweler starts acting haunted, you stop feeding the furnace and count your gems.

Read More

Diablo 4 Players Say Undercity Tribute Runs Are Dropping Nothing

 

Diablo 4 players can tolerate a lot. Bad rolls, cursed RNG, mobs with suspiciously large health bars, the occasional inventory disaster. But spending a Tribute on an Undercity run and walking away with almost no loot? That is how you summon the ancient demon known as Forum Rage.

A fresh Diablo IV bug report has players saying some Undercity Tribute runs are ending with wildly underwhelming rewards. One player says they used a mythic tribute, cleared the run, killed the final boss, and received exactly one blue item. Another reply claims a Tribute of Armaments run on Hard dropped “literally nothing.”

Tributes are supposed to make loot better

That is the awkward little corpse in the room. Tributes are not just decorative dungeon seasoning. Players use them because they are supposed to improve or target rewards. The whole emotional transaction is simple: spend the thing, do the run, get the loot.

When that loop ends with a single blue item coughing itself onto the floor like a pity receipt, something feels off. Maybe it is a bug. Maybe it is tuning. Maybe the system is behaving in some technically explainable but spiritually offensive way. Either way, players are not going to love it.

This hits right after the loot drought debate

The timing makes this more combustible. Diabloz just covered how players are already arguing over Lord of Hatred’s loot drought debate, with some saying drops feel too thin and others defending the new slower gear chase.

An Undercity Tribute run dropping almost nothing pours oil on that exact fire. There is a big difference between “loot is more deliberate now” and “my reward-enhanced run gave me dungeon lint.” One sounds like design philosophy. The other sounds like the treasure goblin filed for bankruptcy.

Not officially confirmed yet

For now, this should be treated as a bug-watch story, not a confirmed widespread issue. The thread is in the PC Bug Report section, and at the time of writing there does not appear to be a visible Blizzard response in that specific discussion.

Blizzard has already moved quickly on some early Lord of Hatred problems, including the first Lord of Hatred hotfixes, so this is exactly the kind of report worth watching if more players pile on with matching examples.

The worst reward is no reward

Diablo can survive stingy loot. It can survive slow progression. It can even survive players pretending they hate the grind while secretly logging back in five minutes later.

What it struggles with is broken trust in reward systems. If a Tribute run asks players to invest a resource and then spits out almost nothing, that does not feel like bad luck. It feels like the dungeon mugged them politely.

For now, Undercity runners may want to keep an eye on their Tribute results. If the boss drops one blue item after a serious run, congratulations: you did not find loot. You found evidence.

Read More

Diablo 4 Players Are Already Fighting Over Lord of Hatred’s Loot Drought

 

Diablo 4: Lord of Hatred has barely cooled off from launch, and players have already found the most sacred Diablo argument of all: where in Hell is the loot?

A new Diablo IV forum thread has kicked off a messy but useful debate about Lord of Hatred’s early loot feel. Some players say drops now feel thin, unrewarding, and overloaded with blue and yellow items. Others argue that this is exactly the point: gear is supposed to matter more, the Horadric Cube is supposed to do some heavy lifting, and maybe players should not have a finished build three days after launch.

The complaint is simple: too much trash, not enough treasure

The original complaint is blunt. Players are seeing a lot of magic and rare items, and not enough of the big orange dopamine bricks that make Diablo’s loot brain light up like a cursed casino machine.

That frustration makes sense on instinct. Diablo is a loot game. When enemies explode into piles of items and most of it feels immediately disposable, players start asking whether the faucet is broken, tuned too low, or just being weirdly philosophical about scarcity.

The Horadric Cube changes the argument

The counterpoint is that Lord of Hatred has changed what low-tier items are supposed to mean. Several replies in the thread point toward the new Horadric Cube systems, where lower-rarity items are not necessarily just floor confetti anymore.

That is a real design shift. If blue, yellow, and even lower-tier gear now feed into crafting, upgrading, or build construction, then the loot game is not simply “wait for orange, ignore everything else.” The problem is communication and feel. A system can be clever on paper and still feel like someone replaced the treasure goblin with a tax auditor.

Some players like the slower hunt

Not everyone hates the new pace. Some players in the thread argue that fewer instant build-completing drops make the chase more meaningful. One reply says they have found several uniques just by playing through the campaign and like that the hunt feels more deliberate again.

That is the tension Blizzard is playing with. Diablo 4 has spent a lot of time being criticized for loot that felt either too stingy, too spammy, or too quickly solved. Lord of Hatred appears to be pushing toward a slower, more structured loot economy. Whether that feels satisfying or just dry depends heavily on where you are in progression, what class you are playing, and how much patience you have left after your twentieth blue item.

Loot debates are Diablo’s natural weather

Diabloz already covered Blizzard’s first Lord of Hatred hotfixes, which cleaned up some early launch problems. This loot debate is different. It is not clearly a bug. It is a fight over feel.

And feel matters. If players believe the game is asking for more grind while giving fewer meaningful rewards, the conversation gets ugly fast. If the Cube loop clicks, the same system could end up feeling smarter and more satisfying than old-school loot rain.

For now, Lord of Hatred’s loot economy is already on trial. The prosecution says the treasure has gone missing. The defense says players need to learn the new machine. The jury is every Diablo player currently staring at another yellow drop and wondering if this is progression or paperwork.

Read More

Diablo 4’s First Lord of Hatred Hotfixes Are Already Cleaning Up the Bodies

 

Diablo 4: Lord of Hatred has barely had time to get blood on the carpet, and Blizzard is already walking through the launch-day wreckage with a mop, a clipboard, and the haunted expression of a developer who has seen the bug forum.

The studio has posted the first Lord of Hatred hotfix notes for patch 3.0.1, covering both Hotfix 1 and Hotfix 2. The short version: some quest blockers, missing Talisman Tab problems, overtuned Necromancer variants, and monsters with inflated health have already been dragged into the repair pit.

Necromancer pain got trimmed fast

Hotfix 2 takes aim at two Necromancer-related issues that were apparently doing far more damage than intended. Blizzard says the Schadenfreude variant for Iron Maiden and the Bramble variant for Bone Prison have both been fixed after dealing excessive damage.

That is the kind of bug players notice quickly because it does not whisper. It kicks the door open, deletes something, and leaves everyone arguing whether the build was secretly brilliant or just broken in a very flattering way.

Some monsters had way too much health

The same hotfix also fixes monsters that had much higher health values than intended, including Pangs of Duriel and Infernal Prison. In normal Diablo language, that means some enemies were not “challenging.” They were probably just sitting there with a health bar that had wandered into the wrong tax bracket.

Lord of Hatred already has enough new systems, builds, and endgame tuning for players to chew through. Accidentally overfed monsters are not exactly the kind of difficulty curve anyone wants on day one.

Hotfix 1 tackled progression trouble

Hotfix 1 is just as important because it addresses the ugly stuff: progression blockers. Blizzard says it fixed an issue where progress could be blocked during The Soil, The Seed, the Fruit quest.

It also fixed a party-related issue with Last of the Horadrim, where only one party member could receive completion credit, leaving the other players without the Talisman Tab unlocked. Diabloz already covered the early Lord of Hatred known issues, and this is the cleaner follow-up: Blizzard has started patching the launch mess, not just acknowledging it.

The launch smoke is clearing, slowly

None of this means Lord of Hatred is suddenly spotless. Players are still reporting separate problems, including crashes and memory errors on high-end PCs, and launch week is still doing launch-week things.

But fast hotfixes matter. Quest blockers are poison. Missing system tabs are miserable. Overtuned damage and monster health can make balance discussions look like a tavern fight with spreadsheets.

For now, Blizzard is moving quickly, which is exactly what Lord of Hatred needs. Mephisto may be the Lord of Hatred, but the real launch villain is still the bug that wastes your evening.

Read More

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