How tag hierarchy matching works

Tags use dot-separated segments. A filter tag matches any item tag that starts with the same complete segments.

Prefix matching at segment boundaries

Tags are hierarchical, using dots to separate segments — similar to how you might classify a “weapon.melee.sword”. When you filter by a tag, it matches any item whose tag starts with that filter at a complete segment boundary. For example, filtering by “weapon” matches “weapon.melee.sword”, and filtering by “weapon.melee” also matches it, as does the exact tag “weapon.melee.sword”. However, matching only works from the root: filtering by “melee” or “sword” alone won’t match “weapon.melee.sword” because those aren’t root prefixes. A filter that is more specific than the item’s tag also won’t match — “weapon.melee” doesn’t match an item tagged just “weapon”. Divergent paths like “weapon.ranged” won’t match “weapon.melee.sword” either. Importantly, partial segment matches are rejected: “weap” does not match “weapon.melee.sword”, and “element.fi” does not match “element.fire”. The filter must align with complete dot-separated segments.

Generated from core/tests/features/tag_matching.feature