AR-Liquidity

AR-Liquidity is a clean, “chart-first” liquidity mapping tool built to automatically identify and maintain Buy-Side Liquidity (BSL) and Sell-Side Liquidity (SSL) levels, classify them as IRL / ERL using a dealing range filter, and mark sweeps/raids with an optional raid zone box—while keeping drawings stable using a fixed object bank (no random disappearing lines).
________________________________________
What it detects
1) BSL & SSL (Liquidity Pools)
• BSL (Buy-Side Liquidity): swing highs clustered into meaningful levels (areas where stops tend to rest above price).
• SSL (Sell-Side Liquidity): swing lows clustered into meaningful levels (areas where stops tend to rest below price).
Instead of plotting every single pivot, the script clusters nearby pivots using an ATR-based margin so you get clean, actionable liquidity levels, not noise.
2) IRL / ERL (Dealing Range Context)
Each liquidity level is labeled as:
• IRL (Internal Range Liquidity): inside the dealing range
• ERL (External Range Liquidity): outside the dealing range
By default, the dealing range uses:
• PDH / PDL (Previous Day High / Previous Day Low) as the IRL boundaries.
This helps you instantly understand whether a level is “internal” (often targeted during consolidation/mean reversion) or “external” (often targeted during expansion/displacement).
3) Sweeps / Raids (Liquidity Taken)
A sweep is flagged when price:
• Wicks through a confirmed level
• Then closes back inside (classic raid behavior)
The script marks swept levels with a ✓ check mark in the label.
Optionally, it can draw a raid zone box showing the wick-extreme to the level.
________________________________________
How it draws (stable & clean)
This indicator uses banked objects for lines/labels/boxes. That means:
• No flickering
• No unstable rendering
• No “objects disappearing” when new levels are created
Lines will extend to the right, and can be configured to stop when invalidated (depending on your build/settings).
________________________________________
Inputs (what each one actually means)
Detection
• Swing length (pivot L=R): controls pivot sensitivity (higher = fewer, stronger swings).
• ATR length: ATR basis for clustering margin.
• Cluster margin × ATR: how close pivots must be to merge into one liquidity level.
• Min touches to confirm: how many pivot touches are required before a level is considered valid.
• Max clusters to scan (perf): performance cap for how many stored levels the script checks.
Show / Filters
• Mode (Present/Historical):
o Present focuses on most relevant/active levels.
o Historical can show deeper history depending on your scan/visibility limits.
• Max visible levels per side: maximum number of BSL lines + SSL lines drawn at once.
• Extend levels right: keeps levels projected forward.
• Only above / only below: filter BSL above price and SSL below price (cleaner “current context” view).
• Hide swept levels: removes already-raided levels from view (if you want only “untouched” liquidity).
IRL / ERL (Dealing Range)
• Use PDH/PDL as dealing range: defines IRL boundaries using previous day high/low.
• Show PDH/PDL lines: plots those boundaries as dotted reference lines.
Sweeps / Raid Zones
• Mark sweeps: enables raid detection + check mark labeling.
• Show raid zone box: displays a box from level to wick extreme.
• Raid box extend (bars): how far the box projects to the right.
Style
Full control over:
• IRL vs ERL colors for BSL/SSL
• Line width
• Label size
• Raid box colors
________________________________________
How to use it (practical)
• Use BSL above price as likely upside draw / where liquidity may be taken.
• Use SSL below price as likely downside draw / where liquidity may be taken.
• Use IRL/ERL to decide whether the market is targeting internals (range) or externals (expansion).
• Use the ✓ sweep mark to identify “liquidity already taken” vs “still resting.”
• Pair it with structure (MSS/BOS), sessions, and displacement to time entries after raids.
________________________________________
Pro tips
• If you want more lines, increase:
o Max visible levels per side
o Max clusters to scan (perf)
• If the chart is too busy, increase:
o Swing length
o Min touches
o Or reduce Max visible levels per side