Diablo II: Resurrected’s Warlock Nerf Backlash Is Getting Ugly Fast

Yesterday, Blizzard dropped the official PTR 3.2 notes for Diablo II: Resurrected. Today, the Warlock community is acting like someone kicked over the altar and stole the candles. This is no longer just a “players react to patch notes” story. It has turned into a full-on backlash cycle, with fresh forum threads accusing Blizzard of betrayal, overcorrection, and gutting the class that just sold an expansion a few weeks ago.

The patch notes lit the fuse

The anger is not hard to understand. PTR 3.2 does not just tap one or two Warlock outliers. Blizzard is hitting multiple parts of the class at once, including Miasma Bolt, Miasma Chains, Ring of Fire, Flame Wave, Echoing Strike, Bind Demon, and the old two-hand-plus-shield setup. Blizzard is also changing Herald and Latent Sunder Charm behavior, while openly admitting Herald spawn rates and charm drops “feel too low.” That last part is probably healthy. The Warlock part is what set the forums on fire.

Players are calling it a rug pull

The tone on the forums has shifted from normal balance grumbling to something much saltier. In one active thread, a player says they feel “betrayed” and asks why Blizzard is nerfing one class instead of uplifting the rest. Another argues the changes “break” Bind Demon and likely the summoner tree by making unique demon binding too expensive in skill points. A separate complaint thread says players already built around these mechanics, spent time and trade wealth on them, and now feel like Blizzard is turning that investment into trash after the fact. That is where the “rug pull” language is coming from.

Not everyone is mad, but the mood is nasty

To be fair, this is not one-sided. There are also active threads defending the nerfs as overdue, arguing Warlock launched absurdly overpowered and was crowding out older class identities. One poster called it a “tough but right decision,” while another said they were actually excited for the patch because Warlock had started replacing too many traditional roles. But even in the pro-nerf camp, the underlying message is basically: yes, Blizzard had to do this, but it probably should not have let things get this messy in the first place.

The real problem is timing

That is why this story has bite. Blizzard is probably right that Warlock needed balancing. But when a class arrives with a paid expansion, dominates the meta, and then eats a giant PTR correction almost immediately, players do not read that as clean stewardship. They read it as Blizzard selling the fantasy first and fixing the consequences later. In Diablo, people can handle nerfs. What they hate is feeling like they bought the honeymoon build and got handed the divorce papers two months later.

Read More

Diablo 4 Players Say Paladin’s Dawnfire Gloves Lose Their Stacks the Second a World Boss Shows Up

Diablo 4 has plenty of bugs that feel annoying. This one feels rude. Players say Paladin’s Dawnfire gloves can lose their built-up stacks the moment you enter a World Boss Zone, which is exactly the kind of bug that turns a carefully prepared build into a shrug and a loading screen. If your big item setup falls apart right before a major fight, that is not “friction.” That is the game kicking your chair away.

The current complaint is visible again on Blizzard’s Diablo IV forums, where the topic “Paladin’s Dawnfire gloves lose their stacks when you enter a World Boss Zone” showed up among the latest active Diablo IV discussions on April 11. The underlying bug report says that if you build up Dawnfire stacks before entering the zone, they vanish as soon as you cross into the World Boss area. The same player also says they may have seen something similar around Belial’s Palace during the PTR, suggesting this might be tied to specific zone transitions rather than just one boss arena.

It matters because Dawnfire is built around ramping power

This is not just some random stat stick losing a buff nobody notices. Blizzard’s own 2.6.0 PTR notes show Dawnfire as a Paladin unique that was actively being tuned: the tooltip was updated to better explain the aura, Holy Light was changed to refresh the duration, the buff duration was increased from 15 to 20 seconds, and Blizzard added a buff number and duration indicator to the icon. In plain English, this is an item that clearly wants players to care about maintaining and tracking its stacks. So if a zone boundary is deleting that setup, the whole item fantasy gets kneecapped right before the part that should feel coolest.

Blizzard has already been fixing Dawnfire-related issues

That is the awkward bit. In the March 20 Diablo IV patch notes, Blizzard already fixed multiple Dawnfire problems, including issues where allies had the visual fire aura when Dawnfire was equipped and where Dawnfire’s Holy Light Aura changed how NPC allies dealt damage. That shows the item has already needed cleanup in live Diablo IV. So when players are still flagging another Dawnfire-related issue on the forums, it starts to look less like a weird one-off and more like an item that keeps finding new ways to misbehave.

Losing stacks at the doorway is a special kind of ugly

There is also something uniquely rotten about a bug like this. Players can live with low damage. They can live with balance tweaks. What they hate is prep work being erased by a technicality. If Dawnfire stacks disappear when entering a World Boss Zone, the problem is not just damage loss. It is that the game teaches you to ramp up a mechanic, then wipes it the second you reach the content where it should matter most. In a loot game, that kind of bug always feels worse than the tooltip makes it sound. 

Read More

Diablo 4 Players Say a New Character Can Leave the Main Story in Limbo, and That Is a Rotten Kind of Bug

Diablo 4 has plenty of ways to waste your time, but a campaign-progression bug is one of the ugliest. The latest fresh report says a player came back during the new season, rolled new characters, and then discovered the main story no longer appeared in the quest list or on the map. That is not a balance issue or a bad drop. That is the game looking you in the face and forgetting how its own campaign works.

The report is simple, which usually makes it nastier

The April 11 post on Blizzard’s Diablo IV PC Bug Report board says the player had started the game with one character, stepped away during a break, then returned for the new season and found the main story missing on new characters. The thread is brand new, and Blizzard’s latest bug-board index shows it sitting there as one of the newest active Diablo IV bug topics, which gives it the exact kind of “this just happened” energy that makes players nervous.

Why this one matters more than a normal quest hiccup

Blizzard’s own Diablo IV seasonal guidance makes the campaign flow pretty clear: seasonal characters are a separate start, and once you have completed the campaign, new seasonal characters can choose to skip the campaign. In other words, the game is supposed to know where you stand. If a player comes back, makes a fresh character, and the story path simply does not appear, that turns a basic account-state decision into a progression mess. It also creates the worst kind of Diablo confusion: not “Where should I farm?” but “Am I bugged, or did the game decide something for me?”

