Two Weeks Into Diablo 4 Season 15, Warlock Still Rules the Tower

Two weeks ago, Diablo 4 Season 15 launched with one fairly obvious question hanging over it.

Did Blizzard actually fix the Warlock?

During the PTR, the class was producing numbers that looked less like damage and more like somebody had accidentally pasted a bank account into the combat log. We covered Warlock builds reportedly hitting 80,000 trillion damage, and by early September we were already asking whether Warlock might completely dominate Season 15.

At the time, there was an important disclaimer: it was the PTR. Numbers could change. Bugs could be fixed. Blizzard still had time to adjust the class before millions of players were allowed near it.

Well, we have live data now.

The Warlock is still ridiculous.

1,000 Warlocks Have Already Cleared Tower 150

The current Tower leaderboard paints a fairly brutal picture. All 1,000 players displayed on the Warlock leaderboard have cleared Tower Tier 150. That means clearing the highest listed Tower tier is no longer enough to make you unusual among serious Warlock players. It is effectively the entry requirement for appearing on the leaderboard at all.

Blazing Scream is the main culprit. The build that looked terrifying during testing has survived into the live season as the defining Warlock setup, combining enormous damage with enough consistency to make Tower 150 look considerably less frightening than Blizzard probably intended.

This is not completely surprising. Our Season 15 PTR review already highlighted the enormous gap between competitive builds, and Warlock was the clearest example. What is surprising is how much of that gap survived the journey from test server to live game.

Paladin Is Still Looking Up at Tier 150

Then there is Paladin.

At the time of the latest leaderboard review, Paladin remained the only class without a Tower 150 clear. The top three Paladins had reached Tier 148, and every single top-20 clear was using Shield of Retribution.

That last part may actually be the more worrying statistic.

We already looked at Blizzard's attempts to improve the class when Judgement received double single-target damage for Season 15. Paladin also received broader scaling improvements, yet the live leaderboard suggests those changes have not produced the same range of competitive endgame options enjoyed by some other classes.

Season 15 even removed some possibilities before launch, including Paladin's ability to use X'Fal's Corroded Signet, which becomes particularly interesting now that Damage over Time has become one of the season's defining mechanics.

Season 15 Is Becoming the Season of Damage Over Time

Warlock is not the only class telling us something interesting about the current meta.

Sorcerer has dozens of Tower 150 clears, with Firewall and Burning effects playing a major role. Druid's strongest pushes revolve heavily around Rabies. Rogue's Penetrating Shot builds are using Poison Imbuement. Spiritborn's leading Stinger setups are also built around Poison.

The common language is Damage over Time.

Season 15 introduced new ways for DoT effects to scale, including Deadly Strike mechanics and powerful interactions with seasonal systems. The result is a leaderboard where poison, burning and other lingering damage effects keep appearing wherever players are pushing the absolute limit.

Warlock simply appears to have received the largest flamethrower.

The PTR Warning Was Correct

This is the interesting part.

Back in August, it would have been easy to dismiss Warlock's absurd PTR numbers as exactly what a test realm is supposed to uncover. Players find broken interactions, Blizzard collects the data, numbers are adjusted and everyone starts again on launch day.

Except the basic prediction survived.

Warlock entered Season 15 enormously powerful. Blazing Scream became the dominant build. Tower 150 clears multiplied until the entire visible Warlock leaderboard was filled with them, while Paladin still had not crossed the same finish line.

Blizzard did not necessarily need every class to perform identically. Diablo has never worked that way, and perfect balance would probably be considerably less entertaining than players imagine.

But there is a difference between having a strongest class and having 1,000 Warlocks sitting at Tower 150 while another class is still trying to reach it once.

We asked before launch whether Season 15 would become the season of Warlock.

Two weeks later, the Tower has supplied its answer.

Read More

Diablo 4’s Arcadia Pants Still Aren’t Fortifying Properly Six Months Later

There are few things more authentically Diablo than finding the Unique your build needs, equipping it, admiring the carefully assembled machinery of affixes and synergies — and discovering that one of the important bits apparently forgot to come to work. That is where some Diablo IV Paladin players once again find themselves with Arcadia, the Unique Pants built around Rally, healing and Fortify. A fresh PlayStation report from September 6 says Arcadia is still failing to provide the expected Fortify when healing, and the same player reports similar trouble with the Kel Rune. The unpleasant part is not merely that a Paladin defensive interaction may be broken. Players first reported Arcadia's healing behaviour back in March.

That gives this particular pair of trousers an unusually respectable bug history. The original PC report appeared on March 13, additional Paladins confirmed the behaviour, another detailed report surfaced in July, and now the complaint has returned in September. Diablo IV has changed considerably during that period. Fortify itself has been redesigned, Paladin balance has been adjusted, Blizzard has fixed numerous class interactions and Wendigo Brand has demonstrated that defensive items occasionally develop surprisingly offensive opinions about their owners. Arcadia, meanwhile, continues attracting reports that its central mechanic simply does not behave as advertised.

Arcadia Is Supposed to Turn Healing Into More Rally

Arcadia is a Paladin Unique whose entire identity revolves around a pleasing little defensive loop. Rally Fortifies the Paladin for a percentage of Maximum Life, while recovering a sufficient portion of Maximum Life is supposed to generate another Rally charge. Healing therefore feeds Rally, Rally feeds Fortify, and the Paladin gets to behave like a heavily armoured perpetual-motion machine powered by refusing to die. At its best roll, Arcadia's Rally can Fortify for 8% of Maximum Life, making the pants particularly attractive for builds that recover health frequently and want to convert that recovery into additional defensive resources.

The design is especially relevant because Blizzard has fundamentally changed what Fortify does. Under the current system, Fortify is no longer simply another Damage Reduction condition. Blizzard describes it as an additional reservoir of Life: Fortify can stack up to Maximum Life, and when the character is below full health, some of that reservoir is consumed to heal the player over time. You are considered Fortified whenever any Fortify remains. That makes reliable Fortify generation an active part of survivability rather than a decorative number tucked beneath the health globe. We recently saw a similar lesson with Diablo IV's Toughness number and why apparently enormous defenses can still mislead players against Lilith. Defensive systems are only useful when the game systems producing them actually fire.

The New September Report Says Arcadia and Kel Both Fail

The newest report comes from a PlayStation player on September 6. According to the post, Arcadia Pants and the Kel Rune are not providing Fortify from the expected healing interaction. The player specifically highlights Paladin builds using Judgement or Disciple skills, arguing that those setups already have relatively limited convenient Fortify options and therefore feel the failure particularly hard. It is currently a single fresh console report, so this should not be interpreted as evidence that every Arcadia or Kel setup is universally broken. But Arcadia itself comes with considerably more history than one forum post.

The earliest thread we found dates to March 13. A PC player reported that Arcadia was not properly registering healing and therefore was not initiating its Fortify/Rally interaction. Another player confirmed the problem several days later and said the failure made their Paladin noticeably squishier because Arcadia was central to the defensive setup. That thread remained active months later. Then on July 2, another PC player submitted a separate report saying only part of Arcadia's Unique power appeared to work: Rally itself could provide Fortify, but recovering health was not generating the Rally charge described by the item. In their words, that failure effectively broke the build.

This Is Exactly the Kind of Bug That Makes a Build Feel Wrong Before You Know Why

Arcadia is not a spectacular meteor, giant demon or enormous damage number. It is plumbing. Good buildcraft contains a surprising amount of plumbing. One mechanic creates healing, another watches the healing threshold, Arcadia grants Rally, Rally creates Fortify, Fortify becomes reserve health, and suddenly the character can stand somewhere it absolutely should not be standing while a demon the size of a farmhouse becomes increasingly annoyed. Remove one connection and nothing necessarily explodes. The build merely becomes worse in a way that can take an evening to diagnose.

That is what makes these bugs particularly frustrating. A player can reasonably assume the problem is their Paragon board, insufficient healing, a missing temper, poor Fortify Generation or simply harder content. Diablo IV now contains enough overlapping character systems that troubleshooting can resemble electrical work conducted during a thunderstorm. We have recently covered how Transfiguration adds another layer of RNG to otherwise excellent endgame items and how Horadric Gems can turn something as mundane as repairing equipment into a surprisingly expensive mistake. Arcadia belongs to the same family of problems: the tooltip tells you what the machine should do, while the actual machine may have other plans.

Arcadia Has Been Reported Broken Since March

The timeline is the strongest part of this story. March brought the initial PC complaint. July brought another player independently describing the healing-to-Rally portion of Arcadia as non-functional. September now brings a PlayStation report involving Arcadia again, this time alongside Kel. Blizzard's current patch notes contain plenty of Paladin fixes and balance changes — including adjustments to Holy Damage display, Oaths, Blessed Shield, Shield Charge, Heaven's Fury and Paladin sets — but we could not find a documented Arcadia fix addressing these healing reports in the current public notes. Blizzard has also recently standardized Arcadia's guaranteed affixes around Primary Core Stat and Maximum Life, showing that the item itself is certainly still being actively maintained as part of the modern loot pool.

