Affix and unique aspect syntax
D4LF recommends importing a planner build or editing through the GUI first, then refining the YAML manually. Manual edits use lower-case names with underscores instead of spaces.
- Use value when you care about an exact threshold and comparison when smaller-than logic matters.
- Use minPercentOfAffix when you want a roll-quality rule instead of a flat number.
- The same syntax applies when the GUI shows aspect or affix controls, so the file and interface stay aligned.
# Filter for attack speed
- { name: attack_speed }
# Filter for attack speed larger than 4
- { name: attack_speed, value: 4 }
# Filter for attack speed where the affix is at least 50% of its range
- { name: attack_speed, minPercentOfAffix: 50 }
# Filter for attack speed smaller than 4
- { name: attack_speed, value: 4, comparison: smaller }
Affix filters for your Diablo 4 loot filter profiles
Affixes live under the top-level Affixes key. Each named block can combine item type, item power, inherent affixes, greater affix requirements, and multi-rule affix pools.
- itemType accepts one type or a list, which is how you narrow the rule to boots, pants, chest armor, and more.
- affixPool count groups let you say 'match at least N of these stats' instead of forcing a full exact set.
- inherentPool applies the same counting model to the built-in affixes on an item, which is useful for boots and similar gear.
Affixes:
- GreatBoots:
itemType: boots
minPower: 800
inherentPool:
- count:
- { name: maximum_evade_charges }
- { name: attacks_reduce_evades_cooldown_by_seconds }
minCount: 1
affixPool:
- count:
- { name: movement_speed, value: 16 }
- { name: cold_resistance }
- { name: lightning_resistance }
minCount: 2
Percent-based thresholds instead of raw values
minPercentOfAffix keeps items based on roll quality across the stat range. That is often easier to maintain than updating flat values every season.
- A greater affix automatically satisfies minPercentOfAffix.
- You cannot combine minPercentOfAffix with value on the same affix rule.
- This is the cleaner choice when you want reusable profiles across different item ranges.
Affixes:
- NiceArmor:
itemType: chest armor
minPower: 925
affixPool:
- count:
- { name: dexterity }
- { name: damage_reduction, value: 40 }
- { name: lucky_hit_chance }
- { name: armor, minPercentOfAffix: 70 }
- { name: maximum_life }
minCount: 3
Greater Affix filtering modes
D4LF gives you two layers: item-level greater affix counts and per-affix want_greater requirements. Together they let you separate 'any two GAs' from 'these exact stats must be GAs'.
- minGreaterAffixCount checks the item as a whole and does not care which stat rolled greater.
- want_greater marks a specific affix as mandatory or preferred, especially when imported from the GUI.
- The two controls combine, so the item can fail even if it has a GA on the wrong stat.
Affixes:
- PerfectBoots:
itemType: boots
affixPool:
- count:
- { name: movement_speed, want_greater: true }
- { name: maximum_life, want_greater: true }
- { name: strength }
- { name: fire_resistance }
minCount: 3
minGreaterAffixCount: 2
Aspect upgrades for codex progress
AspectUpgrades is for build-specific legendary aspects you want to notice immediately. D4LF favorites those items and highlights them so you can update the codex fast.
- This filter is ignored if the item already matches another keep rule.
- keep_aspects still controls unmatched legendaries outside this list.
- The list uses underscore names taken from the aspect data set.
AspectUpgrades:
- of_singed_extremities
- snowveiled
Sigils, blacklist and whitelist priority
Sigils can be filtered by dungeon names, sigil affixes, or conditional pairs. If there is no Sigils section, D4LF keeps all sigils by default.
- blacklist removes bad combinations first.
- whitelist keeps only the dungeons or affixes you want.
- priority: whitelist flips the tie-breaker when a sigil matches both lists.
Sigils:
blacklist:
- armor_breakers
- resistance_breakers
whitelist:
- vault_of_the_forsaken
priority: whitelist
Tributes by name or rarity
Tributes accepts exact tribute identifiers or rarity groups, and mythic tributes are always kept.
- Short names can omit the tribute_of_ prefix when you need faster manual edits.
- Rarity pairs like [legendary, unique] are useful when you just want broad keep logic.
- This section is high leverage for players who only want a tight subset of seasonal tribute drops.
Tributes:
- mystique
- ascendance_resolute
- [legendary, unique]
Uniques by aspect, affix, item power, and GA count
Uniques can be filtered globally or per-item. Global filters cover every unique that is not explicitly matched by an aspect rule.
- Use minPower, minGreaterAffixCount, or minPercentOfAspect when you want broad unique filtering.
- Use aspect plus affix thresholds when you care about one unique item like Tibault's Will.
- If any unique rule matches, the item is kept. Separate list entries act like OR; fields inside one entry act like AND.
Uniques:
- aspect: { name: tibaults_will, value: 25 }
minPower: 900
affix:
- { name: damage_reduction_from_close_enemies, value: 12 }
Recommended next pages
Use profiles and params.ini when you need filesystem layout and hotkeys, open the
Paragon overlay guide if your planner import includes board data, and keep
troubleshooting nearby if the filter output looks wrong in game.