You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've checked for duplicate open and closed issues by using the search function of the issue tracker
What platform are you running Path of Building on?
Windows
Is your feature request related to a problem?
There isn't really a big problem but PoB currently lacks a seeker for adjusting values for unique items that are corrupted by a Volatile Vaal Orb.
The items exceptions should be considered when implementing the function for this in PoB.
Describe the solution you'd like
I'd like to be able to adjust certain values based on the function of a Volatile vaal orb which range from 0.78 to 1.22 multiplier to certain modifiers on unique items.
Describe alternatives you've considered
There is no alternative. There is only implementation.
There isn't really a big problem but PoB currently lacks a seeker for adjusting values for unique items that are corrupted by a Volatile Vaal Orb.
I'm not sure if you meant adjusting values on an item already corrupted in-game. I.e. that you import a volatile orbed unique and can then later adjust the rolls. This is not possible yet, but #9935 adds the corruption menu from pob2. Importing corrupted ranges is probably possible as the oauth api does contain nicely formatted stat values and mod ids, which could be used to figure out the range value, but there are undoubtedly some situations where this doesn't work, such as catalyst quality
Activity
vaisest commentedon Jul 11, 2026
I'm not sure if you meant adjusting values on an item already corrupted in-game. I.e. that you import a volatile orbed unique and can then later adjust the rolls. This is not possible yet, but #9935 adds the corruption menu from pob2. Importing corrupted ranges is probably possible as the oauth api does contain nicely formatted stat values and mod ids, which could be used to figure out the range value, but there are undoubtedly some situations where this doesn't work, such as catalyst quality