Diablo 4 Players Say Grief’s +1,000 Weapon Damage Isn’t Actually Working

Diablo IV Season 15 brought back Grief, one of Diablo II's most famous Runewords, complete with a recipe expensive enough to make every Rune involved feel personally important. There is just one small problem. Players increasingly believe one of the weapon's biggest affixes is doing absolutely nothing. Grief can roll up to +1,000 Weapon Damage before Masterworking, yet multiple player tests suggest that bonus is not actually being added to the weapon's damage. One player spent more than twenty hours farming the Runeword before discovering that a considerably less impressive Rare weapon appeared to hit harder.

The reports have been circulating since shortly after Season 15's hidden Diablo II Runewords were discovered, but the issue has resurfaced on Blizzard's forums on September 25. That makes Grief an increasingly awkward member of the anniversary collection. It has the correct name, the familiar Rune recipe and an extremely attractive tooltip. The numbers underneath may simply have forgotten to participate.

Grief Is Supposed to Add Up to 1,000 Weapon Damage

Season 15's version of Grief uses the classic Eth + Tir + Lo + Mal + Ral combination and can be created from compatible one-handed Swords and Axes through the Horadric Cube. Its current affixes include Attack Speed, Deadly Strike, damage against demons and, most importantly for this problem, +750 to +1,000 Weapon Damage.

Its Unique effect also makes direct damage inflict 40% bonus Poisoning damage over five seconds, giving Grief an obvious place in aggressive melee builds.

On paper, this should be a serious weapon.

That is why players noticed when the paper stopped agreeing with the game.

A +1,225 Grief Lost to a Rare Flail

One of the clearest community tests involved an Item Power 925 Grief that had been Masterworked until its Weapon Damage affix reached +1,225.

The weapon displayed 2,182 DPS and a damage-per-hit range of 1,417 to 1,493.

The same player compared it with a Rare Item Power 925 Flail carrying only +168 Weapon Damage. That considerably less impressive weapon displayed 2,274 DPS and a damage range of 1,607 to 2,183.

The player then checked skill tooltips and tested the weapons against the Training Dummy, reporting that the Rare still produced higher overall damage.

That does not constitute an official Blizzard diagnosis, and differences between weapon bases, attack speeds and skill interactions always need to be considered when players compare equipment. But several people have independently reported the same basic issue: Grief's Weapon Damage number is visible on the item while the expected increase does not appear to materialize in actual character damage.

Players Have Been Reporting This Since September 17

The first Blizzard forum report we found dates back to September 17, only two days after Season of Hell's Legacy launched. The original poster said they had farmed for more than twenty hours to make Grief before concluding that it simply did not work correctly.

Additional players joined the report over the following days, and on September 25 another discussion appeared specifically asking why Grief's +1,000 Weapon Damage was not being applied.

That is important because Blizzard has already touched Grief in a hotfix.

Hotfix 4 corrected an unintended damage interaction between Grief and the five-piece bonus from the Old Mountain Talisman set. Blizzard therefore clearly has Grief on its radar.

The official Hotfix 4 notes, however, do not mention the basic Weapon Damage affix failing to apply.

Grief Has Already Been Involved in One Damage Bug

This gives the Runeword a slightly strange Season 15 history.

When combined with Song of the Old Mountain's five-piece bonus, Grief could contribute to unintended damage and Blizzard stepped in to correct the interaction. At the same time, players are claiming that Grief's ordinary Weapon Damage affix is underperforming or not functioning at all.

So depending on which system is involved, Grief has apparently managed to deal both too much damage and not enough damage during the same season.

That is impressive range.

Grief Was Supposed to Be One of the Big Anniversary Runewords

The problem matters more because this is not an obscure recipe nobody intended to use.

Grief is one of Diablo II's iconic Runewords. In the older game it became famous for its enormous flat damage contribution and its ability to turn several melee builds into extremely efficient killing machines. Seeing Eth Tir Lo Mal Ral return inside Diablo IV immediately gave veterans a very specific expectation.

Season 15 deliberately leans into that recognition. Blizzard has hidden nineteen Diablo II-style Runewords inside the Horadric Cube, allowing players to rediscover combinations such as Stealth, Enigma, Spirit, Infinity and Grief rather than simply reading them from a seasonal tutorial.