This is not the first time “where did my story go?” has shown up

That is the awkward part. A 2024 Diablo IV forum thread described a new character starting with waypoints unlocked and no storyline to follow, while another older thread complained the main quest tab was greyed out. That does not prove the April 11 report is the exact same bug wearing a new hat. But it does suggest this family of campaign-state weirdness has been haunting Sanctuary for a while.

When your new character cannot even find the plot

Blizzard has not posted a public fix or explanation on this fresh report yet. That means this is still one current player report, not a confirmed widespread outage. Even so, it is a sharp story because campaign bugs hit differently. Loot bugs make players angry. Story-progression bugs make them feel stranded. And in an ARPG built around rolling fresh characters, that is a nasty kind of silence. 

Read More

Diablo 4 Players Say Season 3 Cosmetics Are Suddenly Locked, Even Though They Already Earned Them

Live-service games love selling you on permanence right up until something quietly vanishes from your account and everyone suddenly starts speaking in support-ticket dialect. Diablo 4’s latest version of that headache is a fresh report claiming Season 3 cosmetics are now locked, despite the player fully completing the season when it was live. That is not just a wardrobe annoyance. That is the kind of thing that makes people start mentally auditing every cosmetic they ever earned.

The new report hit Blizzard’s Diablo IV PC Bug Report board on April 11, 2026. In the post, the player says they have been playing since launch, completed Season 3: Season of the Construct, and previously had access to those cosmetics on their account. Now, according to the report, those rewards either appear locked or unavailable. Blizzard’s current Diablo IV bug-board index and latest-topics page both show the thread as one of the newest active issues, which at least confirms this is a live, current complaint and not some dusty old forum corpse getting bumped for attention.

The ugly part is what this does to trust

This is why cosmetic bugs hit differently. If a damage number is wrong, players grumble. If an old seasonal reward suddenly looks locked after it was already earned, players start asking a much nastier question: what exactly do you own in a live-service game? Diablo IV’s official Season of the Construct announcement made that season a full-fledged seasonal track with its own rewards and progression loop. So if cosmetics from that period are no longer properly recognized on an account, the problem is not just visual. It cuts into the basic promise that earned rewards stay earned.

Right now, this looks like a fresh scare, not a confirmed widespread outage

It is important not to oversell it. At the moment, this is a fresh bug report, not a Blizzard-confirmed mass issue. There is no public fix attached to the thread yet, and the search results currently show the report with very little reply activity. But that does not make it a weak story. It makes it a sharp one. Cosmetic lockouts tend to spread panic faster than they spread proof, because players know exactly how hard it is to reconstruct what they unlocked months ago.

The kind of bug that makes old rewards feel rented

That may be the real sting here. Diablo 4 has had plenty of bugs involving progression, loot, and systems acting haunted. But when old seasonal cosmetics start looking inaccessible again, it creates a different kind of irritation. Not rage. Suspicion. And in a game built on seasonal grind, that is poison in a fancier outfit.

Read More

Diablo 4 Players Say a Mythic Unique Cache Can Just Disappear After Crafting, Which Is About as Evil as It Sounds

Diablo 4 has plenty of annoying bugs. Some waste time. Some waste materials. This one goes straight for the throat. A fresh player report says a Mythic Unique Cache simply vanished after crafting, with the player losing two Resplendent Sparks and getting no item in return. That is not a minor inventory hiccup. That is the kind of bug that makes a season feel personally hostile.

The report was posted on Blizzard’s Diablo IV PC Bug Report forum on April 10. According to the player, the cache disappeared after crafting in Gea Kul, near the new seasonal area by Kael Rills the Butcher. They say they could still see it on the map, but it was not in their inventory, not in the stash, and not on the ground. In other words, the game seemed fully aware that the reward existed. It just apparently had no interest in letting the player actually touch it.

This is the kind of bug players remember

That matters because Mythic crafting is not cheap throwaway content. If a basic legendary vanishes, people groan and move on. If a Mythic Unique Cache disappears after consuming high-value crafting resources, the mood changes instantly. Blizzard’s Diablo IV forum indexes show the report as one of the newest active bug topics right now, which gives it enough heat to stand as a real current story and not just one lonely complaint buried three pages deep.

The awkward part: this may not be totally new

There is also some uncomfortable history here. An older EU forum thread from late December 2025 describes a Mythic Unique Cache disappearing from inventory after it was created and the player changed difficulty. A recent Reddit thread from last week also describes a player opening a Mythic cache and getting nothing, with one reply claiming certain town geometry can make loot disappear instead of dropping cleanly. That does not prove the current April 10 report is the exact same bug. But it does suggest cache-related vanishing acts may not be a one-night horror show.

When the reward system feels cursed, that is a real story

That is really the whole hook here. Diablo players can handle stingy drop rates. They can handle bad RNG. What they do not handle well is spending top-end resources and watching the payoff evaporate into UI smoke. Blizzard has not posted a public fix or explanation attached to this specific report yet. Until that changes, this is the kind of bug that will make every Mythic craft feel just a little more like a dare.

Read More

Diablo II: Resurrected PTR 3.2 Is Coming, and Yes, Warlock Players Are Already Bracing for Pain

Blizzard is rolling out Diablo II: Resurrected PTR 3.2 from April 14 to April 21, and this one looks less like a casual tune-up and more like the moment Blizzard finally walked back into the room with a sharpened knife and a long list of Warlock adjustments. The official pitch is simple enough: Warlock balance changes, Terror Zone updates, Herald and Sunder Charm tweaks, and a few UI improvements. The player reading of that pitch is even simpler: “So the nerfs have arrived.”

And to be fair, that reaction did not come out of nowhere. Blizzard’s PTR notes hit several key Warlock tools at once, including Miasma Bolt damage, Miasma Chains cloud damage, Ring of Fire, Flame Wave, Echoing Strike, and parts of Bind Demon and Blood Oath. Blizzard is also changing how one-handed two-hand weapon use works for Warlocks, limiting it so the off-hand must be a grimoire rather than a shield. When you stack that many changes into one PTR, players are going to read it less like “fine-tuning” and more like a controlled demolition.

Blizzard is not just touching Warlock

