Support Resistance Price Action MT5

The level worked perfectly—especially if it was drawn after the move. Support Resistance Price Action turns a line, zone or trend line created now into an immutable market hypothesis, then measures everything price does afterward without fitting the geometry to a known result.

Draw a horizontal line, rectangle or trend line, select the object and press Track. From that moment, the indicator watches a specific version of the level—with an activation time, touch rules and a future outcome window—not an abstract idea of “support.”

A level becomes an experiment

• Prospective contract: events before activation do not count. Moving or editing an object creates a new hypothesis revision rather than rewriting old observations. Deletion or finite geometry ends its lifecycle correctly.
• Touch Engine separates live proximity, confirmed touch, gap-through and a new independent episode. Zone tolerance, minimum spacing and rearm distance prevent one price cluster from being counted ten times.
• Outcome Engine determines what happened first after contact: bounce or breakout. If both conditions occur in one candle and their intrabar order is unknowable, the result is marked ambiguous instead of assigned a convenient win.
• The complete post-event path: MFE, MAE and their R values, 0.5R/1R/2R targets, bars to bounce, breakout and retest, bars to next touch, plus incomplete observations at the right edge of history.
• Session-aware evidence separates closed outcomes into Asia, Europe, America and off-hours. Cluster bootstrap produces a confidence interval, while small samples are explicitly flagged.

Lifecycle instead of an alarm on every tick

Zero-Noise State Engine moves a level through Watching → Approaching → Touched → Awaiting Confirmation → Bounced / Broken → Retesting → Completed, Expired or Invalidated. Same-bar deduplication, cooldown and event priorities stop one move from creating a queue of duplicate alerts.

A Playbook defines the observation: First Touch, Breakout and Retest, Support Bounce, Resistance Rejection, Liquidity Sweep or Custom. Each level can have direction, confirmation, maximum touches, targets, expiry, invalidation and notification policy while its evidence history remains separate from interface settings.

A research panel, not a label beside a line

Overview, Events, MFE/MAE, Targets, Timeline, Compare and Sessions expose sample size, bounce/breakout/retest rates, mean excursions, target hits, state sequence and differences between two levels. The embedded radar also sees eligible objects on other open charts and helps navigate to the relevant market.

Summary, events, session metrics and diagnostics can be exported to CSV from the panel. The ledger stores hypothesis versions and state transitions, restores the workspace after restart and never mixes prospective observations with retrospective ones.

The interface automatically uses one of 11 languages, scales, collapses into a slim side rail and refreshes live proximity separately from heavier historical recalculation.

First let the level live through its history

Run the demo in the visual Strategy Tester with Every tick based on real ticks. With Auto Demonstration enabled, the indicator creates sample levels, shows approach and touch, waits for the close and begins filling bounce, breakout, MFE and MAE evidence.

On a live chart, use your own objects and Track. Judge sample size, ambiguous/incomplete cases, confidence interval and session differences—not one attractive reaction.

A level is a hypothesis, not a pending order

Support Resistance Price Action is an indicator, not an Expert Advisor. It observes user-defined levels, builds evidence and sends alerts, but never opens, modifies or closes a trade.

Historical rates, MFE/MAE, targets and confidence intervals do not guarantee a future reaction or profit. Quotes, spread, gaps, liquidity, history quality, timeframe and broker conditions can change outcomes; execution and risk remain the trader's decision.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Settings: measure the rule, not your memory

• Touch zone — 1.0 pip/tick (0.25–10). Wider means more contacts. Forex uses a canonical pip; other markets use the native tick. First test: 0.5–2.0.
• Bars between touches — 3 (1–100) and Reset distance — 3.0 pips/ticks (0.5–50) separate independent episodes; increasing both reduces repeated events.
• Outcome window — 96 bars (8–500). Short captures fast reactions; long includes slower outcomes but leaves observations pending longer. Begin with 48–144.
• R unit — 10 pips/ticks (1–1000) scales MFE, MAE and targets. It is a measurement unit, not an automatically calculated stop size. Match it to instrument volatility before comparing levels.
• Bounce target — 0.50R (0.1–5.0): higher makes a successful bounce harder to achieve. First range: 0.25–1.0R.
• Breakout margin — 0.25 pip/tick (0–10) requires distance beyond the boundary. Confirm at candle close — true waits for the close; false permits intrabar High/Low confirmation and becomes more wick-sensitive.
• Panel scale — 1.25 (1.00–2.00, useful step 0.25) affects presentation only. Visual tester auto demonstration — true creates and follows sample support/resistance levels in a visual test.

Together these settings form one analysis contract. If R, horizon or breakout definition changes, compare the new revision separately; mixing different definitions of success is an excellent way to prove any conclusion you wanted in advance.