Diablo 4 has done plenty of irritating things to player rewards lately, but this one is especially filthy. A fresh April 12 report says a player opened 19 Greater Bloodied Caches, got no items at all, and then watched the game crash seconds later. That is not bad luck. That is the sort of bug that makes a reward screen feel like a mugging.
The report is ugly in exactly the way you think
The current complaint appeared on Blizzard’s PC Bug Report forum under the title “I click all 19 greater bloodied cache , and no items came out. seconds later, game crash and shutdown.” The same issue also shows up on the broader Diablo IV forum index and in a separate Technical Support-style thread, which gives it a little more weight than one lonely post screaming into the void. It is still not proof of a widespread disaster, but it is definitely not nothing.
This lands badly because Diablo 4 already has cache trust issues
That is where the story gets nastier. Diabloz already covered how a Mythic Unique Cache could disappear after crafting, so this new report lands in a game environment where players are already primed to expect reward containers to behave like cursed prank boxes. This new case is different — it is not crafting, it is bulk opening followed by a crash — but the emotional effect is basically the same: you did the work, the reward existed in theory, and then Diablo 4 decided theory was enough.
Bulk opening makes the whole thing feel even worse
That is really the hook here. One missing reward is annoying. Nineteen at once is the kind of thing that makes a player immediately start counting what else they no longer trust. If the report is accurate, this was not just a cache bug. It was a cache bug chained directly into a client crash, which is about the least reassuring combo a loot game can offer. And because the post specifically says the items never came out before the shutdown, players are left with the classic Diablo question: did the loot fail to spawn, or did it spawn just long enough to disappear into some invisible administrative hell?
Reward systems should not feel this haunted
Blizzard has not attached a public fix or explanation to the report yet. So the careful version is still this: fresh player report, not confirmed mass issue. But even at that level, it is a strong story, because Diablo players can tolerate stingy drops far better than they tolerate vanishing ones. When a game starts eating containers, eating rewards, and then crashing on the way out, people stop arguing about balance and start wondering whether the loot system itself is drunk.
