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 the Black Screen Teleport Bug Still Refuses to Die

 

Sanctuary has plenty of horrors already. The loading screen does not need to become one of them.

Diablo 4 has a black screen bug making the rounds again, and this one sounds especially miserable because it tends to hit right after teleporting. According to Blizzard’s own main black screen thread, players are getting dumped into a blank screen while the HUD, cursor, chat, or even music can still keep going in the background. In other words, the game is not fully dead. It is just dead enough to ruin your session.

What players say is actually happening

The reports are pretty consistent. Players say the bug often shows up after teleporting to town or other overworld locations, and the usual fix is the least glamorous one possible: close the game and start over. Several posts in the thread describe the bug hitting multiple times in a single day, with one player saying it now happens every time they play and another saying the game has become “basically unplayable.”

That is what makes this a real story and not just one grumpy forum post. Blizzard’s current PC Bug Report board still lists the black screen teleport thread among the most active Diablo 4 bug topics on April 6, with hundreds of replies and well over 18,000 views. That is a lot of people staring into the void, and not in the philosophical Diablo sense.

Why this one matters more than a random visual bug

A weird animation glitch is funny once. A teleport bug is different, because teleporting is basic Diablo housekeeping. You sell junk, stash gear, hit the occultist, jump back out, and keep the run going. When that loop starts randomly bricking the game, it wrecks the rhythm of play more than a lot of flashier bugs do. Players in the thread say the issue kills momentum, ends runs, and in some cases makes them want to stop the season entirely.

There is also a hardware angle people keep circling. A number of affected players list AMD GPUs, though not every report does, and no official Blizzard post in the thread has pinned the problem on one vendor. So right now, that part stays in the “possible pattern, not confirmed cause” bucket.

Blizzard has at least acknowledged it, but not fixed it

That is the current state of play. In the same forum thread, Blizzard support rep Joynueer asked players to send in FenrisDebug.txt logs by email so the team could narrow the issue down. That is better than silence, but it is not a fix, and players in the thread are clearly past the point where “please send logs” feels comforting. They want the game to stop eating teleports. Fair enough.

Read More

Diablo 4 Players Say Loyalty Mantle Has Multiple Bugs in Season 12

Diablo 4’s Season 12 bug stream is still coughing up fresh problems, and this time the spotlight is on a specific item instead of a dungeon or activity. On March 29, Blizzard’s PC Bug Report board picked up a new thread titled “Loyalty mantle has multiple bugs,” with the player claiming the item is misbehaving in several different ways at once.

That matters because item bugs tend to land harder than minor UI annoyances. If a piece of gear is not displaying correctly, not linking correctly, and not rolling or buffing stats the way players expect, then the problem is no longer cosmetic. It starts to chip away at trust in the loot itself.

What is happening

According to the March 29 report, Loyalty Mantle is showing at least three separate issues. The player says linking it in chat only prints a text-format ID instead of creating an actual clickable item link, even though party members can still see it. They also say the item is only appearing with movement speed as the Ancestral stat. On top of that, when the item is Bloody, the only stat getting buffed is the Bloody stat, which the player says is the same every time when the item is both Ancestral and Bloody.

This is also not the first time Loyalty Mantle has shown up on Diablo IV’s bug boards. Older forum listings show reports tied to the same item in October 2024 and October 2025, including one thread titled “Loyalty Mantle not lowering Cooldown of Unstable power.” That does not prove the March 29 complaints are the same underlying bug, but it does suggest this item has had a history of trouble.

Why it matters

This matters because Diablo 4’s item game is supposed to be the part players can rely on, even when balance gets messy. If a unique item starts generating bad links, odd stat behavior, and questionable Bloody/Ancestral interactions, it becomes harder for players to tell whether they found a bad roll, misunderstood the item, or hit an actual bug. That confusion is part of the damage.

It also lands inside a wider Season 12 atmosphere that already looks unstable. On the same March 29 board view, Blizzard’s forums were showing fresh reports for Bloodmark problems, Rank VI tracking issues, black screens, and Hellish Descent access bugs. In that context, Loyalty Mantle does not look like a quirky one-off. It looks like one more system slipping at once.

Current status / what Blizzard said

Blizzard’s latest official Diablo IV patch notes, version 2.6.1 dated March 24, 2026, focus on Bloodsoaked Sigil tuning and several Season of Slaughter fixes. Those notes do not mention Loyalty Mantle or any of the specific item issues described in the March 29 thread.

When the loot starts feeling suspect

Diablo 4 can survive balance arguments. What it handles worse is the feeling that a unique item might not even be behaving like itself. If Loyalty Mantle is genuinely bugged on multiple fronts, that is the sort of problem that makes every drop feel a little less trustworthy. 

Read More

