Diablo 4 Season 13 Boss Farming Is Now Basically Demon Tax Planning

 

Diablo 4’s endgame has reached a beautiful new stage of maturity: players are no longer just killing bosses for loot. They are now consulting loot tables like cursed accountants trying to optimize a demonic retirement portfolio.

With Lord of Hatred and Diablo 4 Season 13, boss farming has become one of the most important parts of the loot chase. If you want a specific Unique, Mythic Unique, Greater Affix roll, or build-defining item, randomly punching everything with horns is no longer the smartest plan. It is still emotionally satisfying, obviously, but the spreadsheets have entered the cathedral.

Boss Loot Tables Matter More Than Ever

The current Diablo 4 Season 13 boss loot tables show just how targeted farming has become. Different lair bosses now carry specific item pools, meaning players chasing particular Uniques need to know which demon to bully and which one to leave brooding in peace.

That sounds simple enough until you remember this is Diablo, a game where “I just need one item” can quietly become a three-hour ritual involving boss materials, build guides, unlucky drops, and increasingly suspicious eye contact with your stash.

Still, the system has a purpose. Targeted loot tables give players a clearer path toward specific gear instead of asking them to throw themselves into the void and hope the void is feeling generous.

Belial Is the Big Suspicious Prize Machine

The most interesting part of the current boss ladder is Belial. According to updated boss guides, Belial sits near the top of the lair boss structure, and his rewards are especially attractive because his hoard can let players choose loot tables from other bosses.

That makes Belial less like a normal boss and more like a very angry vending machine with horns.

He is also tied to better chances at high-value rewards, including items with Greater Affixes and Mythic Uniques. Naturally, that means he is going to become a major farming target for anyone trying to squeeze the most power out of Season 13 without simply praying to the random number gods and sacrificing another evening.

The New Farming Loop Has a Brain Now

This is probably healthy for the endgame. Diablo 4 works better when players can make informed decisions about what they are farming and why. The old “kill whatever, loot whatever, complain forever” loop has its charm, but it does not always respect the player’s time.

Boss-specific loot tables create structure. They let players chase goals. They make build planning feel more deliberate. They also ensure that every serious endgame player eventually becomes the kind of person who says, “Actually, I need to farm this boss for this slot,” which is how you know the ARPG infection has fully taken hold.

Helpful, But Still Very Diablo

The downside is that the system can feel like homework. Want a particular Unique? Check the boss. Want a better roll? Check the table. Want a Mythic? Check the odds, farm the keys, kill the boss, open the hoard, receive disappointment, repeat until morale improves.

That is Diablo. That has always been Diablo. The only difference now is that the game is more honest about the bureaucracy.

Season 13 boss farming gives players a smarter way to hunt power, and Belial adds a nice layer of choice to the grind. It is cleaner, more targeted, and probably better for long-term endgame planning.

But let’s not pretend this is simple. Diablo 4’s loot chase has become a demonic tax form, and Belial is standing at the top of it with a clipboard, a grin, and absolutely no intention of giving you the item you want on the first try.

Read More

Diablo Immortal Just Added Auto-Battle, Because Sanctuary Apparently Needed a Screensaver

 

Diablo Immortal has officially added Auto-Battle, which means Sanctuary has now reached the stage where even demon-slaying can be delegated like a mildly annoying calendar reminder.

The feature arrived as part of the latest content update, titled Raise the Stakes, or Face Your Exile, alongside new Legendary Affixes, PvP changes, Challenge Rift Season 18, Battle Pass 52, and a handful of system improvements.

But let’s be honest. The headline act here is Auto-Battle. Because nothing says “the eternal war between Heaven and Hell” quite like letting your character wander around and farm while you stare into the middle distance.

How Auto-Battle Actually Works

According to the official update, Auto-Battle can be accessed through the Blessing of Legends interface. Once enabled, your character will automatically roam around the nearby area and fight enemies at your current location.

This is not meant to outperform actual human play. Blizzard describes the system as deliberately less efficient than farming manually, with the goal of giving more casual players another way to keep progressing. In other words, it is not supposed to replace playing the game. It is supposed to soften the grind a little.

