Showing posts with label reward bug. Show all posts
Showing posts with label reward bug. Show all posts

Friday, 18 September 2026

Diablo 4’s Tree of Whispers Is Broken and Can Block All Further Progress


Diablo IV Season 15 has somehow managed to make the Tree of Whispers considerably more generous and completely useless at the same time. Players across PC and consoles are reporting that after reaching 10 Grim Favors, the usual Choose Your Reward screen opens with no caches inside it. The reward slots are blank, the Accept button cannot be used, and closing the window leaves the character sitting above the normal Grim Favor limit. Worse, once that happens, additional Whispers can become unavailable entirely.

This is not simply a visual problem where the cache icons forgot to load while the reward secretly exists somewhere behind the interface. Players are reporting characters stuck at values such as 11/10 and 13/10 Grim Favors, unable to complete the turn-in and therefore unable to properly reset the Whisper cycle. Blizzard has now officially acknowledged the problem, saying it is investigating an issue that prevents completed Whispers from being turned in at either Ravens or the Tree of Whispers.

Season 15 has already had several launch problems.

This one is particularly nasty because it can shut down an entire endgame activity.

The Tree of Whispers Reward Screen Is Completely Empty

The problem itself is easy to recognize.

You complete enough Whisper objectives to reach the required 10 Grim Favors. The map tells you it is time to collect your reward. You interact with a Raven of the Tree or travel all the way back to the physical Tree of Whispers in Hawezar.

The familiar reward window opens.

And there is nothing in it.

No cache names.

No icons.

No selectable reward.

The Accept button remains disabled.

Only Close works.

One of the larger reports on Blizzard's bug forum describes exactly that sequence, with the player reaching 10+ Favors and seeing a completely black reward area where the cache choices should normally appear. Other players quickly confirmed the same behavior across different difficulties and characters.

The issue has also been reported on PlayStation and Xbox, so this does not appear to be confined to one PC installation, one launcher or one especially cursed graphics driver.

It Can Block Every New Whisper Afterward

The bigger problem starts after the failed turn-in.

Normally, handing in 10 Grim Favors clears the required amount and allows the Whisper cycle to continue. Diablo IV also supports overflow. If you are sitting at 9/10 and complete a five-Favor activity, you can temporarily reach 14/10, with the extra progress carrying forward after the reward is collected.

That system has existed for multiple seasons.

With the current bug, however, the reward cannot be collected.

The character remains above the threshold.

Several players then report that additional Whisper activities on the map become greyed out or explicitly show Whispers as unavailable. One player described reaching 13/10 and being unable to do anything else because the game never completed the existing reward cycle.

So this is not simply:

"I lost one cache."

It can become:

"My character cannot continue using the Tree of Whispers at all."

Blizzard Has Officially Acknowledged the Problem

The good news is that this one is no longer sitting entirely inside community bug reports.

Blizzard added an official update to the Hotfix 2 discussion, confirming that the team is investigating an issue preventing players from turning in completed Whispers at both Ravens and the Tree of Whispers.

A later update said the investigation was continuing and that Blizzard was aiming to have a fix ready soon, while warning that the timing could still change.

That is important because it means players do not need to spend the afternoon reinstalling Diablo IV under the assumption that their local files have personally offended the Tree.

The problem is known.

Blizzard is working on it.

There is not yet a confirmed live fix.

Restarting the Game Does Not Reliably Fix It

Unfortunately, the usual first round of troubleshooting does not appear to help consistently.

Players have reported trying:

  • logging out and back in
  • completely restarting Diablo IV
  • restarting Battle.net
  • changing difficulty or Torment level
  • returning to the physical Tree of Whispers
  • using a Raven instead of the Tree
  • leaving the area and returning
  • turning cross-play off
  • repairing the game installation
  • in at least one case, completely reinstalling the game

The reward screen remained empty for many of them.

There are isolated reports of relogging helping earlier instances of the problem, but the current wave appears considerably more persistent. One player specifically noted that an earlier occurrence could be cleared by logging out, while later attempts became completely stuck.

That makes this different from several of the Warlock quest problems we covered yesterday, where changing difficulty or disabling cross-play can sometimes push the quest state forward.

With Whispers, there is currently no broadly reliable community workaround.

The Physical Tree Does Not Save You

One obvious idea is that the new Season 15 Ravens might be the problem.

They are not a reliable escape route.