Diablo 4’s Teleport Black Screen Bug Looks Back — And Players Say It Is Still Forcing Hard Quits

Diablo 4’s Season 12 bug board has already spent days filling up with progression issues, combat problems, and item reports. Now another old headache appears to be back in force: players say teleporting can dump the game into a black screen that never properly resolves, leaving them stuck until they force the client closed.

That is not just a minor loading hiccup. In the newest March 28 reports, players describe the game going black after teleporting while the rest of the PC keeps running normally, with some saying the menu can still be opened but the world itself never comes back.

What is happening

The cleanest new thread is titled “Black screen when teleporting to a location on the map.” In it, the player says every teleport after updating sends the game to a black screen that does not recover, forcing them to quit out completely.

A second March 28 thread, “Constant blackscreens after teleport + disconnects,” describes a similar problem from another angle. That player says every few teleports in Seasonal play the game dies into a black screen, the OS itself remains fine, and they had to fully kill the client at least three times in one day; they also mention random disconnects happening alongside it.

This also does not look isolated to just two fresh posts. Blizzard’s PC Bug Report index currently shows multiple black-screen topics active at once, including “Latest Patch Black Screen with GUI still showing after teleport,” which had more than 500 replies and over 18,000 views by March 27, plus older threads like “Black screen after teleport” and “Black screen with Season 12 start.”

Why it matters

This matters because teleporting is not some niche edge-case mechanic. It is basic movement, pacing, and session flow. When a core travel action starts sending players into forced black screens, the bug stops feeling cosmetic and starts making the game itself feel unreliable minute to minute.

It also fits a broader Season 12 pattern. Blizzard’s current PC bug board is already stacked with fresh reports around lag, healing, item handling, progression tracking, and black-screen behavior. In that context, teleport crashes do not look like one weird technical outlier. They look like another stress point in a season already under pressure.

Current status / what Blizzard said

Blizzard’s latest official Diablo IV patch notes, version 2.6.1 dated March 24, 2026, say the team has been monitoring feedback and include fixes for Bloodsoaked Sigils, Season Rank and Capstone issues, and general stability-related problems. But the notes do not specifically call out the current teleport black-screen reports.

So right now, the clearest picture is still coming from the forums: the new March 28 threads are live, older black-screen threads remain active, and there is no listed official fix yet that clearly maps to this specific teleport problem.

When travel becomes the crash

Diablo 4 can survive rough tuning debates and bad seasonal objectives. What it handles worse is making normal movement feel dangerous to the client itself. If players start treating every teleport like a coin flip, that is the kind of bug that poisons a session fast.

Read More

Diablo 4 Trade Issues May Be Getting Worse — Not Better

Diablo 4’s Season 12 already has enough trouble without the economy wobbling too. But that is where the conversation is drifting now, as fresh PC bug reports suggest trading problems are no longer limited to one awkward item-window glitch. Players are now reporting issues with both item trading and Trade Chat, which makes the whole trading loop look shakier than it did a few days ago.

That matters because Diablo 4 does not need a giant player economy to feel the damage. If players cannot reliably move items through the trade window or even communicate through Trade Chat, then one of the game’s few remaining social market systems starts to feel half-broken.

What is happening

The most direct report is still the March 26 thread “Unable to trade items,” where a player said they tested multiple non-account-bound items and could not place any of them into the trade window. The workaround they used was dropping the item on the ground and trusting the other player to send gold afterward. A March 27 reply added that clicking the item directly in the inventory worked for at least one player, which suggests the system may be failing inconsistently rather than being fully disabled for everyone.

That would already be enough for one article. The newer wrinkle is Trade Chat. In the March 24 thread “No Trade chat on PC,” one player said they could see their own messages going out but could not see anyone else’s, and others could not see theirs either. A March 27 reply claimed the chat channel had apparently turned itself off in settings and had to be re-enabled multiple times. Blizzard’s PC Bug Report board also shows a separate March 26 thread titled “Trade Chat Completely Dead - Trapped in ‘Ghost Instance’ (No Messages In or Out),” which makes this look bigger than one isolated settings problem.

Why it matters

This matters because Diablo 4 trading is already limited compared with more open ARPG economies. When a limited system starts misfiring, the friction hits harder. If players cannot trust the item window, and they also cannot trust Trade Chat to help line up deals, the whole feature starts to feel unreliable instead of merely restricted.

It also lands at a bad time. Blizzard’s current PC bug board is crowded with Season 12 issues across progression, combat, healing, and stability. Trading problems landing in that environment do not look like a side annoyance. They look like one more system slipping at once.

Current status / what Blizzard said