The idea has worked remarkably well. Players have spent days experimenting with bases, Ancestral versions and Transfiguration.

Unfortunately, experimentation has also revealed several things Blizzard presumably did not intend.

The Hidden Runewords Have Had a Rough Technical Debut

Grief is not the first returning Runeword to cause trouble.

We already covered how three Ancestral Stealth armors could accidentally create a Stealth carrying Enigma's power. Blizzard removed that interaction through Hotfix 2 after players briefly discovered that Tal Eth could negotiate its way into Jah Ith Ber territory.

Enigma has also generated fresh reports involving its resource conversion, while Grief has now been involved in both the Old Mountain interaction and the current Weapon Damage complaints.

Some instability is perhaps inevitable. Season 15 is combining old Rune recipes, entirely new Diablo IV item implementations, Transfiguration, Masterworking, class systems and several mechanics that were deliberately hidden from the PTR.

That creates exactly the sort of environment where one number can look perfectly correct on the tooltip while doing something considerably stranger underneath.

Blizzard Has Not Confirmed the Weapon Damage Bug Yet

This is the important qualification.

As of September 25, Blizzard has not publicly confirmed that Grief's +Weapon Damage affix itself is broken. The official hotfix notes acknowledge the Old Mountain interaction, but not this separate complaint.

What we have are repeated player reports, damage comparisons and Training Dummy testing that point toward a problem deserving investigation.

That means players should not assume every Grief is definitively broken in every configuration. Different weapon bases, classes and builds may expose the issue differently, and Blizzard may have additional information that is not visible from community testing.

But if you are currently farming the Runes specifically because Grief's massive flat Weapon Damage looks attractive, this is worth knowing before Eth Tir Lo Mal Ral disappears into the Cube.

Twenty Hours Is a Long Time to Farm a Tooltip

That is ultimately why this particular bug report has some teeth.

Season 15 has produced plenty of funny technical problems. Messerschmidt's Reaver briefly healed monsters. Stealth stole Enigma's homework. Dance of Knives discovered numbers large enough to become philosophical.

Grief is different because players deliberately farm several specific Runes to create it.

The entire point of a hidden Runeword is the moment where remembering or discovering the recipe finally pays off.

You gather Eth.

You find Tir.

You protect Lo as if it were a family heirloom.

You collect Mal and Ral.

You put everything into the Horadric Cube.

The famous name appears.

And according to some players, the most important number on the weapon then quietly goes on holiday.

Grief has returned to Diablo.

Now Blizzard may need to make the damage return with it.

Read More

Diablo 4’s Melee Builds Are Paying A Close-Range Tax Again

Diablo 4 has found another elegant way to remind melee players that standing next to monsters is apparently a lifestyle choice with additional fees.

The latest argument centres on Tears, the circular objectives that players must stand inside until they close.

You do not attack the Tear itself. You simply remain inside the marked area while Sanctuary throws monsters, elite affixes, explosions and enough visual effects to legally qualify as weather at you.

For ranged builds, that can be annoying.

For melee builds, it can feel like being asked to complete paperwork in the middle of a house fire.

The Tear Mechanic Is Simpler Than It Looks

A recent Diablo 4 forum discussion began with a player believing that melee characters had to attack Tears from close range.

Other players quickly clarified that the Tear does not need to be damaged.

You stand inside the circle until the objective closes.

That clarification makes the mechanic easier to understand, but it does not remove the underlying problem.

The player still has to occupy a relatively small area while enemies attack, elite effects cover the ground and dead monsters leave one final complaint behind in explosive form.

Standing still is rarely Diablo 4’s preferred survival strategy.

Yet the Tear objective effectively tells players to remain within a specific zone while the game activates every mechanic designed to make remaining within a specific zone unpleasant.

Melee Has To Fight Where The Danger Happens

Ranged builds can often deal damage while moving around the edge of an encounter.

They can reposition, attack from outside a crowded pack and maintain some distance from enemies carrying dangerous elite modifiers.

Melee builds do not have that luxury.

A Barbarian, close-range Rogue or melee-focused Paladin generally has to move into the centre of the action to deal meaningful damage.

That is also where monsters die.

