[Item Filter] Check for stat requirements of item

Hi.
Is there a way to filter for the requirements needed by an item?
I found some stats in the stat list (Stats) that look like the thing I need, but they do not seem to work.
For example I want to pickup magic items with less than 181 intelligence required:
I created a new pickup filter, checked the "Magic" checkbox and in the affixes section I put this:

Code:

ImplicitStat LocalIntelligenceRequirementPos Value <= 180

But the bot won't pick up my test item.

Is it possible to do something like this with the bot?
What is the stat LocalIntelligenceRequirementPos for?

Thanks

 

Got this problem too while I was testing something for my equipping bot a while ago the problem was that the bot only knows the stats written under the item like +# to int
I needed to create a array where the item requirements and stats are written in so don't know if it is maybe fixed till now but I've got also problem with the armour value of armours

 

The actual item API doesn't have support for non-mod support for items yet. There's no way to get that info for items, since we have to add in the functions to get the info from the client. Support will be added in the future, but right now doing what xtenshisanx mentioned is the only way.

 

It would be nice if we could combine affixes in a single check, alongside with the item's base stats.

For example:

((ItemBaseMinimumPhysicalDamage + ItemBaseMaximumPhysicalDamage + LocalMinimumAddedPhysicalDamage + LocalMaximumAddedPhysicalDamage) * ((100 + LocalPhysicalDamagePosPct )/100) / 2) * (ItemBaseAttackSpeed * ((100 + LocalAttackSpeedPosPct)/100) Value >= 300 Required

Would filter all the items with a pDPS over 300.

This would make filtering items a lot easier.

Or if we could simply access the final value already displayed on an item such as the final Physical Damage(Min - Max) and Attacks Per Second and do calculations with those it could make things easier.

 

You could do this through a runtime filter (via code) after the item API was expand to support the item stats. Otherwise, it doesn't make much sense to add support for things like that in the static filter, when all it needs is some basic code execution to do the same and would be much simpler.