[Item Filter] One Filter to Rule Them All 4.9.2 (Updated 2021-10-25 / EOL)

"

Muldini wrote:

Hey,

I've written a filter¹ that is quite popular and would like to improve it performance wise.

I was wondering who I can get in contact with regarding a couple of questions about performance tuning.

It's very likely to be someone who actually implemented it.

Things I'm curious about:
- Are all conditions in a block checked or does it skip to the next block as soon as one condition fails?

- Does numerical comparison use less resources than string comparison? (E.g. would it make sense to have those checks first in a block?)

- Is there a difference between two blocks for one basetype each and one block that's dealing with both basetypes performance wise?

- Are there any other pointers that we filter creators could use on our end to improve performance without losing specific design goals?

Thanks a lot!

"

1. Yes, all conditions in a block are checked.
2. Sort by conditions that would remove the most items first
3. Yes, each block is executed independently
4. Smaller filters = faster

"

Muldini wrote:

It will be updated, it's almost ready. Should be available a couple hours before the league starts.