[3.3] EZ GG Build. Shackles Wander. 63 sec HH Buffs

"

The_x_ile เขียน:

temp chains have cap at 75%.... here you reached 68%.
the question is will this cap exists also when we curse our self?
or the cap is only when applying to enemies?

"

FreezardB เขียน:

"

The_x_ile เขียน:

temp chains have cap at 75%.... here you reached 68%.
the question is will this cap exists also when we curse our self?
or the cap is only when applying to enemies?

The cap refers to the slow effect, which doesn't apply to you because of Kaom's.

The 68% is the "effects expire slower" thing which is different.

"

The_x_ile เขียน:

"

FreezardB เขียน:

"

The_x_ile เขียน:

temp chains have cap at 75%.... here you reached 68%.
the question is will this cap exists also when we curse our self?
or the cap is only when applying to enemies?

The cap refers to the slow effect, which doesn't apply to you because of Kaom's.

The 68% is the "effects expire slower" thing which is different.

How do you know this? Is there any source for this?
Thank you

"

Arkaether เขียน:

Does anyone have experience running this build with a pure-BV setup? Most of the builds that people seem to be running with it (wander, tornado, etc) scale off attack speed/cast speed so the more soul eater stacks you have the more damage you do, but BV has an easy-to-hit max of 10 stacks so it seems like the damage would plateau and you'd only be getting damage via HH's rare mods and nothing from Soul Eater besides movement speed.

Due to this, I'm slightly worried that a pure-BV build would be pretty low on damage, especially considering how thin you have to stretch yourself to hit all the curse nodes/travel across the tree.

I suppose there's the option of going LLRF for massive damage boosts and the additional damage from RF burn, but then you sacrifice a ton of movement speed from QotF and you lose a ton of ES from the forced core uniques you have to run, none of which give any significant ES. Anyone have experience that says otherwise or suggestions on how to do something like that?

"

Crackulous เขียน:

"A cap of 75% now applies to the action speed reduction caused by Temporal Chains and to the effects of Enfeeble."

https://www.pathofexile.com/forum/view-thread/1514557

Thanks to Ghudda.

There's no cap on the 'other effects on cursed enemies (or yourself)' mod of temp chains.

"

Arkaether เขียน:

Does anyone have experience running this build with a pure-BV setup? Most of the builds that people seem to be running with it (wander, tornado, etc) scale off attack speed/cast speed so the more soul eater stacks you have the more damage you do, but BV has an easy-to-hit max of 10 stacks so it seems like the damage would plateau and you'd only be getting damage via HH's rare mods and nothing from Soul Eater besides movement speed.

Due to this, I'm slightly worried that a pure-BV build would be pretty low on damage, especially considering how thin you have to stretch yourself to hit all the curse nodes/travel across the tree.

I suppose there's the option of going LLRF for massive damage boosts and the additional damage from RF burn, but then you sacrifice a ton of movement speed from QotF and you lose a ton of ES from the forced core uniques you have to run, none of which give any significant ES. Anyone have experience that says otherwise or suggestions on how to do something like that?

Soul Eater grants attack speed for whirling blades or shield charge. I'm playing this build on elementalist (blade vortex) if you're curious.

Path of Building - https://pastebin.com/TsCWuG6S

"

Mark_GGG เขียน:

I was really hoping this wouldn't come up.

There are actually two caps, in different parts of the code. In normal circumstances it's capped at 75%. If you actually push the effect to more than 100% slower (time going backwards for buffs/debuffs), a earlier catch logs a warning message with details about the situation and forces the value to 100% slower (not ticking down at all), adn bypasses the normal code for scaling it (which includes the 75% cap). This isn't supposed to actually be possible for players, but there was a case where it seemed to occur with a specific boss which caused bugs in the past, and the safety check is still there. We've known about this for years, but improving it was never a priority because players scaling the effect this high was not supposed to be possible. Probably we'll have to rework some of that now - certainly we don't want to be spamming warning logs whenever a player does this if it can be done legitimately now.