That distinction matters, because Diablo Immortal is a game built around repetition, resources, upgrades, and the slow transformation of your free time into shiny numbers. Anything that automates even part of that loop is going to raise eyebrows.

There Are Limits, At Least

Auto-Battle is not unlimited. The feature unlocks at level 60, can be enabled for up to one hour at a time, and has a weekly cap of 24 total hours.

There is also one very important catch: your character will not automatically salvage equipment when your bags are full. So if you were imagining a perfect little demon-killing robot printing progress while you live your best life, slow down. Your inventory is still waiting to become everyone’s problem.

There are also settings for Auto Health Potion usage and life thresholds, meaning players can tweak how safely their character behaves while the system is running. That should help, but it also means Auto-Battle now has enough settings to become its own tiny management game.

Convenience or the Point of No Return?

The obvious defense is simple: mobile games are different. Diablo Immortal already lives in a world of daily tasks, currencies, timed systems, and short-session farming. Auto-Battle may just be a realistic response to how many players actually use the game.

The obvious criticism is just as simple: if the game needs an automated farming mode, maybe the grind is starting to look less like gameplay and more like a haunted treadmill.

That is the uncomfortable little skeleton rattling around under this update. Auto-Battle might be useful. It might even be welcome. But it also makes Diablo Immortal look more like a game that knows its own repetition is heavy enough to require machinery.

Diablo Immortal Knows Exactly What It Is

Still, this is probably going to be popular. Plenty of players will use Auto-Battle while doing chores, watching something else, or pretending they are not still emotionally attached to a loot grind that has outlived several healthier hobbies.

And to be fair, Diablo Immortal is not pretending this is high-skill endgame mastery. The feature is capped, limited, less efficient, and clearly aimed at casual farming rather than elite play.

But the optics are deliciously cursed.

Diablo Immortal now has an official mode where your character can grind demons without you. In a franchise about endless hunger, cursed power, and questionable life choices, that is almost poetic.

Sanctuary has automated the slaughter. Somewhere, a Treasure Goblin just updated its LinkedIn.

Read More

Diablo 4 Brought Back Set Bonuses, and Players Are Losing Their Minds

 

Diablo 4 has finally gone and touched one of the most radioactive buttons in ARPG history: set bonuses.

With Lord of Hatred, Blizzard introduced the new Talisman system, using Seals and Charms to add extra affixes, build-shaping powers, and yes, set bonuses. For some players, that sounds like exactly the kind of loot depth Diablo 4 has been missing. For others, it sounds like someone dug up Diablo 3’s bones and started rattling them in the town square.

And because this is Diablo, the argument has already turned into a lovely little bonfire.

The Talisman System Is Meant to Supercharge Builds

Blizzard’s official Lord of Hatred preview describes the Talisman as a new item system built around Seals and Charms. Players apply a Seal to unlock Charm slots, then place Charms into those slots to gain additional bonuses.

Set Charms take that further. Instead of traditional armor sets locking your entire character into a rigid costume party, Diablo 4’s set bonuses now come through Charms that work alongside your gear. In theory, that gives players more freedom: your actual equipment still matters, while your Talisman becomes another layer of buildcraft.

That is the clean version. The version written in blood on the forum wall is a little louder.

The “Big Number” Debate Is Back

One active Diablo IV forum thread asks, with admirable restraint, what is going on with the absurd set bonuses. The complaint is simple: several bonuses appear to lean heavily on huge damage multipliers, and some players fear Diablo 4 is drifting into the same “stack the set, explode the screen” territory that defined large parts of Diablo 3.

That comparison matters. Diablo 3’s late-game set design became infamous for massive percentage bonuses that could make unsupported builds feel like they were fighting demons with a damp spoon. Some players loved the power fantasy. Others felt it crushed creativity by turning builds into pre-approved math prisons.

Now Diablo 4 is walking near that same haunted house, holding a candle, saying everything is probably fine.

But Some Players Actually Like the Chaos

The backlash is not universal. Some players are defending the system because, frankly, ARPGs are built on watching numbers become unreasonable. There is a very real audience that wants their character to go from “competent adventurer” to “walking natural disaster with boots.”

And they have a point. Diablo has never been a minimalist combat simulator. It is a game where you collect cursed jewelry so your skeleton tornado can delete a goatman from three counties away. Big numbers are not automatically bad.

