PROPBREAKER SYSTEM · Multi-Timeframe Confluence · System 09

PB-CONFLUENCE MTF

Independently interpreted, formalized, coded and tested by PROPBREAKER.A US30 multi-timeframe confluence system combining D1/H4 direction, H1 structure, M30 confirmation, and configurable level or PDH/PDL-reclaim entries.
CONCEPT REFERENCECue BanksIndependent implementation — No affiliation or endorsement.
IndicesCFDIntraday
CONCEPT REFERENCE / Cue BanksNOT AFFILIATED / NOT ENDORSED
PROPBREAKER SYSTEMVERIFIED MODEL VIEW
US30 · D1/H4/H1/M30 · M1 executionPB-CONFLUENCE MTF
PROPBREAKER CODE
SETUPD1/H4 bias + H1 S/R/Fib zoneTRIGGERM30 confirmation + execution breakSLStructural stop · 1% equityTP2R / next HTF or Fib level
PLATFORM TARGETSBuilds in development
TradingView logoTradingViewPine strategy
MetaTrader 5 logoMetaTrader 5MT5 bot
NinjaTrader 8 logoNinjaTrader 8NT8 bot
01 / How it works

Strategy rules.
Complete execution model.

The PROPBREAKER implementation runs on the Capital.com US30 index CFD and turns Cue Banks' public multi-timeframe confluence framework into two configurable setup families. Confluence Auto aligns D1 and H4 direction with H1 market structure, support/resistance and Fibonacci location, then requires a lower-timeframe confirmation before execution. Magnet PDH/PDL instead monitors sweeps and reclaims of the previous day's candle-body extremes, with optional moving-average and New York-session filters. The backtest uses one-minute execution, variable equity-risk sizing, structural protection, break-even management and configurable fixed-R or higher-timeframe objectives.

MODEL MAP / CONFLUENCE MTFUS30 HTF + Fibonacci confluence → confirmed executionReference visual: X-A-B-C-D + MA cross · code: D1/H4 direction · H1 S/R and Fib · M30 confirmation · M1 execution
01Map HTF direction and the impulseAlign D1 and H4 direction, then use the H1 impulse and market structure to map support, resistance and the 38.2–88.6% Fibonacci locations.
02Wait inside the confluence zoneThe supplied CueBanks reference adds the X-A-B-C-D harmonic map and daily moving-average cross. In code, the trade zone is qualified by H1 S/R, Fibonacci location and the selected confluence score.
03Confirm, execute and manageRequire the configured M30 confirmation before execution. Protect beyond structure, risk 1% of equity, move to break-even at 1R and use fixed 2R, Fibonacci expansion or the next HTF level.

Representative rule map · entry, invalidation and objective—not a historical trade.

COMPLETE TECHNICAL PLAYBOOK

CONFLUENCE MTF

The PROPBREAKER implementation runs on the Capital.com US30 index CFD and turns Cue Banks' public multi-timeframe confluence framework into two configurable setup families. Confluence Auto aligns D1 and H4 direction with H1 market structure, support/resistance and Fibonacci location, then requires a lower-timeframe confirmation before execution. Magnet PDH/PDL instead monitors sweeps and reclaims of the previous day's candle-body extremes, with optional moving-average and New York-session filters. The backtest uses one-minute execution, variable equity-risk sizing, structural protection, break-even management and configurable fixed-R or higher-timeframe objectives.

01

Operating context

  • Market and model: Dow Jones 30 Index CFD (US30), Multi-Timeframe Confluence family.
  • Operating timeframe: D1/H4 direction · H1 setup · M30 confirm · M1 execution.
  • Execution window: Multi-session · New York rules available.
  • Apply the rules in sequence; one missing condition cancels the signal.
02

Pre-trade checklist

  • Confirm the full operating context before looking for an entry: D1/H4 direction · H1 setup · M30 confirm · M1 execution.
  • Map the complete trigger without anticipation: Confluence score or PDH/PDL sweep-reclaim with bullish confirmation.
  • Calculate size, invalidation and maximum loss before the order: 1% equity risk · structural stop · daily loss guard.
03

Entry protocol

  • Execute only after the complete trigger is printed: Confluence score or PDH/PDL sweep-reclaim with bullish confirmation.
  • Record the level, timestamp and condition that activated the order; never turn a missed order into a chase.