That does not prove the underlying problem has remained completely unchanged for six uninterrupted months. Diablo bugs can disappear, reappear or depend on surprisingly specific combinations of skills, equipment and platforms. The March, July and September reports may also be triggering different parts of the same interaction. What we can say is simpler: players have repeatedly reported Arcadia failing around its advertised healing/Rally behaviour over a six-month period, and on September 6 somebody is still reporting it.

The Kel Report Could Point to Something Broader

The inclusion of Kel is what makes the newest complaint worth watching. If only Arcadia were involved, the obvious suspicion would remain the Unique's internal trigger. A player now claiming that Kel also fails to provide expected Fortify around healing raises the possibility that the problem could sit deeper in the interaction between healing and Fortify generation rather than in Arcadia alone. At present, however, there is not enough evidence to make that leap confidently. We have one fresh report linking the two, while Arcadia has a much longer paper trail.

That distinction matters. Diablo IV players have become understandably good at connecting dots, particularly after years of unusual item interactions, but two dots are not yet a constellation. For now, the safe conclusion is that Arcadia has multiple historical reports and Kel has been named alongside it in the latest PlayStation complaint. If more Paladins begin reproducing both failures across PC and console, then the story becomes considerably more interesting.

Paladin Really Doesn’t Need Its Defensive Gear Becoming Optional

The timing is also awkward for Paladin players because Blizzard has continued making targeted balance changes to the class. Recent patch notes increased several Paladin damage values and adjusted Oaths because Blizzard explicitly felt some Judicator builds were underperforming. That sort of numerical tuning matters, but a class can receive all the percentage buffs in Sanctuary and still feel terrible if a defensive interaction underneath the build does not trigger consistently. A 20% damage increase looks lovely in patch notes. It is slightly less impressive while your character is face-down beside Duriel because the trousers did not understand the assignment.

That becomes even more noticeable in a game where builds are increasingly defined by specific item engines rather than broad collections of good stats. The same principle is why Warlock's Season 15 power has attracted so much attention: the strongest builds are not merely piles of damage percentages; they are interconnected systems where demons, resources, skills and equipment continually feed one another. Paladin deserves the same reliability. If Arcadia is meant to turn healing into Rally and Rally into Fortify, every link in that chain needs to work.

For Now, Test Arcadia Before Building Around It

There is no documented universal workaround for the current reports. Paladin players using Arcadia should therefore verify the interaction themselves before assuming Fortify and Rally generation are functioning correctly. Find a safe area, take controlled damage, recover enough Life to cross Arcadia's stated threshold and watch Rally charges and Fortify directly. If the expected charge does not appear, swapping Arcadia out may be preferable to spending the next several hours wondering why the build suddenly feels made of attractive cardboard.

That advice is particularly important before pushing difficult endgame content or Hardcore. Diablo IV already has enough legitimate ways to kill a character. Longtooth can reportedly consume valuable Mythic Tribute runs without providing the expected reward, Treasure Breach can leave players surrounded by loot they cannot conveniently take back to town, and now a defensive Paladin Unique with reports stretching back to March is again being accused of forgetting part of its job.

Six Months Is a Long Career for a Pair of Broken Pants

Arcadia is exactly the kind of Unique Diablo IV should have more of. Its effect encourages players to connect healing, Rally and Fortify into a recognizable build identity rather than simply choosing whichever trousers contain the largest number. That makes it more interesting — and also makes any failure of the effect much more damaging. When a generic stat is slightly wrong, you lose efficiency. When the engine of a Unique stops working, you lose the reason for wearing the Unique at all.

Players were complaining about Arcadia's healing interaction in March. Another player reported the second half of its effect failing in July. A new PlayStation report on September 6 says Arcadia still does not Fortify correctly around healing and adds Kel to the complaint. We do not yet know whether both problems share the same underlying cause, nor whether every platform and build can reproduce them.

But after six months of Arcadia reports, Paladin players could reasonably ask for one fairly modest Unique effect:

When the pants say Rally, the pants should Rally.

Read More

Diablo 4 Player Tests Hallowed Ground — Two of Its Bonuses Appear Broken

Diablo IV has plenty of build interactions that are difficult to test properly. Multipliers stack on top of multipliers, Paragon nodes quietly join the calculation, equipment adds half a dozen conditional bonuses and eventually the Training Dummy is being hit by mathematics rather than a Paladin.

One player has taken a much simpler approach to a suspected Consecration problem: remove almost everything.

A fresh Diablo IV bug report posted on August 30 contains a controlled test of the Paladin's Hallowed Ground upgrade for Consecration. The player stripped the character down to a white Ancestral weapon, removed Paragon entirely, used only rank-one skills and disabled damage variance on the Training Dummy. Under those conditions, Hallowed Ground's increased Consecration area appears to work normally. Two of the upgrade's other advertised benefits do not.

Holy Bolt does exactly the same damage inside Consecration as outside it, while Divine Lance consumes exactly the same amount of Faith.

Blizzard has not yet confirmed the issue, and this is currently one player's controlled reproduction rather than a widespread confirmed Paladin bug. But unlike the usual “my damage feels lower” report, this one comes with numbers that are remarkably difficult to misunderstand.

Holy Bolt Was Supposed to Go From 310 Damage to Around 332

The tester deliberately removed as many variables as possible. The setup used rank-one Consecration with Hallowed Ground, rank-one Holy Bolt and rank-one Divine Lance. There were no additional skills, no Paragon Boards, only 79 Strength and nothing equipped except a white Ancestral Cleaver.

With damage variance disabled, Holy Bolt consistently dealt 310 damage to the Training Dummy. The player also calculated that number independently using the weapon damage, Holy Bolt multiplier, Strength bonus and the Training Dummy's damage reduction, producing the same expected result.

That established a clean baseline.

The Paladin then stepped into Consecration with Hallowed Ground active.

Expected damage: approximately 332.

Actual damage: 310.

The number did not move.

That is important because random damage rolls have been removed from the experiment. There is no question of the player simply getting an unlucky low hit inside Consecration and a high hit outside it. The same controlled Holy Bolt hit remains at 310 in both situations.

Divine Lance Still Costs 25 Faith

The second test examined resource cost rather than damage. Divine Lance normally consumed 25 Faith. With the Hallowed Ground benefit active, the player expected the cost to fall to roughly 21 Faith.

Again, nothing changed.

The displayed resource cost remained 25, and more importantly, the actual amount of Faith removed when casting Divine Lance also remained 25. That second part matters because Diablo IV tooltips do occasionally fail to update correctly even when the underlying mechanic works. Here, according to the test, both the interface and the actual resource consumption agree.

Hallowed Ground simply does not appear to be reducing the cost.

So we have two different systems producing the same uncomfortable result: one offensive bonus and one resource bonus both appear absent while standing inside Consecration.

The Area Increase Does Work

This is where the report becomes more interesting than Hallowed Ground simply being completely disabled. The player explicitly notes that the upgrade's increased Consecration size works correctly.

That means the game recognizes Hallowed Ground.

The node is selected. Consecration changes. At least one part of the upgrade activates normally. Yet the tested damage and Faith benefits appear not to be applied.

That makes a simple “the upgrade isn't active” explanation less convincing. The more likely possibilities include individual effects failing to register, an incorrect conditional check for standing inside Consecration or a disconnect between the upgrade's functional effects and what its current tooltip says they should provide.

Exactly which explanation is correct requires Blizzard's internal data. The test only tells us what happens at the Training Dummy.

A Separate Consecration Resource Upgrade Also Looks Suspicious

The tester went one step further and checked Consecration's separate Resource Generation upgrade. That test was less conclusive, but they report that taking the upgrade produced no visible change to Resource Generation on the character sheet.

By comparison, equipping gear with a Resource Generation affix does change the displayed value.

That does not prove the Consecration upgrade is broken. Some Diablo IV bonuses are conditional and therefore do not appear as permanent changes on the stat screen. But combined with the failed Hallowed Ground Faith test, it gives Paladin players another interaction worth examining under controlled conditions.

The important distinction is that the Holy Bolt and Divine Lance tests provide actual gameplay results. The Resource Generation observation currently provides a suspicious UI result. Those are not equally strong pieces of evidence.

Consecration Has Had Other Reported Problems Before

This would not be the first time players have questioned whether every part of Consecration is doing what its tooltip claims. Back in December 2025, Paladin players reported that Hallowed Ground could correctly apply its larger area and longer duration while apparently failing to apply a separate Weakened interaction. Another detailed report earlier this year examined discrepancies between Consecration's displayed duration and the actual duration created by different upgrades.

Those older reports do not prove the new damage and Faith issue shares the same cause. Diablo IV has received many patches since then, and skill behaviour changes over time. They do, however, make the current test worth taking seriously rather than dismissing it as somebody misunderstanding how Consecration works.