The question is whether those numbers create interesting choices — or simply tell players which bonus they are now legally required to equip.

Freedom or Another Invisible Set Prison?

That is the real danger with Diablo 4’s new set bonuses. If Charms create flexible build layers, the Talisman could become one of Lord of Hatred’s best systems. If the strongest set bonuses become mandatory, then the system risks becoming another checklist pretending to be choice.

Blizzard clearly wants Talismans, Charms, and the Horadric Cube to make endgame customization deeper. The idea is strong. The presentation is very Diablo. The community reaction is exactly the kind of screaming cathedral choir you would expect.

For now, Diablo 4’s set bonuses are doing what every powerful ARPG system does at launch: making some players theorycraft, some players panic, and some players type “Diablo 3” like they just spotted a demon in the kitchen.

Sanctuary has new toys. Whether they are brilliant tools or cursed calculators is now the argument.

Read More

Diablo 4 Finally Has a Loot Filter, and Players Are Already Fighting It

 

Diablo 4 players finally got a loot filter. Naturally, the celebration lasted about as long as a level-one skeleton in a bad neighborhood.

With Lord of Hatred and the 3.0.0 update, Blizzard added one of the most requested quality-of-life features in the game’s history: a way to hide, show, or color-code gear drops so players can stop reading every cursed pair of boots like it might contain the meaning of life.

On paper, this is exactly what Diablo 4 needed. In practice, players have already moved into phase two of every ARPG quality-of-life feature: arguing about why it does not go far enough.

The Loot Filter Was Supposed to Save Everyone’s Eyes

Blizzard’s official Lord of Hatred preview describes the new Loot Filter as a tool that can hide, show, or recolor gear items that drop, sit in your inventory, live in your stash, or appear on vendors.

That is a big deal. Diablo 4 has spent a long time drowning players in gear, then politely asking them to inspect the corpse pile for one possible upgrade. A proper filter means fewer inventory autopsies and more actual demon murder, which is generally why people installed the game in the first place.

Blizzard also made it clear that the filter does not affect non-gear items such as temper manuals, reagents, gems, or currency. So yes, Sanctuary is cleaner now — but not exactly sterile.

Then the Bugs Crawled Out

Shortly after launch, Blizzard had to fix a rather awkward issue where items with higher Aspect rolls than the player’s current Codex of Power version were being filtered out by the Loot Filter. That fix appeared in the official Diablo IV 3.0.1a patch notes.

That is not a small problem. If a loot filter hides upgrades, it stops being a helpful servant and becomes a tiny demon with a clipboard. The whole point is to remove trash, not quietly bury the treasure.

To Blizzard’s credit, the fix came quickly. But the incident also explains why some players are treating the new system with suspicion. In an ARPG, trust in your loot filter is sacred. Once players start wondering what they are not seeing, every invisible item becomes a conspiracy theory in boots.

Players Want More Control, Because Of Course They Do

The bigger complaint now is not simply that the Loot Filter exists. It is that many players want it to be sharper, smarter, and less limited.

One forum thread argues that Diablo 4’s Loot Filter lacks basic “NOT” functionality, making it difficult to create reverse-style filters. In plain English: players want to say “show me everything except this garbage,” and the system is not always flexible enough to play along.

That matters more now because itemization has changed again, and rare items still have a role in the loot chase. If players cannot filter by the exact things they care about — or exclude the things they already know they hate — the system becomes useful, but not yet elegant.

Console and Couch Co-Op Players Have Their Own Headache

There are also usability complaints. Another player asked for easier access to the Loot Filter on console, suggesting a shortcut or wheel option rather than burying edits deeper in the menus.

Even more painfully, couch co-op players are reporting that the Loot Filter is disabled for local co-op, with one PS5 player calling it a “make or break” issue after buying the expansion to play together. For a feature designed to reduce inventory pain, not having it in couch co-op is basically inviting one player to become the household loot accountant.

A Good Feature With Very Diablo Problems

The funny thing is that the Loot Filter is still a win. Diablo 4 needed this. Players wanted this. The game is better with it than without it.

But the first version also feels like exactly that: a first version.

It solves part of the loot problem, then immediately reveals the next five layers underneath. Players want better logic, better access, better co-op support, and more confidence that the filter is not quietly throwing their upgrades into the void.