And where monsters die is where Diablo 4 likes to place explosions, poison pools, chasing projectiles and other delayed effects designed to punish anyone foolish enough to remain near the loot.

In other words, melee characters are not merely exposed to more danger while attacking.

They are exposed to more danger after they have already won.

Death Effects Remain The Real Problem

Players have repeatedly complained about enemies exploding after death, especially during crowded seasonal encounters.

Fire Enchanted enemies are a common example.

The monster dies, the player moves toward the dropped items or remains inside the objective circle, and the ground detonates shortly afterwards.

In a clean fight, the warning can be avoided.

In a busy Helltide packed with other players, summoned creatures, spell effects and overlapping elite abilities, the warning may disappear beneath several layers of magical soup.

This is where the usual “just move” response becomes less useful.

Movement is obviously part of the solution. Nobody is suggesting that melee builds should be allowed to stand inside every explosion while eating lunch.

But the game often combines objectives that demand positioning with effects that demand immediate evacuation.

The player is told to stand in the circle.

The floor then submits a strongly worded objection.

Visual Clarity Is Part Of Difficulty

Dangerous mechanics are not automatically bad mechanics.

Clear attacks that force players to react can make combat more engaging.

The problem begins when the battlefield becomes so crowded that players cannot reliably identify what is about to kill them.

Diablo 4 regularly places several players, minions, enemies, ground effects, projectiles and death explosions into the same small area.

Some builds cover huge sections of the screen with fire, darkness, lightning or summoned creatures.

Adding a delayed explosion beneath that pile does not necessarily make the encounter more skilful.

Sometimes it simply makes the cause of death harder to see.

Melee builds suffer more because they are usually standing inside the visual clutter rather than observing it from the edge.

For more coverage of builds, seasonal systems and endgame problems, visit our Diablo 4 archive.

The Circle Creates Conflicting Instructions

Tear objectives ask players to remain inside the circle.

Many enemy mechanics ask players to leave immediately.

That contradiction can create tension, which is probably the intention.

The player must decide whether to continue closing the Tear or abandon progress temporarily to survive.

On paper, that sounds reasonable.

In practice, the circle can refill the battlefield with enemies and effects faster than slower or less mobile melee builds can safely manage.

Ranged characters can continue contributing while repositioning around the edge.

Melee characters may have to leave the objective, stop dealing damage and wait for the floor to finish expressing itself.

That is the close-range tax.

It is not one enormous penalty written into a tooltip.

It is a collection of smaller disadvantages attached to positioning, visibility and encounter design.

Not Every Melee Build Is Struggling

Some melee builds can survive the chaos extremely well.

Highly defensive Barbarians may ignore damage that deletes other characters. Strong healing, immunity windows and damage reduction can turn dangerous ground effects into background decoration.

That does not mean the mechanic is equally fair to every close-range setup.

There is a major difference between a powerful endgame build surviving an explosion and the encounter clearly communicating what happened.

A mechanic should not depend on the player becoming nearly immortal before it stops feeling irritating.

Players should be rewarded for reading the battlefield and reacting correctly.

They should not need enough defensive stacking to treat the battlefield as optional information.

The Solution Is Not Making Melee Invincible

Blizzard does not need to remove every explosion or make close-range characters immune while attacking.

A few smaller changes could improve the situation significantly.

Death effects could receive stronger visual priority so their warning zones remain visible beneath friendly abilities.

Objective circles could allow slightly more room for movement without interrupting progress.

Dangerous post-death effects could appear less frequently during events already forcing players into confined areas.

The game could also reduce the amount of overlapping visual noise generated by other players.

Difficulty should come from making the correct decision quickly.

It should not come from identifying which red-orange-purple-black effect belongs to the enemy before the floor explodes.

Melee Should Feel Dangerous, Not Pointlessly Punished

Playing a melee build should involve additional risk.

That risk is part of the fantasy.

You are standing directly in front of demons instead of sending arrows or spells from another postal district.

The reward should be satisfying impact, strong damage and the feeling that the character can survive long enough to remain in the fight.

The risk should not come primarily from invisible explosions hidden beneath five other players’ abilities.

Tears are not broken because melee characters have to attack them. They do not.

