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
This issue may not be fixable without a major rework of the query system and as such might not be actionable, but I do want to track the shortcomings of is:dupe and the potential use cases for a more powerful is:dupe somewhere.
While most filters look at items in a vacuum and can thus be composed with boolean logic, is:dupe looks at your whole inventory and further composition only happens after is:dupe has seen your entire inventory. There are a bunch of ways in which users unsuccessfully try to compose is:dupe:
We used to have is:seasonaldupe as a special filter where items from different seasons would create unique dupe groups. Contrary to the boolean Adept property above (where items always fall into one of two buckets and the user could provide is:adept as a grouping criterion), here the season is an integer and the query system doesn't have a way to extract properties from items right now...
Create entirely new dupe groups
Listing this just for completeness, but some people would use something like "find all weapons of the same type, archetype and element". This is probably better handled by a dedicated solution like Weapon Type + Burn matrix #7790.
(1) Find all items not matching predicate X where there are dupes matching X / (2) find all items where one of the dupes matches X
We have special filters for some of these, but have declined adding a ton more because it'd get out of hand.
An interesting observation is that most of our special filters match all items where at least one of the dupes matches X, but for some of these arguably the more useful matching behavior would be matching items only if there are also items where the predicate doesn't match
is:dupelower (1, X here is "highest power copy of the item")
is:crafteddupe (2, X here is is:crafted)
is:wishlistdupe (2, X here is is:wishlist)
Find not-favorited items where a dupe is favorited (1, X would be tag:favorite)
Find ALL copies of dupes where one dupe is tagged "Infuse" (2, X would be tag:infuse)
This issue may not be fixable without a major rework of the query system and as such might not be actionable, but I do want to track the shortcomings of
is:dupe
and the potential use cases for a more powerfulis:dupe
somewhere.While most filters look at items in a vacuum and can thus be composed with boolean logic,
is:dupe
looks at your whole inventory and further composition only happens afteris:dupe
has seen your entire inventory. There are a bunch of ways in which users unsuccessfully try to composeis:dupe
:Create strictly more restrictive dupe groups
is:dupe
will always match both of them, and combiningis:dupe is:adept
will still highlight the "Fatebringer (Timelost)"is:dupe
should not count ITL weapons as duplicate from original #10321is:seasonaldupe
as a special filter where items from different seasons would create unique dupe groups. Contrary to the boolean Adept property above (where items always fall into one of two buckets and the user could provideis:adept
as a grouping criterion), here the season is an integer and the query system doesn't have a way to extract properties from items right now...Create entirely new dupe groups
(1) Find all items not matching predicate X where there are dupes matching X / (2) find all items where one of the dupes matches X
We have special filters for some of these, but have declined adding a ton more because it'd get out of hand.
An interesting observation is that most of our special filters match all items where at least one of the dupes matches X, but for some of these arguably the more useful matching behavior would be matching items only if there are also items where the predicate doesn't match
is:dupelower
(1, X here is "highest power copy of the item")is:crafteddupe
(2, X here isis:crafted
)is:wishlistdupe
(2, X here isis:wishlist
)tag:favorite
)tag:infuse
)Hide some items from dupe
is:dupe
(the intention being that I will dismantle junk later and I wantis:dupe
to behave as if thetag:junk
items were already gone)The text was updated successfully, but these errors were encountered: