Tool
S/R Event (breakout / bounce / retest TRIGGER)
interpretor.sr_event
Inputs
The S/R info bundle from market.sr_levels — the detected support and resistance levels with their touch counts, strength and lifecycle state.
Outputs
An interpreted S/R bundle: 'matched' (did the event fire), plus anchor_price and confidence SCALARs ready to wire into ORDER_EXIT.
The trigger node for support/resistance trading. It reads the info bundle from market.sr_levels and fires when a specific event happens at a level — a breakout, a bounce, or a retest that held — in the direction you want. It also projects a price anchor and a confidence value so a winning signal can flow straight into your order's stop or target.
How it works
Wire the sr_levels 'info' handle in, then choose the event and direction; the node fires 'matched' when that event occurs, optionally also requiring volume confirmation and meeting a lifecycle floor. It exposes anchor_price and confidence as SCALARs for ORDER_EXIT, and use it for the entry trigger rather than interpretor.sr_level which reports level state.
Modes
Event options
Fires when price pushes through a level and breaks it.
When to use: Momentum entries that buy a break of resistance or sell a break of support.
Fires when price rejects off a level and turns back away from it.
When to use: Reversal entries that fade a level — buy a bounce off support, sell a bounce off resistance.
Fires when price returns to a level it broke earlier and that broken level holds as new support or resistance.
When to use: Confirmation entries that wait for a broken level to be retested before committing.
Direction options
Only fire when the event resolves upward — a break up or a bounce that turns price higher.
When to use: Long-only S/R entries.
Only fire when the event resolves downward — a break down or a bounce that turns price lower.
When to use: Short-only S/R entries.
Fire on the event regardless of which way it resolves.
When to use: Symmetric setups that trade both sides of a level.
Require lifecycle options
Fire on the event at any maturity, including the rawest, repaint-prone state.
When to use: Only when you knowingly want the earliest possible signal and accept repaint risk.
Require the event to be fully formed (the move has finished) before firing.
When to use: A first guard against premature signals while still acting relatively early.
Require a confirmed, tradeable event — a completed breakout or a retest — the safe default.
When to use: The recommended floor for live trading; balances early entry against repaint safety.
Require the level to have been retested and held — the strictest, most confirmed maturity.
When to use: When you want maximum confirmation and accept fewer, later signals.
Configuration
Which S/R event to trigger on: breakout (price pushes through a level), bounce (price rejects off a level), or retest_held (price returns to a broken level and it holds).
The required direction of the event: up, down, or any.
When on, also requires the event to be backed by volume (degrades gracefully on forex tick-volume).
The minimum maturity the event must reach before it fires: any, completed, tradeable, or retested; this is the guard against premature, repaint-prone signals.
Off fires on the event bar itself; on fires on the bars after the event instead.
Connects to
Examples
- Set event to breakout and direction to up as the entry trigger for a long when price breaks resistance.
- Wire the projected anchor_price into ORDER_EXIT to place a stop just past the level the bounce occurred at.
Common mistakes
- Confusing this with interpretor.sr_level — this node triggers on an event happening, not on a level simply existing.
- Turning on require_volume_confirmed for forex, where tick-volume is unreliable, and wondering why signals rarely fire.