Mark_GGG

Conditional modifiers like this can't apply do DoT in general, and even more so can't apply to "aura-like" area DoT like Infernal Legion - the effect the minion puts out has one value, it can't be different to some enemies in the area compared to others.

Correct

Removing an Ailment means removing all instances of that ailment. That stat picks one ailment type you are suffering from, and removes all instances of that ailment.

This is not intended. https://www.pathofexile.com/forum/view-thread/3324396/page/2#p24824609

No, only the final hit actually inflicts bleeding on the target, so only the final hit inflicts Rupture.

Any use of a skill is a single action, no matter how long that use takes or how many times it repeats.

No. Impale is an on-hit effect, not part of damage calculation.

Damage calculation determines:

• The amount of hit damage of each type for the hit.
• The damage per second of each damaging ailment applied by the hit.
• Any stun caused by the hit.

Anything else that happens as a result of being hit, including non-damaging ailments, is part of applying damage, not calculating it, so only happens when the damage is dealt.

Just to confirm, does this mean that if I link Vaal Flicker Strike to Curse on Hit Hextouch, then the initial hits causing wounds will apply the curse to all enemies hit

Yes

and the final hit that deals damage can benefit from the effects of this curse?

That depends what you mean by "benefit from". The damage was already calculated, so anything the curse does to affect damage calculation, such as resistance penalties, can't apply unless the enemy already has the curse when wounding hit occurs. As noted above, this includes damaging ailments, which are part of damage calculation, but also notably includes stun.

But curses adding on-hit effects, including non-damaging ailments, such as Frostbite's chance to freeze, will affect what happens when actually dealing the combined damage.

Just like the hit damage is combined into one hit, the associated damaging ailments from those hits are combined into one ailment of each damaging ailment type - if multiple of the wounding hits calculate an ignite, the total ignite fire damage per second from all such hits will be combined into a single ignite applied by the final damaging hit. The same is true of other damaging ailments.

Calculating the damage of a hit inherently also calculates the damage of the ailments it will inflict. This combines damage from multiple calculated hits in the exact same way as Dual Strike, Cleave, and (most similarly) Explosive Arrow.

You hit each enemy once each time you wound them, calculating the damage of the hit (including damaging ailments) but not applying that damage. You are still hitting, so do get all on-hit effects that don't require damage.

At the end, for each enemy, you hit them an additional time, causing on-hit effects again, and dealing the combined damage of all the wounds applied to that enemy as a single hit. If those hits calculated damaging ailments, the damage of those ailments is merged the same way. If some of those hits were crits, then the critical multiplier will have applied to those specific hits when they calcualted, and will not apply to others, but if any of the combined hits was a crit, the combined hit counts as dealing a criti...

since Bladestorm uses attack time, which should be understood as net of action speed, it should be affected by action speed

This is incorrect. Attack time is the base attack time (from weapon), modified by attack speed. Action speed modifies the speed your character does things at at a "higher level" than that. You can see attack time in the character panel and note it doesn't change when you get chilled, for example.

Those mechanics do not proliferate poison, they cause you to poison enemies when you kill a poisoned enemy. The magnitude of the poison will be the same as the highest-magnitude poison affecting the killed enemy, but the new poisons are not in any way the same as the poisons on the killed enemy, and their source is the player with the effect that's causing them. That player's generic IIQ/IIR modifiers will apply.

It's 0.5 seconds and is not modified by anything. This is not meant as a mechanic you interact with or build around, it's just a way for an on-kill effect that's a major part of a skill to be a little more forgiving in the ambiguous-looking cases where the hit from the skill happens and nearly kills them right before a party member/minion/ongoing other skill hits and finishes the enemy off, where you would have got the kill if the hits had landed in the other order. Power Siphon has the same mechanic, as did the old simpler version of Infernal Blow.

Stat values are inherently integers. To allow granularity, regeneration values are stored internally as per-minute rather than per-second, and multiplied for display.

I believe the base roll on the belt is 20997 life regenerated per minute, which divided by 60 for display gives 349.95, which is rounded up to 350 because this description can only show one decimal place, and the 5 in the hundreths place is rounded up.

With the quality modifier, the base roll of 20997 becomes 25196.4, which rounds down to 25196 as the stored value. When divided by 60 for display, that gives 419.933333..., which rounds down to 419.9 when fit to one decimal place in the description.

This is not a bug. The entire point of Soul's Wick is to prevent bringing specific spectres with you and use what corpses you find in the area as temporary minions, while providing a generically useful power boost to reduce the power gap between that playstyle and the regular ability to have specific types of spectre all the time and optimise around them.