So yes, Diablo 4 finally has a loot filter. And because this is Diablo 4, the next endgame activity is arguing about the loot filter.

Honestly, that might be the most efficient system Blizzard has added yet.

Read More

Diablo 4 Players Can’t Decide If Lord of Hatred Is Genius or a Disaster

 

There are two types of Diablo 4 players right now: the ones calling Lord of Hatred the best thing to happen to the series since Lord of Destruction, and the ones looking at that sentence like someone just dropped a cursed rare helmet into their soup.

That is the current mood around Diablo 4’s latest expansion. Not quiet disappointment. Not universal celebration. Something much more useful for the internet: a full-blown Sanctuary shouting match.

And honestly? That may be the most Diablo 4 thing possible.

The Praise Is Surprisingly Loud

Over on the official Diablo IV forums, one player opened a thread calling Lord of Hatred the best Diablo release since Lord of Destruction, arguing that the expansion finally gives Diablo 4 a stronger foundation after years of system changes, reworks, and seasonal duct tape.

The post has already turned into a lively debate, because naturally it has. You cannot praise Diablo 4 online without immediately summoning a mini-boss called Someone Who Disagrees.

The positive side is not hard to understand. Lord of Hatred has thrown a lot at the wall: new progression layers, new loot systems, endgame changes, and a broader attempt to make Diablo 4 feel less like a game being rebuilt in public and more like one with an actual spine.

For players who wanted Diablo 4 to grow teeth again, this expansion seems to be doing something right.

The Backlash Has Teeth Too

Then there is the other camp.

Another active forum thread claims that Diablo 4’s itemization is now worse than it was at launch, with complaints aimed at crafting, loot management, normal/magic/rare item clutter, and the feeling that fighting demons has become too much like doing unpaid inventory administration.

That complaint hits a familiar Diablo nerve. The series lives and dies on loot. If players feel like drops are exciting, the grind becomes holy work. If loot feels like spreadsheet ash, suddenly every dungeon is just a dimly lit office with skeletons.

There are also broader frustration points still floating around: refund posts, performance complaints, campaign pacing arguments, and the usual “Diablo is ruined / Diablo is saved” ritual sacrifice that happens after every major release. One thread even notes that a Lord of Hatred refund had been issued, which tells you the mood is not exactly all candles, loot beams, and polite applause.

The Endgame Argument Is Already Here

The most dangerous debate may be endgame difficulty.

A recent report from GamesRadar highlighted streamer Mekuna clearing the new Torment 12 difficulty tier in just 17 hours, then criticizing the lack of long-term “aspirational content.” In other words, while many players are still trying to understand the new systems, the top-end crowd is already kicking the ceiling and asking why it is made of wet parchment.

That creates a weird problem for the game. Diablo 4 needs to satisfy the person playing two hours after work and the person who treats demon farming like an Olympic event with worse lighting.

This is not a new ARPG problem, but Lord of Hatred has dragged it back into the spotlight. If the climb feels good for casual players but too short for elite players, Blizzard has a balancing act that looks less like game design and more like juggling knives in a blood ritual.

A Messy Win Is Still a Win

So is Lord of Hatred a triumph or a disaster?

Right now, it looks like both — which may actually be better than being boring.

The expansion has clearly given Diablo 4 players something real to argue about beyond “this bug ate my loot” or “this hotfix broke my build.” There is passion here, even when it is wearing a blood-soaked clown wig.

And for Diablo 4, that might be the real sign of life. A dead game gets silence. A live one gets forum wars, loot essays, streamer complaints, and someone somewhere insisting this is secretly the best Diablo has been in 20 years.

Sanctuary is not calm. But at least it is awake.

Read More

Diablo 4 Players Say Glynn’s Anvil Aspect Isn’t Protecting Them

 

Diablo 4: Lord of Hatred has another build-bug report on the board, and this one is especially rude because it concerns damage reduction. That is not a flashy bonus. That is the thing standing between your character and becoming floor decoration with a health globe.

A fresh Diablo IV PC bug report says the reworked Aspect of Glynn’s Anvil may not be applying its defensive effect correctly. The original poster claims the Aspect’s damage reduction is not working, saying they take the same amount of damage whether they have 0, 1, or 20 stacks of Resolve while the Aspect is equipped.