Players who encounter the blank reward screen at a Raven have traveled back to the Tree of Whispers itself and received the same empty interface. Others who first discovered the problem at the Tree tried Ravens afterward with identical results.

Blizzard's own acknowledgement specifically mentions both locations.

That strongly suggests the problem is connected to the Whisper reward state rather than one particular NPC interaction.

The messenger is not broken.

The message apparently arrived without the loot attached.

Season 15 Made Whispers Much More Valuable

The timing is particularly unfortunate because Season 15 just gave players several good reasons to care about Whispers again.

We covered the changes in our look at Season 15's major Torment, XP and cache buffs. Whisper rewards received some of the biggest improvements in the entire progression update.

Gold Caches now provide substantially more Gold, with Blizzard using Torment XII as an example where a cache rises from roughly 35 million to around 100 million Gold.

Gem Caches provide roughly twice as many fragments.

Cube Material Caches provide around two to three times as many materials.

Salvage Caches receive similar increases.

Key Caches provide twice as many random Tributes and five times as much Sigil Dust, while also gaining a small chance to contain rare access items connected to Mephisto and Echoing Hatred.

Whisper turn-ins also provide more Experience Orbs.

In other words, Blizzard spent part of Season 15 making the Tree worth visiting again.

The Tree has responded by refusing to open the box.

All Three Splinters of Evil Also Interact With Whispers

The bug cuts into the seasonal system itself too.

As we explained in our Diablo, Baal and Mephisto Splinter guide, all three Prime Evil paths modify the Tree of Whispers.

Diablo primarily changes Helltides and Infernal Hordes.

Baal focuses on The Undercity and Lair Bosses.

Mephisto changes The Pit and Nightmare Dungeons.

But Whispers are shared across all three.

That makes them one of Season 15's universal progression activities rather than something relevant only to one chosen Prime Evil.

A bug that blocks Whisper turn-ins therefore reaches across all three seasonal paths.

This Can Also Interfere With Seasonal Objectives

There is another consequence beyond losing caches and activity access.

Season 15 contains seasonal objectives involving Whisper progression and turn-ins. Players stuck at the reward screen are therefore not simply missing one ordinary endgame loop. They can also find themselves unable to complete related seasonal progression until the problem is resolved.

That becomes more annoying because Season 15's new Rank structure contains 125 objectives spread across nine ranks, with the later rewards including Skill Points, Paragon Points, Resplendent Sparks and Mythic caches.

Not every objective has to be completed.

But losing access to an entire category is still something most players would rather avoid.

The Bug Does Not Appear to Require Whisper Overflow

Some early discussion focused on players reaching values such as 11/10 or 13/10 Grim Favors.

That led to speculation that the normal overflow system itself might be causing the problem.

There is currently no solid evidence for that.

Players correctly pointed out that Grim Favor overflow has worked for multiple seasons. Going above 10/10 is not inherently unusual.

More importantly, reports also exist from players who encountered the empty reward screen on what they described as their first normal 10-Favor turn-in.

So while overflow may be visible once the bug occurs, we should not confuse correlation with a confirmed trigger.

Blizzard has not published the root cause.

It Is Happening Across Different Difficulties

The reports also span a wide range of difficulty levels.

Players have reproduced the issue in normal leveling content as well as Torment difficulties ranging into the upper endgame.

One report came from a Torment VI Rogue.

Another from a Torment X character sitting at 11/10 Favors.

Console players have reported the same blank reward window on lower difficulty characters.

Several users specifically tried moving between Torment levels to force the reward list to refresh.

It did not reliably help.

That makes a difficulty-specific reward table failure look less likely from the outside, although only Blizzard can confirm the actual cause.

This Is Not the Same Problem as Solo Self Found

Because Blizzard mentioned the Whisper issue in the same broader communication surrounding Solo Self Found, some players initially assumed the two problems were connected.

Blizzard explicitly described the Whisper problem as a separate issue.

The current Tree problem affects the normal game too. Players in ordinary Seasonal play have reported it across PC and consoles.

SSF remains its own Season 15 problem.

Whispers have simply decided the week needed another one.

Do Not Waste Resources Trying to Reinstall Everything

For players already stuck, the practical advice right now is unpleasantly simple.

Wait for Blizzard's fix.

You can certainly try a relog or restart. They are quick and harmless.

But repeated difficulty swapping, traveling between every Raven in Sanctuary or reinstalling the entire game does not have a demonstrated success rate high enough to justify treating any of those steps as a solution.