There is also a broader Paladin pattern this season where a build can appear correctly configured while an important effect simply fails underneath it. We recently covered how Light's Epiphany can reportedly lose its enormous 500% damage bonus after zone transitions. Players have been able to restore that effect by changing Oaths and switching back, suggesting some Paladin bonuses can become detached from the game state without the equipment itself changing.

That does not mean Light's Epiphany and Hallowed Ground are connected technically. It does mean Paladin players currently have more than one reason to distrust a perfectly normal-looking tooltip.

This Is Why Controlled Dummy Tests Matter

Diablo IV bug reports are often incredibly difficult to evaluate because normal gameplay contains too many variables. A player kills one boss quickly, kills the next slowly and assumes a skill stopped working. Maybe it did. Maybe the second boss had different modifiers. Maybe Vulnerable expired. Maybe a conditional multiplier dropped. Maybe a Talisman interaction changed. Maybe one of Diablo IV's approximately seventeen thousand invisible arithmetic goblins went for lunch.

This test removes most of that noise.

No Paragon.

No legendary equipment.

No complicated rotation.

No damage variance.

One white weapon.

One Holy Bolt.

The result outside Consecration is 310.

The result inside Hallowed Ground is still 310.

That is exactly the sort of reproduction Blizzard can potentially verify very quickly.

The Faith Test May Matter More Than the Raw Damage Loss

A modest missing damage bonus is frustrating, but depending on the build it may not completely change how a Paladin plays. The resource-cost component can be more disruptive because players build rotations around how many abilities they can cast before Faith runs dry.

If Divine Lance is expected to become cheaper while the Paladin remains inside Consecration, players can reasonably build around staying inside that holy area and converting the resource efficiency into additional casts. If the cost remains 25 instead of falling toward the expected value, the entire rotation consumes Faith faster than the skill tree implies.

The player may then compensate elsewhere with additional Resource Generation or resource-cost reduction, sacrificing an affix or passive that should not have been necessary in the first place.

That is the particularly annoying kind of ARPG bug because the character still works.

It is merely worse than the character sheet promised.

Paladin Already Has Enough Build Math to Worry About

The timing is also awkward because Blizzard is still adjusting Paladin balance heading toward Season 15. The recent PTR targeted several underperforming builds, including major improvements to Judgement. We covered how Blizzard doubled Judgement's single-target bonus under the right conditions, while players continued debating whether the class's boss damage had actually improved enough.

Those balance conversations assume the underlying skill bonuses work.

If an upgrade says standing in Consecration improves damage and resource efficiency, theorycrafters naturally put those benefits into their calculations. Build planners compare expected output. Players farm gear to support the resulting rotation. A missing modifier therefore does more than reduce one number; it makes the information used to design the build unreliable.

Diablo IV has also had a particularly busy season for effects that disappear or behave differently from their description. Talisman set bonuses have been reported simply stopping during combat, while generic Set Charms may have their own unusual progression restrictions once players reach Torment. None of these necessarily share a technical cause, but collectively they create the same player problem: it becomes increasingly difficult to know whether a disappointing build is actually weak or whether one of its bonuses quietly failed to show up for work.

Blizzard Has Not Confirmed the Hallowed Ground Bug Yet

As of August 31, the new Hallowed Ground thread has not received an official Blizzard response. It is also extremely fresh, having been posted on August 30, and there is not yet a large group of independent testers posting identical results.

That matters.

The controlled setup makes the report compelling, but one reproduction should still be described as one reproduction. There may be another mechanic affecting how Hallowed Ground is calculated. The tooltip could be misleading rather than the underlying effect being broken. There could be an interaction specific to the Training Dummy.

All of those possibilities remain open until Blizzard or more players test the same setup.

Fortunately, this is unusually easy to reproduce. Any Paladin with access to Consecration, Hallowed Ground, Holy Bolt and Divine Lance can strip away additional modifiers, turn damage variance off and repeat essentially the same experiment.

If You Use Hallowed Ground, Check the Numbers Yourself

For Paladin players currently using Hallowed Ground, the safest advice is not to immediately rebuild the character. Instead, visit the Training Dummy and test it.

Record a repeatable attack outside Consecration.

Stand inside Consecration.

Repeat the attack.

Then compare the Faith consumption of a resource spender inside and outside the area.

If more players consistently reproduce 310 becoming 310 and 25 Faith remaining 25, Blizzard will have a remarkably clean bug report to work with.

Because Sanctuary's holy ground should probably do more than make the circle slightly bigger.

At the moment, that may be the one part we can prove is working.

Sources

Diablo IV Forums: Consecration — Hallowed Ground Does Not Apply Damage Bonus or Cost Reduction

Diablo IV Forums: Earlier Hallowed Ground Weakened Report

Diablo IV Forums: Consecration Duration and Upgrade Testing

```

Read More

Diablo 4 Players Say Talisman Set Bonuses Can Simply Stop Working Mid-Combat

Diablo IV has introduced a fascinating new endgame mechanic.

Sometimes your build stops working.

Players are continuing to report problems with Talisman set bonuses suddenly disappearing during combat, with Sorcerer's Habacalva's Cauldron being one of the clearest examples.

The problem is particularly nasty because it appears most frequently in exactly the places where losing a major chunk of your build is least convenient:

• The Pit
• Kurast Undercity
• Ruptures
• Infernal Hordes
• High-density endgame fights

One Xbox player revived the issue on Blizzard's forums this week after repeatedly losing the set bonus during combat.

The available solutions?

Teleport away.

Die.

Or manually unequip and re-equip part of the Talisman set.

All excellent activities to perform while demons are hitting you.

Habacalva's Cauldron Can Lose Its Heat Mechanic

The most detailed reports involve the five-piece Habacalva's Cauldron Sorcerer set.

The set revolves around building Heat and eventually entering Overheat, providing substantial offensive and defensive bonuses once the mechanic is running properly.

The key phrase there is:

running properly.

Players describe two variations of the bug.

In one version, Heat stacks remain visible, but the actual benefits stop applying. Spells begin consuming Mana again and damage drops even though the UI still suggests the mechanic is active.

In the other, the player suddenly loses every Heat stack and becomes completely unable to generate new ones.

At that point the set can remain broken until something forces the game to refresh it.

Players Have Been Reporting This Since May

This is not a bug that appeared yesterday.

One of the earliest detailed Season 14 reports dates back to May 1, when a Fireball Sorcerer said Habacalva's Cauldron would randomly stop generating Heat after several minutes of gameplay.

Re-equipping a set piece or changing zones temporarily restored it.

Then it broke again.

Further reports continued through May, July and now late August.

A July reproduction report described the problem happening repeatedly inside Helltide Ruptures and occasionally during Pit runs.

Another Xbox player reported the bug occurring as often as several times during a single Rupture.

So while it may not affect every player or every run, this is clearly more than one character having a strange afternoon.

The Bug Gets Worse in Content That Locks Your Build

The obvious workaround is to unequip and re-equip one of the affected Charms.

There is a small problem.

Some endgame activities do not allow you to change equipment freely.

Players specifically mention Kurast Undercity as an example where the set can break after entering the activity, leaving them unable to perform the normal reset.

That turns an annoying bug into something much more serious.

Undercity is timed.

The Pit is timed.

High-level builds are balanced around multiplicative bonuses stacking together.

Removing a major Talisman bonus halfway through a run is not equivalent to losing 5% movement speed.

Your character can suddenly go from:

I am deleting everything.

to:

Why does this elite suddenly have the structural integrity of a bridge?

Habacalva's Cauldron Is Not the Only Set Having Problems

There are also separate reports involving other Talisman mechanics.

Paladin players have recently reported that the five-piece Light's Epiphany bonus can stop applying after loading screens, entering sub-zones or after certain buffs drop and return.

Those players report restoring the effect by switching away from the Disciple Oath and back again.

Except, once again, that workaround becomes impossible in content where build changes are disabled.

That does not necessarily mean both problems have the same underlying cause.

But it does make the broader Talisman system look somewhat uncomfortable when multiple builds can lose set-defining effects after game-state changes.

Blizzard Has Already Fixed Several Talisman Bugs This Season

To Blizzard's credit, Talismans have received plenty of attention in recent patches.

The August 12 update fixed multiple issues involving different Talisman sets and Charms.

Those included problems with Radament's Desecration, Black Shroud, Spellbound Steel and Art of the Bone Weaver.

Blizzard even fixed an issue where the Quintessence buff could be lost randomly.

Which sounds rather familiar.

But the current patch notes do not list a fix for Habacalva's Cauldron randomly losing its Heat functionality.

And players were still reporting the problem on August 25.

There Are Several Community Workarounds

Until Blizzard addresses it directly, players have found several methods that can sometimes wake the set back up:

• Unequip and re-equip one Talisman piece
• Teleport to another area
• Return to town
• Swap a skill on the skill bar
• Mount and dismount in content where mounting is possible
• Die and respawn

Different players report different levels of success with each method.

None are particularly good solutions.

A build-defining set bonus should ideally have one additional workaround:

Continue functioning.

It Is Hard to Trust a Build When the Bonus Can Vanish

This is ultimately what makes the bug more damaging than its raw numbers suggest.

ARPG players build around predictable interactions.

You invest hours farming the correct Talismans.

You adjust skills around the set.

You tune Resource generation, defenses and damage around effects that are supposed to be active.

Then your damage suddenly collapses halfway through a Pit.

Was the enemy stronger?

Did another buff expire?

Did you change something?

Or did Diablo IV simply forget that five Talismans are still equipped?

Players should not have to watch their build like an unreliable kitchen appliance.

The Reports Are Still Active

There is currently no indication in Blizzard's published patch notes that the Habacalva's Cauldron issue has been resolved.

The original reports have now been around for months, and the console bug thread was active again on August 25.

Hopefully that renewed attention helps get it onto the fix list.

Because Talismans are supposed to create builds.

They probably should not randomly dismantle them in the middle of combat.

Sources

Diablo IV Forums: Talisman Set Buffs Stop Working During Combat

Diablo IV Forums: Habacalva's Cauldron Loses Its Five-Piece Bonus Mid-Combat

Diablo IV Forums: Earlier Habacalva's Cauldron Bug Reports

Diablo IV Forums: Light's Epiphany Five-Piece Bonus Reports

Blizzard: Diablo IV Patch Notes

```