They are frustrating because they place players inside a small circle while Diablo 4 continues designing half its combat vocabulary around telling them to leave that circle immediately.

Once again, ranged builds can watch the problem from a sensible distance.

Melee players are already standing on it.

Sources

• Diablo IV Forums: Melee, close-range combat and Tear mechanics
• Diablo IV Forums: Fire Enchanted deaths and visual clarity complaints
• Diablo IV Forums: Seasonal objectives, explosions and melee concerns

```

Read More

Diablo II: Resurrected Players Say Casters Are Still The Golden Children

Diablo II: Resurrected players have found another peaceful topic to discuss.

Just kidding. They are arguing about casters, melee, bow builds, attack rating, Spirit, weapon damage, Warlock balance, and whether the entire game has been quietly kneeling before the altar of +skills for too long.

A fresh Diablo II: Resurrected forum thread argues that caster builds have become the “golden children” of D2R, while weapon-based builds like melee characters and Bowazons still need much stronger support.

And honestly, that is one of the oldest Diablo II arguments in the book.

The book is dusty. The book is angry. The book probably has a Spirit sword in it.

Casters Get The Easy Scaling

The core complaint is that caster builds often scale cleanly through +skills, faster cast rate, and strong spell mechanics, while weapon builds have to deal with a much uglier pile of requirements.

Melee and bow builds need weapon damage. Attack rating. Leech. Attack speed. Crushing Blow. Deadly Strike. Survivability. Good runewords. Good bases. Usually a small mountain of gear before they start feeling properly dangerous.

Meanwhile, a caster can often slap on enough +skills and startMeanwhile, a caster can often deleting screens like the laws of physics filed a resignation letter.

That does not mean casters are brainless.

Several replies point out that strong caster builds still need breakpoints, survivability, positioning, and proper setup.

But the perception remains: if you want to farm fast, casters usually get to the good part sooner.

Weapon Builds Feel Too Gear-Dependent

The thread keeps circling back to the same pain point: weapon-based builds need more help.

Some players specifically call for stronger low and mid-tier runewords, bigger buffs to Barbarians, Whirlwind improvements, throwing support, and better damage scaling for melee and bow characters.

That is not a small ask.

Diablo II’s itemization is legendary, but it can also be brutally uneven. If your build depends heavily on weapon damage, bad gear does not just slow you down. It makes the entire character feel like they brought a butter knife to a demonic workplace dispute.

That is why the caster-vs-weapon divide never really goes away.

Attack Rating Is Still A Sacred Headache

Attack rating also takes a beating in the thread.

One player argues that attack rating should not even exist anymore, while others push back, saying it is part of Diablo II’s old identity and should be adjusted rather than removed.

This is where Diablo II gets dangerous.

Every mechanic is both outdated and sacred. Every rough edge is either bad design or cherished texture, depending on who you ask and how many high runes they found this week.

Remove too much friction, and players say the game lost its soul.

Leave too much friction, and melee players wonder why their character needs five stats, three prayers, and a spreadsheet just to hit something.

The Warlock Has Made The Debate Louder

The newer Warlock discussion adds more fuel to the fire.

Some players in the thread argue that Warlock-level power should not become the new balance target, because boosting every class to that level could destroy the game’s difficulty curve. Others think weaker classes and weapon builds need real skill and damage overhauls instead of tiny kit adjustments.

That is the whole balance problem in one cursed sentence.

Do you nerf the strongest builds, buff the weakest ones, or accept that Diablo II has always been a glorious pile of uneven monsters?

D2R Needs Buffs That Respect The Old Monster

The best answer is probably not “make every build equally good at everything.”

Diablo II works partly because classes have different strengths. Some farm faster. Some survive better. Some clear bosses. Some need gear before they become monsters. That identity matters.

But identity should not become an excuse for half the weapon-based roster feeling like a historical reenactment of suffering.

Casters can stay strong.

But melee, Barb, bow builds, Fury Druid, and other weapon-heavy setups need reasons to feel exciting without requiring a treasure vault, a perfect runeword, and divine intervention from the stash tab.

Because Diablo II players do not need perfect balance.

They have never had that.

They just want the golden children to share the loot table a little.

For more Diablo coverage, check our latest posts on Diablo II and Diablo 4.

Read More