Liquidity Hunter [Flow Dominance + Pending Breaks]

Apr 3

Liquidity Hunter is a pivot-based reaction-zone indicator that estimates flow dominance inside each zone and gives filtered trade guides, but it is best used as a confluence tool, not as a standalone signal engine.

This script is a liquidity zone mapper with a basic execution layer. It finds pivot-based zones, colors them bullish or bearish, tracks how often price touches them, accumulates volume inside them, and estimates internal buy vs sell pressure using candle location and body strength. It also supports session shading and EMA trend filtering.

What it is good at:

showing where price has reacted before
ranking zones by revisit activity and cumulative participation
giving a quick “who was more active here?” read with the B% / S% label
filtering out some weak setups with touch count, dominance threshold, reclaim logic, and trend filter inputs.

What it is not:

not true order flow
not real bid/ask delta
not a guaranteed “smart money” detector
not statistically validated from the code alone
not something I would call a standalone high-accuracy entry system yet. The pressure percentages are still a proxy model, not actual tape data.

Accuracy estimate:

Zone usefulness: about 7.5/10
Flow/dominance read: about 6/10
Signal timing / entries: about 5.5–6.5/10
Overall practical accuracy: about 6.5/10

the zones are based on pivots plus ATR width, so they are structurally reasonable, but still heuristic
the B/S percentages come from candle math, not actual aggressive buy/sell data
the signal logic is filtered, but still relatively simple compared with a fully tested institutional execution model
there is no out-of-sample performance test or win-rate study attached, so I cannot honestly claim a hard percentage accuracy.

Apr 7

Release Notes

It keeps the same core foundation:

pivot-based bull/bear zone creation
cumulative buy/sell flow scoring inside zones
pending-break and broken-zone state handling
session shading
visibility filtering and zone lifecycle management

Upgrades the architecture in a few major ways:

What added

Lower-timeframe confirmation module
This is the biggest change. adds request.security_lower_tf() arrays plus per-zone LTF metrics like:
LTF touches
LTF reclaim closes
LTF break closes
LTF bull/bear pressure
LTF probe depth
Reaction engine instead of trade-guide engine
shifts toward zone-behavior validation:
bull reaction
bear reaction
pending break
confirmed zone failure
Better break qualification
Instead of simple wick-through/reclaim logic only, adds:
probe-depth filtering
relative-volume threshold for warnings
reclaim-count requirements
LTF break-close confirmation
More advanced badge coloring
changes the cumulative-volume badge color based on actual flow leadership:
buy-leading
sell-leading
neutral
Richer zone state
stores much more information per zone, so it is more of a behavior engine than a simple plotting/signal tool.

What removed compared

Entry / stop / take-profit guide engine
BUY / SELL setup generation
Signal mode toggle (Reversal vs Momentum)
Trend-filtered trade setup logic
Risk:reward guide plotting

May 1

Release Notes

1. Confirm-signals-on-close toggle.
2. Session filter now actually affects:
- zone creation
- signals
- or both
3. EMA trend filter is now functional:
- Price vs EMA
- EMA slope
- Price + slope
4. Optional trend filter for:
- zone creation
- reaction signals
5. New overlap rule:
- Block all overlap
- Same-side only
- Allow opposite conflict
6. One-reaction-per-zone option.
7. Better aging cleanup:
- remove aged unbroken zones
- remove aged mitigated zones
8. Zone quality classification:
- Premium
- Strong
- Valid
- Weak
9. Reaction markers added.
10. Compact / full dashboard added.
11. Dashboard now shows:
- bull/bear zone counts
- best quality
- pending/broken count
- signal gate status
- trend/session state
- last event
- LTF touch/reclaim/break counts
- OHLCV proxy note


Disclaimer

This script is provided for educational and research purposes only. It is not financial advice, investment advice, or a recommendation to buy or sell any security, futures contract, cryptocurrency, or other financial instrument.

The buy/sell pressure, net delta, imbalance, absorption, and profile readings shown by this indicator are estimated from publicly available OHLCV candle data. TradingView Pine Script does not provide true bid/ask aggressor volume, actual order-flow tape, or real exchange-level buy/sell delta. Therefore, all “buy,” “sell,” “delta,” and “pressure” values in this script should be understood as modelled pressure proxies, not actual market-order flow.

Lower-timeframe reconstruction, when enabled, may improve the granularity of the estimate, but it still does not convert the script into a true bid/ask delta or order-flow tool. It remains an OHLCV-based approximation.

No indicator can predict future price movement with certainty. Market conditions can change quickly, and signals may repaint visually during an active candle until the bar is confirmed. Users are responsible for their own analysis, risk management, and trading decisions.

Always test any script thoroughly in replay, simulation, and forward observation before considering live use.

May 9

Release Notes

Key updates included:

LTF reclaim/break logic now only counts after actual LTF zone interaction
Mitigation is no longer automatically triggered by any wick touch
Zone creation session filter now uses the actual pivot bar
Zone creation trend filter now uses the actual pivot bar
Broken zones can be excluded from dashboard focus
Dashboard text size input added
Dashboard wording improved: “Defense / Probe” instead of misleading “Pending Break”
Zone label flow now uses effective flow, matching dashboard behavior
LTF processing is performance-gated to nearby/touched zones

A FAIL marker means the zone has been invalidated, not that price should reverse from there. So once a demand zone fails, price can continue lower; once a supply zone fails, price can continue higher. In the QQQ screenshot, price broke above the prior supply/liquidity areas and then continued upward, so those FAIL labels are basically saying:

That supply/resistance zone did not hold.
Buyers accepted above it.
The failed zone may now act as support on retest.

Supply FAIL → convert to potential support
Demand FAIL → convert to potential resistance