False Breakout Trap Radar MT5
- Indicators
- Konstantin Chechnev
- Version: 1.0
A false breakout is always obvious—roughly three candles after you believed the real one. False Breakout Trap Radar does not react to the first poke through a level; it waits for evidence: how price left, whether it was accepted outside, who became trapped and whether the market could reclaim the boundary.
It is a non-repainting probabilistic radar for false breakouts, liquidity sweeps and trapped traders. A developing event can be watched live, but its arrow and alert are released only after closed-bar confirmation.
From an obvious level to a confirmed trap
- Liquidity mapping combines swing highs and lows, previous-day high/low, repeated touches and rejections, plus round-price proximity. The more obvious a level is to the crowd, the more closely its response is monitored.
- State Engine moves a level through ARMED → APPROACH → BREACH → RETURNED → RETIRED. One wick is not promoted to a trap: breach depth, closes outside, the extreme and time spent beyond the boundary all matter.
- Liquidity Sweep means a fast excursion and return without acceptance outside. Trapped Longs / Shorts means the market first shows acceptance of the break, then reclaims the level and traps late participants.
- Battle Zone detects a different mechanism: low movement efficiency, repeated center crossings, compression, wicks and activity. It is a neutral expected-expansion zone, not a preselected direction.
- A calibrated logistic model combines commitment, acceptance, failure, liquidation pressure, sweep depth, return, candle body, trends, activity, range and session. Its output is corridor-reach probability for directional events or escape probability for a Battle Zone.
Microstructure without rewriting history
Live CopyTicks data provides a diagnostic pulse: tick count, path reversals, average and maximum spread. It is deliberately kept out of the confirmed score, because an identical live stream cannot always be reconstructed after a terminal restart.
The final score relies on reproducible bar data: tick volume, range and spread are compared with an adaptive robust norm for each session. No imaginary DOM and no “synthetic delta” hidden behind a sophisticated label.
On attachment, the indicator rebuilds old levels and events to restore context, but does not paint historical arrows that could never have been seen live. New markers are permitted only for confirmations that occur after launch.
What remains on the chart
A confirmed event receives a gradient zone, weighted pain price, forward liquidation corridor, invalidation level and score. Standard panel shows the conclusion; Detailed exposes the components. Directional zones remain active for up to 36 bars and Battle Zones for up to 12, then become memory, liquidated or invalidated.
The interface automatically supports 11 languages. Display filtering can retain All events or only Signals, Traps, Sweeps or Battle Zones; developing structures may be hidden without changing calculation.
Let the trap form in the tester
Run the demo in the visual Strategy Tester with Every tick based on real ticks. Move forward from launch: watch APPROACH, BREACH and RETURN, then verify that confirmation appears only after the candle closes.
Old context is reconstructed, but retroactive arrows are deliberately absent. You see what would have been available to the trader at that moment—not promotional archaeology.
The radar can spot a trap; it cannot disarm risk
False Breakout Trap Radar is an indicator, not an Expert Advisor. It never opens, manages or closes a position; a score or corridor is neither an order to enter nor a guaranteed Take Profit.
Probabilities, historical observations and testing do not guarantee future accuracy or profit. Quote flow, spread, liquidity, history quality, volatility and broker conditions can change the event; the trading decision and risk remain with the trader.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Settings and starting ranges
- M1 signal mode — Hourly average. This means roughly one event per hour on average, not a compulsory arrow every hour. Accurate is typically 0–2 signals/day; Frequent 5–10. Custom uses score 70, valid 60–90.
- M5+ minimum score — 75 (60–90). For a first test, try 70–82: higher values reduce frequency and retain more pronounced structures.
- Level visibility — 80 bars (40–200). Higher values make level selection stricter and leave fewer levels; lower values expose more candidates.
- Minimum sweep depth — 0.06 ATR (0.02–0.30) and Return confirmation — 0.45 ATR (0.25–1.20). The first defines a meaningful excursion; the second defines reclaim strength. Do not optimize them as if they were the same control.
- Same-side pause — 6 bars (0–30) limits clusters of similar confirmations. Spread filter — 3.5 z (1.5–6.0) rejects execution cost that is abnormal for its session.
- Visible events — All; Panel — Standard; width — 34% (30–45); Show developing events — true. Alerts: Off, Popup, Push or Both; Popup is default.
Change score first, then sweep/return geometry, and only then frequency. Otherwise optimization can build a superb false-breakout detector whose greatest skill is recognizing yesterday's chart.