Read More

Diablo 4’s Paladin Can Lose a 500% Damage Bonus Just by Changing Zones

Diablo 4 Paladins have discovered a remarkably efficient way to lose damage.

Walk through a door.

Players are reporting that the five-piece bonus from the Light’s Epiphany Charm Set can stop applying its enormous 500% multiplicative damage bonus after loading screens, zone transitions and other changes in game state.

The bonus is supposed to increase Discipline Skill damage by 500% while Arbiter of Justice is active.

When it works, that is obviously enormous.

When it does not, players say their damage can collapse until they manually reset their Oath.

Blizzard has not publicly confirmed the cause, so this remains a player-reported bug. But multiple reports stretching back into July describe remarkably similar behaviour.

Light’s Epiphany Is Built Around a Huge 500% Multiplier

The five-piece Light’s Epiphany bonus is supposed to transform Arbiter of Justice into one of the Paladin’s biggest damage windows.

Casting Arbiter triggers the Paladin’s Ultimates, replaces Arbiter of Justice with Zenith temporarily and makes all Ultimates count as Discipline Skills.

Most importantly, Discipline Skills receive 500%[x] increased damage for the duration of Arbiter of Justice.

This is not a decorative little 8% passive hiding somewhere on the character sheet.

The multiplier is basically the reason you wear all five pieces.

Which makes it rather noticeable when it disappears.

Loading Screens Can Apparently Break It

A detailed bug report posted on August 12 describes several situations where the bonus reportedly stops functioning.

The player says ordinary loading screens can trigger the issue.

Distinct sub-zones can trigger it too, including boss rooms and treasure rooms, even when there is no traditional loading screen.

The player also reports that if the Arbiter buff expires and is later reapplied, the five-piece damage bonus sometimes fails to reactivate with it.

The result is a Paladin that still appears to have the correct set equipped and can still activate Arbiter of Justice, but suddenly deals dramatically less damage.

Everything looks normal.

Except the part where the demons stop dying.

Switching Oaths Temporarily Fixes It

Players have found a workaround.

Switch away from Disciple Oath.

Then switch back.

According to several reports, doing this forces the game to recalculate something connected to the Oath or set bonus, restoring the missing 500% multiplier.

An August 1 reproduction report describes the same behaviour: entering new content can leave the multiplier inactive, while toggling Disciple Oath off and back on causes the expected damage increase to return.

Unfortunately, the fix only lasts until the next transition if the reports are accurate.

Change area again and you may have to repeat the ritual.

Apparently maintaining divine power now requires turning Paladin off and on again.

Some Activities Make the Workaround Impossible

This becomes much more serious in content where players cannot freely change their build.

The August report specifically highlights The Tower and Kurast Undercity.

If the bonus breaks after entering an area where Oath switching is disabled, the player cannot use the temporary workaround.

They may simply be stuck with dramatically reduced damage until leaving the activity.

That is particularly unpleasant in timed content such as Kurast Undercity, where losing the central damage multiplier from a five-piece set can turn a perfectly normal run into an emergency surprisingly quickly.

This Problem Has Been Reported Since July

The August reports are not the first.

A console bug report from July 5 describes Light’s Epiphany failing to activate its 500% Discipline damage bonus and says switching Oaths restores it.

Another report from July 14 describes essentially the same test: equip all five Light’s Epiphany pieces, enter combat content, activate Arbiter and compare the damage with the set disabled.

The player reported that damage remained unexpectedly similar until the Oath was refreshed.

An even earlier July discussion includes players describing enormous practical differences after toggling the Oath, with one saying a boss could go from taking more than a minute to dying almost immediately.

These are community observations rather than controlled Blizzard testing, but the consistency is difficult to ignore.

A 500% Bonus Should Not Be Easy to Miss

That is what makes this particular report unusually compelling.

Small multipliers can be difficult to verify inside Diablo 4’s avalanche of Critical Strikes, Vulnerable damage, Paragon bonuses and temporary buffs.

A 500% multiplicative bonus is somewhat less subtle.

If players are repeatedly seeing similar damage before and after activating what should be one of the build’s largest multipliers, something deserves investigation.

And because manually refreshing Disciple Oath appears to restore the expected increase, players naturally suspect the set bonus is failing to initialize correctly rather than merely displaying the wrong tooltip.

That suspected cause has not been confirmed by Blizzard.

Paladin Has Enough Math Problems Already

The timing is also unfortunate for the class.

We have already covered Paladin players questioning whether Judgement remains strong enough despite substantial Season 15 PTR buffs.

Light’s Epiphany represents a different problem entirely.

This is not players asking Blizzard for a larger multiplier.

The multiplier is already enormous.

They just want the one written on the item to remain attached to their character after walking into another room.

That seems like a reasonable theological position.

For Now, Paladin Players Should Watch Their Damage

Until Blizzard confirms the issue or provides a fix, Light’s Epiphany users may want to pay attention after loading screens and area transitions.

If Arbiter of Justice suddenly feels dramatically weaker, players report that toggling away from Disciple Oath and back can restore the bonus in content where build changes are allowed.

In locked activities, there may be no equivalent workaround.

Again, Blizzard has not officially confirmed the bug or its exact cause.

But after multiple reports over more than a month, one thing seems increasingly clear:

A Paladin should probably not lose 500% damage because Sanctuary needed to load the next room.

Sources

Diablo IV Forums: Paladin’s 5-Piece Light’s Epiphany Bonus Frequently Breaking

Diablo IV Forums: Light’s Epiphany 5 Set Bonus Is Bugged

Diablo IV Forums: Charm Set of Light’s Epiphany — The 5 Piece Bonus Is Not Active

Read More

Diablo 4 Doubled Judgement’s Single-Target Damage — Paladin Players Still Aren’t Convinced

Blizzard clearly knows Diablo 4's Judgement Paladin needs help.

The Season 15 PTR gave it help.

Quite a lot of help, actually.

Judicator Oath now makes Judgement deal 100% increased damage when it hits only one enemy. Aspect of the Judicator was buffed. Blessed Shield gained another way to increase Judgement damage. Paladin's core Strength scaling went up as well.

On paper, this sounds like the moment Judgement finally graduates from interesting idea to serious endgame build.

Paladin players who tested it are considerably less convinced.

Blizzard Specifically Targeted Judgement’s Single-Target Problem

The most obvious Season 15 change is attached to Judicator Oath.

If Judgement hits only a single enemy, it now deals 100% increased damage.

That is effectively double damage under the right circumstances.

And those circumstances are clearly aimed at bosses.

Judgement-based builds could already deal with groups more comfortably because marks and detonations naturally spread through packs. Single-target encounters were where the build frequently started looking as though it had forgotten why it entered the dungeon.

Blizzard's solution is simple.

One enemy.

Twice the Judgement damage.

Unfortunately, Diablo bosses have developed the inconvenient habit of bringing friends.

Adds Can Turn the Bonus Off

That is the biggest criticism appearing in post-PTR Paladin feedback.

The Judicator Oath bonus requires Judgement to hit only one enemy.

If a boss summons adds, or ordinary monsters remain close enough to be caught by the skill, the condition is no longer satisfied.

So the build's special single-target solution can disappear precisely during a boss encounter.

One player demonstrating the build after the PTR closed argued that this forces Judgement Paladins to clear surrounding enemies before receiving the bonus again, costing both boss damage and time.

It creates a peculiar situation.

The skill is better against one target.

The boss is one target.

Until the boss invites Greg and three skeletons over.

Blessed Shield Is Becoming Almost Mandatory

Blizzard also strengthened the interaction between Blessed Shield and Judgement.

