Has anyone else seen damage stop working on some DOT and proc builds in Nightmare mode?

November 5, 2026 5 answers
Asked by bitlance

Some players have been flagging a bug in Nightmare mode where certain damage over time skills and proc sets look like they trigger, but the damage never actually lands. It seems to happen more with some builds than others, and restarting or leaving the mode may or may not clear it.

Has anyone else run into this, and is there a reliable fix or workaround?

Answers

m0dcrash

This sounds like one of those state desync issues where the game says the effect went off, but the server never fully registers the damage ticks. If it is happening across several different proc sets and regular DOTs, that points less to one bad set and more to Nightmare mode itself or whatever event logic is running there.

The practical workaround is usually to watch a test target closely and swap out anything that depends on delayed ticks or conditional procs. If the issue shows up mid-run, leaving the instance and re-entering might help, but if it keeps coming back after a restart, that usually means the build type is just more likely to hit the bug.

quietmint:

Yeah, the weird part is that it can look totally normal in combat logs until you notice the target is barely moving. That makes it easy to miss unless you are checking damage on a dummy or single mob.

Reply to this answer
kartpulse

I would not rely on proc-heavy setups in that mode right now. If the bug is tied to animation firing without actual damage, then anything that stacks multiple passive hits, DOTs, or delayed explosions is going to be the first thing to feel broken.

For the moment, a simpler direct damage setup is probably safer. Fewer moving parts means it is easier to tell whether the mode itself is bugged or whether one specific skill is failing. If your build absolutely needs DOTs, keep a backup setup ready so you can swap when the damage starts dropping off for no obvious reason.

bitlance:

That matches what I have been seeing. The build still looks active, but the real damage falls off hard and it is not always obvious in a hectic fight.

sprocket_owl:

Exactly, and that is why these bugs are so annoying. They do not always show up as a clean failure, they just quietly gut the build.

Reply to this answer
RAIDKITE

If the issue is only in Nightmare mode, I would treat it like a mode-specific interaction bug rather than a general combat bug. Sometimes certain zones or instances break persistent effects, especially when lots of summons, ground effects, and proc checks are happening at once.

The best temporary fix is usually boring stuff like reloading the area, relogging, or avoiding effect-heavy gear until it gets patched. Also worth testing whether the problem happens on a dummy or only in that mode, because that helps narrow down whether the issue is the set, the skill, or the instance rules.

Reply to this answer
plinthplay

I have seen a few build types get hit harder than others in these kinds of situations, and the common thread is usually effects that depend on timing. DOTs, multi-hit procs, and anything that needs the game to keep tracking a target over time are the first to go weird when an instance starts acting up.

If you are warning other players, I think the most useful advice is to assume damage may be lower than it looks. People should test on trash packs, not just bosses, and keep an eye on whether the proc animation is actually matched by damage numbers. If not, change loadout before the run gets messy.

hexdabble:

That is the part people miss. The visuals can make the build seem fine for a while, then suddenly the parse or fight length tells a different story.

Reply to this answer
uplink!zed

This is the kind of bug that makes proc builds feel flaky even when the gear is fine. If several unrelated sets are all showing the same symptom, the safest assumption is that the mode is breaking effect resolution, not that every item is suddenly bad.

I would keep the warning short and practical. Use it for awareness, swap to something more direct if you are doing serious runs, and do not waste too much time trying to force a broken setup to behave. If a restart sometimes helps and sometimes does nothing, that is a pretty strong sign there is no clean player-side fix yet.

bitlance:

Pretty much. I just wanted people to know it is not always a build issue when the damage seems off.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions