Diablo II: Resurrected Players Say Repeated Disconnects Are Starting to Feel Like the Real Endgame Boss

Diablo II: Resurrected just had its patch-cycle mess with the Steam launch issue and the follow-up hotfix, so you would hope things were settling down a bit. Instead, a newer complaint is now bubbling up in Blizzard’s Technical Support forum, and this one hits a lot harder if you actually play the game the way D2R tends to demand: long sessions, careful farming, and enough patience to make a monk look impulsive.

A fresh wave of disconnect complaints is popping up

A new Technical Support thread posted on April 5 says repeated disconnects are knocking players out of online sessions mid-run, with one player describing an Uber Tristram attempt that died right as Uber Diablo was about to go down. After reconnecting, the portal was gone and the whole run was effectively wasted. That is not a minor inconvenience. That is Diablo II turning your prep work into smoke.

Why this one stings more than a normal crash

In a modern live-service game, a disconnect is annoying. In Diablo II: Resurrected, it can be expensive. The forum post spells that out pretty clearly: keys, organs, Terror Zone farming time, and the kind of slow solo setup that takes actual effort can all disappear because the session falls apart at the wrong moment. If you are farming online and the game drops you at the worst possible second, there is no graceful recovery here. Sanctuary is not exactly famous for refunds.

It does not look like a one-player setup problem

That is the part that makes this worth watching. By April 6, other players had piled into the same thread saying they were seeing disconnects despite stable fiber connections, and one said the day had been the worst so far with more than 15 disconnects. Another said switching internet source did not help, while one more reported the issue showing up every five to fifteen minutes after otherwise stable play. Blizzard’s Technical Support index also shows the thread as active on April 6, so this does not look like one random complaint that vanished into the void.

Right now, the problem is uncertainty

That may be the ugliest part of all. Players can work around a known bug. They can avoid a broken skill, skip a bugged quest, or put off a farm until a fix lands. What they cannot really plan around is the feeling that any productive run might get yanked out from under them with no warning. Diablo II has always been ruthless. It just usually tries to kill you with demons first. 

Read More

Diablo Immortal Players Say a Login Bug Is Hiding Server Lists, and Blizzard Is Still Investigating

Diablo Immortal has a new kind of problem on its hands, and it is not the fun sort where a boss drops too much loot by accident. Over the past week, multiple players have reported that the game successfully logs them into Battle.net, shows the usual “tap to play” prompt, and then simply refuses to display a server name, which means they cannot get to character select at all. The reports showed up first in late March and were still active on April 5.

What players are actually seeing

The most common version of the issue is brutally simple: the login works, but the server list does not. Players in Blizzard’s Diablo Immortal forums describe restarting the game, repairing the client, uninstalling and reinstalling, and still getting stuck on a blank server section. One player said the issue had dragged on for more than 10 hours at one point, while others said they had lost several days of playtime.

It started looking like an iOS problem

The early reports were heavily tied to iPhone and iPad users. Blizzard’s Technical Support and Bug Report sections both show active iOS-tagged threads for the same issue, and affected players listed devices including iPad Pro, iPhone 15, and iPhone 14 Pro Max. The game versions reported in those threads center on the 4.3.0 branch that followed Diablo Immortal’s recent The Taking update.

The weird workaround makes this even stranger

The most interesting detail is that several players say they can sometimes get in over cellular or by using a hotspot, but not over home Wi-Fi. One player said they could log in on LTE and then switch back to Wi-Fi after getting into the game. Another thread participant suggested the issue might involve how the client reaches game servers after authentication, although that part remains community speculation rather than an official explanation.

Blizzard has at least acknowledged the problem

This is the part that matters. In the forum thread, Blizzard community manager Kalviery asked affected players to provide device, OS version, game version, location, and internet provider details so the Immortal team could investigate. Players in the same discussion also shared a support response saying the issue is known and under investigation, though Blizzard has not posted a public fix yet.

Right now, this is a login problem with real collateral damage

That is what makes it worth watching. A bad balance patch annoys people. A login bug keeps them out of events, battle pass progress, clan activity, and the rest of the daily treadmill Diablo Immortal is built around. When a live-service game cannot reliably get players from login to character select, that is not background noise. That is the game failing at the front door.

Read More

Diablo 4’s First Lord of Hatred Cutscene Finally Makes the Expansion Feel Real

For a while, Lord of Hatred has mostly existed as a release date, a feature list, and a growing pile of pre-purchase bonuses. Now Blizzard’s marketing push finally has something meatier to show. The first cutscene from the expansion, revealed through IGN First coverage, gives Diablo 4 something it badly needed: an actual mood. Not a bullet-point mood. A real one.

The rollout has moved past store-page energy

That matters more than it sounds. Blizzard’s official expansion page says Lord of Hatred launches on April 28, 2026, brings a new campaign, new endgame activity through War Plans and Echoing Hatred, and major updates for all Diablo IV players including deeper hero progression changes and a loot filter. Those are solid features, but features alone do not sell an expansion this close to launch. Atmosphere does.

“The Queen and the Saint” is doing more than teasing lore

The first revealed cutscene, “The Queen and the Saint,” leans into ritual, public devotion, and the sort of smiling manipulation Diablo does well when it is not busy drowning the screen in blood and item text. As recapped by Icy Veins, the scene centers on a ritual atmosphere, Queen Adreona, Lorath, and the suggestion that something deeply wrong is hiding beneath all the reverence. That is a much better opening note than another generic “evil is coming” trailer.

Why this matters now

Diablo 4 has spent a lot of recent weeks trapped in bug reports, reward complaints, and Season 12 weirdness. So Blizzard pivoting the conversation toward faith, control, and Mephisto’s influence is probably not an accident. It is a reminder that Lord of Hatred is supposed to feel like a proper next chapter, not just a content drop with extra cosmetics taped to it. Season 12 was also framed by Blizzard earlier this year as part of the broader road toward the expansion’s launch, which makes this story-focused push feel very deliberate.

Blizzard is clearly building a month-long drumbeat

Blizzard has already been feeding out supporting material around the expansion, including a Warlock lore story in March and a full class spotlight that confirmed the Warlock arrives with Lord of Hatred on April 28. Pair that with the IGN First reveal cycle, and the strategy is obvious enough: stop explaining the expansion like a product page and start selling it like a dark fantasy campaign again. Honestly, about time.

