Rule 1. Condition one. Must contain one of 2 affixes: life leech or mele life leech
Rule 1. Condition Two. Must contain one of 25 affixes: x, y, … z (can leave life leech there to save coding time cause the user can figure out redundancy and/or suffer it)
I went to make a similar rule and was shocked that the user can not select affix as a condition when already. I’m guessing the coding wouldn’t have to be changed almost at all, just delete the part that removes affix as an option (if previous condition is affix = true, hide affix option in condition drop down). Just delete that and i’m guessing the rest of the coding already does the rest.
Since discovering this I have learned that others also try to make such a rule and end up with reaching max rules to accomplish it which seems a waste of a perfectly good filter system.
Yes, this would make making filters so much easier. They should allow you to have up to 4 affix conditions in one rule.
Would also be nice to be able to name unique affixes, or have some other way of identifying uniques, because right now you have to go through a bunch of hoops to isolate specific uniques (using things like item type and level).
Even if it would have to be coded a bit differently, it increases efficiency of the filter system many manifold just to have only two affix conditions possible on the same rule.
Perhaps from the perspective of making a filter, but not necessarily from the perspective the resources required. If I remember correctly, there are reasons why they don’t do things like this, at least, not right now.
