PoE 2 Regex Searchbox Mastery Guide

 

Advanced Searchbox Filters for PoE 2

Path of Exile 2 moves fast. Loot piles up, maps blur together, and the difference between a tidy profit and a missed opportunity is often a single keystroke. This guide gives you a practical, battle-tested playbook for using regex and the in-game Searchbox to slice through noise and surface the items and maps that matter. You’ll get clear building blocks, copy‑and‑paste patterns, real-world workflows for stash and map scanning, and a compact cheat sheet you can keep beside your keyboard.

This is a completely original, hands‑on manual focused on actionable patterns and workflows for PoE 2 0.5. Expect examples you can paste directly into the Searchbox, explanations of why they work, and tips to avoid common pitfalls. Bold and italic emphasis highlights the most important keywords and concepts so you can skim and still learn.

Why use regex in PoE 2 Searchbox

The Searchbox is fast, but its raw text matching can miss nuance. Regex gives you precision: match numbers, ranges, combinations of mods, and exclude false positives. With a few patterns you can:

• Find maps with high rarity and high quantity mods.

• Highlight stash items with multiple desirable affixes.

• Filter trade-ready items by exact stat ranges.

• Combine textual keywords with numeric thresholds.

Regex is not magic; it’s a tool. Use it to reduce manual scanning, not to replace judgment. The patterns below are designed to be conservative and reliable in the noisy text environment of PoE 2.

Regex building blocks you need to know

Before pasting patterns, learn these essentials. They’re short, but they unlock everything that follows.

• \d — matches any digit (0–9).

• \w — matches word characters (letters, digits, underscore).

• . — matches any single character.

• + — one or more of the previous token.

• * — zero or more of the previous token.

• ? — makes the previous token optional or denotes non-greedy quantifier.

• () — groups expressions.

• | — alternation (logical OR).

• \b — word boundary; useful to avoid partial matches.

• (?=...) — positive lookahead; assert that what follows matches without consuming it.

• (?!...) — negative lookahead; assert that what follows does not match.

Use lookarounds to require the presence or absence of nearby text without including it in the match. That’s how you match “30% rarity” but exclude “30% chance”.

How PoE 2 Searchbox behaves (practical notes)

• The Searchbox treats input as a single-line pattern. Keep patterns compact.

• Some clients and external stash tools support full regex; others accept a subset. Test patterns in-game first.

• Case sensitivity varies by implementation; use case-insensitive flags if supported or include both cases in alternation.

• The Searchbox often displays the matched item line; craft patterns that match the smallest reliable snippet to avoid false positives.

Quick workflow: test, refine, combine

• Paste a simple pattern and confirm matches.

• Refine with numeric ranges or lookarounds.

• Combine with | to broaden or (?=.*X)(?=.*Y) style to require multiple conditions.

• Save snippets in a text file or macro for quick reuse.

Copyable patterns and what they do

Below are ready-to-use patterns with short explanations. Replace spaces and punctuation exactly as your client expects. These are conservative and designed to avoid accidental matches.

High rarity maps (30%+ rarity)

Code

\b([3-9]\d|1\d{2})%.*rar

Matches a percentage between 30% and 199% followed by text containing “rar” (rarity, rare). Use to flag maps with strong rarity mods.

High pack size (40%+ pack size)

Code

\b([4-9]\d|1\d{2})%.*pack

Targets pack size mods of 40% or higher.

High quantity (15%+ quantity)

Code

\b(1[5-9]|2\d|3\d)%.*quan

Finds quantity mods of 15% or more.

Maps with both high rarity and high pack size

Code

(?=.*\b([3-9]\d|1\d{2})%.*rar)(?=.*\b([4-9]\d|1\d{2})%.*pack)

Requires both conditions on the same line.

Items with two or more desirable mods (example: life and resist)

Code

(?=.*\blife\b)(?=.*\bresist\b)

Use this to surface items that mention both life and resist.

Exclude false positives (exclude “chance” when searching for rarity)

Code

rar(?!chance)

Matches “rar” but not “rarchance” or “rar chance” contexts.

Exact numeric range for a stat (e.g., 80–100 strength)

Code

\b(8[0-9]|9[0-9]|100)\s*str\b

Matches 80–100 strength values.

Sockets pattern (4 linked sockets)

Code

4L|4linked|4-link

Covers common ways 4 linked sockets are written.

