A friend of mine was surprised to see my Divine Blessing Lifetap setup, so I thought there must be more people who are unaware of how this works.
Socketing Divine Blessing with Lifetap on a percentage-based aura means that the Health Cost will be calculated from your maximum mana, not your maximum health. What this means is that you can cast a 50% aura from your life pool despite the 300% mana multiplier on lifetap.
External link →Har Har. It might have been an oversight, or you might argue it was unintended or that it's overpowered, but it's not a bug, because the descriptions are accurate. That's all I'm sayin.
For those who aren't following, on eternal blessing support, "... while you have an aura from a supported skill ON YOU" doesn't apply in this case because pride is never on the player who casts it.
This is a bug (and is not even directly caused by pride not affecting you). Pride is on you. It does not have any effect on you, but it is on you. An aura being on you means you are the source/centre of the aura. An aura (or other buff/debuff) having an effect on you means it is applying stats to you. Pride does not do this.
Which is kinda funny if you compare it to similar cases of literal modifiers. I mean, it's obviously unintended and op, I won't debate that, but it's funny.
The modifier "increased effect of non-curse auras on you" has never affected Pride, because Pride doesn't affect the player. This has never been considered a bug because that's literally how the modifier works. But the exact same wording is used on Eternal Blessing and now that is a bug. It's not a bug. It's a f**k-up. They just f**ked it up.
I mean the same thing can't be, simultaneously, a bug when it's advantageous to the players and not a bug when it's disadvantageous. But yeah, GGG said it's a bug so that must be it.
But the exact same wording is used on Eternal Blessing and now that is a bug.
That is not the "exact same wording". There is a distinction between an aura being on you (you are the source/centre for the aura), and an aura having an effect on you (the aura is applying stats to you). An aura can be on you and not have any effect on you (pride), or can have an effect on you without being on you (an ally's aura buff).
The wording you quote is specifically modifying the effect that certain auras have on you. It does not care whether those auras themselves are on you or not - it has always modified the effect that ally's auras have on you, despite those auras not being on you. The wording is directly analagous to e.g. "x% increased effect of Arcane Surge on you" - it's an effect modifier.
Eternal Blessing refers to auras being on you, regardless of whether they have an effect on you, as did the old Mortal Conviction keystone. This is not a new distinction.
Can you shed any insight into the reasoning behind isolating Pride as a beneficiary like this? It's clearly been a consideration given the wording but it's counter intuitive to what I think the spirit of the gem represents
Pride has not been isolated as a beneficiary, it (and a few other auras) are currently bugged with this support. I have edited my above post to be more clear about what I was pointing out.
I see. I guess I (and others) drew a faulty correlation, as Pride is seemingly the only aura that is working in this way. Thanks for the clarification!
Flesh and Stone is also bugged in a similar way for a different reason, and I think there might also have been one of the aura skills from a unique item as well?
Was Divine Blessing meant to do anything useful for Death Aura, from Death's Oath? At the moment, it disables the aura and (because it's passive) you don't get a button to turn it on.
I was hoping it would be a functional 6th link, replacing Lifetap. It's not that.
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.
devtrackers.gg