One player reported repairing the installation and then performing a full reinstall without changing the result.

That is a great deal of data transfer to rediscover that the Tree still has no prizes.

Other Endgame Activities Still Work

The bug blocks Whisper progression on affected characters, but it does not mean the entire Season 15 endgame has stopped functioning.

Players can still run Helltides, Nightmare Dungeons, The Pit, Lair Bosses, Infernal Hordes, Waking Nightmares and the season's other systems.

The problem is that some of those activities normally overlap beautifully with Whispers.

You kill what you were already going to kill.

You collect Grim Favors in the background.

You eventually cash everything in at the Tree.

When that final step breaks, one of Diablo IV's cleanest multi-purpose progression loops becomes dead weight.

This Is Exactly the Kind of Bug Season 15 Did Not Need

Season of Hell's Legacy has had a rough opening.

Launch-day login problems became serious enough that Season 15 itself had to be temporarily delayed.

Players then reported old Paragon, Gold and materials appearing on fresh seasonal characters.

Solo Self Found remained unavailable.

Warlock class quests began getting stuck.

Old Eternal Mythics ran into new Crafted restrictions.

And now one of the game's oldest endgame systems can simply stop paying out.

That does not make Season 15 a bad season. Underneath the technical problems, the actual content contains some excellent ideas, including the hidden Diablo II Runewords players discovered inside the Horadric Cube.

But the first few days have asked for a remarkable amount of patience.

Blizzard Says a Fix Is Being Worked On

The most important thing now is that Blizzard has acknowledged the issue quickly.

The team says it is continuing to investigate and is aiming to have a fix ready soon, although timing remains subject to change.

Until that fix lands, affected characters may remain unable to turn in their completed Grim Favors or begin another proper Whisper cycle.

So if your Choose Your Reward screen contains absolutely no rewards, you are not missing a hidden button.

You are not at the wrong Raven.

You did not anger the Tree by choosing Mephisto.

And reinstalling Diablo IV probably will not convince it to negotiate.

The Tree of Whispers currently has exactly one thing to offer some players.

Silence.

Tuesday, 14 July 2026

Diablo 4’s Tower Rewards Bug Is Exactly Why Solo Self-Found Needs Clean Rules


Diablo 4 Patch 3.1.1 fixed a lot of loot problems.

Some were loud. Some were ugly. Some were the kind of patch notes that make players stare at their farming history and quietly wonder how much time the loot table owes them.

But one smaller fix says a lot about a mode that needs clean rules more than almost anything else:

The Tower had a bug where only one party member could receive rewards.

Blizzard also fixed an issue where the Solo Self-Found icon was missing on a player’s profile in the Friends list.

Two small fixes. One bigger point.

If Diablo 4 wants Solo Self-Found and competitive endgame systems to feel meaningful, the game has to be painfully clear about who earned what, when, and under which rules.

The Tower Bug Sounds Small Until It Happens To You

According to Blizzard’s Diablo IV Patch 3.1.1 notes, Patch 3.1.1 fixed an issue where only one party member could receive rewards from The Tower.

That is the kind of bug that sounds like background noise until you are the player who got nothing.

Then suddenly it is not background noise.

It is the entire orchestra falling into a pit.

The Tower is supposed to reward effort. Players push content, deal with enemies, spend time, and expect the basic contract to work: complete the activity, receive the loot.

When only one party member gets paid, the activity stops feeling like an endgame challenge and starts feeling like a cursed raffle run by a demon with spreadsheet access.

Reward Bugs Hit Competitive Modes Harder

Reward bugs are always annoying.

But they hurt more when they touch content connected to progression, competition, ranking, or self-imposed rule sets.

That is where Diablo 4 has to be extra careful.

In casual farming, a bugged reward is frustrating. In a mode where players care about clean progression and legitimacy, a bugged reward can poison the whole conversation.

Players do not just ask, “Did I lose loot?”

They ask, “Did this affect my push?”

They ask, “Did someone else get an advantage?”

They ask, “Was this run even counted properly?”

And once those questions start, good luck putting the demon back in the bottle.

Solo Self-Found Needs Visible Trust

The Solo Self-Found icon fix is smaller, but it points at the same issue from another angle.

Patch 3.1.1 also fixed a problem where the Solo Self-Found icon could be missing from a player’s profile in the Friends list.

That may sound cosmetic.

It is not only cosmetic.