Blizzard’s latest official Diablo IV patch notes for 2.6.1, published March 24, include Season of Slaughter fixes, reward fixes, and general stability improvements. They do not specifically list a current fix for these item-trading or Trade Chat reports. That does not prove Blizzard is ignoring them, but as of now, the trading complaints are still visible on the active bug board after that patch went live.

When even the market feels unstable

Season 12 does not just have a balance problem. It is starting to feel like the small systems around the edges are fraying too. And when players have to choose between broken trade tools and trust-trading items on the ground, that is a bad look for Sanctuary. 

Read More

Diablo 4 Season 12 Is Running Into a Bigger Problem Than Balance — Basic Survivability and Stability

Diablo 4’s Season 12 has already spent days buried under complaints about Bloodsoaked tuning, broken objectives, and reward issues. Now the mood on Blizzard’s PC bug board is drifting into something more fundamental: some players say the game is starting to feel unstable at the level of basic survival and responsiveness.

On March 27, Blizzard’s Diablo IV PC Bug Report board showed active threads for “Extreme lag and instability season 12,” “Defiance Aura with Rite of Prayer not healing for correct amount,” and an older “Healing and fortify suddenly not working on my paladin character” thread that was still active again today. That is not one narrow class complaint. It is the kind of cluster that makes a live season feel shakier than Blizzard probably wants.

What is happening

The lag thread paints the broadest picture. Players describe freezes, rubber-banding, stuck animations, enemy pop-in, queued attacks and damage, repeated disconnect-style behavior, and menus or interactables needing multiple attempts to work. Multiple replies say the issue happens regardless of activity and started recently enough to feel tied to the current season state.

At the same time, healing-related reports are adding a nastier edge. In a new March 27 post, one player said Defiance Aura with Rite of Prayer was healing for only 5–6 HP per second instead of the roughly 91 HP per second shown by the tooltip. The older paladin thread reports healing and fortify being “completely busted,” with healing ticking for less than 10 HP and fortify failing to register from healing at all.

Why it matters

This matters because players can tolerate a rough objective or a badly tuned activity longer than they can tolerate systems that make the game feel unreliable second to second. Lag can kill characters. Broken healing or fortify can make builds feel suddenly hollow. When both appear in the same live conversation, the season starts to look less like it has isolated bugs and more like it has general instability.

It also widens the story beyond one subclass or one mechanic. Blizzard’s own bug board today shows survivability complaints sitting alongside trading issues, progression blockers, and even reports of characters being unable to attack or cast spells. The pileup is part of the problem now.

Current status / what Blizzard said

Blizzard’s latest Diablo IV patch notes, version 2.6.1 from March 24, focused on Bloodsoaked Sigils and several Season 12 fixes, including various Season Rank and Capstone completion problems. Those notes do not specifically mention the current lag thread, the new Defiance Aura healing report, or the older paladin healing-and-fortify issue.

When survival starts to wobble

Season 12 can survive angry balance threads. What it handles worse is the feeling that core play is slipping. When players are questioning whether the game can track actions cleanly, heal correctly, or stay stable under normal play, that is a darker problem than tuning.

Read More

Diablo 4 Trading Looks Shaky Right Now — And That Is a Bigger Problem Than It Sounds

Diablo 4 has spent most of the last week dealing with Season 12 complaints around difficulty, rewards, and progression. But another issue is starting to creep up through the forums, and this one cuts into something more basic: trading. On March 26, fresh PC bug reports described players being unable to place items into the trade window at all, even while gold trading still worked.

That may sound niche compared to a broken season mechanic, but it is not. Once trading starts behaving unpredictably, the damage spreads beyond one transaction. It hits player trust, item circulation, and the small economy Diablo 4 still has left.

What is happening

The clearest report came from a March 26 PC Bug Report thread titled “Unable to trade items,” where a player said they tested multiple non-account-bound items and could not add any of them to the trade window. Another active thread the same day, “I cannot add items to trade window PC, only gold,” described the same behavior: items would not enter the trade window, but gold could still be offered.

What makes the story stronger is that this does not look like one isolated bad click. Forum activity shows related trading problems hanging around beyond a single thread, including reports of the trade option being greyed out, players being stuck with trade chat issues, and one PlayStation report asking whether Season 12 trade chat was “working…BUT is it?”

One player in the March 26 item-trade thread said they ended up dropping the item on the ground and trusting the other player to pay gold afterward. That is a workaround, not a system. In a loot game, forcing players into honor-system trading is the kind of detail that makes the whole setup feel shakier than Blizzard probably wants.

Why it matters

Diablo 4 does not have a huge freewheeling player economy like some ARPG rivals, and players already debate how limited trading feels in general. That is exactly why system friction matters here. When the trade window itself stops behaving, even a modest economy can start to feel half-broken.