The other big half of PTR 3.2 is the Terror Zone / Herald / Sunder Charm overhaul, and honestly, that may matter just as much as the class changes. Blizzard says Heralds will now start hunting players immediately after kills in Terror Zones, Latent Sunder Charms can drop from any monster using Magic Find, and the Herald-related Sunder drop chance now ramps up earlier and is less heavily tied to player count. Blizzard’s own developer note says the current Herald spawn rate and Latent Sunder Charm drop rate “feel too low,” which is about as close as you get to an official “yeah, we heard the yelling.”

The forum mood is already split between relief and alarm

That is where the article gets more interesting than the patch notes. In the official forum thread, some players are calling the PTR changes “really good” and praising Blizzard for finally reacting. Others are saying the PTR is late, that the Warlock launched too hot and is now being hit too hard, or that the Sunder Charm changes may go too far in the opposite direction and make rare drops feel too common. One of the more blunt reactions says, “Warlock is gonna suck next season,” which is not exactly subtle feedback.

The real story is that Blizzard is finally correcting course in public

That is probably the biggest takeaway here. Whether these exact PTR numbers survive unchanged is almost beside the point. PTR 3.2 is Blizzard openly admitting that Reign of the Warlock still needs real balancing and system cleanup after launch. That is healthy, even if it is also a little awkward. D2R players can live with strong balance passes. What they hate is the feeling that nobody is steering the wagon. PTR 3.2, at the very least, looks like somebody grabbed the reins again.

Read More

Diablo III Quietly Brought Back a Tiny Rift UI Feature, and Players Are Weirdly Happy About It

Not every Diablo story needs a bug, a meltdown, or a demon made of unpaid QA overtime. Sometimes the news is smaller than that. Sometimes Blizzard sneaks in one tiny quality-of-life change, and Diablo players react like someone quietly fixed a light switch that had been annoying them for twelve years. That is basically where Diablo III is today.

The spark for this one is a fresh April 10 Diablo III forum post with the gloriously unhinged title “Holy crap, they actually added a beta feature back in!” The player says the game now shows rift progress text above the bar again, so you no longer have to mouse over the bar just to check your percentage. According to the post, that text indicator existed back in beta, disappeared on retail, and has now quietly returned.

A tiny UI fix with very old bones

That probably sounds microscopic if you do not actually play Diablo III. But if you do, it is exactly the kind of small friction point that gets under your skin over time. Rift progress is one of those things players check constantly during a session, especially in a season built around speed, repetition, and tuning runs efficiently. Blizzard’s official Season 38: Ethereal Memory post confirms the season is live now, which makes a little readability improvement like this land at a pretty good moment.

The funny part is how unannounced it feels

That is what makes this more charming than dramatic. Blizzard’s current Diablo III news feed still lists Season 38: Ethereal Memory as the latest actual Diablo III news post, and the April 10 forum reaction reads like players discovered the UI tweak on their own rather than through some flashy official “look what we did” patch write-up. In other words, this was not sold like a feature. It was noticed like a pleasant accident.

Diablo players do notice the small stuff

There is also a nice tonal contrast here. The broader Diablo III forum front page is still full of the usual season chatter — Ethereal drop complaints, stash grumbling, technical issues, and the usual low-level friction that follows any active season. Against that backdrop, a post celebrating a restored little interface detail stands out because it is not angry. It is just relieved. That may be the most shocking part.

A rare little win that does not need a trailer

No, this is not some massive Season 38 overhaul. It is not going to drag Diablo III back into the cultural center of the franchise. But it is the kind of small, practical change that reminds players somebody still touched the wires. And in a game this old, that can matter more than Blizzard probably realizes. Sometimes a tiny UI fix is not just a UI fix. Sometimes it is proof the old crypt still has a pulse.

Read More

Diablo II: Resurrected Players Say Uber Ancients Jewel Drops Still Feel Wrong

Diablo II players can survive bad odds. They have been training for that emotionally since before broadband was common. What they do not take well is when a reward system starts feeling less like cruel RNG and more like a mechanic that might be broken, badly explained, or both. That is where the Uber Ancients conversation has landed this week. (us.forums.blizzard.com)

The fresh spark is a new April 10 bug-report thread titled “Uber Ancients Not Dropping Jewel Ladder.” In the forum snippet, the player says they killed the Ancients 16 times and saw the jewel drop only about 50% of the time. They also wonder whether a mercenary kill or some other condition is preventing the reward from registering properly. That is exactly the kind of report that makes a farm target go from “hard” to “suspicious.”

This is not just one frustrated post

That is the important bit. On the current Diablo II: Resurrected forum index, “Uber Ancients is Trash” and “Uber Ancients Not Dropping Jewel Ladder” are both active on April 10, which tells you the issue is not living in one lonely bug thread no one saw. Over on the D2R bug-report index, there is also a recent topic called “Colossal ancients still doesn’t drop jewel,” which suggests the reward complaint has been hanging around for more than a single bad night of farming.

Blizzard sold these fights as a big part of Reign of the Warlock

And that is why players are getting prickly. Blizzard’s official Reign of the Warlock announcement specifically pitched Colossal Ancients as one of the expansion’s major features, right alongside the Warlock class and fresh Terror Zone content. When a flagship endgame activity is tied to reward complaints this quickly, people are not going to shrug and say, “Well, that’s Diablo.” They are going to start asking whether the system is stingy on purpose, bugged in practice, or simply not explained well enough.

The real problem is trust

That is what this story is really about. Diablo players can live with low odds if they believe the machine is honest. But once people start wondering whether kill credit, mercenary behavior, or some hidden condition is blocking drops, the whole loop starts to smell off. And when the parallel community thread is literally called “Uber Ancients is Trash,” you do not exactly need a sociologist to decode the current mood.

When the reward feels random in the wrong way

Maybe this really is just ugly RNG. Maybe there is a kill-condition issue buried under the hood. Maybe Blizzard needs to explain the drop logic more clearly so players stop treating Uber Ancients like a slot machine with anger issues. But until that happens, this fight is going to keep generating the worst kind of endgame feeling: not challenge, not excitement, just doubt.

Read More

Diablo II: Resurrected Players Are Reporting Disappearing Warlock Characters, and That Is About as Bad as It Sounds