The stat sheet may be lying, or forgetting

The thread gets more interesting with a follow-up from another player, who says the Aspect appears to increase damage reduction on the character sheet after unequipping and re-equipping the item. Their Paladin reportedly jumps from 17.7% to 43.1% damage reduction when they do that.

That sounds promising for about five seconds. Then the same player says going back to town resets the value to 17.7%, and leaving town does not restore it unless they unequip and re-equip the item again.

That is the sort of bug that makes players start treating their gear like a temperamental old printer. Take it off. Put it back on. Hope the numbers remember how to exist.

Paladin builds do not need ghost defenses

If the report is accurate, this could be a nasty problem for Paladin players building around Resolve and defensive uptime. A damage reduction Aspect that only works after a gear-juggling ritual is not exactly reliable buildcraft.

Defensive systems are supposed to be boring in the best possible way. They should sit in the background, do their job, and stop you from being erased by whatever angry thing just sprinted out of a nightmare hallway. If they flicker off because you walked into town, that is not build depth. That is cursed bookkeeping.

Small thread, clear concern

At the time of writing, this appears to be a player-submitted bug report rather than an official Blizzard-confirmed known issue. Still, several replies in the thread say they are seeing the same or similar behavior, and one player calls it easily testable on the target dummy.

That makes this one worth watching. Diabloz has already covered bigger Lord of Hatred issues, including Barbarian’s Limitless Rage being temporarily disabled and players questioning whether War Plan upgrades are working correctly. Glynn’s Anvil is smaller, but it hits the same launch-window nerve: players want to know whether their builds are functioning or merely pretending very confidently.

Check before trusting the Anvil

If you are using Aspect of Glynn’s Anvil, it may be worth checking your damage reduction before and after entering town, changing zones, or re-equipping the item. That does not prove the Aspect is broken for everyone, but it can help affected players spot whether their setup is behaving strangely.

In Diablo, dying because you made a bad play is fair enough. Dying because your defensive Aspect quietly clocked out after a town visit is a different kind of evil. That is not Sanctuary difficulty. That is HR trouble with armor stats.

Read More

Diablo 4 Players Say Cosmic Archives Stronghold Is Still Trapping Them

 

Diablo 4: Lord of Hatred has another stronghold bug-watch story, and this one sounds like the kind of problem that turns “I’ll just clear one more objective” into “why am I locked in a room arguing with architecture?”

A growing Diablo IV PC bug report thread has players reporting trouble inside the Cosmic Archives stronghold. The reports vary, but the theme is painfully consistent: players get stuck, doors stay closed, enemies or quest steps fail to behave, and the only escape sometimes appears to be leaving the game.

The Angelic Wings room seems especially cursed

Several players point to the Angelic Wings room as the main trouble spot. One player says they got stuck after killing Ludea. Another says the objective progressed to the next step, but the door still stayed locked and teleporting out was not possible.

That is the exact flavor of bug that makes a stronghold feel less like a challenge and more like a haunted waiting room. Killing the thing is supposed to open the path. When the path looks at your victory and shrugs, the dungeon has failed the assignment.

Some players blame stagger or killing too fast

The most useful part of the thread is that players are comparing possible workarounds. A few say the issue may happen when the enemy dies while staggered, or when certain damage sources keep hitting during dialogue triggers. One Warlock player says they avoided using Profane Sentinel, stayed close to the door, and managed to progress on a later attempt.

Another player says killing slowly rather than deleting the enemy while staggered helped the room open properly. That is not exactly an elegant solution. “Try playing worse so the quest script does not panic” is not the kind of build guide anyone wanted, but here we are.

It is not just one report anymore

This is still not an official Blizzard-confirmed known issue in that thread, but it is no longer just one isolated complaint either. Players across multiple replies report being stuck, rerunning the stronghold, relogging, and hitting the same locked-room problem again.

One comment says they had to restart the game. Another says they ran the stronghold several times and still got trapped. There are also mentions of enemies getting stuck in walls and earlier steps failing to progress properly, which makes Cosmic Archives sound less like one broken switch and more like a stronghold with several loose floorboards.