Currency shorthand (common abbreviations)

Code

chaos|exalt|exa|chaos orb|exalted

Use alternation to match multiple currency names.

Trade-ready rare with specific mods (example: +# to maximum life and resist)

Code

(?=.*\bmax.*life\b)(?=.*\bresist\b).*rare

Requires both phrases and the word “rare”.

Combining patterns for advanced searches

You can combine patterns to create multi-criteria filters. Two common strategies:

OR-based broad scan Use | to highlight any of several desirable mods:

Code

rar|quan|pack|life|resist|4L

This is a broad net—good for initial sweeps.

AND-based strict scan Use chained lookaheads to require multiple conditions:

Code

(?=.*\b(1[5-9]|2\d)%.*quan)(?=.*\b([3-9]\d)%.*rar)(?=.*\blife\b)

This finds items or maps that meet all three criteria.

Practical stash workflows

• Keep a primary pattern for high-value quick scans (broad OR list).

• Keep a secondary pattern for deep scans (AND-based strict filters).

• Use a trade pattern to surface items that match common marketable templates (e.g., high life + resist + sockets).

• Maintain a map pattern set for your atlas goals (rarity, pack size, sextant mods).

Example stash session Open stash, paste the primary pattern, sweep tabs quickly. When you see a match, paste the strict pattern to confirm. If confirmed, move to a “sell” tab or price-check.

Map scanning strategies

Maps are text-heavy and often include multiple mods. Focus on the mods that multiply loot: rarity, quantity, pack size, and monster modifiers.

Map pattern for high-value maps

Code

(?=.*\b([3-9]\d|1\d{2})%.*rar)(?=.*\b(1[5-9]|2\d)%.*quan)|pack

This flags maps with high rarity and quantity or any pack size mention.

Spotting meta maps Look for combinations like “no regen” or “beyond” that change playstyle. Use alternation to include these:

Code

beyond|no regen|no regen|nemesis|beyond monsters

Trade and market patterns

When preparing items for trade, you want patterns that match buyer expectations. Buyers often search for exact numeric ranges and keywords like “+ to maximum life”, “resist all”, or “4L”.

Trade-ready life/resist template

Code (?=.*\b(8[0-9]|9[0-9]|100)\s*life\b)(?=.*\b(20|30|40)\s*all\s*resist\b)

Adjust numeric ranges to match market tiers.

Price-check pattern

Code

chaos|exalt|exa|mirror|divine

Quickly surfaces currency mentions in item descriptions or notes.

Performance and safety tips

• Keep patterns as specific as necessary. Overly broad patterns return noise.

• Avoid catastrophic backtracking: nested .* inside repeated groups can freeze some clients. Prefer targeted ranges and word boundaries.

• Test patterns on a small sample before running across many tabs.

• Save patterns in a plain text file and label them clearly (e.g., maps_high_rar.txt, trade_life_resist.txt).

• If your client supports it, use case-insensitive flags to avoid missing matches due to capitalization.

Cheat sheet: copy/paste essentials

Purpose	Pattern	One-line use
High rarity	`\b([3-9]\d	1\d{2})%.*rar`	Maps with 30%+ rarity
High pack	`\b([4-9]\d	1\d{2})%.*pack`	Dense map layouts
High quantity	`\b(1[5-9]	2\d)%.*quan`	15%+ quantity
Life + resist	(?=.*\blife\b)(?=.*\bresist\b)	Items with both mods
4 linked	`4L	4linked	4-link`	Socketed items

Example annotated patterns with explanation

Pattern:

Code

(?=.*\b([3-9]\d|1\d{2})%.*rar)(?=.*\b(1[5-9]|2\d)%.*quan)

Why it works: Two positive lookaheads require both a rarity percentage of 30%+ and a quantity percentage of 15%+. The pattern doesn’t consume characters, so it’s safe to use on lines with other text.

Pattern:

\b(8[0-9]|9[0-9]|100)\s*str\b

Why it works: Matches strength values 80–100. \s* allows optional spaces between the number and the stat abbreviation.

Avoiding common mistakes

• Don’t assume every client supports full PCRE. If a pattern fails, simplify it.

• Avoid greedy .* when you can use \s+ or specific tokens.

• Remember that some item text uses synonyms; include alternation for common variants (e.g., resist|resists|resistance).

• When matching percentages, anchor with \b to avoid matching parts of larger numbers.

Comparison of pattern strategies

Strategy	Pros	Cons
Broad OR	Fast discovery; low chance to miss items	More false positives
Strict AND	High precision; fewer false positives	May miss items with slightly different wording
Numeric ranges	Targets market tiers	Requires maintenance as meta shifts

Real-world examples and scenarios

Scenario: You want maps for fast currency farming Use a broad map pattern to find maps with high pack size and quantity, then refine to exclude dangerous mods (e.g., “no regen” if you avoid them). Paste the broad pattern, sweep, then apply the strict pattern to promising matches.

Scenario: You’re selling a rare with life and resist Use the life+resist pattern to find similar items in your stash and in trade listings. Confirm numeric ranges manually and price accordingly.

Scenario: You want to find 4L bases for crafting Use the sockets pattern and then visually confirm links. If your client supports it, combine with item base names.

Maintaining your pattern library

• Keep a single file with labeled patterns.

• Add a short comment above each pattern describing its intent and last test date.

• Periodically prune patterns that return too many false positives.

• Share patterns with guildmates and iterate—community feedback is invaluable.

Troubleshooting

If a pattern returns no matches:

• Simplify it to a single token (e.g., search for rar alone) to confirm the Searchbox is working.

• Remove lookaheads and test each component separately.

• Check for case sensitivity or punctuation differences.

If a pattern freezes the client:

• Remove nested .* constructs.

• Break the pattern into two simpler patterns and run them sequentially.

Advanced tips and tricks

• Use anchored lookaheads to require multiple mods without matching the entire line. This is powerful for multi-mod items.

• Use alternation to cover synonyms and abbreviations. For example: resist|resists|resistance|all resist

• For very specific numeric matches, use explicit ranges rather than \d+ to avoid accidental matches.

Small reference: regex tokens quick list

• \d digit

• \w word char

• \s whitespace

• . any char

• + one or more

• * zero or more

• ? optional

• () group

• | or

• \b word boundary

• (?=...) positive lookahead

• (?!...) negative lookahead

Comparison table: sample patterns and expected match types

Pattern	Matches	Typical use
\b([3-9]\d)%.*rar	30–99% rarity	High rarity maps
(?=.*\blife\b)(?=.*\bresist\b)	Lines with both words	Trade-ready rares
`4L	4linked`	4 linked sockets	Crafting bases
`chaos	exalt	exa`	Currency mentions	Price-checks

Printable cheat sheet (one-line snippets)

• High rarity: \b([3-9]\d|1\d{2})%.*rar

• High pack: \b([4-9]\d|1\d{2})%.*pack

• High quant: \b(1[5-9]|2\d)%.*quan

• Life + resist: (?=.*\blife\b)(?=.*\bresist\b)

• 4L: 4L|4linked|4-link

Keep this on a sticky note or a small text file for quick pasting.

FAQ

How do I start if I’ve never used regex before Begin with the simple tokens: \d, \b, and |. Paste a single token like rar into the Searchbox to see how matches appear. Then try a numeric range and a lookahead. Build patterns incrementally.

Will these patterns work in third-party stash tools Many community tools support regex or similar pattern matching, but implementations vary. Test patterns in the tool you use and simplify if necessary.

How do I avoid false positives Use word boundaries \b, specific numeric ranges, and negative lookaheads to exclude unwanted contexts. Test on a small set before sweeping.

Can I match exact phrases like “+ to maximum life” Yes. Use literal text with optional spacing: \+.*maximum\s*life or maximum\s*life.

What if my client doesn’t support lookaheads Simplify patterns to use alternation and explicit sequences. You’ll lose some precision but retain functionality.

How often should I update patterns Update when the meta changes or when you notice consistent false positives. Quarterly checks are a good baseline for most players.

Is there a performance cost to complex patterns Yes. Complex nested patterns can slow or freeze some clients. Keep patterns as simple as possible and avoid greedy constructs.

Can I use these patterns for automated price-checking They’re useful for surfacing candidate items, but automated pricing requires additional tooling and careful validation.

Closing notes and next steps

This guide gives you a practical foundation to master regex and the Searchbox in PoE 2 0.5. Start small: pick three patterns from the cheat sheet, test them in a single stash tab, and refine. Over time you’ll build a personal library tuned to your playstyle—mapping, crafting, or trading.