Purity of Ice Lvl 21 extra cold res?
I have a 20/20 Purity of Ice that gives me +4 maximum cold res
A level 21 also grants +4 max cold per description But when i change my 20/20 to 21/0 in PoB, i get +5 max cold Is this a bug? Dont want to spend 1 Div just to find out its a bug Im bad at math. Last edited by LoTharios#3338 on Nov 11, 2022, 6:03:57 AM Last bumped on Nov 11, 2022, 8:59:26 AM
|
![]() |
Extra max res happens on lvl 23 for any Purity (except elements)
So if you have +2 to your skill gems, from global mods on gear, local, or Empower support, going from 20 to 21 on gem will effectively give you +1 to max res. |
![]() |
You probably have aura effect somewhere that in combination with the +1 level is enough to get an extra max cold res even if level 21 by itself wouldn't.
|
![]() |
ok, bougth it.
didnt change anything. but also bought ashes of the stars, now i have +5 So its a PoB bug since i have purity linked with determination, malevolence and enlighten. Im bad at math.
|
![]() |
You are still capped at 90%.
However it would allow you to remove other items providing additional max res |
![]() |
" While not entirely impossible, it's unlikely that it's a bug. More likely explanation is that there is a difference between your actual setup and what you have in POB. A single aura effect % can make the difference so maybe check again if both setups really are identical? |
![]() |
Also the aura effect will only change the stats on the character screen, not in the gem description.
|
![]() |
" Just as I said, you get +5 when hitting lvl 23. You have global +1 from Ashes and local +1 from gloves, so a lvl 21 gem will effectively be lvl 23, while a lvl 20 gem will be 22, so only +4 Aura modifiers won't affect this. Whether your gem is 20 or 22 is the same for %increased aura effect, as it applies to the +4% max res value (so each 25% increased aura effect will give +1% to mas cold res). However, with a lvl 23 purity, each 20% increased aura effect will provide another +1%, making hitting lvl 23 an absolute priority. So, no bug here. |
![]() |