Lord of Hatred’s bug board keeps filling up

Diabloz has already covered several Lord of Hatred launch issues, from Hotfix 4 removing the Pit and Tower portal to War Plan upgrade complaints. Cosmic Archives fits neatly into the current pattern: not necessarily game-breaking for everyone, but very capable of ruining a player’s evening when it hits.

Strongholds need clean scripting because they are structured encounters. If a door stays locked after the fight, or a dialogue trigger fails because the enemy died too fast, the player does not feel challenged. They feel punished for being efficient.

Maybe do not vaporize the room

Until Blizzard responds or patches the issue, the best player-suggested workaround appears to be taking the Angelic Wings fight slowly, avoiding a stagger kill, staying near the door or barrier, and being careful with persistent damage effects like Profane Sentinel.

That advice is ridiculous, but it may help. Cosmic Archives should be a stronghold, not a delicate antique machine that breaks if your build is too good at murder. For now, though, players entering it may want to bring patience, screenshots, and a healthy distrust of closed doors.

Read More

Diablo 4 Players Are Already Sick of the Reprisal Affix

 

Diablo 4 players have found a new monster affix to glare at, and this one has a very special talent: making powerful builds accidentally delete themselves.

A new Diablo IV forum thread has kicked off a heated argument over the Reprisal Affix, with players complaining that reflected damage feels cheap, punishing, and wildly out of step with the basic Diablo fantasy of hitting monsters until they stop having opinions.

The complaint: killing things now kills you

The core frustration is easy to understand. Diablo is built around speed, damage, momentum, and turning the screen into a loot-flavored crime scene. Reprisal pushes back on that by reflecting damage, which means a build that hits extremely hard can suddenly become its own worst enemy.

That creates a weird emotional problem. Dying because a boss outplayed you is one thing. Dying because your own damage bounced back like a cursed invoice is another. It does not feel heroic. It feels like Sanctuary installed a “stop having fun” mirror.

Is this difficulty or just punishment?

The debate is not just “affix bad.” The real question is whether Reprisal creates interesting gameplay. In theory, damage reflection can force players to slow down, read enemies, manage burst windows, and avoid brainless screen-clearing.

In practice, some players argue that it mostly tells them to stop attacking, wait awkwardly, or let pets and companions do the work. That is where the affix gets dangerous from a design perspective. Difficulty should make players adjust. It should not make them feel like the correct move is to play less Diablo.

Blizzard has already touched Reprisal once

This is not happening in a vacuum. Recent Diablo IV patch notes tracked by Wowhead’s Blizzard blue tracker mention a fix for Holy damage reflected by the Reprisal Monster Affix doing more damage than intended. So Blizzard clearly knows the affix can land badly when the numbers are off.

That does not automatically mean Reprisal is broken now. It does mean players are extra sensitive to it, especially during a Lord of Hatred launch window already full of balance drama, hotfixes, and disabled power spikes like Barbarian’s Limitless Rage.

Reprisal needs to feel fair, not smug

Monster affixes are at their best when they create fast, readable danger. They should make players react, reposition, and make decisions under pressure.

If Reprisal feels like a clear projectile, a readable window, or a counterplay moment, players may learn to respect it. If it feels like instant punishment for doing exactly what their build is designed to do, the backlash will keep growing.

Diablo players love danger. They even love unfairness when it feels earned. But a monster affix that turns your own damage into a tax collector with a knife? That one was always going to start a fight.

Read More

Diablo 4 Players Say War Plan Upgrades Still Aren’t Working Right

 

Diablo 4: Lord of Hatred has already had a hotfix aimed at making War Plans feel less miserable in parties, but the system may not be done causing headaches yet. Because apparently Sanctuary’s newest endgame paperwork has layers.

A fresh Diablo IV forum thread has players questioning whether some War Plan upgrades are actually working as advertised. The main complaint focuses on a Tier 3 Infernal Hordes upgrade that says players should get a challenge at the start of an Infernal Horde, with +200 Aether awarded if that challenge is completed.

The challenge allegedly never appeared

The player says no challenge appeared, no notification showed up, and no +200 Aether was awarded. They also say they earned plenty of Aether during the run, so if a challenge had quietly existed in the background, it should probably have been completed naturally.