The Shield of Justice variant already detonates Judgement and empowers subsequent Blessed Shield throws.

Season 15 adds another effect: detonating Judgement now increases your Judgement damage by 50% for five seconds.

That is a considerable bonus.

It also creates another complaint.

Why should Blessed Shield be the obvious skill for scaling Judgement?

Players arguing for more Judicator variety point out that the Paladin has several Judicator skills, but this one interaction makes Blessed Shield increasingly difficult to avoid if the goal is maximizing Judgement itself.

The result risks turning a system that should support several builds into another familiar Diablo equation:

You technically have choices.

One of them is just much better.

Aspect of the Judicator Got Buffed Too

Blizzard did not stop with the Oath.

Aspect of the Judicator previously increased Judgement's damage and size by 40–60%.

Season 15 raises that to 60–80%.

Aspect of Watkin's Law was also redesigned so Judicator Skills can consume and immediately reapply Judgement while using Judicator Oath, although this can only happen once every three seconds per enemy.

There is clearly a deliberate attempt here to make Judgement flow better through a full Judicator build rather than existing as a mark players apply because another skill tells them to.

The issue is whether the numbers and interactions are finally strong enough at the highest difficulties.

PTR Players Say the Answer Is Still No

Feedback throughout the Season 15 PTR repeatedly described Paladin single-target damage as one of the class's biggest weaknesses.

One tester said that even with the new 100% Judicator Oath bonus, high-end bosses remained painfully slow and suggested Judgement would need dramatically larger increases to compete with stronger builds.

Another player dedicated much of the PTR to a Judgement Paladin and managed to push into the high Pit 120s.

That was better than the previous season.

But the player still described the build as behind stronger Paladin options and far behind the top output available elsewhere.

That does not prove Judgement is mathematically doomed.

PTR characters, gear, player skill and build decisions vary enormously.

But it does show that doubling one part of Judgement's damage has not immediately convinced the people actually trying to push it.

Cathedral Song Still Sounds Expensive

The new Cathedral Song design has attracted criticism too.

In Season 15, consuming Judgement 100 times calls down Spear of the Heavens onto a random enemy.

Judgement consumed on bosses counts as ten.

That sounds considerably more reasonable against a single boss.

In large packs, however, the reward is still one Spear targeting one random enemy after a substantial number of consumptions.

Some testers are already asking Blizzard either to reduce the requirement or dramatically increase the payoff.

One heavenly spear after one hundred administrative procedures does feel slightly bureaucratic for divine intervention.

The Paladin Buff Is Bigger Than Just Judgement

It is worth remembering that Judgement does not exist in isolation.

Season 15 also increases Paladin's core Strength damage scalar from 1.25% to 1.625% per 10 Strength.

That is a broad class-wide damage increase.

Combined with the Judicator changes, Season 15's live version could therefore perform noticeably better than the same build did before the PTR.

Blizzard still has time to adjust numbers based on the test.

The PTR is finished.

The balance pass is not necessarily finished with it.

The Idea Is Good. The Conditions May Be the Problem.

There is something fundamentally appealing about Judgement.

Mark enemies.

Condemn them.

Build around divine punishment.

It is exactly the sort of mechanic a Paladin should have.

The concern after Season 15 testing is that too much of its power remains attached to conditions that can become awkward in actual endgame fights.

Double damage against one enemy sounds excellent.

Until two enemies stand next to each other.

A 50% Judgement boost from Blessed Shield sounds excellent.

Until every Judgement build feels obligated to use Blessed Shield.

The Season 15 PTR made Judgement stronger.

That part is not really in dispute.

The question is whether Blizzard has made it strong enough to justify all the hoops players still have to jump through.

Judgement has been passed.

The Paladin community is requesting an appeal.

Sources

Blizzard Entertainment: The 3.2.0 PTR — What You Need to Know

Diablo IV Forums: Paladin Judgement — PTR Feedback

Diablo IV Forums: Paladin Feedback Season 15 PTR

Read More

Diablo 4’s Paladin Can No Longer Equip X’Fal’s Corroded Signet

Diablo 4’s Paladin is receiving more baseline damage in Season 15.

It is also losing an entire category of itemisation.

On the Patch 3.2.0 PTR, Damage over Time affixes will no longer appear on Paladin equipment, and X’Fal’s Corroded Signet can no longer be equipped by the class.

The holy warrior is getting stronger.

The fire department has confiscated one ring.

X’Fal’s Corroded Signet Is Built Around Damage Over Time

X’Fal’s Corroded Signet is a general Unique ring designed specifically for Damage over Time builds.

Its current effect causes each Damage over Time type applied by the player to erupt every second, dealing additional damage to surrounding enemies over several seconds.

The ring also carries a guaranteed Damage over Time multiplier, making its purpose extremely clear.

Poison, Burning, Bleeding and other lingering effects provide the fuel.

X’Fal provides the explosion.

Without reliable Damage over Time effects, the ring becomes an expensive piece of jewellery with excellent branding and very little employment.

Paladin Is Losing Damage Over Time Affixes

The restriction is broader than one Unique.

Blizzard is removing Damage over Time affixes from items generated for Paladins.

That means the class will no longer naturally find or craft equipment designed around increasing persistent damage.

The change suggests Blizzard does not want Damage over Time to become a supported Paladin archetype in Season 15.

Rather than balancing individual Burning or Holy damage interactions, the developer is closing the itemisation path at its entrance.

The Ring Will Be Completely Unequippable

Blizzard is not simply warning Paladins that X’Fal offers poor value.

The class will no longer be able to equip it.

That matters because X’Fal is normally a class-neutral Unique.

Most general items can be used by any class capable of meeting the equipment requirements, even when their effects are more useful to certain builds than others.

Season 15 creates a direct exception.

The ring remains general.

The Paladin is no longer on the guest list.

Existing Paladin Builds Will Need A Replacement

Any PTR character currently using X’Fal should expect the item to become unavailable once the restriction applies.

Players testing Damage over Time experiments will need to replace the ring with something supporting direct damage, Critical Strikes, Overpower, Judgement or another intended Paladin mechanic.

This is particularly important for players who invested in Masterworking or altered the ring’s affixes.

The item itself is not being deleted.

It may still be useful on another compatible class.

It simply cannot continue serving under the Light.

Why Is Blizzard Removing The Interaction?

Paladin’s identity is primarily built around direct weapon attacks, Holy abilities, Judgement effects, shields and explosive divine damage.

Damage over Time may have created awkward interactions without enough class support to become a complete build.

Allowing X’Fal and general Damage over Time affixes to remain available could encourage players to invest in an archetype that lacks the skills, Paragon support and specialised equipment needed to scale properly.

Blizzard appears to prefer a clean restriction over leaving a misleading option inside the loot pool.

That can make item drops more relevant.

It also makes the class considerably less flexible.

Removing Bad Affixes Can Improve Paladin Loot

There is a practical benefit to the change.

If Damage over Time is not intended to support viable Paladin builds, removing the affix prevents it from occupying valuable equipment slots.

A Paladin item can roll bonuses that actually support the class instead of arriving with a large multiplier for a mechanic the character barely uses.

Fewer irrelevant affixes can make useful items easier to recognise and improve.

The loot pool becomes cleaner.

It also becomes more heavily supervised.

The Restriction Raises A Bigger Itemisation Question

Diablo is built around discovering unusual combinations.

General Uniques traditionally help players bend class expectations and create builds that may not have been obvious from the skill tree.

Preventing an entire class from equipping a general Unique limits that experimentation.

Even if X’Fal is currently weak on Paladin, future skills, seasonal powers or item changes could have made the interaction interesting.

Blizzard is choosing clearer class identity over open-ended possibilities.

That may improve balance.

It may also remove a build before players have finished discovering whether it exists.

Paladin Still Receives Major Damage Buffs

The X’Fal restriction arrives during an otherwise positive PTR update for Paladin.

The class’s primary-stat damage scaling rises from 1.25% to 1.625% for every 10 Strength.

Holy Bolt gains additional multiplicative damage.

Several Judgement-related abilities and effects receive buffs, including Blessed Shield, Judicator Oath and Aspect of the Judicator.

Blizzard is clearly not trying to weaken the class overall.

It is strengthening the supported Paladin archetypes while removing one that does not fit the current design.

Direct Damage Is Becoming The Clear Direction

The combined changes point Paladins toward immediate, visible damage rather than effects that slowly tick in the background.

Judgement explosions, Holy attacks and powerful single-target strikes receive stronger support.

Damage over Time affixes disappear.

X’Fal becomes forbidden.

The message is not especially subtle.

The Paladin may burn evil with righteous fury.

It must apparently complete the burning immediately.

What Happens To Existing X’Fal Rings?

Blizzard’s notes describe an equipment restriction rather than an item conversion.

Players should not assume an existing X’Fal will transform into another ring or automatically receive replacement affixes.

The likely outcome is that the item remains intact but becomes unusable while logged into a Paladin.

PTR players should test:

• Whether an equipped X’Fal is automatically removed.
• Whether the ring can remain equipped after copying an existing character.
• How the tooltip explains the class restriction.
• Whether it can still be stored and transferred to another character.
• Whether old Paladin items keep existing Damage over Time affixes.

Clear warnings will be important, especially for characters copied from the live game.

The Tooltip Needs To Explain The Restriction

Players should not discover this change only after attempting to equip the ring.

X’Fal’s tooltip should display the incompatible class clearly.

Existing Damage over Time items should also explain whether their affixes have become inactive, removed or restricted.

Diablo 4 already uses class icons and disabled-affix notices for incompatible effects.

The Paladin restriction should follow the same system.

A forbidden ring is manageable.

A mysterious grey button is considerably less informative.

The PTR Will Decide Whether Anyone Misses It

The most important question is how many real Paladin builds currently depend on X’Fal.

If almost nobody uses the ring, the restriction may simply remove a misleading drop and improve item quality.

If players have found effective Burning or hybrid setups, Blizzard may be eliminating a legitimate archetype instead of cleaning up useless loot.

That is precisely what the PTR should reveal.

Players should test current Damage over Time setups before dismissing them and compare their performance with the stronger direct-damage alternatives.

Paladin Is Stronger, But Less Flexible

Season 15 gives the Paladin better primary-stat scaling and stronger support for several intended builds.

In exchange, Blizzard is drawing a firm line around Damage over Time itemisation.

X’Fal’s Corroded Signet is the clearest casualty.

The ring remains available in Diablo 4.

The Paladin simply cannot touch it.

The Light forgives many things.

Apparently, persistent damage is not one of them.

For more Season 15 PTR news, Paladin changes and Diablo 4 itemisation coverage, visit our Diablo 4 archive.

Sources

• Blizzard: The 3.2.0 PTR — What You Need to Know
• Blizzard: Diablo IV Patch Notes

```

Read More

Diablo 4 Buffs Three Classes While Barbarian Gets Weaker

Diablo 4’s Season 15 PTR has produced three clear winners and one extremely muscular loser.

Druid, Necromancer and Paladin are all receiving a major increase to the damage provided by their primary stats.

Barbarian is moving in the opposite direction.

While the three buffed classes gain more damage from every important stat roll, Barbarian receives less from Strength and several additional nerfs across its skills, Paragon boards and equipment.

Three classes received a pay rise.

Barbarian was asked to return the company hammer.

Druid, Necromancer And Paladin Get The Same Baseline Buff

Patch 3.2.0 increases the core-stat scalar for Druid, Necromancer and Paladin from 1.25 to 1.625.

That means each class will gain 1.625% damage for every 10 points invested in its primary stat.

• Druid gains damage from Willpower.
• Necromancer gains damage from Intelligence.
• Paladin gains damage from Strength.

A character with 2,000 points in the relevant stat would move from a 250% damage bonus to 325%.

That represents 75 additional percentage points before skills, equipment, Glyphs and other multipliers are considered.

The exact effect on final damage will vary by build.

The direction is very clear.

Barbarian Strength Scaling Falls Instead

Barbarian currently receives 1.1% damage for every 10 Strength.

On the Season 15 PTR, that falls to 0.8%.

A Barbarian with 2,000 Strength would receive 160% damage instead of 220% from the class’s primary stat.

That places the class 165 percentage points behind a Druid, Necromancer or Paladin with the same amount of their relevant core stat.

The comparison is not perfectly direct because every class has different mechanics, item access and skill multipliers.

It still demonstrates how aggressively Blizzard is adjusting the foundations beneath each class.

Blizzard Is Using Core Stats As A Balance Lever

Blizzard gives the same explanation for all four changes.

The developer is evaluating how the classes differ as complete packages and using the core-stat scalar to compensate for those differences.

This approach allows Blizzard to increase or reduce a class’s general damage without editing every individual ability.

It is efficient.

It is also extremely broad.

A stronger primary-stat multiplier helps almost every offensive build within a class.

A weaker multiplier reduces almost everything, including builds that may not have been causing balance problems.

Druid Receives More Than A Stat Increase

Druid’s new core-stat scaling arrives beside several substantial item buffs.

Greatstaff of the Crone increases its damage bonus from 60–80% to 120–150%.

Fleshrender’s returning Tornado damage rises from 40–50% to 100–135%.

Airidah’s Inexorable Will jumps from 7–10% increased damage to 30–45%.

Human Form also gains 10% multiplicative damage for applicable skills, while Shifter’s Aspect adds Damage Reduction when changing form.

Not every change is positive. Might of the Ursine receives a major reduction and becomes limited to Werebear skills.

Even so, Druid enters the PTR with several new reasons to revisit older equipment.

The wardrobe has discovered buffs behind items nobody had touched recently.

Necromancer Gets A Long List Of Direct Damage Buffs

Necromancer receives the same increase to primary-stat scaling alongside improvements to several underused skills.

Reaping Lotus increases its secondary attack damage from 40% to 60%.

Plunging Darkness raises Bone Prison’s Desecrated Ground damage from 300% to 450%.

Blood Wave’s Path of Darkness version rises from 600% to 800%.

Soulrift increases from 300% to 350%, while Blight gains stronger boss support and a lower Essence cost through its variants.

Several Aspects and Uniques are also improved.

The Unmaker climbs from 200–250% damage to 300–350%, and Ebonpiercer increases from 40–50% to 60–70%.

Necromancer is not receiving one adjustment.

It is receiving a handwritten apology to several neglected skills.

Paladin Gains Damage But Loses An Entire Item Interaction

Paladin also moves from 1.25% to 1.625% damage per 10 Strength.

Several Judgement-focused abilities receive additional buffs.

Holy Bolt gains a direct 20% multiplicative damage upgrade.

Blessed Shield can increase Judgement damage by 50%, and Judicator Oath doubles Judgement damage when it hits only one enemy.

Aspect of the Judicator also increases its damage and size bonus from 40–60% to 60–80%.

However, Blizzard is removing Damage over Time affixes from Paladin equipment.

X’Fal’s Corroded Signet will no longer be equippable by the class.

Paladin receives more baseline damage while losing access to a specific style of itemisation.

The class has been buffed.

The fire department has still confiscated one ring.

The Barbarian Nerfs Go Beyond Strength

Barbarian’s weaker stat scaling arrives beside reductions to several other systems.

Madawc’s damage is halved in two different Ancient abilities.

Two-Handed Sword Expertise loses half of its multiplicative Bleeding bonus.

Disembowel, Crusher, Hemorrhage, Blood Rage and Flawless Technique all receive lower Paragon damage values.

Writhing Aspect and Battle-Mad Aspect become weaker.

Ring of the Ravenous loses damage and duration, while Ramaladni’s Magnum Opus begins draining 10% of Maximum Fury per second instead of a flat 10 Fury.

There are several Barbarian buffs in the notes, including improvements to Ring of Red Furor, Nomad’s Longing Heart and Raid Leader’s Aspect.

They are standing in a considerably longer queue of reductions.

The Real Gap May Be Larger Than The Stat Numbers Suggest

Comparing 1.625 to 0.8 does not tell the entire story.

Druid, Necromancer and Paladin are gaining stronger baseline scaling while also receiving improvements to multiple skills and items.

Barbarian is losing baseline scaling while several important multipliers are reduced at the same time.

Those changes can compound.

A smaller core-stat bonus reduces the foundation.

Lower Expertise, Paragon and Aspect multipliers then act on that weaker foundation.

The final difference may therefore be significantly larger than a simple comparison between two core-stat values.

This Does Not Automatically Make Barbarian The Worst Class

Barbarian has access to four weapon slots through the Arsenal system.

That allows the class to carry more offensive affixes, Tempering bonuses and weapon-based powers than most alternatives.

Blizzard may believe the class’s equipment advantage has become too strong when combined with existing damage scaling.

Druid, Necromancer and Paladin may also require higher primary-stat returns because their complete class packages produce less damage elsewhere.

The PTR must determine whether these changes create balance or simply exchange one class gap for another.

Players Should Test Equal Investment

The most useful PTR comparisons will use characters with similar gear quality, Paragon investment and primary-stat totals.

Players should compare:

• Boss damage before and after the core-stat changes.
• Clear speed in equivalent Torment content.
• How heavily each build depends on primary-stat rolls.
• Whether weaker Barbarian builds are punished alongside the strongest ones.
• Whether the buffed classes suddenly produce unintended outliers.

Testing only the most powerful build for each class will not reveal how these changes affect ordinary progression.

The lower and middle sections of the build ladder matter too.

These Numbers Are Still PTR Values

The Patch 3.2.0 changes are not guaranteed to reach Season 15 unchanged.

Blizzard is using the PTR to collect data and feedback before the season launches.

If Barbarian falls too far behind, its stat scalar or secondary nerfs could be adjusted.

If Druid, Necromancer or Paladin produce excessive damage, their new scaling may also be reduced.

This is exactly the kind of broad class change that needs real testing rather than spreadsheet confidence.

Season 15 Is Redrawing The Class Baseline

Blizzard is not merely adjusting a handful of overperforming abilities.

It is changing how much value entire classes receive from their most important attribute.

Druid, Necromancer and Paladin will gain substantially more damage from normal character progression.

Barbarian will gain substantially less.

The intention may be to bring the classes closer together.

The immediate impression is considerably simpler.

Three classes are climbing the ladder.

The Barbarian is being asked to hold it.

For more Season 15 balance changes, PTR analysis and class news, visit our Diablo 4 archive.

Sources

• Blizzard: The 3.2.0 PTR — What You Need to Know

```