Read More

Diablo 4 PTR Players Say Boss Loot Chests Can Literally Trap You

 

The loot room is not supposed to become the boss fight

Diablo 4’s PTR has produced a fresh little nightmare, and it is the kind only a loot game could invent. A new April 5 PTR bug report says a player got physically stuck between boss loot chests, with teleporting to town and coming back doing nothing to fix it. According to the post, the only way out was using the Leave Dungeon option.

That is a very Diablo sort of problem. You kill the boss, walk over to claim your prize, and the real reward is discovering the chest geometry has decided to hold you hostage. It is not the biggest bug in the world, but it is exactly the kind of awkward PTR issue that instantly makes a feature feel clumsy.

What the report actually says

The report itself is short and painfully clear. The player says they became stuck in between the Boss Loot Chests, and that normal quick fixes did not work. Porting back to town and returning failed. Only manually leaving the dungeon got them unstuck. That suggests the issue is not just a visual overlap or some harmless collision weirdness. It is a movement-blocking problem tied directly to the post-boss reward area.

This is also not buried somewhere obscure. Blizzard’s PTR Bug Report forum shows “Boss Loot Chests - Stuck on them” as an active topic on April 5, and the main Diablo IV latest-topics page surfaced it there too. That gives it enough freshness to count as real current PTR chatter rather than some old leftover report no one saw.

Why this one matters

Normally, a player getting wedged into map geometry would be a minor curiosity. The reason this one matters is context. Blizzard’s newer boss-loot structure already leans heavily on chest interaction after the kill, with Hoard-style loot chests acting as the real payout point rather than the boss simply vomiting all the good stuff onto the floor. So if the chest cluster itself can trap the player, that is not just a funny collision bug. It is the reward system tripping over its own furniture.

There is also a practical PTR angle here. PTR bugs are narrower than live-server bugs, sure, but this is exactly what the PTR is for: finding systems that technically function while still feeling terrible in practice. A loot chest should create a moment of payoff, not a tiny panic where the player wonders whether they now have to abandon the run just to move again.

A small bug that makes the whole reward flow look sloppy

That is the real issue. Nobody is going to quit Diablo 4 forever because a PTR chest pinned them in place one time. But bugs like this make the game feel awkward at the exact moment it is supposed to feel satisfying. You beat the boss. You move toward the loot. You get stuck between the containers like Sanctuary’s dumbest sandwich filling. That is funny once. It is less funny if it ships.

Read More

Diablo Immortal Players Say Repeated Crashes Are Still Wrecking Sessions

 

One of the most basic problems in any live-service game is still showing up the hard way

Diablo Immortal has a fresh crash complaint on the forums, and it is not the polite kind. A new April 5 General Discussion post says the player has been dealing with crashes for around two months, with the game closing completely while Battle.net stays open, sometimes in bursts of four to six crashes in a row before things calm down again for a while.

That alone would be enough for a service piece. What makes it more interesting is the effort the player says they already put in trying to fix it. According to the post, they reinstalled the game multiple times, checked GPU drivers, reinstalled Windows, and even tested the same Battle.net account on a different PC, only to see the same pattern there too. If that account is accurate, this stops looking like one cranky machine and starts looking a lot more like a deeper game-side or account-side problem.

What the player is actually reporting

The report says the crashes can happen across a wide spread of activities, including TR, dungeons, towers, vault, and more. The player also notes that there is no lag warning beforehand, no obvious slowdown, and no clear trigger beyond the fact that the crashes keep returning in clusters. That kind of randomness is part of what makes crash bugs so maddening. A performance problem you can reproduce is annoying. A performance problem that appears to roll dice first is much worse.

The same post adds a useful detail: the player says Blizzard support directed them to the forums and suggested a developer might need to look at it, with the player even wondering whether their character might be bugged. That is not proof of an account-specific issue, but it does show the complaint is not just “my PC is old, please help.” The player had already gone through the usual support loop before posting publicly.

Why this one is worth covering

This is not yet a giant multi-page meltdown thread, so it is fair to keep expectations in check. But it is fresh enough to matter. Blizzard’s Diablo Immortal forums show “Crash spamming me!” as an active April 5 discussion topic, and the general forum page places it among the latest live threads right now. That gives it enough immediacy to count as current bug chatter rather than some dead complaint from weeks ago.

It also lands in a broader environment where Diablo Immortal’s bug-report board is still active with multiple current technical and gameplay complaints, including interaction bugs, server-load issues, tracker problems, and update-related glitches. That does not prove all of those are connected to this crash issue, but it does reinforce that the game is not exactly having a quiet, spotless technical week.

A crash bug does not need to be flashy to be destructive

That is probably the cleanest angle here. Diablo Immortal can survive a weird tooltip, a messy tracker, or one confused event toggle. Repeated hard crashes are different. If players are getting dumped out of the game four to six times in a row across multiple activities, the real problem is not class balance or event timing. It is whether the session can stay alive long enough to matter. And that is a much uglier story than most patch-note bugs ever become.

Read More

Diablo Immortal Players Say the Bloody Rage Essence Can Break Basic Interactions

 

A Barbarian bug is turning one combat setup into a weird quality-of-life trap

Diablo Immortal has a fresh Barbarian bug on the board, and this one is less about damage numbers and more about your character suddenly forgetting how doors work. A new April 5 bug report says equipping the Bloody Rage legendary essence and then activating Wrath of the Berserker can leave the character unable to interact with objects like shops, doors, chests, and other interactables until another skill is used.

That is a pretty ugly little bug because it hits one of those basic systems players never think about until it breaks. Nobody loads into Diablo Immortal expecting to fight the UI just because they used a skill combo. If your Barbarian can still kill demons but cannot open a chest without casting something else first, the game starts feeling less like an action RPG and more like an oddly hostile escape room.

What players are reporting

The report itself is very specific. The player says that after equipping the off-hand essence labeled Bloody Rage and triggering Wrath of the Berserker with the listed setup, object interaction becomes completely blocked. According to the report, the issue persists indefinitely and only clears after using another skill, with Whirlwind given as one example that restores normal behavior. The report lists the platform as PC and the operating system as Windows 11.