There are regular Diablo bugs, and then there are the ones that make your stomach drop before your brain even finishes the sentence. A disappearing character is in that second category. The latest Diablo II: Resurrected scare comes from fresh April 10 forum reports claiming Warlock characters are simply vanishing, which is the sort of problem that instantly turns a normal login into a crime scene.

The clearest report is a new post on Blizzard’s D2R Bug Report board titled “Warlock character dissapeared!” In it, the player says they logged in on April 9, 2026 and found their Warlock gone, while the local files still remained on their drive. On the same April 10 forum index, there is also a separate “Characters dissapeared” bug-report entry; opening it shows the same user adding a fresh 2026 reply saying their Warlock vanished as well. So this is not yet a giant flood of reports, but it is also not just one typo-ridden ghost post floating in the abyss.

The timing makes players extra jumpy

That is partly because Reign of the Warlock only arrived in February as a major D2R update that added the first new playable class in more than 25 years. Since launch, the expansion has already had its share of technical friction, including Blizzard-published PSAs explaining how shared stash behavior changes when characters are converted into the new ruleset. In other words, players are not exactly coming into this with a calm, “I’m sure everything is fine” mindset.

This is where the story gets awkward

The stash issue at least had an explanation. Blizzard explicitly told players that shared stash contents do not transfer automatically during conversion and explained how to move items correctly. A vanished Warlock character is different. In the fresh disappearance report, there is no blue reply, no workaround, and no clear explanation attached to the thread right now. That does not prove a widespread character-loss catastrophe is underway. It does mean the current public answer is basically silence, which is not exactly the ideal companion to “my class is gone.”

The kind of bug that scares people faster than it spreads

And that is why this one matters even if the report count stays small. Diablo players can tolerate stingy loot, ugly balancing, and the occasional patch that kicks them in the shins. What they do not tolerate well is anything that smells like lost progression. When a paid expansion’s headline class starts showing up next to words like “disappeared,” the panic writes itself. Sanctuary has always been cruel. Players just prefer the monsters to be the reason.

Read More

Diablo 4 Players Say Boss Loot Is Still Falling Off the Map, and Lord Zir Is a Very Annoying Example

Diablo 4 has found yet another way to make loot feel cursed. This time, the problem is not bad rolls, stingy drops, or some occult spreadsheet nonsense buried in a menu. It is much dumber than that: players say boss loot can still fall out of bounds, show up on the minimap like it is mocking you, and then refuse to appear where you can actually pick it up. The named example in the latest report is Lord Zir, which is a lovely choice if your goal is to make repeated boss farming feel just a little more infernal.

In a fresh post on Blizzard’s PC Bug Report forum, the player says boss loot “still falls out of bounds” for some encounters and specifically calls out Lord Zir. According to the report, the loot is visible on the minimap but not on the ground, and while it can end up going to the postmaster, that is “suboptimal” when farming multiple runs because of possible item overflow. That is not a small annoyance. That is your reward system behaving like it got bored halfway through its job.

The minimap says yes, the floor says no

What makes this one good article material is how easy it is to picture. You kill the boss. You know the loot exists. The minimap knows the loot exists. The game is basically pointing at your reward like a cruel tour guide. And yet the actual ground where you are standing says no. For players chain-farming bosses like Lord Zir, that turns a routine run into a weird inventory hostage situation. If you are already doing the kind of repeated farming covered in our earlier Lord Zir guide, the last thing you want is to wonder whether the floor just ate your drop.

Blizzard has been here before, which is the awkward part

This is not even the first time Diablo 4 has had boss-loot placement issues hanging around the edges. In Blizzard’s official patch 2.1 notes, the team previously fixed an issue where loot was difficult to pick up on controller if it dropped on top of Boss Summon Altars. That is not the exact same bug, but it does show that “boss dies, loot lands in a stupid place” is not exactly a brand-new genre for Diablo 4.

Loot should not need a rescue mission

That is really the whole story. Diablo can get away with cruel RNG. It can get away with low drop rates, bad luck streaks, and bosses that feel like vending machines with anger issues. What it should not get away with is making players fight geometry for the right to collect loot they already earned. When the minimap can see your reward and you cannot, the problem is no longer drop quality. It is basic dignity.

Read More

Diablo 4 Players Say Imprinting Better Aspects Still Isn’t Updating Gear to the Higher Value

Diablo 4 has a nasty little habit of turning upgrade moments into trust exercises, and the latest complaint fits that pattern perfectly. This time the issue is not that an Aspect looks wrong in the Codex. It is worse in a more practical, wallet-draining way: players say they are imprinting a better Aspect, spending the materials, and watching the item not actually update to the higher value. That is not a loot problem. That is an “are we sure the blacksmith is sober” problem.

The fresh report comes from Blizzard’s Diablo IV PC Bug Report forum on April 10. The player says that when they imprint an Aspect with higher values than the one currently on the equipped item, the game does not apply the new values. They also say it appears to happen when adding the Aspect to a rare item, and that they saw the behavior across multiple Aspects on a Barbarian. Blizzard’s current bug-board index shows the thread as one of the newest active Diablo IV bug topics today.

The annoying part is that this does not look brand new

That is what gives this one extra stink. Recent Diablo IV forum history shows Aspect-imprinting complaints have already been floating around for weeks. On March 25, one player said they were trying to overwrite an existing Aspect with a higher-value version and the sword would not upgrade to the stronger number. On March 14, another report said the problem happened specifically when trying to overwrite the same Aspect on an item that already had a lower-value imprint. There are also separate reports from March and April claiming imprint upgrades were landing at minimum values or throttled on lower-power gear.

Blizzard already patched one Aspect-value problem, which makes this harder to shrug off

That is the part Blizzard will not love. In the current official Diablo IV patch notes, Blizzard says it fixed an issue where values for Aspects were different between the Codex of Power and when imprinted or found on items. That sounds reassuring until a fresh April 10 report shows players are still talking about higher-value imprints not sticking properly. To be fair, this may not be the exact same bug under the hood. But from the player side, the feeling is basically identical: you earned the upgrade, you paid the cost, and your item still acts like it did not get the memo.

When upgrades stop feeling reliable, the whole system starts to smell off

