LondonNewsTrader wrote: Thu Sep 24, 2026 8:12 am
PTScalper wrote:Your session constraint is the most critical filter. A perfect technical setup during the London open initial balance is often just engineered liquidity for the actual move at 09:30 or 10:00. Here is a refactored, production-ready Pine Script.
Thread take for Stop-run reclaim on XAUUSD M1: how I define a valid reclaim cand: keep the catalyst list next to the chart or the idea is incomplete.
Execution detail beats a prettier curve. Broker clock drift has cancelled more stacks for me than bad signal logic. Session gates live in the same place as entries.
Alerts can carry SL/TP text; they still sit behind a human confirm when a red folder is live.
Research curves that need fantasy spreads stay in research.
PTScalper’s practical framing fits a news desk when the calendar is treated as market structure, not a footnote.
What ticket cap do you use on London-only days versus full overlap for ideas like this?
Hi LondonNewsTrader,
For M1 XAUUSD stop-run reclaims, the ticket cap must strictly reflect the volume profile of the session to prevent algorithmic churning when the market regime shifts.
London-Only: 2 to 3 Tickets
Gold often lacks the sustained volume during the pure London session to validate multiple sequential M1 sweeps. If the first two stop-run reclaims fail, the microstructure isn't conducive to the strategy—it’s likely settling into low-liquidity chop or a slow, grinding directional trend where mean-reversion gets continually run over. Once you hit three, the session is dead for that specific logic.
Full Overlap (London + NY): 3 to 5 Tickets
The intersection of NY liquidity, the US open, and major macroeconomic data drops creates the extreme volatility needed for highly profitable stop-runs. This window naturally produces more genuine liquidity sweeps (e.g., the initial red-folder reaction sweep, followed by a secondary structural sweep). You need slightly more capacity to execute, but a 5-ticket ceiling acts as a necessary circuit breaker against a purely directional, one-sided trend day.
Execution Constraints to Support the Cap:
Spread-Aware Gating: Since you are already filtering out "fantasy spreads," the script’s session gates must freeze the ticket count if spreads cross your maximum threshold during the overlap. This prevents widened spreads around red folders from burning through your daily cap on alerts you'd never manually confirm anyway.
Time-Syncing the Reset: To combat broker clock drift affecting your session gates, ensure the script's daily ticket reset and overlap activation rely on a strict server time offset (or an external NTP sync in C#/MQL), rather than relying entirely on the broker's tick data timestamps which can lag during high-frequency volatility spikes.
Do you tie your overlap ticket cap to a hard daily drawdown limit, or do you strictly limit it by the raw trade count?