Solo Self-Found is built on trust and identity. It tells other players that a character is progressing under stricter conditions. No trading safety net. No group-fed loot. No outside economy helping smooth the grind.

That badge matters because the restriction matters.

If the game supports Solo Self-Found, it needs to show it cleanly. Everywhere players expect to see it.

Otherwise, the mode starts to feel like a serious rule set wearing a missing name tag.

Clean Rules Are Part Of The Reward

Diablo players like difficult grinds.

They pretend they do not, but then they spend three hours running the same boss and call it “efficient.”

The real issue is not hardship.

The real issue is uncertainty.

Solo Self-Found and Tower-style progression only work when the rules are clean. The game needs to be clear about what counts, what rewards, what restrictions apply, and what other players can see.

If the systems are muddy, then achievement gets muddy too.

A player pushing hard under strict conditions wants the game to reflect that properly. A group clearing Tower content wants every eligible player to receive what they earned. A seasonal endgame mode needs to feel like a ruleset, not a haunted suggestion.

Diablo 4 Already Has Enough Loot Anxiety

Season 14 has not exactly been relaxing.

Players have been dealing with Iconic Mythic rarity, El’Druin chase routes, Pandemonium Fragments, Lair Boss questions, Forgotten Souls issues, War Plans reward bugs, and enough endgame resource tracking to make the Currency tab look like a tax audit.

That is why these smaller fixes matter.

Every bug that touches rewards adds to the same anxiety: is the game actually respecting my time?

The Tower reward fix answers one part of that. The Solo Self-Found icon fix answers another.

Neither one is glamorous.

Both are part of making the season feel less suspicious.

The Tower Cannot Feel Like A Lottery

If multiple party members complete an activity, the reward rules should be clear and reliable.

That is not a luxury feature. That is the floor.

The Tower bug failing to reward more than one party member is exactly the kind of thing that damages confidence because it makes players wonder what else is quietly failing behind the curtain.

And Diablo 4 does not need more curtain problems.

It needs endgame activities that feel consistent.

Hard? Sure.

Unforgiving? Absolutely.

Stingy? This is Diablo. The treasure goblin union probably demands it.

But inconsistent? That is where players start sharpening pitchforks.

Small Fixes, Big Legitimacy

Patch 3.1.1 is easy to frame as a loot patch, but it is also a legitimacy patch.

It fixes broken sources. It adjusts rewards. It repairs seasonal friction. And in these smaller Tower and Solo Self-Found fixes, it cleans up the rule layer around progression.

That matters more than the patch note size suggests.

Because the moment a player commits to Solo Self-Found, a Tower push, or any strict endgame route, Diablo 4 has to stop being vague. The rules need to be visible. The rewards need to land correctly. The profile needs to show the right identity.

Otherwise, the mode loses weight.

Solo Self-Found is only meaningful if the game treats it like more than a tiny icon.

The Tower is only worth pushing if the rewards behave.

Patch 3.1.1 fixed both.

Good. Now keep the rules clean, because Hell is already chaotic enough without the reward screen joining the enemy team.

Sources

Sources: Blizzard Diablo IV Patch Notes, More Diablo 4 coverage on Diabloz.net.

Friday, 17 April 2026

Diablo 4 Players Say Season 12 Rewards Are Still Going Missing, and the Latest Complaint Hits Bloodied Boss Loot

 