That is why this matters. Diablo players can tolerate bad luck. What they hate is fake progress. If imprinting a stronger Aspect is still unreliable, then one of the game’s core upgrade loops starts feeling less like character building and more like a cursed coin flip with extra crafting fees attached. In a season already carrying a full backpack of bug reports, that is not exactly great timing.

Read More

Diablo II: Resurrected Players Are Already Tearing Into the Herald System

Diablo II players will put up with a lot. Terrible luck. Ancient drop tables. The occasional weekend lost to one rune that absolutely refuses to exist. But if there is one thing they hate more than bad loot, it is bad loot attached to a mechanic that wastes their time first. That is pretty much where the current Herald system conversation has landed.

The mood on the official Diablo II: Resurrected forums is not subtle. In “The Herald System is Trash”,  one player says they spent multiple weekends grinding Heralds and came away with no sunder charms at all. In “Hunting Heralds - They dont drop anything good - Part 1”,  another says they cleared multiple acts, killed 16 Heralds in one game, and still got nothing worth getting excited about. That is not “the chase.” That is admin.

The rewards are the problem, but the structure is getting blamed too

This is where it gets more interesting. Players are not just complaining about bad drop luck. They are also dragging the mechanic itself. In “Stop the herald cringe please”,  one player says Heralds take forever to spawn, rarely drop anything good, and can still roll immunities that make them miserable to fight. Another says the whole hunt feels like “unproductive work.” Over in “Suggested TZ/Herald system changes”, players are openly asking Blizzard to simplify the “drawing ire” setup and let Latent Sunders drop from regular Terror Zone enemies again at a reduced rate.

This is becoming a real D2R talking point, not one random rant

That matters because the Herald backlash is not buried in one forgotten thread. The current Diablo II: Resurrected forum index still shows “Hunting Heralds - They dont drop anything good - Part 1” and “Herald mechanic rework suggestion” among the active recent discussions. The bug board is not helping the mood either, with fresh reports like “Unable to hork herald” and “Non-latent sunder charm dropped” still visible this week. When the rewards feel weak and the surrounding system looks shaky, players start treating the whole feature like cursed plumbing.

The worst crime: it makes farming feel less fun

That is the real danger here. Blizzard’s official Reign of the Warlock announcement pitched stronger Terror Zones and greater rewards as part of the update. But right now, a loud part of the D2R community seems to think the Herald setup turns Terror Zone farming into a long setup for disappointment. Diablo can get away with cruel RNG. It has been doing that for decades. What it cannot get away with, at least not forever, is making the grind feel like paperwork.

Read More

Diablo 4 Players Say Butcher’s Brutality Can Break in Your World and Work Fine in Someone Else’s

Diablo 4’s Season 12 has already built a nice little side career as a bug anthology, and now it has produced one of its weirder entries yet. This time the complaint is not just “something feels off.” It is much nastier than that: one player says Butcher’s Brutality can be active on the quest log while the actual seasonal systems fail in their own world, then suddenly work properly when they jump into a friend’s. That is not a balance issue. That is your season acting like it has commitment problems.

The bug report is oddly specific, which usually makes it worse

In a fresh post on Blizzard’s PC Bug Report forum, the player says their Seasonal Necromancer appears stuck in a desynced seasonal progression state. According to the report, activating a Slaughterhouse key in their own world triggers the message that the Slaughterhouse is active, but the entrance at the Butcher’s location becomes an open doorway that does not actually lead anywhere. The same post says killstreak/brutality progression does not work correctly in that world, related seasonal interactions in Gea Kul do not appear properly, and the entire setup works normally when the player joins a friend’s storyline instead.

That matters because this is not some side feature nobody uses

Blizzard’s official Season of Slaughter overview makes clear that the Butcher systems are a major part of Season 12. The seasonal questline A Taste of Power starts in Gea Kul, the season revolves around the Killstreak system, and Slaughterhouses are one of the main ways to play as the Butcher throughout a run. In other words, if your world state is bugged here, this is not a cosmetic inconvenience. It is the season’s central gimmick falling through the trapdoor.

Blizzard has already been patching Killstreak-related issues, which makes this extra annoying

What makes this uglier is that Blizzard has already touched Season 12’s killstreak systems in post-launch updates. The current official patch notes say Killstreak multipliers are now highlighted in the UI and Killstreaks no longer reset when going between floors in dungeons, which shows Blizzard has already been tuning and fixing this part of the season. So when a fresh report shows up saying the entire Butcher progression loop can desync in one world while functioning in another, it starts to feel less like one random freak bug and more like the season still has unstable wiring under the floorboards.

A co-op season should not punish you for playing co-op

The player who filed the report says the issue appears to have started after co-op seasonal quest progression in another player’s world. That is still only one report, and Blizzard has not publicly confirmed a broader issue here. But it is the kind of bug that immediately gets attention because it cuts straight into trust. If a season built around shared demon murder starts scrambling your own world state because you played with a friend, that is not “quirky live-service behavior.” That is Sanctuary eating its own save file with a knife and fork. 

Read More

Diablo 4 Players Say Season 12 Is Quietly Turning Valuable Reserve Sigils Into Generic Junk

Diablo 4 has a real talent for making loot feel cursed in ways Blizzard probably did not intend. The latest example is not some giant flashy crash or a boss exploding into the void. It is smaller, meaner, and somehow more annoying: players say valuable reserve sigils in Season 12 are being quietly converted into plain old “Gem reserves” by the game itself.

The fresh report on Blizzard’s Diablo IV PC Bug Report forum comes from a player running both Paladin and Barbarian in Season 12. According to the post, stash items with specific reserve affixes like Ruby, Emerald, Diamond, Topaz, and Sapphire were gradually changed into regular Gem reserve affixes after switching between characters. The player says those color-specific sigils matter this season, that the converted ones had been favorited, and that the bug effectively wiped out around 5 to 7 of the sigils they actually wanted to keep.

The ugly part is how easy this is to miss

That is what makes this one nasty. If a dungeon crashes, you notice. If a teleport black-screens, you notice. But if your stash slowly mutates your good sigils into generic filler, that can sit there like a quiet little scam until you finally realize your best stockpile has been spiritually mugged. Blizzard’s current PC bug board shows the report as one of today’s newest Diablo IV issues, which at least confirms this is part of the live Season 12 bug churn and not some ancient forum ghost resurfacing for attention.

