-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exploit weakness miscalculation #841
Comments
It’s your only source of armour break so removing the gem, removes your ability to break armour enemies |
@LocalIdentity please read below and reopen issue if that makes sense (not sure if you'll see this msg) If I add another source of armour breaking (mace strike + splinter), removing or adding exploit weakness still has no effect. https://pobb.in/rLx96vHA9iTK |
@chewbacca2314 your second example doesn't work cause you chose the 1h mace strike skill instead of the 2h one |
The same happens with Rolling slam\using any slam skill. Breaking armor has no effect to exploit weakness tho it should give it 50 more as it consumes fully broken armor |
I believe #801 fixed this. But it's not in the release build yet, but Exploit Weakness does work on dev. You can opt in to weekly beta builds in the options, although of course there could be other issues. And I believe any issues posted to github are assumed to be using the latest release, not beta. So if you come across another issue, make sure you see how it functions on release, not beta. |
Check version
Check for duplicates
Check for support
What platform are you running Path of Building on?
Windows
What is the value from the calculation in-game?
Ingame it doesn't increase anything as it's conditional damage
What is the value from the calculation in Path of Building?
It doesn't increase damage in Path of Building
(Probably for that support gem just add "Is enemy armour fully broken")
How to reproduce the issue
PoB for PoE2 build code
Screenshots
https://i.imgur.com/iCl3sm2.png
https://i.imgur.com/hVK8Lm6.png
The text was updated successfully, but these errors were encountered: