Page 1 of 2
Continuation only after a higher-low reclaim — my simple filter
Posted: Thu Sep 17, 2026 3:06 am
by LondonScalper
Continuation entries got cleaner when I demanded a
higher-low reclaim (or lower-high in a down move) after the impulse.
No reclaim of that micro higher-low means no continuation click, even if the breakout chatter is loud. The reclaim shows the pullback was bought or sold, not just a pause before failure. Invalidation is loss of that higher-low — clean and boring.
Rule is intentionally simple so I cannot decorate it mid-trade with extra confluence theatre. I define the higher-low on M5 for bias and may execute on M1, but I will not invent an M1 higher-low that M5 does not recognise.
This filter alone cut a surprising number of "continuation" losers that were really early fades of strength.
If the higher-low is only visible after heavy zoom and storytelling, it does not count for this filter.
- Do you require a higher-low or lower-high reclaim before continuation?
- On which timeframe do you define it for scalps — M1 or M5?
Simple filters survive mornings better than elaborate ones.
Re: Continuation only after a higher-low reclaim — my simple filter
Posted: Sun Sep 27, 2026 6:13 pm
by PropScalpDesk
M5 for the structure, same as you. The detail I had to pin down was what "reclaim" means as a trigger, because I was using it loosely. My version: the pullback prints a higher low, then an M1 candle closes above the small lower high that the pullback itself made. The close matters; a wick through it doesn't count.
The awkward part is the stop. Below an M5 higher low on GBPUSD can easily be 8 to 12 pips, so the position ends up small and the target needs to be at least the previous impulse high to be worth it. If the previous high is closer than 1.5 times the stop, I skip even with a clean reclaim. That rule removed more trades than the reclaim filter did.
Re: Continuation only after a higher-low reclaim — my simple filter
Posted: Sun Sep 27, 2026 6:45 pm
by PTScalper
LondonScalper wrote: Thu Sep 17, 2026 3:06 am
Continuation entries got cleaner when I demanded a
higher-low reclaim (or lower-high in a down move) after the impulse.
No reclaim of that micro higher-low means no continuation click, even if the breakout chatter is loud. The reclaim shows the pullback was bought or sold, not just a pause before failure. Invalidation is loss of that higher-low — clean and boring.
Rule is intentionally simple so I cannot decorate it mid-trade with extra confluence theatre. I define the higher-low on M5 for bias and may execute on M1, but I will not invent an M1 higher-low that M5 does not recognise.
This filter alone cut a surprising number of "continuation" losers that were really early fades of strength.
If the higher-low is only visible after heavy zoom and storytelling, it does not count for this filter.
- Do you require a higher-low or lower-high reclaim before continuation?
- On which timeframe do you define it for scalps — M1 or M5?
Simple filters survive mornings better than elaborate ones.
Hi LondonScalper,
I absolutely require a structural reclaim before a continuation entry, but my timeframe combination is zoomed out a bit further than the M1/M5 noise to filter out that exact temptation for "storytelling."
For my strategy, the "whole picture" and overarching bias are defined strictly on the medium-term charts—specifically the H4 or D1. That higher timeframe gives me the indisputable directional narrative based entirely on raw price action.
I then drop down to the M15 for execution. I look for that clean higher-low (or lower-high in a downtrend) reclaim specifically on the 15-minute chart, fully aligned with the H4/D1 bias.
If the daily chart is bullish, I need to see an M15 pullback that visibly gets bought, establishing a clean, structural higher-low before I enter. If the M15 doesn't confirm the reclaim with clear candlestick structure, the trade doesn't happen—no matter how loud the breakout chatter might be on a 1-minute or 5-minute chart.
Relying on raw M15 structure keeps the invalidation level clean and boring. It completely removes the need to heavily zoom into micro-timeframes to invent a setup that isn't really there. As you said, simple, unforced filters definitely survive the mornings best.
Re: Continuation only after a higher-low reclaim — my simple filter
Posted: Sun Sep 27, 2026 6:51 pm
by PTScalper
Here is a clean, non-repainting Pine Script (v5) designed specifically around your raw price action logic.
Since you code in C# and MQL, you know that translating visual price action into strict programmatic rules requires defining exactly when a pullback is considered "bought."
In this script, here is how your rules are translated into code:
The HTF Bias (H4/D1): We pull a higher timeframe filter using a simple EMA. While you trade raw PA, using an HTF EMA programmatically is the most robust way to gauge the "whole picture" trend in Pine without repainting issues.
The M15 Structure (Higher Lows): We use a strict leftBars and rightBars pivot definition. A Higher Low is only valid if the current pivot low is strictly greater than the previous one.
The Reclaim (The Trigger): The script doesn't just buy because a Higher Low formed. It waits for the pivot to be confirmed (rightBars later), takes the high of that confirmation candle as the "reclaim level," and requires price to close above it. No reclaim = no continuation click.
Invalidation: The Stop Loss is automatically calculated just below that newly established Higher Low—clean and boring.
Re: Continuation only after a higher-low reclaim — my simple filter
Posted: Sun Sep 27, 2026 6:51 pm
by PTScalper
The Pine Script (v5)
Code: Select all
//@version=5
strategy("M15/H4 Structural Reclaim [PA Scalp]", overlay=true, initial_capital=1000, default_qty_type=strategy.percent_of_equity, default_qty_value=2)
// =========================================================================
// 1. INPUTS
// =========================================================================
grp1 = "Timeframe Settings"
htf = input.timeframe("240", title="Higher Timeframe (e.g., 240 for H4, D for D1)", group=grp1)
grp2 = "Price Action Structure (M15)"
leftBars = input.int(5, title="Pivot Left Bars (Impulse)", minval=1, group=grp2)
rightBars = input.int(3, title="Pivot Right Bars (Pullback Bought)", minval=1, group=grp2)
rr_ratio = input.float(2.0, title="Risk/Reward Ratio", step=0.5, group=grp2)
// =========================================================================
// 2. HIGHER TIMEFRAME BIAS (The "Whole Picture")
// =========================================================================
// Using a 20 EMA on the HTF as a reliable programmatic proxy for trend direction
htf_ema = ta.ema(close, 20)
htf_trend_filter = request.security(syminfo.tickerid, htf, htf_ema, lookahead=barmerge.lookahead_off)
htf_bullish = close > htf_trend_filter
htf_bearish = close < htf_trend_filter
// =========================================================================
// 3. M15 STRUCTURE (Defining Higher-Lows & Lower-Highs)
// =========================================================================
pl = ta.pivotlow(low, leftBars, rightBars)
ph = ta.pivothigh(high, leftBars, rightBars)
var float last_pl = na
var float prev_pl = na
var float last_ph = na
var float prev_ph = na
var float hl_reclaim_level = na
var float lh_reclaim_level = na
var bool waiting_for_long_reclaim = false
var bool waiting_for_short_reclaim = false
// Detect Higher Lows (Uptrend Continuation)
if not na(pl)
prev_pl := last_pl
last_pl := pl
// Valid Higher Low aligned with HTF bias
if last_pl > prev_pl and htf_bullish
// The Reclaim Level is the HIGH of the candle that confirmed the pivot
// This ensures the pullback is actually bought before we click
hl_reclaim_level := high
waiting_for_long_reclaim := true
waiting_for_short_reclaim := false
// Detect Lower Highs (Downtrend Continuation)
if not na(ph)
prev_ph := last_ph
last_ph := ph
// Valid Lower High aligned with HTF bias
if last_ph < prev_ph and htf_bearish
// The Reclaim Level is the LOW of the candle that confirmed the pivot
lh_reclaim_level := low
waiting_for_short_reclaim := true
waiting_for_long_reclaim := false
// =========================================================================
// 4. THE RECLAIM (Execution Logic)
// =========================================================================
// Reclaim triggered when price closes structurally past the confirmation barrier
long_reclaim = waiting_for_long_reclaim and close > hl_reclaim_level
if long_reclaim
waiting_for_long_reclaim := false // Reset state after trigger
short_reclaim = waiting_for_short_reclaim and close < lh_reclaim_level
if short_reclaim
waiting_for_short_reclaim := false // Reset state after trigger
// =========================================================================
// 5. VISUALS & PLOTS
// =========================================================================
// Show HTF bias as a colored line
plot(htf_trend_filter, color=htf_bullish ? color.new(color.teal, 0) : color.new(color.red, 0), linewidth=2, title="HTF Bias Proxy")
// Plot the established Higher Lows / Lower Highs exactly where they formed
plotshape(not na(pl) and last_pl > prev_pl ? pl : na, style=shape.circle, color=color.teal, location=location.absolute, offset=-rightBars, size=size.tiny, title="Higher Low")
plotshape(not na(ph) and last_ph < prev_ph ? ph : na, style=shape.circle, color=color.red, location=location.absolute, offset=-rightBars, size=size.tiny, title="Lower High")
// Mark the Reclaim Execution Entry Points
plotshape(long_reclaim, title="Long Reclaim Entry", text="RECLAIM", style=shape.triangleup, location=location.belowbar, color=color.teal, size=size.small)
plotshape(short_reclaim, title="Short Reclaim Entry", text="RECLAIM", style=shape.triangledown, location=location.abovebar, color=color.red, size=size.small)
// =========================================================================
// 6. STRATEGY ORDERS & INVALIDATION (Clean and Boring)
// =========================================================================
if long_reclaim
// Invalidation is the exact Higher Low that was just established
sl = last_pl
tp = close + ((close - sl) * rr_ratio)
strategy.entry("Long", strategy.long)
strategy.exit("Exit Long", "Long", stop=sl, limit=tp)
if short_reclaim
// Invalidation is the exact Lower High that was just established
sl = last_ph
tp = close - ((last_ph - close) * rr_ratio)
strategy.entry("Short", strategy.short)
strategy.exit("Exit Short", "Short", stop=sl, limit=tp)
Re: Continuation only after a higher-low reclaim — my simple filter
Posted: Sun Sep 27, 2026 6:52 pm
by PTScalper
How to tune it for your exact eye:
The rightBars input is crucial for your reclaim logic. By default, it's set to 3. This means the script waits for 3 candles to print after the absolute low of the pullback. If those 3 candles stay above the low, the pullback is formally recognized. The "Reclaim level" is then set at the high of that 3rd candle. You can tighten this to 2 if you want a more aggressive structural break, or widen it to 4 if you want a deeper confirmation that the pullback is finished.
No Storytelling Allowed: If the HTF isn't aligned, or the M15 last_pl isn't strictly higher than prev_pl, the reclaim barrier is never set. The script ignores the noise entirely.
Re: Continuation only after a higher-low reclaim — my simple filter
Posted: Sun Sep 27, 2026 6:53 pm
by PTScalper
Since you are a C# software engineer and algorithmic trader, we need to move past the basic retail Pine Script skeleton and build this like a proper state machine.
A "pro" trading algorithm needs robust state management (cancelling invalid setups), dynamic memory allocation for visuals (drawing and garbage-collecting lines), fixed-fractional risk management (sizing based on the exact distance to invalidation), and session filters (keeping you out of the Asian session chop).
Here is the professional-grade implementation.
The "Pro" Upgrades:
Strict Setup Invalidation: If price prints a Higher Low, but then sweeps that low before the reclaim level is breached, the setup is instantly killed. It won't hold onto stale biases.
Dynamic Visual State: It uses line.new() to draw the exact Reclaim Trigger (dashed green/red) and Invalidation Level (solid gray). These lines extend dynamically with price and delete themselves once the setup executes or fails, keeping your chart perfectly clean.
Fixed Fractional Risk Sizing: Instead of a lazy % of equity, it calculates the exact lot size based on a strict Risk % per trade divided by the distance to the invalidation level.
Session Constraints: Allows you to isolate execution to high-liquidity sessions (e.g., London/NY).
Re: Continuation only after a higher-low reclaim — my simple filter
Posted: Sun Sep 27, 2026 6:53 pm
by PTScalper
The Pine Script (v5)
Code: Select all
//@version=5
strategy("Pro Structural Reclaim [PA Scalp]", overlay=true, initial_capital=10000, currency=currency.USD, commission_type=strategy.commission.cash_per_order, commission_value=3)
// =========================================================================
// 1. INPUTS & CONFIGURATION
// =========================================================================
grp1 = "1. Risk & Trade Management"
riskPct = input.float(1.0, title="Risk per Trade (%)", step=0.1, group=grp1)
rrRatio = input.float(2.0, title="Risk/Reward Target", step=0.5, group=grp1)
grp2 = "2. Session Filter"
useSession = input.bool(true, title="Use Session Filter?", group=grp2)
tradeSession = input.session("0800-1700", title="Trading Session (e.g. London/NY)", group=grp2)
inSession = not useSession or not na(time(timeframe.period, tradeSession))
grp3 = "3. Price Action Microstructure (M15)"
leftBars = input.int(5, title="Pivot Left (Impulse Leg)", minval=1, group=grp3)
rightBars = input.int(2, title="Pivot Right (Confirmation)", minval=1, tooltip="Tighter = earlier reclaim detection. 2 or 3 is optimal.", group=grp3)
grp4 = "4. Higher Timeframe Bias (H4/D1)"
htfRes = input.timeframe("240", title="HTF Resolution", group=grp4)
// =========================================================================
// 2. HIGHER TIMEFRAME BIAS
// =========================================================================
// We calculate the HTF EMA and pull it down without lookahead bias
htfEma = ta.ema(close, 20)
htfBiasFilter = request.security(syminfo.tickerid, htfRes, htfEma, lookahead=barmerge.lookahead_off)
isBullishHTF = close > htfBiasFilter
isBearishHTF = close < htfBiasFilter
// =========================================================================
// 3. STATE MACHINE & MICROSTRUCTURE DETECTION
// =========================================================================
// Detect standard pivots
pl = ta.pivotlow(low, leftBars, rightBars)
ph = ta.pivothigh(high, leftBars, rightBars)
// State variables for tracking the PA setup
var float lastPL = na
var float prevPL = na
var float lastPH = na
var float prevPH = na
var bool isLongSetupActive = false
var bool isShortSetupActive = false
var float triggerLevel = na
var float invalidationLevel = na
// Visual state pointers (for garbage collection)
var line triggerLine = na
var line slLine = na
// --- LONG SETUP LOGIC (Higher Lows) ---
if not na(pl)
prevPL := lastPL
lastPL := pl
// Condition: Clean Higher Low + Bullish HTF Context
if lastPL > prevPL and isBullishHTF
isLongSetupActive := true
isShortSetupActive := false
invalidationLevel := lastPL
// The trigger is the highest point reached during the 'rightBars' confirmation period
triggerLevel := ta.highest(high, rightBars)
// Clean up old visuals
if not na(triggerLine)
line.delete(triggerLine)
if not na(slLine)
line.delete(slLine)
// Draw new active setup levels
triggerLine := line.new(bar_index, triggerLevel, bar_index + 1, triggerLevel, color=color.new(color.teal, 0), style=line.style_dashed, width=2)
slLine := line.new(bar_index, invalidationLevel, bar_index + 1, invalidationLevel, color=color.new(color.gray, 0), style=line.style_solid, width=1)
// --- SHORT SETUP LOGIC (Lower Highs) ---
if not na(ph)
prevPH := lastPH
lastPH := ph
// Condition: Clean Lower High + Bearish HTF Context
if lastPH < prevPH and isBearishHTF
isShortSetupActive := true
isLongSetupActive := false
invalidationLevel := lastPH
// The trigger is the lowest point reached during the 'rightBars' confirmation period
triggerLevel := ta.lowest(low, rightBars)
// Clean up old visuals
if not na(triggerLine)
line.delete(triggerLine)
if not na(slLine)
line.delete(slLine)
// Draw new active setup levels
triggerLine := line.new(bar_index, triggerLevel, bar_index + 1, triggerLevel, color=color.new(color.red, 0), style=line.style_dashed, width=2)
slLine := line.new(bar_index, invalidationLevel, bar_index + 1, invalidationLevel, color=color.new(color.gray, 0), style=line.style_solid, width=1)
// =========================================================================
// 4. DYNAMIC VISUAL EXTENSIONS & SETUP CANCELLATION
// =========================================================================
// Extend lines dynamically if a setup is active
if isLongSetupActive or isShortSetupActive
line.set_x2(triggerLine, bar_index + 1)
line.set_x2(slLine, bar_index + 1)
// KILL SWITCH: Void the setup if invalidation is hit BEFORE the reclaim
if isLongSetupActive and low <= invalidationLevel
isLongSetupActive := false
line.set_color(triggerLine, color.new(color.gray, 70)) // Fade out voided setup
if isShortSetupActive and high >= invalidationLevel
isShortSetupActive := false
line.set_color(triggerLine, color.new(color.gray, 70)) // Fade out voided setup
// =========================================================================
// 5. EXECUTION & RISK SIZING
// =========================================================================
// Calculate Position Size based on absolute distance to stop loss
getQty(slPrice) =>
riskAmount = strategy.equity * (riskPct / 100)
distanceToSL = math.abs(close - slPrice)
qty = distanceToSL > 0 ? (riskAmount / distanceToSL) : 0
qty
// Execute Reclaims
triggerLongReclaim = isLongSetupActive and close > triggerLevel and inSession and strategy.position_size == 0
if triggerLongReclaim
qty = getQty(invalidationLevel)
tpPrice = close + ((close - invalidationLevel) * rrRatio)
strategy.entry("Long", strategy.long, qty=qty)
strategy.exit("Exit Long", "Long", stop=invalidationLevel, limit=tpPrice)
// Clear state after execution
isLongSetupActive := false
line.set_style(triggerLine, line.style_solid) // Solidify line on execution
triggerShortReclaim = isShortSetupActive and close < triggerLevel and inSession and strategy.position_size == 0
if triggerShortReclaim
qty = getQty(invalidationLevel)
tpPrice = close - ((invalidationLevel - close) * rrRatio)
strategy.entry("Short", strategy.short, qty=qty)
strategy.exit("Exit Short", "Short", stop=invalidationLevel, limit=tpPrice)
// Clear state after execution
isShortSetupActive := false
line.set_style(triggerLine, line.style_solid) // Solidify line on execution
// =========================================================================
// 6. CHART CONTEXT
// =========================================================================
plot(htfBiasFilter, color=isBullishHTF ? color.new(color.teal, 50) : color.new(color.red, 50), linewidth=2, title="HTF Bias")
bgcolor(inSession ? na : color.new(color.gray, 95), title="Out of Session Dimming")
Re: Continuation only after a higher-low reclaim — my simple filter
Posted: Sun Sep 27, 2026 6:54 pm
by PTScalper
Why this architecture scales:
The "Kill Switch": Lines 96-103. In the previous script, if price formed a higher low, went lower (breaking the low), and then violently shot up through the old reclaim level, the script would still buy. This pro version actively invalidates the setup if the low is swept before execution. Stale data is discarded.
Microstructure Accuracy (triggerLevel): Instead of just using the confirmation candle, ta.highest(high, rightBars) strictly identifies the micro-peak of the structural formation. This means the reclaim requires breaking actual local structure, not just a random candle high.
Garbage Collection (Visuals): It deletes previous pivot lines as soon as a new one forms, and fades out lines of invalidated setups. Your chart won't look like a laser tag arena after a few hours of trading.
Dynamic Sizing (getQty()): The exact distance from your entry to the invalidationLevel is calculated tick-for-tick to size your lot so you strictly lose exactly riskPct if stopped out.
Re: Continuation only after a higher-low reclaim — my simple filter
Posted: Sun Sep 27, 2026 6:55 pm
by PTScalper
Here is the direct C# cAlgo implementation for cTrader.
This port leverages cTrader’s MarketData.GetBars() for the multi-timeframe proxy without lookahead bias and uses a lightweight state machine to track the structural setups tick-by-tick or bar-by-bar.