It may not even be completely new

Here is the less comforting part: this does not look entirely unprecedented. An older Diablo IV PC bug-board page from January 3, 2026 shows a thread called “Gem Sigils converted over night.” That does not prove today’s report is the exact same bug with the same trigger, but it does suggest this family of problem may have been lurking around Sanctuary for a while instead of being a one-off seasonal freak accident.

A stash bug is still a progression bug

And that is the story here. This is not just about one mislabeled item. If players are holding specific reserve sigils because they are more useful or more valuable this season, and the game is flattening them into generic versions, then Blizzard is not just messing with inventory labels. It is messing with player planning, stash management, and the basic trust that the loot you saved yesterday will still be the loot you log in to tomorrow. In a game this obsessed with grind value, that is not a cosmetic problem. That is rot.

Read More

Diablo Immortal x DOOM: The Dark Ages Is Exactly the Kind of Crossover This Game Was Built For

Diablo Immortal has spent a lot of recent headlines doing very live-service things: fixing bugs, nudging events around, and trying to keep the wheels from wobbling too loudly. So it is honestly refreshing to get a Diablo Immortal story that is not about something refusing to load, disappear, or break in a creative new way. This time, Blizzard is doing something much louder and much dumber in the best possible sense: it is dropping DOOM: The Dark Ages straight into Sanctuary.

The new crossover event is called Slayer’s Reign, and Blizzard says it runs from April 16 through May 13. The headline feature is a DOOM-flavored rework of Survivor’s Bane, where players get access to Slayer-inspired weapon skills pulled from the DOOM arsenal. Blizzard specifically calls out the Shield Saw, Dreadmace, and the Super Shotgun, which is a sentence that sounds fake until you remember what kind of franchise Diablo has become in 2026.

This one actually has a clean hook

And that is why this works. It is not just “here is a cosmetic, please clap.” Blizzard is pitching an actual event structure around the crossover, including combat skills, a new Legendary Gem called The Crucible, and limited-time rewards. There are also free Sentinel Forged Armory weapon cosmetics during the event, plus a Ruthless Hellwalker Phantom Market set built around the Slayer’s Praetor Armor. That is a lot more substantial than the usual crossover routine where a game slaps a logo on one skin and hopes everyone is too distracted to ask questions.

It also makes weird thematic sense

This is the funny part: as absurd as “Diablo meets DOOM” sounds on paper, it is actually a pretty natural fit. Both series are built on mowing through Hell’s worst residents with extreme prejudice. Diablo is the slower, moodier uncle who lives in a cathedral basement. DOOM is the one who kicks the door off the hinges and solves the demon problem with industrial violence. Put them together, and the tone barely even has to stretch. That is probably why Blizzard’s announcement does not feel apologetic about the crossover at all. It feels like the company looked at two hellish franchises and decided subtlety was overrated.

A rare Diablo Immortal update that feels fun on purpose

That might be the real selling point here. Diabloz has spent the last stretch covering Diablo Immortal bugs, event issues, and systems that felt shakier than they should. Today’s crossover is different. It is flashy, a little ridiculous, and much more importantly, it gives Diablo Immortal something it has not had enough of lately: a story that feels fun before it feels broken. In a game that often acts like maintenance is a content strategy, that alone is worth noticing. 

Read More

Diablo III Players Still Can’t Agree Whether Season 38 Ethereals Are Bugged or Just Brutal RNG

Diablo III’s Season 38 brought Ethereals back, which should have been easy fan service. Big nostalgic weapons. Big power spikes. Big “just one more rift” energy. Instead, part of the current conversation has turned into something much more Diablo-coded: players staring into the loot abyss and asking whether the abyss quietly forgot to spawn the loot.

On the official Diablo III forums, the debate is now pretty clear. Some players say they have pushed deep into the season with little or nothing to show for it, including one report from a Hardcore player at Paragon 541 claiming they had not seen a single Ethereal, while a friend at a similar level had seen more than 15. Another player said they were 111 Greater Rifts in without a drop. That is the kind of bad luck that makes people stop blaming chance and start side-eyeing the code.

The season is working — but the mood is not

Blizzard’s own Season 38 overview says Ethereals are this season’s main theme, that they only drop in Seasonal play, and that their rarity sits somewhere between Ancient and Primal items. In other words, these things were never meant to rain from the sky like candy from a cursed piñata. They are supposed to be rare.

That said, the player mood is not just random whining. In the active S38 Ethereals Feedback thread, one player said they completed the Seasonal Journey on Barbarian and got zero useful Ethereals outside of early leveling. Another said they had around 24 hours played and still had not seen a single one. So yes, there is real frustration here.

The other side says this is just Diablo being Diablo

The counterargument is also loud, and honestly, not completely unreasonable. In those same threads, other players say they found several Ethereals early, or dozens within the first days of the season, and flat-out call it RNG. Some replies argue that efficiency matters more than raw time played — higher difficulty, faster clears, and better farming routes mean more chances at a drop, which can make unlucky players look bugged when they may simply be farming badly.

That is why this story is interesting. Blizzard has not confirmed an Ethereal drop bug, but the forums are active enough that the issue has clearly become part of the Season 38 conversation rather than one weird post screaming into the graveyard. The current Diablo III forum index still shows both S38 Ethereals Feedback and Not getting any Ethereal weapon drops as active recent topics this week. That does not prove the loot system is broken. It does prove players do not trust it right now. And in a loot game, that is its own kind of problem.

When the loot stops feeling mythical and starts feeling suspicious

Maybe this really is just rotten luck wearing a spooky mask. Maybe some players are farming inefficiently and blaming Blizzard for math. Or maybe Ethereal drop behavior this season is a little rougher than advertised. Either way, when the main fantasy of a season is “go chase the cool weapon,” players tend to get cranky when the weapon starts feeling like a rumor.

Read More

Diablo II: Resurrected Console Players Want Blizzard to Finally Say Something About Post-Warlock Performance

Diablo II: Resurrected’s console crowd is getting to that familiar stage of forum anger where people stop asking for miracles and start asking for a sentence. Not a fix. Not a roadmap. Just a human voice from Blizzard confirming someone is actually in the room. Right now, that seems to be the real missing feature on console.

