Lootfilter Exact match (==)
|
The Exact match is not working anymore sins 3.26.
I have tested it especially with Unique Rings. I want Kalandras Touch as a T0 so i used the BaseType == "Ring". Before 3.26 it worked fine but now all Basetyp that contain the Word Ring is shown with it. Example: Show Rarity Unique BaseType == "Ring" SetTextColor 175 96 37 255 SetBorderColor 175 96 37 255 SetBackgroundColor 255 255 255 255 PlayEffect Red MinimapIcon 0 Red Star If i am doing something wrong, I would appreciate the Help. Ells it's a Bug. Last bumped on Nov 12, 2025, 7:58:33 PM
|
|
|
I'm also having the same issue, now in 3.27. The example filter below causes items to look like the screenshot.
It seems only "Ring" is affected or at least "Silver Flask" isn't affected. ![]() Bug Report ID: #2,204,666,960 The Silver Flask matches the BaseType in the 3rd block so it has a bright background. The Quicksilver Flask doesn't match the 3rd block but it does match the 4th block so it has a dark background. Based on that, I thought Two-Stone Ring and Ringmail Gloves would not match the 1st block since that is BaseType == "Ring" and only match the 2nd block which has a dark background. But it does match the 1st block like the Ring and has a light background. " | |
|
Resolvesd in 3.27.0c
- Fixed a bug where item filters could interpret exact string matches as non-exact matches (or vice versa). |
|

























