questions about burning effect

Is it intended that burn damage is affected twice by resistances?

For example if a monster has 75% fire resistance then burn damage will be reduced by 75% because the initial hit is reduced by 75% and then the actual burn damage itself will be reduced by 75% again.

This results in burn damage being really trivial on monsters with fire resistance and really devastating on monsters that have negative resists (from a curse or from keystone passives.)

I tried making a fireball witch and it was really noticeable how much harder it was to kill fire resistant enemies and rares, especially if they were curse immune.

I think it would be better if the burning effect itself wasn't affected by resistances since its already being affected because it's based on the initial hit.

Also another question: If I have 20% chance to burn from a 20% quality fireball gem, an additional 45% chance to burn from a linked ignite support gem, an additional 10% chance to burn from a curse, and 25% base crit chance, does that mean that every fireball I cast will cause the burning effect or do they not stack additively?

Burning being affected twice by resistance would be news to me. It's possible, I guess, but I haven't noticed anything like that. Burning damage is supposed to be 4/3rds of the initial fire damage (after resistances, of course) that caused the burn, applied over 4 seconds. If you prefer, it's 1/3rd of the damage caused by the initial fire effect, applied every second, for 4 seconds.

If it is a critical hit with a fire component, that is an automatic burn effect, and that burn damage will be 4/3rds of whatever that fire damage critically hits for, which is going to be at least 150% of your normal fire damage.

If it is not a critical, your other chance to ignite effects should be additive, I think. So you'd have a 75% chance to burn on any hit that wasn't a critical, in your example. But it would still only do 4/3rds of the initial fire damage that caused that burn.

Here is what I mean: Assume you hit for 100 fire damage and it causes a burn for another 100 damage for 200 total damage.

If the monster you are hitting has 75% fire resist the initial hit will be reduced to 25 and the burn damage will be reduced to 25 (because its based on the initial hit, which was reduced) for a total of 50 damage, which is only 25% of 200 which would be correct since the fire resistance reduced it by 75%. BUT THEN the burn damage itself is reduced by 75% because of the fire resistance which only leaves 6.25 burn damage for a total of 31.25 damage overall. That's what I mean when I say it's affected twice.

It's not technically twice, resistance should apply to all source of damage.

About the ignite chance, it is additive. You can see chance to ignite from the character screen (pre-curse). Crit chance happen independently of ignite chance.

Interesting. I never would have guessed that it works that way. Does that mean that decreasing fire resistance below 0% actually grants an additional bonus to burning damage? So, it increases the damage of the main hit, and then further increases the burning damage?

WTF? this is absolutely ridiculous. how are you guys OK with this?

This mechanic never even cross my mind considering how absolutely absurd it is, and I could only ever see it existing as a bug.

At least that explains why the value of 4/3 over 4 seconds seemed to be overstating the value, and especially why the damage is so epically terrible in PvP.

You should reduce burning damage to something like 3/4 over 3 seconds (or less), and remove this silly reduction of burning damage.

Please fix Ignite :( Remove this silly double resist check and make it stackable.

"

Illedran wrote:

Please fix Ignite :( Remove this silly double resist check and make it stackable.

That doesn't make any sense.

1) If you can resist fire damage, you can resist damage caused by being on fire. Elemental resistance should apply to all sources of elemental damage.

2) You can't light the same thing on fire twice at the same time. It shouldn't be stackable.