The current flashpoint is a new thread on the official Diablo II: Resurrected console forum asking for a blue post about post-Reign of the Warlock performance, especially on PS5. One reply goes even harder, saying the game has been freezing and pausing at random points since Warlock’s release and accusing Blizzard of doing nothing about it. That is not exactly the kind of post people write when everything feels stable and under control.

The complaints are not living in just one thread

That is the bigger problem here. This does not look like one lonely rage post drifting through the abyss. Blizzard’s console discussion board is currently stacked with recent threads like “Ps5 OFFLINE ‘LAG’/Stutter since update,” “Micro stutters and frame drops still persist,” and “What exactly did the latest patch 1.37 fix?” Over in the console bug section, there are also fresh reports about PS5 teleport lag, console crashes, and stuttering still being present after patch 1.37. When a forum starts sounding like a support group, players tend to notice.

Warlock brought the hype, then the hitching

Blizzard launched Reign of the Warlock on February 11 as a major Diablo II: Resurrected expansion, headlined by the Warlock class, new Terror Zone features, the Colossal Ancients encounter, and quality-of-life changes. In theory, that should have been a nice little necromantic victory lap for D2R. In practice, some console players say the update period since Warlock has turned performance into its own miniboss.

One of the clearest examples is the long-running PS5 offline lag/stutter thread, where players describe severe hitching, brief freezes during combat, stutters after leveling, UI glitches, and even black-screen behavior after later patches. Another recent thread says that even after version 1.037.000, PS5 performance still is not close to where it was before Reign of the Warlock. That does not automatically prove one single root cause, but it does show this is no longer just background noise.

Silence is starting to do more damage than the bug reports

Blizzard’s latest 3.1.2 patch notes do list fixes for crash issues, resolution and UI sizing, and graphics rendering problems. That is useful. But when console players are still asking what patch 1.37 actually fixed, and whether anyone at Blizzard is seriously looking at PS5 performance, patch notes alone stop feeling like reassurance and start feeling like vague weather forecasts from hell.

Read More

Diablo Immortal’s New Refined Battle Pass Push Looks Smart, and The Hells Quake Is Blizzard’s Little “Don’t Drift Away” Bonus

 

This update is basically Blizzard saying: please stay on the treadmill, but here’s a shinier treadmill

Diablo Immortal has spent the past week generating headlines for bugs, broken menus, missing items, and general live-service chaos. So Blizzard finally throwing out a cleaner, more forward-looking update feels almost suspiciously civilized. In the official Become Sanctuary’s Undoubted Savior post, Blizzard confirms that the first Refined Battle Pass cosmetic set arrives in Battle Pass Season 51 on the upgraded track, while The Hells Quake event runs from April 9 at 3:00 a.m. to April 18 at 3:00 a.m. local server time. That is not exactly a giant expansion reveal, but it is a very obvious “here’s why you should keep logging in” kind of update.

The Refined Battle Pass idea is actually more interesting than it sounds

This is the part that matters. Blizzard says Battle Pass cosmetics now follow a multi-season progression that started with Season 50: you earn a cosmetic in one season, refine it in a second, and then unlock it for three additional classes in a third. In plain English, Blizzard is trying to make Battle Pass cosmetics feel less disposable and a bit more like something you build over time. Honestly, that is a smarter pitch than just tossing another outfit into the pass and hoping players clap politely.

It also fits where Diablo Immortal has been heading lately. We already covered how April’s big Diablo Immortal PvP change is not subtle, and this new cosmetic structure feels like part of the same broader push: keep players tied to the season loop, but make the rewards feel a little more layered than the usual “claim and forget” routine. That is probably the right move for a game that lives and dies on habit.

The Hells Quake is the smaller hook, but it still does its job

Then there is The Hells Quake, which Blizzard says is a limited-time login event running from April 9 to April 18. The company is keeping the pitch pretty mysterious, saying it offers rewards and “a glimpse of what is to come,” which is corporate fantasy-speak for “please take the bait and stay curious.” It is not a huge standalone system reveal, but as a short event dropped next to the Refined Battle Pass announcement, it works. Blizzard gets a cleaner news beat, players get one more reason to check in, and the whole thing lands a lot better than another week of bug drama.

For once, this is a Diablo Immortal story that is not on fire

That might be the real selling point. After pieces like our shop loading bug report, the vanishing Battle.net purchases story, and the Party Finder bug that hides activities,  it is almost refreshing to write about Blizzard trying to sell a system instead of apologize for one. The Refined Battle Pass pitch is a sensible long-tail retention idea. The Hells Quake is a neat little nudge. No, it is not earth-shattering. But by current Diablo Immortal standards, “mostly normal and reasonably well thought out” is already doing pretty well.

Read More

Diablo 4 Players Say the Wardrobe Is Still Bugging Out, and Somehow Even Dressing Up Has Become a Season 12 Problem

 

You can slay demons just fine. Picking a mount trophy? Apparently that is where the real challenge starts.

Diablo 4 has a fresh wardrobe complaint on the board, and it is exactly the kind of bug that sounds small until it starts wasting your time. In a new Blizzard forum report posted on April 8, one player says the wardrobe will let them interact with armor, but not with pets, mounts, mount armor, weapons, backpieces, or headstones. They also say armor only selects as a whole set, pigments behave the same way, and even a full reinstall did not fix it. The report is live in Blizzard’s Not able to select in the Wardrobe thread and also shows up among the newest items on the current PC Bug Report board.

This does not look like one completely isolated wardrobe tantrum

That is what makes it more than a one-post curiosity. A separate Blizzard thread from March 20, Wardrobe Bugged, describes a very similar problem: players saying clicked wardrobe pieces will not equip properly, that the interface can force the entire set instead of a single item, and that weird workarounds like pressing number keys or spacebar while clicking can sometimes make it respond. Blizzard’s latest topics pages also show related wardrobe complaints still surfacing this week, including “Wardrobe bug unable to select cosmetics” and “Issue with Wardrobe – Cannot interact (no response) – Diablo 4.” That does not prove every report is the exact same bug under the hood, but it does suggest the wardrobe has not exactly been living a stable life lately.

Why this bug is more annoying than it sounds

