Note on the 15m question: the original lesson description mentioned pulling Monday ranges on a 15-minute chart. When the actual Pine Script indicator code was checked, it uses request.security(syminfo.tickerid, "30", ...) — 30-minute bars — for all Monday body high/low tracking. The 15m reference in the lesson was either an approximation or an earlier version of the indicator. The backtester matches the actual indicator source, so 30m is correct.

1× = 12 pips beyond Asia high/low — one full session range extended
2× = 24 pips — two full ranges
3× = 36 pips — three full ranges, and so on

Replaces the old min/max fib filter — proximity to price is a more structurally sound filter than which fib multiple a confluence happens to fall at.

Re-entry mechanics: after a trade exits (TP, SL, BE-stop, or EOD), the level is marked as "not cleared." A re-entry only fires once price has moved at least 0.5× ATR away from the level — confirming it genuinely left the zone. The direction check still applies on re-entry, so price must approach from the correct side. The trade log shows a # column — 1 = first entry, 2 = re-entry, highlighted in orange so you can filter re-entry performance separately.

Important: the engine also applies a cap — if the range is very small, confluence distance is capped at 50% of the minimum fib gap to prevent adjacent levels from falsely merging. This matches the indicator's exact logic.

The indicator uses 10% as its visual default because on screen you want to highlight only the very sharpest alignments. For backtesting, 50% is more useful — it gives enough tight signals to measure performance meaningfully.

The equity curve and P&L figures in the results are illustrative — they show the shape of performance but the actual account impact depends on your real position sizing.

High vol: BE at 2.0R — market is moving freely, give it room before locking in
Med vol: BE at 1.5R — standard conditions
Low vol: BE at 1.0R — compressed market, protect profit sooner as extensions are harder to sustain

Daily %: tightest switch — fires most often, protects against a bad single day
Weekly %: catches runs of bad days that individually stayed under the daily limit
Monthly %: hardest stop — once hit, no more trades for the rest of the calendar month

Step 1 — Hit detection: for each fib extension level, every 5m bar in the entry window (07:15–20:00 London) is scanned. A level is hit when a bar's wick crosses the fib price — bar high for short setups, bar low for long setups. If price never reaches the level that day, no trade is recorded.

Step 2 — Outcome walk: from the touching bar, the engine walks forward bar by bar checking SL and TP against real highs and lows. Break-even fires once price reaches beR × SL distance, moving the stop to entry + 1 pip. Exit is at SL, TP, BE-stop, or 22:00 London EOD — whichever comes first.

Step 3 — Exit types: TP (full target hit), SL (stopped out before BE), BE (moved to breakeven then stopped), EOD (open at session close). These appear in the trade log and fib breakdown table.

This is the correct simulation of real trading — you would not open a second position while managing the first. The single-trade lock means oscillation trades within a ranging session are not captured, but it prevents the unrealistic stacking of losses that would occur with multiple simultaneous positions.

The TP always targets a confluence level — not just any SD level. If no confluence exists beyond the entry in the trade direction, the fallback ATR multiple is used instead (shown as ATR in the trade log TP basis column).

Example: Short from SD2.50, TP at SD-1.50 + 5 pip buffer. When TP fires, the engine immediately makes SD-1.50 available as a long entry. If the next 5m bar touches SD-1.50, a long fires — going the other direction back toward the sell zone above. This is the chain-trading behaviour where each confluence level acts as both the TP for the current trade and the entry for the next.

The # column in the trade log shows entry number per level per day — 1 = first entry, 2+ = re-entry, highlighted in orange. Compare first-entry vs re-entry win rates to see whether re-entries add or subtract edge.

Ext only preset — ticks SD≥1.50 and SD≤−1.00, the pure extension zones outside the Asia range. These are the levels where price has genuinely overextended and exhaustion is most likely.

Inside-range levels (SD0.25, SD0.50, SD0.75) — tradeable on ranging days where price oscillates within the Asia session without breaking out. Direction is context-dependent: the bar's open relative to the level determines whether it's a short or long approach.

The SD leaderboard at the bottom of results shows win%, net pip, and P&L per SD level — use it to identify which specific levels are profitable and untick the losers.

① Bar deceleration — the last N bars before the touch are getting progressively smaller. Price arriving at a sell level on shrinking bars suggests momentum is fading, increasing the probability of a reversal. Score +1 if true.

② Wick rejection — the wick that touched the level is ≥ X% of the full bar range. A large rejection wick (e.g. upper wick = 40% of bar range at a sell level) is the most direct price action signal that the level pushed back. Score +1 if true.

③ Rate of change — price moved ≥ X × ATR in the last N bars before the touch. Confirms the move into the level was meaningful — not a slow drift but a real push. Score +1 if true.