There is a small wrinkle in the thread: one reply suggests the player may actually mean Bloodseizer rather than Bloody Rage. That matters because it introduces a little naming uncertainty around the exact essence involved. But the core bug claim stays the same either way: some version of this Barbarian setup appears to be breaking object interaction after Wrath of the Berserker is activated.

Why this is worth covering

On Blizzard’s current Diablo Immortal bug-report board, the thread is already sitting among the active April 5 topics, which gives it enough freshness to count as live bug chatter rather than some old issue being exhumed for content. It is not a giant multi-page meltdown yet, but it is current, specific, and easy for affected players to understand immediately.

It also lands badly because this is not some niche visual glitch. Interacting with objects is basic gameplay plumbing. If a class setup can shut that off until the player manually “unsticks” the character with another skill, that creates friction in dungeons, menus, town stops, and any fast-paced loop where movement and interaction timing matter. In a game built on speed and repetition, that kind of bug becomes annoying very fast.

A small bug that makes the game feel clumsier than it should

Maybe Blizzard fixes this quickly and it disappears before it grows into a bigger issue. That would be the clean outcome. But right now, the report points to one of those awkward bugs that makes the game feel less polished in a very obvious way. A Barbarian build should make you feel stronger, faster, and more dangerous. It probably should not make you bounce off a shopkeeper like you forgot how hands work. 

Read More

Diablo 4 Players Say Season 12 Rewards Still Aren’t Paying Out Correctly

 

Another fresh reward complaint has hit the forums

Diablo 4’s Season 12 reward issues do not look fully dead yet. A fresh April 5 forum post says a player did not receive the Level 7 seasonal capstone reward, adding another complaint to the growing pile of “I finished the thing, where is my loot?” threads that have been circling Season of Slaughter.

That would already be irritating on its own. The bigger problem is that it does not feel isolated. A separate April 4 bug report says a player completed the relevant seasonal progression and still did not get the expected Resplendent Spark, tying the frustration to one of the season’s more meaningful reward hooks rather than some forgettable cosmetic scrap.

What players are reporting

The newer thread is blunt: the player says they hit Level 7 seasonal capstone and the reward simply did not arrive. No big mystery, no elaborate reproduction steps, just the kind of report that usually means the system looked complete on the front end and then failed at the exact moment it was supposed to pay out.

The April 4 report adds more context and a slightly uglier angle. In that thread, the player says they completed Season Journey Chapter 6 / Bloodied Lair Boss progression and still did not receive the Resplendent Spark reward they were expecting. That matters because Sparks are not fluff. If one goes missing, the player does not just feel mildly inconvenienced. They feel robbed.

Why this matters more than a routine bug thread

Reward bugs land harder than a lot of combat or UI bugs because they strike at the basic contract of the season. Diablo can be grindy, messy, and sometimes weirdly overcomplicated, but players will tolerate a lot if the game actually pays them when they finish the objective. When it does not, the whole loop starts to feel untrustworthy.

Blizzard’s official 2.6.1 patch notes already show that Season of Slaughter has needed multiple fixes, including reward-related ones. The patch specifically addressed issues like the Brutality challenge not awarding a Resplendent Spark and problems with Bloodied Nightmare Dungeon Obducite drops. That is important context because it shows Blizzard already knew Season 12 reward logic was misfiring in at least some places.

The season’s reward trust problem is not gone yet

That is what makes these newer complaints worth covering. Even if the latest missing Level 7 reward and missing Spark reports turn out to be narrower than earlier bugs, they fit a pattern players have already been trained to distrust. Season 12 has had enough payout problems that every fresh “reward missing” thread now lands with a lot less benefit of the doubt.

And honestly, that is the real damage here. A seasonal reward is supposed to feel like a payoff. If players are hitting major milestones and immediately opening the forums to check whether the loot bugged out again, the season starts feeling less like progression and more like customer support with extra demons.

Read More

Diablo 4 Players Say the “Taste of Power” Quest Can Block Progress Entirely

 

A seasonal quest bug is turning one missing checkbox into a hard stop

Diablo 4 players have found another Season of Slaughter headache, and this one is nastier than a missing tooltip or a bugged cosmetic. A fresh April 4 bug report says the seasonal quest “Taste of Power” can fail to count its steps correctly, leaving the player unable to progress after using a Meaty Offering at the Shrine of Slaughter.

That is a rough bug for one obvious reason: this is not about efficiency or bad drop luck. It is a progression blocker. According to the report, the player transformed into the Butcher, summoned demons, killed them, and collected their blood, but only got credit for the blood collection step. The quest did not credit the summon step, and because the player had already spent the offering, they were stuck without another immediate way to retry.

What players are reporting

The forum post is short, but the problem is very clear. The player says they used their Meaty Offering, triggered the event correctly, and completed the combat portion, yet the quest state only advanced partway. In other words, the game appears to recognize the aftermath of the event without recognizing the event itself. That is exactly the kind of quest bug that makes players want to alt-tab straight into a support thread.

This is also not buried in some dead corner of the forums. Blizzard’s Diablo IV PC Bug Report index showed “Taste of Power quest not counting steps correctly - can’t progress” as an active April 4 topic, which is enough to make it part of the current live bug conversation around Season 12.

Why this one matters more than a routine bug

Season of Slaughter is built around Butcher-themed progression, including the new Butcher Lair Boss, Blood-related rewards, and systems tied to embracing the season’s whole butcher fantasy. Blizzard’s official season overview makes that framing pretty explicit. So when a quest like Taste of Power breaks at the point where the player literally transforms into the Butcher and performs the required sequence, it hits right in the middle of the season’s main identity instead of off to the side somewhere harmless.

There is also no obvious comfort in the current official patch notes. Blizzard’s March 20 Diablo IV patch notes include several Season of Slaughter fixes, including issues with transformation behavior, Shrines of Slaughter, and Butcher-related interactions, but nothing there specifically calls out Taste of Power or this exact quest-state failure. That does not mean Blizzard will not fix it quickly. It does mean players hitting it now do not have a neat official “known issue resolved” line to lean on.