It also lands at a bad time. March 26 forum traffic was already crowded with Season 12 bug reports, known-bug discussion, and fresh complaints across multiple systems. Trading issues arriving in that environment do not look like a small side problem. They look like another crack in a season that is already under pressure.

What Blizzard has said

Blizzard’s latest Diablo 4 patch notes, updated March 24 for version 2.6.1, addressed Bloodsoaked Sigils and several season-related bugs. They did not list a fix for current item-trading problems. The most recent official trading-related fix visible in earlier patch notes was for PlayStation players being unable to use Trade Chat, which was addressed in January’s 2.5.3 notes, not in the current 2.6.1 update.

When the system starts to wobble

Trading bugs rarely become the biggest headline in Diablo 4. But when players cannot reliably move items through the game’s own trade window, the issue stops being cosmetic fast. It starts to make Sanctuary feel less stable than it should. 

Read More

Diablo 4 Players Are Still Reporting the Teleport Black Screen Bug

 

A long-running Diablo 4 PC bug is back in the spotlight, and players say it is still causing problems in Season 12. Across Blizzard’s official bug report forums, players continue reporting a black screen after teleport issue where the game appears to load the destination, the GUI remains visible, but the world never properly appears and the client effectively hangs. 

This is not a brand-new complaint that appeared overnight. The main bug thread dates back to August 21, 2024, but it has remained active for a long time, and Blizzard’s current PC bug report index still shows the topic with 527 replies, 17,813 views, and activity on March 20, 2026. That alone makes it a real Diablo story again, because it suggests the issue is not dead, buried, or solved enough for players to stop reporting it. 

What Players Say Happens

According to the main Blizzard forum thread, the bug usually hits during or immediately after teleporting, especially when moving to towns or crowded locations. Players say the teleport animation finishes, the HUD stays on screen, but the actual world never renders correctly, leaving them unable to interact normally. Some say they can exit to character select, while others report full crashes or disconnects. 

The thread’s original poster says the issue became more severe after an old patch, changing from a loading problem into a full black screen with GUI still showing. They also claim the bug seems more likely when teleporting to crowded locations, in groups, or between visually different regions. That is not an official Blizzard diagnosis, but it is one of the more detailed player attempts to identify a pattern. 

Players Have Been Reporting It for a Long Time

What makes this story notable is the sheer persistence of the bug. In the same thread, multiple players report seeing it every few teleports, especially when going to or from town, and some say it can consume their flow badly enough that they lose portals, waste time, or get kicked out of their session. One player says it happens every 3rd or 4th teleport, while another says it is especially noticeable when leaving The Pit. 

The PC bug report index also shows related threads still appearing now, including “Black screen after teleport,” “Game blanks out after teleport,” and “Constant disconnects on teleport” with activity on March 19–20, 2026. That suggests players are not just reviving one old complaint thread out of habit — they are still encountering similar teleport-related issues in the current version of the game. 

The Community Has Tried to Troubleshoot It Themselves

One reason the thread is so unusual is how much self-diagnosis players have already done. The original poster lists a long series of things they say did not fix the problem, including changing RAM, testing different graphics cards, reinstalling Windows, swapping network setups, and trying both DirectX 11 and DirectX 12. They speculate the problem could be tied to data loading during warps, but they also admit only Blizzard can really confirm what is happening under the hood. 

That is part of what keeps the frustration going. Players are not just reporting “game broke.” They are spending months trying to isolate the trigger, comparing hardware, reading Fenris logs, and still ending up in the same place: waiting for clearer Blizzard communication.

Blizzard’s Bug Index Shows It Is Still Current

The strongest reason to revisit the story now is the simple fact that the bug is still visible in Blizzard’s current PC Bug Report listings. On March 20, 2026, the category still shows the main black-screen thread near the top with fresh activity, alongside newer teleport-related bug reports. That does not prove Blizzard has internally classified them all as the same issue, but it does show that teleport black-screen complaints remain a live topic for Diablo 4 PC players right now. 

At the time of writing, I have not found a fresh Blizzard hotfix or patch note specifically confirming a fix for this teleport black-screen problem. So this should be framed as a community bug report story, not as a confirmed Blizzard resolution or newly acknowledged fix. 

Why This Matters in Season 12

Season 12 already has players talking about progression friction, bugged systems, and endgame headaches. A long-running teleport bug fits right into that broader mood, because it hits one of the most routine things players do in Diablo 4: moving around the world quickly. When that breaks, it does not just create one annoying moment. It disrupts the entire rhythm of farming, inventory clearing, dungeon chaining, and returning to town. 

And that is why this is still worth covering. It is not flashy. It is not a big Blizzard reveal. But when players are still reporting a teleport black screen bug with GUI visible in March 2026, nearly two years after the main thread began, that says something important about the current Diablo 4 experience on PC. 

Read More