Blackflame ignite and Contagion
|
Not sure if this is a bug or intended, but Contagion does not propagate ignites when you have the Blackflame Covenant keystone even though they should be considered Chaos DOTs when you have it.
Last bumped on Sep 30, 2025, 9:07:51 PM
|
|
|
+1 im trying to say this in as many places as possible. i feel like its an interesting build idea that shouldnt be locked out. hopefully they take notice of this and fix asap, im still playing edc in hopes this comes out at some point
|
|
|
My understanding is that buffs/debuffs have fixed internal tags. And they behave in accordance with the tags. Because the game definitely can't track what type of damage every DoT deals for performance reasons.
Even though ignite deals Last edited by MonaHuna#6449 on Sep 21, 2025, 5:19:52 AM
|
|
" Probably the case since "chaos" ignites are not recognized as chaos damage over time effect by Dark Effigy either |
|
|
That's definitely what's happening. It's not only lame because it messes up the build concept, its also just inconsistent with in-game language. I understand its probably not technically a "bug" per se, but using the in-game definitions necessarily implies it should work. They either need to make the descriptions more precise, or allow this cool interaction to work
|
|
|
Is this meaning that any other Debuff/Trigger/etc ... and passive points does not work as Chaos but still remain as Fire?
At what lvl on damage calculation is "applied" the Fire to Chaos conversion ? Last edited by waltzie#1516 on Sep 10, 2025, 5:06:10 AM
|
|
|
Bump
Can we get a GGG response on what the intent is? Even a confirmation on the speculation here? It seems really counterintuitive that Contagion spreading 'it and all other Chaos Damage over time Debuffs' doesn't work with a keystone that says 'Ignites inflicted with Fire Spells deal Chaos Damage instead of Fire Damage'. It walks, quacks, and acts like a duck, but it's actually a rhoa. |
|
|
Bump.
I got so excited when I saw 'ignite' in proximity with 'Blackflame Covenant' in the 0.3.1 notes, only to see it was addressing a visual bug lol |
|
