Saturday, 25 July 2026

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

```