04

Invalidation

  • Define the invalidation before submitting the order: 1% equity risk · structural stop · daily loss guard.
  • Exit when invalidated: do not average down and do not widen the stop.
05

Position management

  • Manage the open position exactly as specified: Fixed 2R / next HTF level · break-even management.
  • Coded exit model: Fixed 2R / next HTF level · break-even management.
  • Discretionary changes are allowed only when defined in the preset before entry.
06

When not to trade

  • Skip incomplete signals, late entries and any setup that cannot preserve the documented risk model.
  • Skip the setup when spread, slippage, volatility or liquidity make the calculated risk unreliable.
  • Do not treat historical results as a guarantee of future performance.
Mandatory sequenceContext → setup → trigger → risk → management → exit
Reference & independenceRead details +

This is an independent PROPBREAKER implementation inspired by concepts presented on Cue Banks's official YouTube channel. PROPBREAKER interpreted, coded and tested the rules shown here.

The referenced trader did not develop, review or approve this software and is not affiliated with PROPBREAKER. The coded model may differ from the trader's own methodology.

Official YouTube sourceView channel +

The public strategy reference is exclusively the trader's official YouTube channel.

02 / REVIEW THE RESULTS

Backtest.
Stress test.
Prop test.

Follow the tabs in order. Start with the historical result, check whether it survives weaker trade sequences, then apply the rules of your prop account.

PROPBREAKER SIMULATIONResults shown are generated exclusively by PROPBREAKER's independent coded implementation. They are not results achieved, reported or endorsed by the referenced trader.
HISTORICAL BACKTEST · JAN 12–AUG 14, 2026

PB-CONFLUENCE MTF

US30 · D1/H4 direction · H1 setup · M30 confirm · M1 execution · Multi-session · New York rules available

PROPBREAKER SIMULATION · NET P&L+$7,334.70
TRADINGVIEW TRADE LOGUS30 · Dow Jones 30 Index CFDTradingView · CAPITALCOM · Multi-session · New York rules available
Total P&L+$7,334.70
Return7.33%
Sharpe ratio0.83
Win rate27.21%
Max drawdown-$8,645.90 · 7.51%
Profit factor1.107

Equity curve · PROPBREAKER SIMULATION

IMPORTED CLOSED-TRADE LEDGER · TRADE BY TRADE
Execution equity and drawdown chart.
Jan 2026MarAprJunAug 2026
View detailed statistics +

Win/Loss details

Total trades136
Winning trades37
Losing trades68
Breakeven trades31
Average win$2,048.84
Average loss-$1,006.95
Largest win$2,251.60
Largest loss-$1,150.00

Risk details

Max consecutive wins3
Max consecutive losses5
Sortino ratio3.30
Recovery factor0.85
Average trade$53.93
Expectancy$53.93
Average favorable excursion$1,118.53
Average adverse excursion-$702.56
STRATEGY FAQ

Before you test the model.

01What is the PB-CONFLUENCE MTF strategy?

PB-CONFLUENCE MTF is PROPBREAKER's independent coded implementation inspired by concepts presented on Cue Banks's official YouTube channel. The trader is a concept reference only, is not affiliated with or endorsing PROPBREAKER, and did not develop or approve the software or its results.

02Which market and timeframe does this CONFLUENCE MTF model use?

The page models Dow Jones 30 Index CFD (US30) on D1/H4 direction · H1 setup · M30 confirm · M1 execution. The primary setup is confluence score or pdh/pdl sweep-reclaim with bullish confirmation, with 1% equity risk · structural stop · daily loss guard.

03How are the PB-CONFLUENCE MTF results tested?

The PROPBREAKER simulation is calculated from the imported US30 closed-trade ledger for JAN 12–AUG 14, 2026. Monte Carlo and prop-firm tools reuse that implementation's trade history; the results are not results achieved, reported or endorsed by Cue Banks and do not guarantee future performance.

04Which platforms support this CONFLUENCE MTF implementation?

The same coded decision model is designed for TradingView, MetaTrader 5 and NinjaTrader 8. Parameters can be changed, but every changed configuration should be backtested and stress-tested again before use.

Return to libraryExplore all strategies ↗