Another fresh reward complaint has hit the forums, which is not exactly the kind of sentence Diablo 4 wants attached to Season 12 at this point. This time the issue is simple, ugly, and very easy to understand: a player says they killed a Bloodied Greater Lair Boss on Torment IV and did not get the reward they were supposed to get. No confusing tooltip. No weird edge-case interaction. Just kill boss, receive disappointment. ([us.forums.blizzard.com](https://us.forums.blizzard.com/en/d4/t/season-12-reward-bug/245250?utm_source=chatgpt.com))

The fresh report comes from a new thread on the official Diablo IV PC bug report forum, posted on April 17, 2026. The player says they defeated a Bloodied Greater Lair Boss in Season 12 on Torment IV and simply did not receive the rewards. That thread is now sitting alongside another live topic in Blizzard’s latest PC bug listings called “Season Journey Rewards Bugged”, which is not new by itself but does help show that reward friction is still hanging around the seasonal experience like a bad smell. ([us.forums.blizzard.com](https://us.forums.blizzard.com/en/d4/c/bug-report/7?utm_source=chatgpt.com))

This is not the same bug, but it rhymes with all the others

That distinction matters. The older Season Journey Rewards Bugged thread is more about a fake “reward available” prompt that will not go away. The new Season 12 reward bug complaint is more direct: the player did the activity, killed the boss, and says the rewards never showed up. Different bug, same family, same growing suspicion that Season 12 is still a little too comfortable messing with player rewards. ([us.forums.blizzard.com](https://us.forums.blizzard.com/en/d4/t/season-journey-rewards-bugged/241982?utm_source=chatgpt.com))

And that is what makes this story useful even if the thread is still small. Diablo players can live with stingy drops. They can live with long grinds. What they do not love is uncertainty over whether a boss reward is actually going to pay out at all. That turns the whole progression loop from harsh-but-fair into “maybe the machine just eats this one.”

Season 12 has already trained players to be suspicious

The bigger problem is that Diablo 4 has already burned through a lot of reward trust this season. We recently covered how players were still getting fake “Season Rank Rewards Available” notices, and how Band of First Breath was reportedly dropping like a cursed object. Those are not the same issue. But they absolutely help set the mood around a fresh report like this. When rewards disappear in Diablo 4 right now, players are not shocked. They are annoyed in a very practiced way.

Fresh report, familiar anxiety

To be fair, this is still one fresh public report, not proof of a giant widespread meltdown. Nobody should oversell that. But it is live, current, and attached to one of the most sensitive parts of any ARPG: the moment when a boss dies and the game is supposed to hand something back. If players start feeling unsure about that exchange, everything else gets uglier fast.

At this point, Diablo 4 does not just need rewards to exist. It needs players to believe the rewards will still be there after they do the work.

Friday, 27 March 2026

Diablo Immortal’s Equalized PvP Push Looks Smart — But Bugs Are Already Crowding the Conversation

Diablo Immortal may have just made its most interesting PvP move in a long time. With Challenge of Equals, Blizzard introduced a new Bout of Realms variant that normalizes player power and strips out many of the progression advantages that usually shape high-end PvP. In a game that has spent years fighting pay-to-win criticism, that is not a minor systems tweak. It is a real statement.

The problem is that the rollout is already picking up the wrong kind of attention. Fresh bug reports from March 25–26 show players complaining about missing Bout of Realms placement rewards and a “scaling anomaly” inside Challenge of Equals itself, which is exactly the kind of friction this mode could not afford on week one.

What is happening

Blizzard’s March 12 and March 16 update posts framed Challenge of Equals as a fairer competitive format. Legendary affixes and set bonuses stay active, but systems like Normal Gems, Charms, Resonance, Legacy of the Horadrim, and Ancestral Tableau do not apply. Five-Star Legendary Gems are also normalized down to Two-Star values, and Blizzard even added curated Elite Slayer Loadouts to lower the barrier to entry.

But while Blizzard was selling a cleaner battlefield, players were posting about messier reality. One March 26 bug report says a team entered Challenge of Equals expecting normalized stats, only to see a player with “significantly amplified” damage and survivability, despite the event’s equalized rules. Another March 25 report says a top-32 team reward could not be collected before the event closed, even after the player tried both PC and Android.

Why it matters

This matters because Challenge of Equals is not just another side event. It is Blizzard testing whether Diablo Immortal can make PvP feel more legitimate without tearing out the game’s existing progression structure. If that test works, it gives Blizzard a credible answer to years of criticism. If it launches with reward issues and stat-normalization doubts, the whole pitch gets weaker fast.

There is also a wider pattern here. Reward complaints tied to Bout of Realms were already showing up earlier in March, including reports that “1st in points” rewards were not handed out correctly and that server-first tournament rewards went to the wrong team. That does not prove every new report has the same cause, but it does suggest tournament reward confidence was already shaky before Challenge of Equals arrived.

Current status / what Blizzard said

Blizzard has said it will continue monitoring feedback around Challenge of Equals, and its earlier preview also confirmed a broader Battlegrounds seasonal refresh is coming in April 2026, with new visual themes and gameplay rhythm changes for both Classic and Convoy maps.

A strong idea with no room for a sloppy first impression

Equalized PvP is one of the smartest ideas Diablo Immortal has put on the table in a while. But a mode built around fairness has a very small margin for technical confusion. If players start questioning the scaling, the rewards, or both, Blizzard’s best PvP idea in years could end up buried under the same old distrust.