Protector's Stone in helm still worth?

Even though the ED will be bugged, and other stats aside, is it still worth doing this for the minus enemy physical resistance? Specifically for ES/MB Warlock and/or WW Barbarian.

As a blanket statement:
Absolutely.

-10 phys res is quite a bit. Plus the other non-ED stats still work.
And depending on your helmet, you can still make the ED work as well.

Whether it really is worth it for your exact build depends on the build as it can be counterproductive if say you lose a breakpoint that ends up netting you more and that you can't get by other means. Especially for an ES lock in the current state of the game as you can rely on nearly 100% amp uptime, making -res less impactful.
More likely than not though, at least with some shuffling around of other gear, it'll still be worth it.

That said, if you can slot it into your weapon directly, that'd usually be the better way to go.

WW bar, you need to see your monster fight status before use it.

Usually it work good for ww bar when equipment is not so good.

if you see 3%-5% hp remaining in your monster fight. it may help. most case, no effect.

The other scenario is against sunder phy monster. it will help a little bit but you still need spend some time to kill sunder phy immunity.

Also, please experiment it with worst phy Stone if you feel perfect one may help. This jewel is not strong enough. most case, worst jewel = perfect jewel.

Schnorki wrote: 15 hours ago

And depending on your helmet, you can still make the ED work as well.

How can I make it still work in a helmet?

there is a method, I remember, find some kind of ED or special rare

Helm. it will overwrite bug, but it is not so good.

rare

Helm are weak. there is special rule there but no people use it for some reason...

If you have

Ist or

Lem in your

Helm or

Rune Master /

Tomb Reaver and don't rely on

Burst of Speed then Protector Stone sure is an improvement .

Fade proc is yummy. Additional Experience too. As a hoarder I am working to have 5*

Shako socketed with each type of Stone in my stash. Only have fire and Light ATM. First physical I will get will go right in the

Shako, especially if it will be so-so. If I ever get one close to JP, then I will consider other gear.

It sounds like it probably will be worth it for my ES/MB 'lock since I'll have the free slot in the

Hellwarden's Will anyways. I'm not so sure about my WW Barb because I only really use him for Trav and I have a

Cham in there for CBF. I could move stuff around at the cost of MF or dmg but meh.

The real wonder I didn't think of would be if I put it in my Bowazon's

Giant Skull, would it just be a downgrade? I have a 15% IAS jewel and a 40% ED jewel in there now. I could put in a

Protector's Stone and an IAS/ED jewel, but I'm afraid that would trigger the bug for both jewels (?)

justinman114 wrote: 11 hours ago

Schnorki wrote: 15 hours ago

And depending on your helmet, you can still make the ED work as well.

How can I make it still work in a helmet?

If an item has or receives ED before it receives the ED & +dmg, the bug typically got cancelled out, making all of it work fully.
So if you use say a

Crown of Ages (random example, any helmet with 2+ sockets would do) and you socket it with a

Protector's Stone first and then whatever else, you'll end up bugged and losing the ED.
If however you use that same

Crown of Ages, socket it with an ED/IAS jewel first to give it "ED only" and after that slot a

Protector's Stone into the 2nd socket, all of it should work fine.

The same works in 1-socket helmets that come with ED by default such as "deadly" prefix circlets.

So in the case of your zon's

Giant Skull, just make sure you socket the ed/ias jewel first and then the

Protector's Stone second and it should all work.


Diclaimer:
That's how it used to play out. Not 100% certain nothing's changed and they didn't somehow "keep the bug but make it different".
All I've got from more recent times is anecdotal evidence from my pally as I was too tired initially and socketed his helmet the wrong way round (Stone first). Adjusted that to Stone last later on and it seemed to still result in it now working but that's without actively testing/intentionally keeping track so take with a grain of salt.
Might do some actual testing on it if/when I get around to it just to confirm. Though there are plenty of folks still claiming it works the same as it used to (which might as well be assumption of nothing having changed rather than actively tested though, who knows).

justinman114 wrote: 7 hours ago

It sounds like it probably will be worth it for my ES/MB 'lock since I'll have the free slot in the

Hellwarden's Will anyways. I'm not so sure about my WW Barb because I only really use him for Trav and I have a

Cham in there for CBF. I could move stuff around at the cost of MF or dmg but meh.

The real wonder I didn't think of would be if I put it in my Bowazon's

Giant Skull, would it just be a downgrade? I have a 15% IAS jewel and a 40% ED jewel in there now. I could put in a

Protector's Stone and an IAS/ED jewel, but I'm afraid that would trigger the bug for both jewels (?)

WW bar, not worth change. If you arent sure, run calculator.

Ismail Life 32,102 , around 1.3 second kill without Stone, dps 28k, standard soso ba Grief.

it doesnt looks like much room to improve...so... no need the trouble. ed ias Stone rare circle.
Just use Stone as extra mf

Schnorki wrote: 3 hours ago

[..]
Diclaimer:
That's how it used to play out. Not 100% certain nothing's changed and they didn't somehow "keep the bug but make it different".
All I've got from more recent times is anecdotal evidence from my pally as I was too tired initially and socketed his helmet the wrong way round (Stone first). Adjusted that to Stone last later on and it seemed to still result in it now working but that's without actively testing/intentionally keeping track so take with a grain of salt.
Might do some actual testing on it if/when I get around to it just to confirm. Though there are plenty of folks still claiming it works the same as it used to (which might as well be assumption of nothing having changed rather than actively tested though, who knows).

Bit o' testing never hurts so I went ahead and made the time.
Apparently, it actually doesn't quite work the same way anymore.

Stone socketed before ED/IAS: ED/IAS socketed before Stone: Stats on the CoA look exactly the same as the bug isn't visible anywhere on the item but as you can clearly see, the ED only applies when the ED/IAS jewel is socketed first which is exactly what you'd expect, based on how the bug has always played out in the past.

Except..and here is where it differs, if you math it out, things don't match up with expectation: *"Stone Only" we assumed is bugged so expected ED is only from strength, ignoring the Stone's ED.
*"Stone, then Jewel" is equally assumed bugged, expecting only ED from strength to work.
*"Jewel, then Stone" should work, based on testing in the olden days, expected ED is hence strength + jewel + Stone.

Weapon only and jewel only work fine, as expected.
Stone only and Stone, then jewel are bugged, ignoring all non-strength ED, as expected.

The "Jewel, then Stone" scenario, which is the one that should function however actually only functions in part, not matching expectations. Specifically, it only considers the ED from strength and the ED/IAS jewel. The 50% ED from the Stone itself are still counted as 0. After mathing it out and spotting the failure, I went ahead and farmed a proper test Stone in-game to avoid the testing/editor version just being bugged somehow and the result is the same:
If you socket the Stone, followed by the jewel, neither one's ED is counted.
If you socket the jewel, followed by the Stone, the jewel's ED works fine, as does the Stone's min/max but the Stone's ED is still not counted.

TL;DR:
You can make a jewel's ED work in the same item as the Stone but the Stone's ED will always be lost and is hence effectively irrelevant unless you socket it into a weapon.

Correction added for the post above. Turns out it seemed to work at first glance but doesn't really work as it should when you check the math.

Unless the LCS is lying again. Which is possible, too. But mweh. ^^