Because wardrobe bugs are not supposed to be hard problems. This is the cosmetic menu. This is where players go to make their character look slightly cooler, slightly uglier, or much more expensive than they need to. If the interface starts refusing normal selections and forcing whole sets instead, the system stops feeling polished and starts feeling like one of those menus you have to “fight” into working. And for Diablo 4, that lands badly in a season already carrying too many technical complaints at once. We have already covered how the black screen teleport bug still wasn’t dead, how rubberbanding was getting worse in Season 12, how PC crashes were still killing sessions, and how Season Journey Paragon Points were reportedly going missing Another bug hitting a basic system does not help the mood.

The funny part is that players are now troubleshooting a dress-up menu like it is a raid boss

That is the vibe here. Reinstalling the game to fix a cosmetic selector is already silly. Having older threads suggest keyboard tricks just to convince the wardrobe to equip the right piece is even sillier. Diablo 4 is very good at theatrical darkness, but it probably did not mean for the transmog screen to become part of the survival experience. Right now, this is still a fresh bug report rather than a full-scale community fire, but it is exactly the sort of issue that spreads fast once enough players realize the workaround is “start clicking weird and hope.”

Read More

Diablo 4 Players Say Season Journey Paragon Points Are Going Missing, and That Is a Nasty Bug to Find This Late in the Grind

 

Claim the reward. Watch nothing happen. Very cool.

Diablo 4 has a fresh progression complaint on the board, and this one hits a little harder than your average annoying UI wobble. In a new Blizzard forum post, a player says they completed the “Lesser Than Evil” objective under Season Journey Rank V, claimed the reward, saw it marked as claimed in the interface, and still never received the 4 Paragon Points tied to it. They say the objective was completed on April 6, but by April 8 the points still had not shown up. That is not a tiny visual bug. That is the game telling you “congratulations” and then quietly keeping the prize. Blizzard’s bug thread and the current PC Bug Report board both show the report as a fresh April 8 issue.

Why this one matters more than a random bug-board grumble

Paragon Points are not fluff. They are progression. If a seasonal reward says it gave you four and your account total does not move, players are not going to shrug and call it one of life’s mysteries. The original post also says the player suspects other rewards may not have credited correctly earlier, though that part is still one player’s suspicion rather than something Blizzard has publicly confirmed. That distinction matters. The evidence right now supports a real fresh player report, not yet a proven wider outbreak. Still, when the missing thing is permanent progression, people understandably get twitchy fast.

The ugly part is that this does not feel completely out of nowhere

This new complaint lands in a season that already has a bit of a rewards-trust problem. We recently covered how Season 12 rewards still weren’t paying out correctly, and older public chatter also suggests Season Journey reward weirdness has been floating around for a while. An Icy Veins report previously flagged claim issues around Season Journey rewards, and a Reddit thread from weeks earlier described a player getting fewer Paragon Points than expected from seasonal progression. None of that proves this new Rank V report is the exact same bug. It does suggest the broader reward flow has not exactly earned blind trust lately.

Right now, the real problem is confidence

That is the story more than anything else. Diablo 4 can survive balance drama, wardrobe bugs, and even the occasional cursed Occultist moment. But when players start wondering whether claimed progression rewards are actually real, the season starts feeling flimsy in a much less funny way. For now, this is still a fresh report and not a full community firestorm. But it is exactly the kind of bug that can go from “one bad post” to “everybody is checking their Paragon total” in a hurry. And honestly, once players start auditing the game’s math by hand, the mood has already gone bad.

Read More

Diablo Immortal Players Say the Haunted Carriage Sometimes Just Never Shows Up, Which Is a Bold Choice for an Event With “Carriage” in the Name

 

The game announces it. Players run to Ashwold. Then everybody stands there looking silly.

Diablo Immortal has another Haunted Carriage complaint on the board, and this one is almost impressive in how basic it is. In a fresh Blizzard bug report, a player says the game throws up the usual warning that the Haunted Carriage is coming in three minutes, tells everyone to head to Ashwold, and then… no event. No carriage. No boss. No spooky procession. Just a crowd of players showing up on time for a world event that apparently decided not to attend its own appointment.

What players are actually reporting

The report is short, but the hook is clean: this is not being described as a one-off fluke. The player says it does not happen every time, but “like half” of the Haunted Carriage attempts simply do not spawn. That is what makes it a usable story. If the event notification fires and players respond the way the game expects, only for the event itself to ghost them, then the whole loop starts to feel less like scheduled content and more like Sanctuary’s least reliable bus service.

It also fits a broader Haunted Carriage pattern

This is not even the first Haunted Carriage-related headache Diablo Immortal players have been dealing with lately. Blizzard’s own Bug Report board showed multiple Haunted Carriage threads active around April 6–7, including the new non-spawn report and other recent complaints tied to Haunted Carriage progress. There was also a separate March report about the Horrid Haunted Carriage event notification not taking players to the event, which Blizzard marked resolved, plus older threads where players said Haunted Carriage kills or completion were not registering properly. So even if this specific non-spawn issue is new, the broader Haunted Carriage track record is not exactly clean.

Why this matters more than it sounds

A world event bug like this is not as dramatic as a login failure or vanishing paid bundle, but it is exactly the kind of thing that makes a live-service game feel sloppy. Diablo Immortal is built on timers, routines, and quick little loops where players jump in, knock something out, and move on. If the game pings the server with “event’s up” energy and then serves empty cemetery air, people notice fast. And right now, Diablo Immortal is not exactly short on trust issues. We already covered the shop loading bug that keeps blocking rewards, the Battle.net purchase bug where claimed bundles can vanish,  and the Party Finder bug that hides activities. Another event acting weird is not catastrophic on its own, but it absolutely adds to the “what is broken today?” mood.

The weird little problem with event-based games

The funniest part is that this is the sort of bug that makes players feel foolish more than angry at first. They got the prompt. They went where the game told them to go. They did the responsible little live-service thing. And then Diablo Immortal basically left them standing in Ashwold waiting for a ghost cart that never arrived. If more players start reporting the same thing, this could turn from a stray annoyance into a very real event-reliability problem. For now, it is one of those wonderfully dumb bugs that sounds fake right until it wastes your evening.

Read More