When one consumed item becomes one wasted attempt

That is the part that makes this land badly. If a quest step fails after consuming an item needed to trigger it, the problem stops feeling small very quickly. Players can forgive a little jank. They are much less forgiving when the game takes the item, half-completes the objective, and then shrugs. In a season already packed with bugs, reward weirdness, and progression complaints, this is exactly the kind of issue that makes a quest chain feel brittle instead of exciting.

Read More

Diablo Immortal’s Mirrored Jewels Event Is Live Again, but Players Are Already Arguing About How It Actually Works

 

A familiar gem event is back for a short run

Diablo Immortal’s Mirrored Jewels event is back again, with fresh forum posts confirming it went live on April 1 at 03:00 server time and runs until April 7 at 03:00 server time. That gives players another short window to squeeze extra value out of Elder Rift gem runs, which is why the event tends to get attention fast whenever it returns.

If you have not dealt with Mirrored Jewels before, the basic appeal is pretty simple: when the event is active and you toggle it before an Elder Rift run, each Legendary Gem you earn from Legendary Crests or Eternal Legendary Crests is accompanied by an additional random Legendary Gem of the same type and random quality. Blizzard described that setup in earlier official event coverage, and the current community discussion still reflects that same core mechanic.

Why players care every time this shows up

Mirrored Jewels is one of those Diablo Immortal events that does not need much explanation because the value proposition is obvious. More gem output in a game built around gem progression tends to get people moving quickly, especially when the event window is short and tied to a resource players already think about in terms of timing, efficiency, and whether now is the “right” moment to spend crests.

That also explains why the event immediately generates confusion whenever players think it failed to pay out correctly. On April 1, one bug-report thread claimed a player received only 12 gems when they expected 20, but replies in that same discussion argued the misunderstanding came from using a mix of crest types. According to the explanation shared there, Mirrored Jewels duplicates rewards generated by Legendary and Eternal Legendary Crests, not the 1-star gems generated by Rare Crests.

The event is live, but the bug chatter is already here too

There is also at least one newer bug report suggesting the event may still behave in confusing ways even when the player changes their mind mid-setup. In that April 2 thread, a player said they checked the Mirrored Jewels box at the Elder Rift, then unchecked it before finishing the run, but the event still triggered anyway. That is just one report, not proof of a widespread bug, but it fits the usual Diablo Immortal pattern where a straightforward event gets a layer of uncertainty added by edge-case behavior and messy UI clarity.

A good event is still only as good as its explanation

That is probably the cleanest read on Mirrored Jewels right now. The event itself is back, the timing is clear, and players who understand the crest rules can still get solid value out of it. But the first wave of forum posts also shows the usual friction: questions about what counts, complaints about expected rewards, and at least one report of the toggle not behaving the way the player thought it would. In a game this systems-heavy, even a generous event can start feeling sketchy if the rules are not obvious the moment you click the box.

Read More

Diablo Immortal Players Still Sound Uneasy About Battlegrounds, Even With Blizzard’s New Matchmaking Tweaks

 

Blizzard adjusted the system, but the mood around PvP does not exactly scream “problem solved”

Diablo Immortal’s latest PvP conversation is landing in a familiar place: Blizzard has made another matchmaking adjustment, and players are still debating whether Battlegrounds actually feels healthier or just differently frustrating. Blizzard’s official Patch 4.3.1 post says overall player power is once again a matchmaking factor for Legend rank and above in Assault, Convoy, and Tower War, a change the company says should improve the experience and competitive integrity.

That sounds sensible on paper. But the Diablo Immortal forums are still showing fresh late-March discussion threads like “Battleground MM trolling?”, “The current meta of PvP”, and “Barbs still way too strong at pvp,” which is usually a pretty good sign the community does not think one switch-flip suddenly fixed the whole mode. Even without a giant single-thread meltdown, the pattern is there: players are still arguing about matchmaking quality, class balance, and whether PvP is actually fun or just something they tolerate for rewards.

What Blizzard says is changing

Blizzard’s own description of 4.3.1 is pretty modest. It calls the update a minor maintenance update, not some sweeping Battlegrounds overhaul. The biggest PvP-facing change is that player power has been reintroduced as a matchmaking factor at high rank, while the rest of the post leans more on Refined Battle Pass cosmetics and event rotation than on any dramatic PvP rescue plan.

That matters because Blizzard has already signaled that a bigger PvP rethink is coming. In its earlier The Taking preview, Blizzard said Diablo Immortal’s Battlegrounds would get their first major seasonal refresh in April 2026, with new visual themes and gameplay rhythm adjustments across both Classic and Convoy maps. In other words, Blizzard itself has already framed Battlegrounds as a mode that needs more than tiny maintenance nudges.

Why players still do not sound convinced

This is where the community angle gets interesting. If high-rank matchmaking changes were enough on their own, you would expect the forum mood to calm down a bit. Instead, the visible discussion mix still points to broader frustration: class-specific PvP complaints, meta complaints, and matchmaking complaints are all alive at the same time. That does not prove Battlegrounds is broken beyond repair, but it does suggest the current PvP unease is bigger than one bad queue or one overpowered build.

And honestly, that lines up with Blizzard’s own messaging. You do not promise a major seasonal refresh that reimagines PvP flow, spectacle, and emotional arc unless you know the existing version has started to feel stale, uneven, or overly mechanical. Patch 4.3.1 may improve some high-end match quality, but it also feels a bit like Blizzard buying time until the real Battlegrounds rewrite arrives. That is an inference, but it is a grounded one based on how Blizzard has described both updates.

PvP needs more than another polite patch note

That is probably the fairest read right now. Diablo Immortal’s PvP scene is not short on activity, but activity and health are not the same thing. Blizzard is clearly still tuning the mode, and the upcoming refresh suggests it knows deeper changes are needed. Until that lands, the community mood seems pretty simple: Battlegrounds is still under the microscope, and players are not ready to declare victory just because the patch notes used the phrase “competitive integrity.”

Read More

Diablo Immortal Players Say the Gem Find Tracker Looks Busted After the Update

 

A small tracker bug can still make the whole grind feel sketchy

