I was wondering if anyone was having an issue with the shown damage numbers from fire auras damage.
Currently if I’m in an empowered echo I see numbers around 10-20k. If I’m damaging a boss it’s 500k+ in same time line.
Few points:
- it’s the same corruption 100+ empowered
- it’s all timelines
- it’s not a case of there was a echo modifier that I had in an echo completed it removed modifier and then challenged the boss
- it’s not an issue of stack differences when running echo/boss
- the mobs die instantly so I believe the damage is higher then shown in echo
- dummy damage is over 4 million (I know that’s not true dmg but it’s just to note that the numbers are different and not capped)
I don’t have an answer to your question but I have another question about fire aura. Between the different cast fire aura on crit, kill, hit (up to 3 per second). are all 3 of these categories separate (crit, kill, hit) or do they share the same cooldown?
If they’re phrased like “Cast fire aura on crit (up to 3 times per second)” and “Cast fire aura on kill (up to 3 times per second)” (paraphrasing), then they’re separate cooldowns. Each trigger type will have its own cooldown, unless the skill itself specifically says it can’t be triggered more than x times per second, which isn’t the case here.
1 Like
In this case they are separate conditions so they can all trigger separately at once. Just note that the same conditions on different items are additive and don’t have a separate trigger.
So if you have an idol that says 10% cast fire aura on crit and your chest says 10% cast fire aura on crit. You now have 20% cast fire aura on crit and not two cases of 10% cast fire aura on cri.
If you have an idol with 10% cast fire aura on crit and another idol with 10% cast fire aura on fire skill kill. You have two chances (10% each) to cast fire aura providing you fulfill their conditions.
No matter where the source comes from item/skill/passive unless stated otherwise what I just said should apply to it all and be additive if same wording. Or separate procs that can trigger on condition fulfilment depending on wording.
1 Like