Read More

Diablo 4’s Disciple Oath Bug Can Delete Most Of A Paladin’s Damage

Diablo 4’s Paladin can lose most of its damage by performing one of the game’s most dangerous activities.

Walking through a loading screen.

Players using Disciple Oath with Wing Strike and the Light’s Epiphany set say the build can stop receiving crucial bonuses whenever the character enters a new instance.

The result is not a small tooltip discrepancy.

Reported damage can collapse by roughly 80% to 95% until the player switches away from Disciple Oath and selects it again.

That workaround may restore the build in ordinary areas.

Inside activities where Oaths cannot be changed, the Paladin is left fighting with the damage output of someone who forgot to equip several systems at once.

Wing Strike Can Lose The Disciple Tag

The reported problem appears to involve Disciple Oath failing to reapply correctly after a zone change or loading screen.

Disciple Oath is supposed to grant the Disciple tag to Mobility skills.

That tag allows Wing Strike to benefit from several effects designed specifically around Disciple skills.

Players say the tag can effectively disappear after entering a new instance.

Wing Strike remains available and still deals damage.

It simply stops receiving the bonuses that make the build function.

The Paladin has not changed equipment.

The player has not altered the skill tree.

The game has quietly forgotten why the ability was powerful.

Players Report Massive Damage Losses

Several reports describe damage dropping by an enormous amount.

One player said Wing Strike fell from hits in the 50–120 billion range to roughly 5–10 billion after activating Arbiter of Justice or changing zones.

Another reported seeing approximately 3–6 billion damage while the bug was active, compared with more than 300 billion after resetting Disciple Oath.

A separate detailed report estimated the loss at around 17 to 20 times less damage.

The exact number will depend on the build, equipment and activity.

The pattern is consistent.

The character enters an instance.

Wing Strike damage falls through the floor.

The player changes Oaths and selects Disciple again.

The damage immediately returns.

Sanctuary’s holy warrior is apparently powered by turning the class feature off and on again.

Light’s Epiphany Makes The Failure Worse

The bug is especially damaging for builds using the Light’s Epiphany set.

That set provides bonuses tied to Disciple skills and forms a major part of the Arbiter Wing Strike endgame setup.

If Wing Strike stops being treated as a Disciple skill, the Paladin can lose access to several interacting bonuses at once.

Players specifically mention scaling from the Oath, set bonuses, Glyphs, Tempers and other effects that depend on the correct skill classification.

This explains why the damage reduction can be so extreme.

The bug is not necessarily disabling one isolated multiplier.

It may be breaking the connection between Wing Strike and an entire collection of systems built around the Disciple tag.

One missing label can turn a completed endgame build into an expensive demonstration character.

The Workaround Must Be Repeated After Every Instance Change

Players have discovered a simple temporary fix.

Switch from Disciple Oath to another Oath.

Then switch back to Disciple.

This appears to force the game to reapply the missing bonuses.

The problem is that the workaround does not remain active.

Players say it must be repeated after entering a Pit, Infernal Horde, dungeon, Kurast Undercity, Citadel or another new instance.

That transforms routine gameplay into a pre-dungeon checklist.

Check equipment.

Check consumables.

Reset the class mechanic because the loading screen may have deleted it again.

The workaround is easy enough to perform in the open world.

It becomes far more serious when the game prevents the player from changing Oaths.

The Tower Can Lock Players Into The Broken State

The Tower is one of the worst places for the bug to appear.

Players entering competitive or locked content may be unable to change their Oath after the run has started.

If Disciple fails to initialise correctly, the Paladin cannot use the normal workaround.

The player must either continue with a fraction of the intended damage or abandon the attempt.

In content governed by a timer, an 80% damage loss is not a manageable handicap.

It is the run ending before the first serious enemy pack.

The build may be fully capable of clearing the tier when functioning normally.

The Tower receives the version assembled by the loading screen.

Kurast Undercity Has The Same Basic Problem

Kurast Undercity also punishes unexplained damage loss severely.

The activity revolves around completing objectives and killing enemies before time expires.

A Paladin entering with broken Disciple scaling may not immediately realise what happened.

The skills still animate correctly.

Enemies still take damage.

Nothing necessarily appears visually broken.

The character simply performs dramatically worse.

By the time the player recognises the reduced numbers, valuable seconds may already be gone.

Because the activity can restrict build changes, the Oath reset may not be available until the run is over.

The player brought a finished build.

The dungeon issued a rental version at the door.

The Pit Can Waste Upgrade Attempts

The Pit creates another painful scenario.

Players use it to push difficult tiers and improve Glyphs.

Higher levels require consistent damage, especially against bosses with large health pools.

One player specifically complained that the bug made their character effectively unplayable in endgame Pit content.

Their Wing Strike damage reportedly increased from a few billion to more than 300 billion after resetting the Oath.

That is not a difference solved through cleaner positioning or better resource management.

It is the difference between progressing and watching the timer expire while a boss politely absorbs everything.

The Bug Can Be Difficult To Notice Immediately

Not every player watches damage numbers closely during every encounter.

A build may still clear ordinary enemies while the bug is active, particularly in lower-difficulty content.

The problem can therefore remain hidden until the character reaches a boss or a dense elite pack.

Players may initially blame enemy scaling, a changed item, a missing buff or an undocumented balance adjustment.

Some may spend time rebuilding Paragon boards or comparing equipment before discovering that the solution is simply reselecting the same Oath.

This is one reason state-reset bugs are so frustrating.

The game does not tell the player that anything failed.

It merely presents a character who has become mysteriously terrible at work.

Loading Screens Should Not Rebuild The Character Incorrectly

Diablo 4 recalculates a large number of effects whenever a character changes zones.

Skills, equipment, set bonuses, seasonal systems, class mechanics and temporary buffs must all remain synchronised.

The Disciple issue suggests that at least one part of that process is not restoring the character state correctly.

The Oath appears selected in the interface.

The effects tied to it may not be fully active.

Manually selecting the Oath again forces the missing calculation to occur.

This behaviour strongly suggests a state or initialisation problem rather than an intentional balance interaction.

The button says Disciple.

The damage calculation has apparently selected unpaid leave.

Cross-Platform Reports Make It Harder To Dismiss

The issue has been reported by players on PC and consoles.

Forum discussions include confirmations from PlayStation users, while related bug threads appear in both PC and console sections.

That matters because it makes a platform-specific installation or input problem less likely.

The shared behaviour points toward the underlying game logic.

Players describe the same zone-change trigger, the same damage loss and the same Oath-switching workaround.

When different platforms reproduce the same ritual, the ritual probably should not be required.

Blizzard Recently Buffed Disciple Oath And Wing Strike

The timing is particularly awkward because Blizzard recently increased the power of both Disciple Oath and Wing Strike.

Disciple Oath’s damage bonus was raised from 50% to 80%.

Wing Strike’s base damage was increased from 160% to 200%.

Those changes were intended to improve the Paladin’s performance.

The bug can erase far more damage than the balance patch added.

Players therefore have a stronger skill on paper and a build that may collapse after entering the activity where they intended to use it.

The patch gave Wing Strike a larger sword.

The loading screen occasionally confiscates the arm holding it.

This Is More Than A Tooltip Bug

Diablo 4 has had plenty of tooltip inconsistencies.

Sometimes an icon displays the wrong value while the underlying effect continues working.

The Disciple Oath reports describe the opposite.

The interface continues showing the chosen Oath while the damage output indicates that crucial benefits are missing.

Players can observe the effect directly by attacking before and after reselecting Disciple.

The damage changes immediately without any equipment modification.

That makes the issue measurable in ordinary gameplay.

No spreadsheet archaeology is required.

The monster’s health bar provides the bug report.

Paladin Builds Rely On Tags Working Consistently

Skill tags are essential to Diablo 4’s build system.

Aspects, Glyphs, Tempers, Paragon nodes and set bonuses frequently apply only to skills carrying a particular tag.

Players make equipment decisions based on those classifications.

If a class mechanic dynamically grants a tag, that tag must remain reliable across every activity.

A build cannot function when the same skill counts as Disciple in town but becomes an ordinary Mobility skill inside a dungeon.

Tags are not flavour text.

They are wiring.

Removing one can disconnect half the machine.

The Workaround Is Not An Acceptable Long-Term Fix