Diablo Immortal has a fresh post-update annoyance on its hands, and this one hits a system players watch closely. A bug-report thread posted on April 1 says the game’s Gem Find Tracker is showing numbers that do not line up with what players are actually finding, with the in-game party buff and the Codex tracker apparently telling two different stories. The thread stayed active into April 4 on Blizzard’s bug-report board, so it is not just a one-minute complaint that disappeared into the void.

That matters because gem tracking is not cosmetic fluff in Diablo Immortal. Players use those counters to measure whether they are hitting daily limits, whether a run paid out properly, and whether event bonuses are actually doing what they are supposed to do. If the tracker starts lying, even a little, the whole reward loop starts to feel slippery.

What players are reporting

The clearest report says the player’s 4-man party buff claimed they had found 5 bound gems that day, while their Codex Gem Tracker showed 11 daily gems found instead. The player specifically says the issue is not about their final totals matching after one last drop. The real complaint is that the display itself seems inconsistent and confusing, especially around the way bound and unbound gems are being counted.

A second Diablo Immortal bug thread, posted the next day, points to the same general problem. That player says after their first few daily gem drops, the icon was showing the wrong split between bound and unbound gems, even though their actual drops did not match what the counter was claiming. That follow-up thread explicitly references the earlier Gem Find Tracker report, which makes this look less like one strange screenshot and more like a pattern players are noticing after the update.

Why this is worth covering

On Blizzard’s Diablo Immortal bug-report index, “The Gem Find Tracker seems BUSTED after the update” was still sitting among current active topics on April 4, alongside other fresh reports. That does not prove the bug is widespread across the whole player base, but it does show the complaint is current enough to be part of the live post-update bug chatter.

There is also a decent theory floating around from Reddit: one player suggested Blizzard may have been trying to prepare the gem counters for the incoming Winds of Fortune event and ended up creating a mismatch in the display. That is still community speculation, not an official explanation, but it is at least a plausible read on why the tracker would suddenly start acting weird right after an update.

When the counter becomes the problem

This is the kind of bug that sounds small until you remember how much live-service games rely on trust. If players cannot tell whether their gem drops are being counted correctly, they start second-guessing the run, the event, and the system itself. Diablo Immortal does not need more uncertainty in a rewards economy that already asks players to watch numbers like hawks. A tracker is supposed to remove doubt, not become part of it. 

Read More

Diablo 4 Players Say Season 12 Lag Complaints Are Still Getting Hard to Ignore

 

The bugs may rotate, but the latency threads are not going away

Diablo 4’s Season 12 lag problem is still hanging around, and at this point it is getting harder to write off as a few isolated bad sessions. Blizzard’s own Diablo IV forum pages still show active April 4 threads for “High latency, EU, 260 - 500ms, after last patch?”, “Intermittent High Latency,” and the still-active “Extreme lag and instability season 12” report. That does not automatically prove one single root cause, but it does show the same basic complaint is alive across both Technical Support and bug-report categories right now.

What players are reporting

The most specific current thread is the EU latency one. There, players say ping has been jumping into the 260 to 500 ms range after the recent patch, with one April 2 reply saying cross-play helped only “a bit in the fields” while lag and disconnects were still happening regularly. That is not subtle stutter-talk. That is the kind of latency where the game starts feeling like it is making combat decisions three seconds after you did.

And it is not just one thread sitting there unloved. Blizzard’s Diablo IV latest-topics page still shows Intermittent High Latency, the EU high-latency thread, and Extreme lag and instability season 12 all surfacing together on April 4. When multiple lag threads keep floating to the top at once, it usually means the issue is not fully dying in the background. It means players are still running into it often enough to keep feeding the fire.

Why this matters more than a random support complaint

Normally, one technical-support post is not much of a story. But recurring latency complaints hit differently in Diablo 4 because this is a game built around timing, movement, positioning, burst damage, and not getting flattened while your screen lies to you. If the connection goes bad, the whole game gets stupid fast. Dodges come late. Skills feel delayed. Enemies appear where they were not a moment ago. And suddenly the real boss fight is the route between you and Blizzard’s server. That is not a fun surprise in any ARPG, let alone one that keeps asking players to push harder seasonal content.

Blizzard’s patch notes do not offer much comfort here

That is part of why the complaints still land. Blizzard’s current Diablo IV patch-note entry for 2.6.1 is packed with Season of Slaughter fixes, reward fixes, and gameplay adjustments, but there is no obvious broad latency or server-performance fix called out there. That does not prove Blizzard is doing nothing behind the scenes, but it does mean players looking for a neat public explanation are not finding one in the official notes.

When the season’s hardest mechanic is packet travel

Maybe Blizzard gets this under control quietly. Maybe it is more regional than global. Maybe it is one of those ugly post-patch connection spells that clears up after a few days. But right now, the forum pattern is clear enough to say this much: Season 12’s lag complaints are not gone, and players are still talking about them like a real part of the game experience. In Diablo terms, that is a bad sign. Nobody wants their strongest seasonal enemy to be latency spikes with a decent internet plan. 

Read More

Diablo 4 Players Say the Wardrobe Is Just Not Working

 

Sanctuary has many horrors. Your closet should not be one of them.

Diablo 4 players have found a new bug to trip over, and this one is not exactly endgame-defining. It is just deeply annoying in a very live-service sort of way. A fresh April 4 bug report on Blizzard’s Diablo IV forums says the Wardrobe can become completely unresponsive, with no popup, no error, and no visible reaction whether the player clicks the Wardrobe NPC or the wardrobe icon from the inventory menu.

That might sound minor next to all the usual Diablo drama about loot, balance, or broken seasonal systems. But cosmetic systems matter more than game forums like to admit. If players are spending time collecting transmogs, pets, and outfits, then the basic expectation is simple: the part of the game meant to show them off should at least open.

What players are reporting

The current report is extremely straightforward. The player says the Wardrobe gives “absolutely nothing” back when interacted with. No error message. No UI window. No response at all. They also note that the issue happens both through the actual Wardrobe interaction point and through the icon inside the inventory, which makes it feel less like one broken NPC and more like the entire feature deciding to clock out for the day.

