Mark_GGG

Exactly the same kind that has existed since closed beta to prevent the additional life monsters get from party size affecting detonate dead.

To be specific, Detonate Dead already uses "intermediary maximum life", which is a separate stat calculated from the base and applying most but not all modifiers. Further modifiers are applied to that stat to get actual max life used for the amount of life stuff has.

Path of Exile isn't isometric, it uses perspective projection - stuff further from the camera looks smaller.

1) That would be a much less clean way to implement Varunastra than the current way, because that would require substantial redefinition of what weapon base types are that would affect all weapons.

2) That would not solve this issue, because this issue is not actually about Varunastra, which was the main point of my post.

I'm not frustrated at all, I'm just trying to explain the parts people don't understand.

Varunastra does work with Nightblade support. If you have Nightblade supporting a skill, and wield Varunastra, you can use that skill and get the benefits from the support.

Nightblade support does not support skills if the weapon restrictions of that skill have no overlap with the additional weapon restrictions imposed by Nightblade. This interaction has nothing directly to do with Varunastra, nor can it - gem supportability is fundamentally determined only by the gems, external aspects of the character can't change supportability.

Originally, the support that add weapon restrictions didn't have that supportability restriction - you could happily support Ground Slam with Nightblade, or Cobra Lash with Close Combat. This resulted in a skill which was limited to be unusable, except with weapon types that couldn't use the skill. Varunsatra, by counting as all weapon types, was the only way to satisfy the conflicting weapon restrictions. But mostly what actuall...

This is correct.

By default, armour only applies to physical damage, and provides Physical Damage Reduction based on comparing the physical damage of the hit to your armour value.

That same calculation occurs for each type armour applies to - if armour applies to lightning damage, then it calculates Lightning Damage Reduction by comparing lightning damage of the hit to armour value.

Because it's calculating "[type] Damage Reduction" for types it applies to, this calculation is inherently independant in cases where armour applies to multiple types.

Yes, that is a bug, and I have confirmed the behaviour and the cause of this bug for future fixing. Using a totemified channelled skill should be consuming the cooldown to use the skill, and is not.

It does get the cooldown. A cooldown prevents you using the skill again, it doesn't interrupt your use of it before it's finished.

The corpse is not dealing the damage, so it's damage modifiers don't have any effect.

It does work. The burning ground from searing exarch altars is identical to other sources of burning ground.

After discussion with some designers, I think I've worked out why so many people think it's bypassing immunity, and it's because there's a different effect not caused by the altar mod - entirely separate to the altar, apparently some exarch monsters use the oil ground effect introduced in heist, where they spread an oil ground effect, that can later be set on fire to add burning damage to the existing oil ground effect. That's not burning ground because it's spawned as a separate ground effect with a different effect that doesn't burn, and later has a second stat added. We're looking into whether this can be changed so the burning part is done using the regular burning ground debuff so that part of the effect would be treated as burning ground.

It does, but it is the trap hitting with your weapon, not you hitting with your weapon, which is what the item cares about

It can be supported, but if you want to use the signal prey skill while the sword is out and about you'll need to have another copy of the gem socketed into an item that stays equipped to you.

It's not supposed to do anything there because that aura is triggered and already has no reservation - unfortunately when that change was made the aura didn't get the internal type set to note it had a built-in trigger, and we didn't have a type for things with no reservation. That will be fixed and the support will not apply.