That is exactly the kind of vague system behavior that makes players suspicious. If an upgrade is supposed to trigger a challenge, players need to see the challenge. Diablo 4 already has enough invisible math running under the floorboards. Reward mechanics do not need to join the witness protection program.

The 50 million gold refund cost makes it worse

The sharper complaint is not just that the node may be bugged. It is that refunding War Plan nodes reportedly costs 50 million gold. That turns a possible broken upgrade from “annoying” into “why am I paying a dungeon mortgage to fix this?”

War Plans are supposed to give players meaningful choices. But if a node does not work, and changing away from it is expensive, the system starts feeling less like strategy and more like being fined for trusting the tooltip.

Helltide nodes are getting questioned too

The same thread also raises concern about a Helltide node that says ambushes can spawn up to four additional Hellborne. The player says they only saw one Hellborne and expected more from the upgrade.

Replies push back on the wording, pointing out that “up to” can technically mean fewer than four. That may be true, but it also highlights the bigger issue: War Plan language needs to feel clear, especially when players are investing time, gold, and seasonal progression into it. “Technically correct” is not always the same thing as satisfying.

War Plans need clarity as much as fixes

Diabloz recently covered how Hotfix 3 fixed War Plans party rewards, including helper caches and meta progression XP. That was a good step. But this newer discussion suggests the system still has rough edges, whether through actual bugs, unclear language, or rewards that do not feel reliable.

For now, this is a player-report debate, not an official Blizzard-confirmed known issue. Still, War Plans are one of Lord of Hatred’s big new seasonal systems. If players cannot tell whether upgrades are broken or just badly explained, that is a problem by itself.

Endgame planning should feel like strategy. It should not feel like arguing with a tooltip while 50 million gold watches from the corner.

Read More

Diablo 4 Disables Limitless Rage After Barbarian Damage Goes Off the Rails

 

Diablo 4 Barbarians have once again looked at the word “limitless” and taken it as a personal challenge. Blizzard has now stepped in before the damage numbers needed their own postal code.

In a new official Diablo IV forum post, Blizzard says it has temporarily disabled the Barbarian Limitless Rage affix due to unintended interactions with Melted Heart of Selig and Endurant Fate. The issue, according to Blizzard, caused Limitless Rage to scale damage “near infinitely.” That is not balance trouble. That is the math leaving Sanctuary on horseback.

Limitless Rage finally found a limit

The affix is supposed to reward Barbarians for generating Fury, building up damage through aggressive resource generation. That sounds very Barbarian. Hit things, get angry, hit things harder. Beautifully simple. Very on-brand.

The problem appears to be that the interaction with Melted Heart of Selig and Endurant Fate pushed the scaling far beyond what Blizzard intended. PC Gamer reports that players were able to reach absurd damage levels, including quadrillion-scale hits, by abusing the loop before Blizzard shut the affix down.

Barbarian players may see disabled items

Blizzard says the affix is temporarily disabled while the team works on a fix. That means players using items with Limitless Rage may find that the affix is not functioning until it is re-enabled.

That will sting for anyone who built around it legitimately, but it is also hard to blame Blizzard for pulling the emergency lever here. Diablo 4 can survive strong builds. It can survive silly builds. It cannot really leave “near infinite scaling” running loose while the endgame, ladders, and competitive systems are trying to look serious.

This is exactly the kind of bug Blizzard has been hunting fast

Lord of Hatred’s launch window has already been full of quick fixes. Diabloz has covered Hotfix 4 removing the Pit and Tower portal, exploit closures, quest blockers, and other early cleanup work. This Limitless Rage shutdown fits the same pattern: if something breaks progression, rewards, or damage scaling badly enough, Blizzard is not leaving it to ferment.

And honestly, that is probably healthy. Nobody loves seeing their build disabled, but nobody loves an endgame where the top answer is “become a damage calculator crime scene” either.

The Barbarian casino is closed for repairs

For now, Blizzard says it wants to resolve the issue and re-enable Limitless Rage as soon as possible. No exact timing has been given.

Until then, Barbarian players may need to put the near-infinite murder engine back in the garage. Limitless Rage will likely return, but after this little incident, it may come back with a leash, a helmet, and a stern note from accounting.

Read More

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