This is not buried in some ancient dead forum either. Blizzard’s current Diablo IV bug-report index shows “Issue with Wardrobe – Cannot interact (no response)” among the active April 4 topics, and the main latest-topics feed also surfaced it the same day. So even if it is not yet a giant multi-page disaster thread, it is fresh enough to count as live bug chatter, not archaeology.

Why this one is worth covering

Wardrobe bugs are not exactly new in Diablo 4. Blizzard’s forums also contain older reports from 2024 and March 2026 describing wardrobe and transmog problems on PC and Steam, including broken saves, cosmetics not sticking, and the feature failing to work properly after returning to the game. That does not prove today’s issue is the exact same bug, but it does suggest the Wardrobe has a bit of history when it comes to behaving like a cursed piece of furniture.

And that is what makes this more than a throwaway complaint. Diablo 4 already asks players to engage with cosmetics, mounts, pets, and premium looks as part of the broader live-service loop. When the styling room itself stops responding, it makes the whole system feel flimsier than it should. Nobody wants the real final boss of fashion to be a dead button.

A small bug that still makes the game feel cheap

Maybe Blizzard fixes this quickly and it disappears without much fuss. That would be ideal. But right now, the Wardrobe issue lands in that especially irritating category of bug where nothing explodes, nothing crashes, and yet the game still manages to feel broken in a way players notice instantly. In a loot game built partly on looking cool, a closet that will not open is not just cosmetic. It is a tiny quality-of-life failure wearing a very visible hat. 

Read More

Diablo Immortal’s Battlegrounds Refresh Looks Like Blizzard Finally Admitting PvP Needed More Than Small Tweaks

 

April’s big Diablo Immortal PvP change is not subtle

Diablo Immortal is lining up its first major Battlegrounds seasonal refresh for April 2026, and Blizzard is pitching it as more than a balance pass. According to the company’s official preview for The Taking, this refresh will rework the flow, spectacle, and emotional rhythm of PvP across both Classic and Convoy maps, with new visual themes and gameplay pacing changes meant to make fights feel more impactful.

That wording matters, because it reads like Blizzard finally admitting what long-time Immortal PvP players already know: Battlegrounds did not just need a few knobs turned. It needed a fresher coat of paint and some mechanical rethinking too. When a developer starts talking about “flow” and “emotional arc,” it usually means the old version had started feeling a little too routine, a little too solved, or a little too exhausting for the wrong reasons. 

What Blizzard is actually changing

Blizzard says the refresh touches both presentation and match tempo. The official description points to new visual themes and gameplay rhythm adjustments that are supposed to heighten tension, reinforce player impact, and deepen immersion in Sanctuary. That is still fairly broad language, so this is more of a directional preview than a full mechanical breakdown. But the key takeaway is clear enough: this is not being framed as a tiny side tweak. It is a PvP refresh Blizzard wants players to notice. 

There is also a smaller but more concrete PvP change already attached to Patch 4.3.1. Blizzard says overall player power is once again a matchmaking factor for Legend rank and above in Assault, Convoy, and Tower War. That gives the Battlegrounds refresh a little more context. Blizzard is not only repainting the arena. It is also still poking at the numbers behind who gets thrown into it. 

Why this is worth watching

The biggest reason this matters is simple: PvP systems do not usually get a “major seasonal refresh” label unless the existing version has started to show some wear. Diablo Immortal has spent plenty of time pushing events, passes, modes, and monetized cosmetics, but Battlegrounds is the kind of long-term feature that can quietly sour if players start feeling every match plays out with the same tempo and same frustrations. A refresh like this is Blizzard saying it knows that risk is real. 

A better Battleground is better than another menu event

That is probably the strongest angle here. Diablo Immortal does not need more stuff to click through nearly as much as it needs its core activities to stay sharp. If this Battlegrounds refresh genuinely makes PvP feel faster, clearer, and less stale, it could end up mattering more than a lot of louder update bullet points. And if it does not, players will figure that out fast too. PvP has a nasty habit of exposing fake fixes in public.

Read More

Diablo II: Resurrected’s New Hotfix Is Tiny, but It Fixes One of Those Bugs That Should Never Stick Around

 

Blizzard moved quickly after 3.1.2

Diablo II: Resurrected just got Hotfix 1 for patch 3.1.2, and this one is about as small as a post-launch fix can get. Blizzard’s official note contains exactly one gameplay change: Warlock Bind Demon pets will no longer leave interactable corpses. That is the whole hotfix. No balance shake-up, no ladder drama, no giant cleanup list. Just one targeted fix, pushed live on April 2.

That may sound minor, but honestly, this is the kind of bug that gets annoying fast if it sits around. Anything that leaves behind interactable corpses when it should not can create confusion, clutter, and weird player behavior, especially in a game where loot, summons, corpses, and targeting all already compete for attention on screen. Diablo does not really need extra fake body management on top of its normal corpse economy.

What the hotfix actually does

Blizzard’s wording is blunt: the hotfix “fixed the issue with Warlock’s bind demon corpses” and “Bind Demon pets will no longer leave interactable corpses.” That suggests the pets were leaving behind remains that the game still treated like valid corpse objects, which is the kind of thing that can feel harmless for five minutes and then gradually turn into nonsense once enough players start poking at it.

It also fits the broader shape of 3.1.2, which was already a technical cleanup patch. Blizzard’s April 1 patch notes for Reign of the Warlock focused on crashes, disconnects, UI sizing, graphics issues, chat-name display, Blood Oath behavior, Warlock pet deaths tied to Blood Boil, Death Hex visuals, and vendor dagger counts. So this new hotfix reads like Blizzard spotting one extra Warlock-related mess after launch and stamping it out before it had time to become a bigger forum hobby.

Why this still matters

The interesting part is not that this hotfix is huge. It very clearly is not. The interesting part is that Blizzard followed 3.1.2 with a fast corrective patch instead of letting one awkward leftover bug linger for another week while players turned it into memes and workarounds. In a season built around a new class and class-specific mechanics, that kind of follow-up matters more than the word count in the patch note.

Small patch, useful signal

So no, this is not the most dramatic Diablo story of the week. But it is a useful one. Diablo II: Resurrected’s latest hotfix shows Blizzard is still actively sanding down the rough edges around Reign of the Warlock, even when the issue is narrow enough to fit in a single bullet point. And in patch-note terms, one clean bullet that removes a dumb bug is usually better than ten lines of noise pretending to be content.

