Mark_GGG

This is not a bug. CI makes you immune to chaos damage, it does not actually affect resistance. This matters for things that scale based on how much actual chaos resistance you have. The displayed values now correctly reflect that and show your actual resistance value rather than showing 100%, which is not actually how immunity works anyway.

I never realized that Knuth started TeX himself.

He created TeX specifically to typeset one book because he wasn't happy with the other options available.

I do know whether that changed, yes.

The Mirage Archer cannot gain frenzy charges and would not benefit from them if it did. It does not use it's own skill, it uses your skill, just like a totem, so your stat modifiers that affect that skill are applicable.

Yes. Intensely.

Yes.

Huh, so I did. I have no memory of that - it's been a busy time.

Also, technically I only said the third installment would be inevitable after they were known, not that those would be the things that made it inevitable. Lots of other things will probably be known at roughly the same time :P

No problem. Going and looking up the current text to copy-paste it here actually got me to notice and fix a typo in it, so this conversation has contributed to improving the game.

"Supports spell skills that deal damage with hits and have no reservation. Cannot support Vaal skills, triggered skills, or skills used by totems, traps or mines. Cannot modify the skills of minions."

Good job on these videos. I look forward to the inevitable third installment once all the enchanments and alternate qualities for the skill are known.

I don't think I've seen anyone else consider the Savage Hit interaction, so I'll confirm here that you are correct on that one.

Correct.

A number of hits is not a measurement of time. "slower" thus does not apply to it.

Impale does have a duration (8 seconds) and temporal chains will make that duration expire slower. It also being removed after 5 hits does not interact with that in any way.

Support gems have supportability text specifically to describe which kinds of skills things they can support. The supportability system is complicated enough that there isn't really any other way to communicate that information than stating it in text.

Ah, whoops, I got that wrong. The supportability on Archmage in 3.14 is actually that it can support any skill without a reservation. While the cost part could technically apply to a reservation skill, the way it interacts with damage wouldn't really make sense, so it was disallowed.

No. Corrupting Fever is similar to a Herald, in that the skill does two things:

1. Applies a buff to you, specifically.
2. Tracks what you do while you have the buff, and does it's effect when you do a specific thing (in this case both "spend life" and "hit enemy" are tracked for different purposes).

A Mirage Archer isn't you and doesn't have the buff, so the skill never notices it hitting things, because it's not looking at the archer, it's looking at you.

No - there's no ongoing component to your skill, it created a vortex with set values, then finished casting. You created a thing which is separate to you, and your skill doesn't continue happening to be able to maintain it.

Fortify, like Ailments, is a "generic" buff/debuff which is not considered a skill effect (regardless of how you gain it), and thus not modified by skill effect duration (or the more restrictive version that only applies to buffs). The duration of Fortify is only modified by modifiers specifically to Fortify Duration.

The "Duration" gem tag refers to specifically skill effect duration, so doesn't belong on this gem - it doesn't have a skill effect duration to modify.

It is a descriptive tag (as are all tags to some extent), it does not affect supportability.

Exsanguinate, mechanically, can chain.

Because of this, the Chain Support can support it - its supportability text says "Supports projectile skills, and any other skills that chain.", and Exsanguinate is in that second group. The tag has no effect on this.

Because Exsanguinate is a (non-projectile) skill that can chain, it is given the Chaining tag, primarily to make it clear to users that the skill is capable of chaining (I don't think we give out any bonuses to gems based on having the Chaining tag and I hope we never do because then we'd probably have to go back and add it to all the projectile gems that are currently assumed to be able to chain by default).

The supportability and the tag do not affect each other. Both are there because the skill works in a way that allows it to chain. The tag is not needed for supportability, the supportability is not nee...

It doesn't in 3.14. Prior to 3.14, all gems had either a mana cost or a mana reservation, and it was fundamentally impossible to have both. Thus Archmage had to be limited to skills with mana costs, because that was all the skills it could work on - skills with mana reservations couldn't have mana costs.

In 3.14 skills all have a cost, and some skills also have a reservation, neither of which have to be inherently of mana. As such Archmage can support any skill, because it's effect can apply to any skill.

EDIT: This is wrong - the cost-modifying part of Archmage could technically apply to any skill, but it's restricted to only support skills without a reservation (which is the closest thing to the actual meaning of it's previous restriction), because it's full effect only makes sense in the context of skills where the amount of damage you do has some relation to how many times you pay the cost.

If you're putting an individual debuff on something, like Ignite, the values of that debuff are inherently set at the time it's created and do not change after that point.

Something like Righteous Fire ort Death's Oath, where your skill is constantly maintaining an aura debuff will be updating it's value on you, which in turn changes the effect on enemies in the area of effect.