Reselecting Disciple Oath is useful information for affected players.

It is not a proper solution.

The workaround adds friction before every activity and fails entirely where build changes are locked.

It also places responsibility on the player to remember that the game may have forgotten its own mechanics.

A player who misses the reset can waste dungeon keys, Tower attempts, Tributes or other activity resources.

The build should enter content in the same functional state it had before the loading screen.

That is not an advanced quality-of-life request.

It is the basic job description of a character sheet.

A Temporary Automatic Refresh Could Help

If Blizzard cannot immediately identify the deeper cause, an automatic Oath refresh after loading could provide a temporary safeguard.

The game could reapply the selected Oath whenever the character enters an instance.

It could also validate skill tags before combat begins.

This would reproduce the effect of the player’s manual workaround without requiring access to the class menu.

A permanent repair should ensure that Disciple and Light’s Epiphany remain active correctly throughout zone transitions.

Until then, an automatic state refresh would be better than asking Paladins to perform ceremonial menu maintenance before every dungeon.

Blizzard Should Add A Visible Disciple Indicator

A clearer buff indicator could also help players identify the problem.

If Wing Strike is currently benefiting from the Disciple tag, the interface could display a specific active effect.

When the tag fails, the missing indicator would warn the player before they begin a timed activity.

This would not fix the bug.

It would reduce the amount of content wasted before the player notices it.

Diablo 4 contains many hidden calculations.

Build-defining class states should not be among them.

The Bug Damages Confidence In Build Testing

Players test builds by comparing damage, clear times and equipment changes.

An inconsistent Oath state makes those comparisons unreliable.

A new item may appear weaker because the previous test happened with Disciple active and the next test occurred after a broken zone transition.

A Paragon adjustment may seem responsible for a damage collapse it did not cause.

Players can draw incorrect conclusions because the game changes the build’s functional state without explaining it.

Reliable testing requires repeatable conditions.

At the moment, Wing Strike Paladins must first establish whether their class mechanic survived the journey to the training area.

Competitive Content Makes The Bug Urgent

Not every bug needs emergency treatment.

A cosmetic clipping issue can wait.

A broken description may be annoying without preventing progression.

A bug that removes most of a build’s damage inside timed and competitive content deserves higher priority.

It directly affects leaderboard attempts, dungeon completion and character viability.

The player cannot compensate through skill when the build’s core scaling disappears.

They cannot always use the workaround.

And they may spend activity resources before recognising the failure.

This is exactly the kind of issue that can make a strong build feel unplayable despite excellent balance numbers on paper.

Blizzard Has Not Listed A Specific Fix Yet

At the time of writing, Blizzard’s current patch notes do not include a specific correction for Disciple Oath failing after instance changes.

The developer has previously fixed Wing Strike interactions and other Paladin state problems.

That provides some reason to expect the issue can be addressed.

For now, affected players should check their damage after entering a new area and reselect Disciple Oath whenever the game allows it.

Players entering locked content may need to reset the Oath before launching the activity and hope the state survives the transition.

That is not reassuring advice.

It is the only ritual currently available.

Paladins Should Not Lose Their Oath At The Loading Screen

Disciple Oath is not an optional visual effect.

It defines how Wing Strike interacts with Light’s Epiphany, Glyphs, Tempers and the wider Arbiter build.

When the Oath fails to reapply, the character can lose most of its intended damage.

The manual reset proves the power is still available.

The game simply fails to activate it consistently.

Blizzard needs to fix the underlying state problem and ensure that dynamically granted skill tags survive every zone transition.

Paladins already have enough problems fighting the armies of Hell.

They should not also need to renew their sacred Oath after every loading screen.

For more coverage of Paladin builds, class bugs and Season 14, visit our Diablo 4 archive.

Sources

• Diablo IV Forums: Initial Disciple Oath zone-change bug report
• Diablo IV Forums: Detailed reproduction steps and reported damage loss
• Diablo IV Forums: Wing Strike and Light’s Epiphany player reports
• Blizzard: Current Diablo IV patch notes and Paladin balance changes

```

Read More

Diablo 4’s Paladin Holy Damage Fix Is Small, But Class Identity Needs It

Diablo 4 Patch 3.1.1 has plenty of fixes that look more important at first glance.

Mythic drops. Lair Boss sources. Pandemonium Fragments. War Plans bugs. The sort of patch notes that make endgame players sit up because loot is involved and the loot table has once again been caught holding a wrench suspiciously close to the plumbing.

But one small Paladin fix deserves a closer look:

Blizzard fixed an issue where Damage with Holy was not displayed in the Stats and Materials tab for Paladin.

That sounds tiny.

Until you remember that a holy warrior should not need divine intervention to find his own damage stat.

Holy Damage Should Be Visible

Paladin is built around identity as much as mechanics.

Holy power. Heavy armor. Shields. Judgment. Righteous violence delivered with the confidence of someone who has never once apologized to a demon.

So when the class has a stat called Damage with Holy, that stat needs to be visible.

According to Blizzard’s official Diablo IV Patch 3.1.1 notes, Patch 3.1.1 fixed a Paladin issue where Damage with Holy was not shown in the Stats and Materials tab.

That is not a balance revolution.

It is not a new build. It is not a massive buff. It will not make your next dungeon explode into golden loot confetti.

But it does make the class easier to understand.

And that matters.

Class Fantasy Needs Clean Numbers

Players do not just pick a class because of raw math.

They pick it because the fantasy clicks.

Necromancer players want corpse nonsense. Rogue players want speed, blades, and questionable survival instincts. Sorcerers want the screen to become a weather crime. Paladin players want holy damage to feel like holy damage.

But fantasy still needs numbers.

If a class is built around a damage type, players need to see how their gear, skills, passives, and upgrades support that damage type. Hiding the stat makes the build feel less readable.

It turns a clear class fantasy into menu archaeology.

And Diablo 4 already has enough menu archaeology to qualify as a cursed dig site.

This Is A UI Fix, But Also A Trust Fix

Patch 3.1.1 has been full of trust repairs.

Some are obvious. Bosses needed to drop loot correctly. Lair Boss sources needed to actually produce Mythic versions. Fragments needed better flow. Rewards needed to show up when players earned them.

The Paladin Holy Damage fix sits in a quieter corner, but it points at the same basic issue:

The game needs to tell players the truth.

If a stat exists, show it.

If a build scales with something, make that scaling visible.

If players are investing in Holy damage, they should not have to guess whether the character sheet remembered to bring the candles.

That is not asking for hand-holding.

That is asking the interface to stop hiding the class fantasy in a drawer.

Buildcraft Gets Worse When Information Is Missing

ARPG players love experimenting.

They test gear. They compare affixes. They swap skills. They check numbers. They convince themselves they are doing science while surrounded by demons, skulls, and twenty-seven items they swear they will sort later.

That loop breaks down when basic stat information is missing.

For Paladin players, Damage with Holy is not just flavor text. It is a signpost. It helps players understand whether their choices are actually pushing the build in the direction they want.

Without that visibility, the player is left reading skill text, inspecting gear, and mentally stitching together a build with incomplete information.

That is not depth.

That is fog.

Small Fixes Help New Classes Feel Finished

New or freshly reworked class systems need extra polish because players are still learning their language.

They need to know which stats matter. Which damage types scale what. Which affixes are bait. Which synergies are real. Which tooltip is secretly trying to ruin their evening.

That makes stat display problems more annoying than they look.

A missing stat on an established class is irritating.

A missing identity stat on a class where players are still building confidence is worse.

Paladin needs clean presentation because the whole appeal depends on players understanding how their holy kit comes together.

If the game wants players to build around sacred damage, the sacred damage number should probably show up to work.

Diablo 4 Does Not Need More Hidden Math

Diablo 4 has complicated enough systems already.

Players are tracking aspects, tempering, affixes, resistances, armor, cooldowns, resource costs, uniques, Mythics, seasonal currencies, reputation rewards, and whatever fresh endgame nonsense the season has decided to throw into the blender.

That is fine when the information is readable.

It becomes a problem when important class data disappears from the place players expect to find it.

The Stats and Materials tab exists for exactly this reason. It should be the place where players can check their character’s actual mechanical shape without performing a ritual.

Holy Damage missing from that tab was a small bug.

But it touched one of the most important things an ARPG can offer:

Clarity.

Not Every Patch Note Needs To Be Huge

This fix will not dominate the Patch 3.1.1 conversation.

It should not. The patch has bigger problems to solve, and many of them involve rewards, boss sources, and seasonal systems that needed emergency maintenance.

But the Paladin Holy Damage display fix is still worth noting because it makes the class feel more complete.

Not stronger.

Not easier.

Just clearer.

And sometimes that is exactly what a class needs.

Paladin should feel like a holy warrior, not a holy spreadsheet with missing columns.

Patch 3.1.1 puts the Damage with Holy stat where players can actually see it.

Small fix.

Correct fix.

Even Heaven needs a readable character sheet.

Sources

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

Read More