Read More

Diablo 4 Players Say a Mythic Goblin Bug Can Turn a Rare Key Into Nothing

 

A rare dungeon reward is getting attention for the worst possible reason

Diablo 4 players are flagging a new frustration around the Mythic Prankster dungeon setup: a fresh April 3 bug report says a player used their first-ever Mythic Prankster key, found the goblin inside, and then watched it become effectively untouchable before it vanished, taking the reward with it. The forum post describes the goblin as taking no damage at all for a few seconds and then disappearing, leaving the player with no mythic payout and no key.

That is a nasty little bug story because the hook is brutally simple. This is not some common overworld goblin that slipped away in the usual chaos. It is tied to a rarer key-based reward setup, which means the failure feels more expensive the moment it happens. And since Blizzard’s own current Diablo IV patch notes already reference the Mythic Prankster Nightmare Dungeon reward pool, the feature itself is clearly live and relevant in the current season.

What the forum thread actually says

The original report is short, but specific. The player says they located the goblin in the dungeon, tried to kill it, and found that it could not be damaged before it disappeared. They also say this was their first mythic key of this type and asked for the key to be refunded. That part matters, because it frames the issue less as “annoying goblin behavior” and more as “rare seasonal reward consumed, nothing meaningful returned.”

There is an immediate wrinkle, though. A reply in the same thread argues this may not be a literal invulnerability bug at all. According to that response, if a goblin has already been spooked and started its escape sequence, it can remain visible for a few more seconds while no longer being damageable. In that interpretation, the player may have reached the goblin too late rather than hitting a broken enemy state. That does not make the experience feel any better, but it does mean the current evidence points to two possible readings: real bug, or badly communicated goblin escape behavior.

Why this still feels like a real story

Even with that caveat, the story works because the result is the same from the player side: a rare key was spent, the goblin could not be killed when it mattered, and the reward window slammed shut. Blizzard’s forum indexes show the thread surfacing among fresh Diablo IV bug reports on April 3, which at minimum tells you the complaint is current enough to be part of the live season’s bug chatter.

And that lands awkwardly against Blizzard’s broader Season 12 tuning. In the official Diablo IV patch notes, Blizzard already reduced Mythic Prankster Nightmare Dungeon rewards from five Mythic Uniques to one, which means the whole activity has already become less generous than before. So if players now feel they can also lose the run entirely to goblin behavior they cannot clearly read in the moment, the feature starts looking less like a jackpot and more like a slot machine with an attitude problem.

A rare reward should not end with “maybe you were too late”

That is really the issue here. Maybe this turns out to be a misunderstood escape timer rather than a true invulnerability bug. Fine. But then the design still failed in another way, because a player spent a rare key and came away thinking the encounter was broken. In a loot game, that distinction matters less than developers sometimes think. If the goblin is technically working while still feeling completely wrong, players are not going to send thank-you cards to the tooltip team. 

Read More

Diablo 4 Players Say the Codex of Power Imprinting Bug Is Still Alive

 

Blizzard said aspect values were fixed. Players say the Occultist missed the memo.

Diablo 4 has another “wasn’t this supposed to be fixed already?” problem on its hands. Players are reporting that the Codex of Power still isn’t imprinting aspects correctly, with fresh forum activity on April 4 pushing the issue back into view. The core complaint is ugly in a very Diablo way: you unlock a stronger Codex rank, head to the Occultist, and the game stamps the aspect onto your gear at the minimum possible value anyway.

That would already be annoying on ordinary gear. On endgame pieces, it feels worse. The original March 15 bug report says an Ultimate Shadow Aspect at Rank 14/21 still imprinted at the floor value instead of using the higher Codex rank the player had earned. The thread then stayed active into late March and early April, which is usually a sign the problem did not quietly solve itself in the background.

What players are saying is broken

The current complaint is pretty specific. Players say the Occultist is ignoring their stored Codex progression and applying the weakest version of an aspect when imprinting. That turns the Codex into something halfway between a library and a practical joke. You grind out better rolls, the interface shows the better rolls, and then the imprint comes out looking like you never earned them.

What makes it harder to dismiss is that this is not just one buried report from mid-March. Blizzard’s own Diablo IV forum index still showed the thread active again on April 4, and recent Reddit discussion around the same issue says players are seeing minimum-value imprints on current-season gear as well. Reddit is not proof by itself, but it does support the idea that this is still being felt by actual players, not just preserved in one old bug post like a fossil in the forum tar pit.

Why this lands badly

The awkward part is that Blizzard already published a fix that sounds very close to this problem. In the 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 wording matters, because from the player side, the live complaint sounds an awful lot like exactly that.

That does not automatically prove Blizzard’s fix failed completely. It could be a narrower issue, a new version of an old bug, or a season-specific edge case. But from the outside, the player experience is pretty simple: the patch notes say one thing, and the Occultist is apparently still out here handing out bargain-bin aspect rolls.

When progression stops feeling real

This is why Codex bugs irritate people faster than some flashier issues. Diablo is a loot game. If players cannot trust a core progression system to preserve the power they already earned, the whole gearing loop starts to feel slippery. And when the Occultist turns your upgraded aspect into a minimum roll, that is not just a bug. That is the game taking your homework, setting it on fire, and charging crafting materials for the privilege. 

Read More

Diablo 4 Players Say Clearing Pit 100 Can Wreck the Season’s Fresh Meat Farm

 

Progression is supposed to open doors, not slam one shut

A fresh Diablo 4 bug report is getting attention for a pretty ugly reason: one player says clearing Pit Tier 100 effectively bricks the season’s Fresh Meat farming loop by forcing all future sigils into the harder Bloodsoaked version. The complaint, posted on Blizzard’s Diablo IV bug-report forum on April 4, argues that this turns endgame progression into a punishment instead of a reward.

What players say is happening

The core complaint is simple. Once a character clears Pit 100, Bloodstained sigils reportedly stop being the practical farm option and the loop shifts into Bloodsoaked sigils, which are much tougher. According to the report, that means farming Fresh Meat and chasing Bloodied gear suddenly becomes dramatically less efficient, even for players who were otherwise enjoying the seasonal grind.

