Where D4LF stores profiles, params.ini settings, and Paragon-ready YAMLs.

How D4LF profiles are evaluated

• All profiles are whitelist filters. If none of your active profile rules match an item, D4LF discards it.
• Each YAML file can hold one filter family or many. D4LF merges all profiles listed in params.ini before it decides what to keep.
• If a filter family is missing entirely, D4LF keeps that item class by default. For example, no Sigils section means sigils are not filtered out.
• Config files are validated on startup, so broken structure or invalid YAML can stop D4LF from launching until the file is fixed.

Config folder

The config root is C:/Users/<WINDOWS_USER>/.d4lf.

• profiles/*.yaml stores loot filters and can also include Paragon data.
• params.ini stores settings such as hotkeys, browser selection, stash tabs, and vision mode.
• The GUI is still the safest place to manage settings when you are not intentionally hand-editing YAML.

D4LF params.ini settings that matter most

If you searched for d4lf params.ini, these are the settings that usually matter first: profile loading, stash tab scanning, vision mode behavior, hotkeys, and whether D4LF is allowed to control the mouse.

• profiles decides which YAML filters D4LF loads.
• check_chest_tabs and max_stash_tabs affect stash scanning behavior.
• vision_mode_type and run_vision_mode_on_startup shape the overlay workflow.
• vision_mode_only is the first setting to check if mouse control is not working.

Supported profile sources

The GUI can import build pages from Maxroll, D4Builds, and Mobalytics. Profiles can also be created manually from the YAML examples below and refined with the loot filter rules.

General settings you will touch most often

• profiles: comma-separated YAML filenames that D4LF loads from the profiles folder.
• check_chest_tabs and max_stash_tabs: defines which stash tabs the Diablo 4 loot filter is allowed to scan.
• keep_aspects and handle_uniques: controls how unmatched legendaries and uniques are treated after profile checks.
• junk_rares and do_not_junk_ancestral_legendaries: decides how aggressively rare and legendary cleanup should run.
• mark_as_favorite, run_vision_mode_on_startup, and vision_mode_type: shapes the overlay and favorite-marking behavior.
• browser and minimum_overlay_font_size: affects imports and readability when using planner-driven workflows.

Advanced hotkeys and recovery settings

• run_filter, run_filter_drop, and run_filter_force_refresh: start the main loot filter in normal, drop, or full refresh modes.
• move_to_inv and move_to_chest: powers the fast move workflow between stash and inventory.
• run_vision_mode and toggle_paragon_overlay: controls the overlay hotkeys, with F10 as the default Paragon toggle.
• process_name, vision_mode_only, and fast_vision_mode_coordinates: helps special setups, remote play, or mouse-disabled operation.
• log_lvl and exit_key: useful when you need faster diagnosis or cleaner shutdown behavior.

D4LF profile editing examples

# Filter for attack speed
- { name: attack_speed }

# Filter for attack speed larger than 4
- { name: attack_speed, value: 4 }

# Filter for attack speed larger than 50 percent of the affix range
- { name: attack_speed, minPercentOfAffix: 50 }

Manual editing caution

Config files are validated on startup. Invalid structure or syntax can prevent D4LF from launching, and the error message should point to the problem area.

If you are tuning filter behavior instead of filesystem layout, open the Diablo 4 loot filter rules. If you imported a planner build, pair it with the Paragon overlay setup. If you want to compare D4LF profiles with the official in-game import-code workflow, read D4LF vs built-in loot filter.