As both the helpfile and code indicate, you have a CHANCE to get one of X benefits. Meaning you might get X, or Y, or Z, etc.

So let's say you get X.
But you are ALREADY RESISTANT to X.
Then you won't get X since it no longer stacks, as you are already resistant to X.

So if you WOULD get resist poison, but you are a dwarf (already resisting poison), then you won't get anything this time.

But if you WOULD get resist negative, and you are a dwarf (not resisting negative), then you will be resisting negative.

I don't understand the reason to nerf this power. But if that is the direction you want to go, so be it. Really sad that a basic cabal power that is by far not considered OP by everyone got shafted. So don't play a Dwarf Paladin with Faith cause you can only get Resist Negative basically. This his a horrible change.

As far as I can read it, this isn't affected the resists you can get.
You've always had the resists, it was just giving them to you AGAIN
(which does nothing). Now you just aren't getting duplicated resists at
all.


Ishuli's more or less saying how it worked previously -

If you're resist X (via whatever reason), and Favor of the Sun tried to
give you that resist, it would apply the affect to give you the resist
again...but that does nothing. If the other affect wears off, it takes
the resist with it. This could make it so that Favor of the Sun thinks
it's giving you resist still, but isn't, but also prevent you from
renewing the resist via other methods.



How it works now -

You resist something, and Favor of the Sun tries to give you that resist
again. Code notices that, and aborts the 2nd favor of the sun affect.


Net change: No differences in the resists you receive. In the new case,
you should never be BLOCKED from renewing a protection due to the code
thinking you have it when you don't now.


Admittedly I could be misunderstanding what's happening, but I don't
think you're losing anything here.

It used to stack, for example, with azure conviction I could have huge *resist* to neg eng instead of just negating the vuln.

I forgot about Zulghinlour's resist/vuln changes a while back where it became a sliding scale. Used to be you either had resist, vuln, or neither, and none of it stacked.

Looks like there was a code change relevant to the skill now anyways. Won't get the super-resist (which probably wasn't the initial goal), but more likely to have broad resists now.

So what people are complaining about is that now instead of getting something 100% of the time, you get something 33 or 66% of the time if you already have resistance(s).

How people would PREFER it to function, I'm sure, would be to target a resistance you don't have - e.g. a dwarf would always get one of the two types they don't have on a 50/50.