This does not look like a one-thread tantrum either. Related forum discussions from March 24 and March 25 were already describing the same broader problem: players who crossed the Pit 100 threshold saying they could still do Bloodsoaked content, but at a much slower pace, making their Fresh Meat farm feel noticeably worse. One reply even suggested leveling a separate character just to keep access to the easier sigil loop, which is exactly the sort of workaround that sounds clever until you remember it is completely ridiculous.

Why this matters in Season 12

Blizzard’s own 2.6.0 patch notes frame Bloodstained sigils as a key part of the Season 12 endgame, with Bloodsoaked sigils positioned as an even harder step up. Then, in Patch 2.6.1 on March 24, Blizzard said it had already reduced the difficulty of Bloodsoaked sigils significantly because many players could not reasonably complete them after unlocking access. That official note matters because it shows Blizzard already knew this part of the progression curve was causing friction.

So when players now say Pit 100 progression effectively locks them into a worse farming loop, it does not sound like random whining. It sounds like another version of the same structural problem: Season 12’s harder tier exists, but the route into it may still be punishing players who were just trying to progress normally.

The real problem is the season feeling backward

That is the part that lands badly. Diablo is built on the fantasy that stronger characters get better options. If reaching a major milestone makes your farm slower, clunkier, and more annoying, the system starts feeling upside down. And nothing kills an endgame grind faster than the sense that your reward for pushing higher was making your own season worse. 

Read More

Diablo Immortal’s Trading in Blood Event Has Moved Into Trial of the Hordes, and Patch 4.3.1 Is Mostly Here to Keep Things Tidy

 

This week’s Diablo Immortal update is more maintenance pass than major moment

Diablo Immortal is in one of those live-service weeks where the game is clearly doing something, even if it is not exactly screaming for attention. Blizzard’s Trading in Blood event is now in its Trial of the Hordes phase from April 1 to April 8, while Patch 4.3.1 has gone live with a lighter set of changes focused on matchmaking, Battle Pass cosmetics, and a couple of event handoffs. It is less “huge content drop” and more “the machine is still running, here is what is currently worth checking.”

Trial of the Hordes is now the active Trading in Blood phase

The useful bit for players is straightforward. Blizzard says Trading in Blood runs from March 25 to April 15 and rotates its progression activities week by week. The first phase was Survivor’s Bane. The current phase is Trial of the Hordes through April 8, and after that the event rolls into Fractured Plane from April 8 to April 15. Blizzard also describes Trading in Blood as a more unified version of the old Event Center flow, with a shared rewards tracker and escalating rewards across its phases.

What Patch 4.3.1 actually changes

Patch 4.3.1 itself is pretty modest, which is not necessarily a bad thing. Blizzard says the update brings back overall player power as a matchmaking factor for Legend rank and above in Assault, Convoy, and Tower War, a move meant to improve match quality at the high end. It also introduces the first Refined Battle Pass cosmetic set in Season 51 on the upgraded track, continuing the new multi-season cosmetic progression system Blizzard started in Season 50.

The other event pieces worth knowing about

There are also a couple of side events wrapped around this update. Spring into Action runs from April 1 to April 16, with daily and weekly tasks tied to rewards like Aspirant’s Keys, Runes, Telluric Pearls, Set Items, Legendary Items, and a Legendary Crest. Then on April 9, Blizzard kicks off Winds of Fortune, which doubles several reward types for a limited time, including Gold, Experience, Battle Pass Points, Normal Gems, and Legendary Items from a long list of activities.

Not a glamorous week, but a useful one

That is probably the honest read here. This is not the week Diablo Immortal reinvents itself. It is the week Blizzard rotates the active event, tweaks high-rank PvP matchmaking, pushes its refined cosmetic system forward, and lines up the next reward boost. In other words, not flashy, but functional. And live-service games usually need a few of those weeks to keep the louder ones from falling apart.

Read More

Blizzard Says Diablo II: Resurrected’s Steam Launch Bug Has Been Fixed, but Players Are Still Comparing Results

 

The broken-patch story now has an actual update

Yesterday’s Diablo II: Resurrected Steam mess has moved from pure damage report into follow-up territory. After players flooded Blizzard’s forums with complaints that the new 3.1.2 update was causing an “Initialization Error: Failed to initialize data (corrupted?) — Error Code: 1” on launch, Blizzard posted that it had rolled out a fix on Steam and that players should now be able to get back into the game. That makes this a real update, not just the same bug story reheated.

What Blizzard said

The clearest official response showed up directly in the forum threads where players were reporting the issue. In both General Discussion and Technical Support, Blizzard staffer Marcoose replied that a fix had been rolled out on Steam. That is the important part here: Blizzard did not just acknowledge the bug existed. It said a platform-specific fix was already live.

What players were seeing before the fix

Before that response, the problem looked pretty ugly. Multiple Steam players said Diablo II: Resurrected stopped launching immediately after the April 1 update, while forum posts described the error as affecting the Steam version specifically and contrasted it with Battle.net installs that appeared to be working normally. Blizzard’s own 3.1.2 patch notes had framed the update as a practical cleanup patch covering crashes, disconnects, UI, graphics, chat names, Blood Oath, and Warlock pets, which made the launch failure land even harder. A patch meant to fix technical issues had, for some players, become the technical issue.

The awkward part: not everyone was instantly back in

That said, the fix rollout did not seem to produce instant universal relief. In the same Technical Support thread where Blizzard said the Steam fix had been deployed, later replies still reported the game was not working for everyone right away. At the same time, players were sharing a manual .build.info workaround in separate forum threads, which suggests the community was still patching around the patch while waiting to see whether Blizzard’s Steam-side fix had fully settled in.

A cleaner ending, but not a pretty one

So yes, this one has moved forward. Blizzard says the Steam issue is fixed, and that is real news. But it is still the kind of patch-day story that leaves a mark, because the follow-up is not “what a smooth maintenance update.” It is “the emergency response arrived after the patch faceplanted on launch.” Diablo players are used to dealing with demons. They are a little less patient when the loader screen becomes one.

Read More