Path of Exile 3.7 introduces a refreshed loot filter system that helps players manage item clutter and focus on high-value drops. This guide explains how the new filter logic works and why it matters for endgame efficiency.
Designed for both casual and hardcore players, the POE 3.7 loot filter brings tighter control over currency, maps, and unique items without sacrificing speed.
| Filter Category | Default Behavior in 3.7 | Recommended Tweak | Impact on Gameplay |
|---|---|---|---|
| Currency Items | Show all common currency | Hide low-value scrolls and orbs | Reduces visual noise, speeds tab management |
| Rare Items | Highlight rares with colored borders | Enable name and stat filters | Focuses on keepsakes and builds |
| Map Items | Show maps above tier 2 | Auto-dismiss stacked maps | Clears inventory space for key upgrades |
| Unique Gear | Show all uniques with highlight | Whitelist only desired unique bases | Prevents accidental sales and clutter |
How the New Loot Filter Engine Works
The POE 3.7 loot filter introduces a rule evaluation pipeline that processes items in real time. Items are matched against conditions in priority order, and the first matching rule determines color and visibility.
Conditions can combine item level, rarity, sockets, and player-defined tags. This granularity allows efficient management of currencies, delirium orbs, and quest items without manual color coding.
Behind the scenes, filter files are parsed at load and updated on trade. Understanding condition precedence helps prevent accidental discards and keeps high-end loot highlighted exactly when it matters.
Customizing Rules for Speedrunning and Endgame
For speedclear runs, tighten rules to show only essential items. Hide trivial currency, stackable maps, and common crafting materials to keep the interface clean during intense encounters.
Use color groups to represent real-time priorities, such as attacking, defending, and selling phases. A streamlined palette ensures you can glance at your screen and immediately recognize threat or opportunity.
Advanced users can leverage section inheritance and conditional syntax to create modular filter profiles. Swapping presets between league mechanics and personal playstyles becomes seamless with organized rule hierarchies.
Common Setup Mistakes and Fixes
Misordered rules can cause important uniques to be hidden under broad catch-all conditions. Always place specific exceptions before general hiding rules to protect key drops.
Overlooking socket and requirement conditions may accidentally display unwanted items for your build. Double-check numerical ranges and class filters to match your character progression plan.
Trade safety is another frequent pain point. Use safe hiding for currencies above a threshold and whitelist unique bases you intend to farm actively. This combination reduces panic drops and trading mishaps.
Optimizing Playstyle Around 3.7 Loot Rules
- Set up tiered conditions that prioritize currency management, then rares, then map control.
- Use color groups aligned with your build damage phases to maintain situational awareness.
- Define safe thresholds for currencies to avoid panic selling during busy trade windows.
- Profile your filter before tackling high-tier maps or league bosses to avoid missing key drops.
- Keep a minimal backup preset for emergency resets when experimenting with advanced syntax.
FAQ
Reader questions
Does the 3.7 loot filter apply to items already in my inventory?
No, the filter only affects items currently on the ground or displayed in loot window previews; items stored in your stash remain visible based on their own stash tab settings.
How do I prevent map stacking from cluttering my view in 3.7?
Create a condition that hides maps when you already carry a certain quantity or tier, so your interface stays focused on maps you can actually run next.
Can I share filter presets between leagues without manual edits?
Yes, export and import filter files through the build configuration menu, but verify rule priorities after import because league-specific item bases may shift.
What should I do if my filter hides a unique I want to farm?
Add an explicit exception rule before the hiding condition, specifying the unique base name or item level range, then test in a controlled area to confirm visibility.