All-In-One Breakout EA Defined – Buying and selling Methods – 20 March 2025

Vary Filter Sort (RangeType)

• Off (RangeByOff): No filter utilized.
• Mounted Level (RangeByFixedPoint): Filter primarily based on a hard and fast level vary.
  Instance: MinRangePoint = 40, MaxRangePoint = 100 → Trades are solely taken if the field measurement is between 40 and 100 factors.
• ATR (RangeByATR): Filter primarily based on a proportion of ATR.
  Instance: ATR = 80 factors, MinRangeATR = 50, MaxRangeATR = 150 → Trades allowed if field measurement is between 40 and 120 factors (50%-150% of ATR).
• ADR (RangeByADR): Filter primarily based on a proportion of ADR.
  Instance: ADR = 120 factors, MinRangeADR = 20, MaxRangeADR = 80 → Field have to be between 24 and 96 factors.
• Worth (RangeByPrice): Filter primarily based on a proportion of worth.
  Instance: Worth = 1.3000, MinRangePrice = 0.05, MaxRangePrice = 0.1 → Allowed field measurement: 65 to 130 factors (0.05%-0.1% of worth).

3. Cancel Orders

These settings management when pending orders are cancelled, if not triggered by this time.

This defines the length after which pending orders are canceled, measured from the Field Finish Time (not from the Field Begin).

• Cancel Order Period (CancelOrdersHour, CancelOrdersMinute, CancelOrdersSecond): Period added to the Field Finish Time after which pending orders are canceled.
• Randomise Cancel Order (RandomCancelOrder): Allow or disable bounded randomization of cancel order time.
• Randomised Cancel Time (CancelOrderSecondDelta): Most seconds to randomize the cancel time.

Instance:

• RangeStartHour = 2, RangeStartMinute = 0
• RangeEndHour = 5, RangeEndMinute = 30
  → Field ends at 07:30
• CancelOrdersHour = 6, CancelOrdersMinute = 0
  → Cancel Time = 07:30 + 6:00 = 13:30
• If RandomCancelOrder = true, CancelOrderSecondDelta = 180
  → Cancel time might range between 13:27:00 and 13:33:00

4. Shut Positions

This defines the length after which positions are force-closed, measured from the Cancel Orders Time. That is helpful to keep away from holding trades past particular hours or market classes and shut earlier than the day ends.

• Shut Sort (CloseType):
• CloseByTime: Shut trades strictly on the shut time.
• ClosebyTP: Shut trades solely when take revenue is hit.
• CloseByTP_Time: Shut by both take revenue OR compelled shut time, whichever comes first.
• Shut Positions Period (ClosePositionsHour, ClosePositionsMinute, ClosePositionsSecond): Period after cancel time to shut open trades.
• Randomise Shut Time (RandomClosePosition): Allows/disables randomisation of place shut time.
• Shut Time Random Delta (ClosePositionSecondDelta): Max variety of seconds to randomly shift the shut time.

Instance:

• Field Finish = 07:30, CancelOrdersHour = 6:00 → Cancel time = 13:30
• ClosePositionsHour = 2, ClosePositionsMinute = 0 → Shut time = 13:30 + 2:00 = 15:30
• If RandomClosePosition = true, ClosePositionSecondDelta = 180 → Closing shut might occur between 15:27 and 15:33

5. Cease Loss

These settings outline how the cease loss (SL) is calculated for every commerce. You’ll be able to select from varied calculation strategies together with a hard and fast variety of factors, range-based elements, or dynamic volatility indicators like ATR and ADR.

Cease Loss Sort (SLType):

• Field Issue (SLByFactor): Cease loss is about as a a number of (issue) of the field measurement.
  Instance:

o   If field measurement = 100 factors, and SLFactor = 1.5 → SL = 100 × 1.5 = 150 factors

o   If field measurement = 100 factors, and SLFactor = 0.5 → SL = 100 × 0.5 = 150 factors, that is good to shut a commerce with smaller cease loss if a breakout is just not profitable.

• Mounted Level (SLByPoint): Cease loss is about as a hard and fast variety of factors.
  Instance: SLPoint = 80 → SL = 80 factors
• ATR-Primarily based (SLByATR): Cease loss is calculated as a proportion of the ATR worth.
  Instance: ATR = 50 factors, SLATR = 120 → SL = 50 × 1.2 = 60 factors
• ADR-Primarily based (SLByADR): Cease loss is calculated as a proportion of the ADR worth.
  Instance: ADR = 100 factors, SLADR = 70 → SL = 100 × 0.7 = 70 factors
• Worth Issue (SLByPrice): Cease loss is calculated as a percentage-based issue of the present worth.
  Instance: Worth = 1.10000, SLPrice = 0.1 → SL = 0.1% of worth = 1.10000 × 0.001 = 11 factors
• Off (SLOff): No cease loss will likely be utilized. That is extremely dangerous and never really helpful for many use instances.

Random Cease Loss Sort (RandomSL):

Randomization introduces managed variation to make your SL ranges much less predictable, which may also help in prop agency environments or scale back predictability by brokers.

• Random SL Off (RandomSLByOff): No randomization is utilized to cease loss.
• Random by Level (RandomSLByPoint): SL is randomized by various factors above or beneath the bottom SL.
  Instance: RandomSLPoint = 15 → Closing SL = Base SL ± random worth between -15 and +15 factors
• Random by Share (RandomSLByPC): SL is randomized by a proportion issue of the bottom SL.
  Examples:
• RandomSLPC = 5 → SL fluctuates inside ±5% vary of base SL
• RandomSLPC = 10 → ±10% vary
• RandomSLPC = 15 → ±15% vary
  If base SL = 100 factors and RandomSLPC = 10 → SL will range between 90 and 110 factors

6. Take Revenue

These settings management how the Take Revenue (TP) degree is calculated for every commerce. You’ll be able to outline TP primarily based on a hard and fast distance, or dynamically utilizing indicators like ATR, ADR, or present worth ranges. TP placement is essential for controlling reward-to-risk ratios and exit habits.

Take Revenue Sort (TPType):

• Cease Loss Issue (TPByFactor): TP is about as a a number of of the cease loss. That is the setting for conventional risk-to-reward ratio.
  Instance: If SL = 80 factors, and TPFactor = 2 → TP = 80 × 2 = 160 factors, a RRR of two.
• Mounted Level (TPByPoint): TP is about at a hard and fast variety of factors from the entry.
  Instance: TPPoint = 100 → TP = 100 factors
• ATR-Primarily based (TPByATR): TP is calculated as a proportion of the ATR worth.
  Instance: ATR = 60 factors, TPATR = 150 → TP = 60 × 1.5 = 90 factors
• ADR-Primarily based (TPByADR): TP is calculated as a proportion of the ADR worth.
  Instance: ADR = 120 factors, TPADR = 80 → TP = 120 × 0.8 = 96 factors
• Worth Issue (TPByPrice): TP relies on a proportion of the present market worth.
  Instance: Worth = 1.10000, TPPrice = 0.15 → TP = 1.10000 × 0.0015 = 16.5 factors
• Off (TPOff): No Take Revenue degree will likely be utilized. Trades can shut solely by cease loss or handbook intervention.

Random Take Revenue Sort (RandomTP):

To extend commerce robustness and scale back system predictability, TP ranges may be barely diversified round their calculated worth.

• Random TP Off (RandomTPByOff): No randomization is utilized to Take Revenue.
• Random by Level (RandomTPByPoint): Randomize TP degree by various factors.
  Instance: RandomTPPoint = 20 → TP = Base TP ± random quantity from -20 to +20 factors
• Random by Share (RandomTPByPC****): Randomize TP degree by a proportion of the bottom TP.
  Examples:
• RandomTPPC = 5 → TP varies inside ±5% of calculated worth
• RandomTPPC = 10 → ±10% vary
• RandomTPPC = 15 → ±15% vary
  If base TP = 100 factors and RandomTPPC = 10 → TP will range between 90 and 110 factors

7. Trailing Cease

This part defines how the EA adjusts the Cease Loss (SL) as the value strikes in your favor. Trailing Stops assist lock in earnings whereas holding positions open throughout beneficial developments. You’ll be able to select from completely different trailing strategies and optionally randomize them to scale back system predictability.

Trailing Cease Swap (Trailing_Stop_Switch)

• Allows or disables trailing cease performance.

Trailing Cease Sort (TSType)

• By Cease Loss Share (TSBySL): Trailing Cease is calculated as a proportion of the unique SL.
  Instance: If SL = 100 factors, TSSL = 33.33 → Trailing Cease = 33.33 factors
• Mounted Level (TSByFixedPoint): Trailing Cease is about to a hard and fast variety of factors.
  Instance: TSPoint = 333 → Trailing Cease = 333 factors
• ATR-Primarily based (TSByATR): Trailing Cease relies on a proportion of the ATR worth.
  Instance: ATR = 60 factors, TSATR = 5 → Trailing Cease = 60 × 0.05 = 3 factors
• ADR-Primarily based (TSByADR): Trailing Cease relies on a proportion of the ADR.
  Instance: ADR = 150 factors, TSADR = 1 → Trailing Cease = 150 × 0.01 = 1.5 factors
• Worth Share (TSByPrice): Trailing Cease is calculated as a proportion of the present worth.
  Instance: Worth = 1.20000, TSPrice = 0.1 → Trailing Cease = 1.20000 × 0.001 = 12 factors

Path Level Share (Path)

Defines how a lot of the calculated Trailing Cease is used because the set off to maneuver SL.
Instance:

• If TSPoint = 333 and Path = 50 → SL trails when worth strikes by 333 × 0.5 = 166.5 factors

Path Above Break-Even Swap (Trail_Above_Switch)

• Allows or disables extra management that triggers trailing solely when the value goes additional above breakeven.

Path Above Issue (Trail_Above)

• Defines how far the value should transfer past breakeven earlier than the trailing logic begins.
  Instance:
• Trail_Above = 0.25 and TSPoint = 333 → Path begins after 333 × 0.25 = 83.25 factors above breakeven

Random Trailing Cease Sort (RandomTS)

Randomization helps add variability to trailing cease ranges to scale back the possibility of system exploitation or overfitting.

• Random Off (RandomTSByOff): No random variation utilized to trailing cease.
• Random by Level (RandomTSByPoint): Provides or subtracts random factors from trailing cease.
  Instance: RandomTSPoint = 5 → Trailing Cease might range between ±5 factors
• Random by Share (RandomTSByPC): Applies random variation as a proportion.
  Examples:
• RandomTSPC = 5 → ±5% of base trailing cease
• RandomTSPC = 10 → ±10%
• RandomTSPC = 15 → ±15%

8. Trades

These settings management commerce habits.

Cancel Reverse Order (COO_Switch): Cancel reverse pending orders when a commerce is opened.

Purchase and/or Promote Trades (BorS):

• Purchase and Promote (BuyandSell): Permit each purchase and promote trades.
• Purchase Solely (BuyOnly): Permit solely purchase trades.
• Promote Solely (SellOnly): Permit solely promote trades.
• Purchase and Promote Off (BuyandSellOff): Disable buying and selling completely.

Max Lengthy Trades (MaxLongTrades):
Defines the utmost variety of purchase trades per day.
Instance: MaxLongTrades = 2 → Solely two purchase orders may be positioned per day.

Max Quick Trades (MaxShortTrades):
Defines the utmost variety of promote trades per day.
Instance: MaxShortTrades = 3 → As much as three promote orders may be positioned per day.

Max Whole Trades (MaxTotalTrades):
Defines the utmost complete variety of trades per day (purchase + promote).
Instance: MaxTotalTrades = 5 → A most of 5 trades (mixed purchase and promote) will likely be executed in a single day.

9. Day to Commerce

These settings management which days of the week the EA is allowed to position trades. You’ll be able to selectively allow or disable buying and selling for every day.

• Commerce Monday (TradeMonday):
  true – EA will open trades on Mondays.
  false – EA won’t open trades on Mondays.
• Commerce Tuesday (TradeTuesday):
  true – EA will open trades on Tuesdays.
  false – EA won’t open trades on Tuesdays.
• Commerce Wednesday (TradeWednesday):
  true – EA will open trades on Wednesdays.
  false – EA won’t open trades on Wednesdays.
• Commerce Thursday (TradeThursday):
  true – EA will open trades on Thursdays.
  false – EA won’t open trades on Thursdays.
• Commerce Friday (TradeFriday):
  true – EA will open trades on Fridays.
  false – EA won’t open trades on Fridays.
• Commerce Saturday (TradeSaturday):
  true – EA will open trades on Saturdays (not often used until buying and selling crypto).
  false – EA won’t open trades on Saturdays.
• Commerce Sunday (TradeSunday):
  true – EA will open trades on Sundays (not often used until buying and selling crypto).
  false – EA won’t open trades on Sundays.

10. Confluence

These settings add extra filters for commerce entry, enabling stronger affirmation primarily based on development and volatility confluence. Use of confluence on some devices, can enhance winrate and drawdown.

3 Shifting Averages Filter

• Allow 3 MA Filter (CMASwitch): Allow or disable utilizing three shifting averages for development affirmation.
• MA Timeframe (MAATF): Timeframe used for calculating the shifting averages (e.g., PERIOD_H1).
• MA Methodology (MAMethod): The tactic used for calculating the shifting common (e.g., SMA, EMA).
• Quick MA Interval (CMA1Period): Interval for the fast-paced common.
• Medium MA Interval (CMA2Period): Interval for the medium shifting common.
• Sluggish MA Interval (CMA3Period): Interval for the sluggish shifting common.

Instance: If CMA1 = 21, CMA2 = 50, CMA3 = 200, then:

• Entry allowed provided that: MA21 > MA50 > MA200 (uptrend), or MA21 < MA50 < MA200 (downtrend).

ADI (Common Directional Index) Filter

• Allow ADI Filter (CADISwitch): Allow or disable the ADI confluence filter.
• ADI Timeframe (CADITF): Timeframe used for calculating ADX.
• ADI Interval (CADIPeriod): Interval used for ADX calculation.
• ADX Threshold (CADIMainLevel): Minimal required ADX worth for development affirmation.
• Minimal DI+ / DI− Degree (CADILevel): Required minimal power of DI+ vs DI− for Purchase/Promote indicators. DI+ confirms Purchase and DI− confirms Promote.
• DI Issue (CADIDiff****): Minimal distinction between DI+ and DI− to substantiate directional development.

Logic:

• Purchase Sign = DI+ > DI− × CADIDiff AND DI+ > CADILevel AND ADX > CADIMainLevel
• Promote Sign = DI− > DI+ × CADIDiff AND DI− > CADILevel AND ADX > CADIMainLevel

Examples (assuming CADILevel = 40, CADIDiff = 3):

• DI+ = 46, DI− = 15, ADX = 42
  → This setup produces a Purchase sign as a result of:
  46 > 15×3 = 45, 46 > 40, and ADX = 42 > 30
• DI+ = 12, DI− = 43, ADX = 38
  → This setup produces a Promote sign as a result of:
  43 > 12×3 = 36, 43 > 40, and ADX = 38 > 30
• DI+ = 36, DI− = 11, ADX = 35
  → No entry sign as a result of:
  Though 36 > 11×3 = 33, the DI+ worth 36 is just not larger than the edge CADILevel = 40

ADR Filter

• Allow ADR Filter (CADRSwitch): Allows or disables filtering primarily based on the Common Every day Vary (ADR).
• ADR Timeframe (CADRTF): The timeframe used to calculate ADR (e.g., PERIOD_D1).
• ADR Interval (CADRPeriod): The variety of days over which the ADR is averaged.
• Minimal ADR Degree (CADRLevelMin): The minimal ADR worth required for a commerce to be legitimate.
• Most ADR Degree (CADRLevelMax): The utmost ADR worth allowed for a commerce to be legitimate.

Objective:
This filter ensures trades are solely taken when the present market volatility (as measured by ADR) is inside an outlined vary. It avoids indicators throughout overly quiet or excessively unstable market situations.

Instance:

• CADRPeriod = 14, CADRLevelMin = 50, CADRLevelMax = 150
• The EA calculates the typical of the final 14 each day candle ranges and determines it’s 85 factors.
• Commerce is allowed as a result of 85 is inside the 50–150 level vary.
• If ADR = 40 → commerce is skipped (inadequate volatility).
• If ADR = 200 → commerce is skipped (volatility exceeds the higher threshold, probably attributable to information or irregular market situations).

Bollinger Bands Confluence

• Allow Bollinger Bands Filter (CBBSwitch): Allows or disables using Bollinger Bands as a confluence filter.
• Bollinger Bands Timeframe (CBBRTF): Timeframe used for calculating the Bollinger Bands (e.g., PERIOD_D1).
• Bands Interval (CBBPeriod): Variety of intervals used to calculate the bands.
• Customary Deviation (CBBDev): Deviation multiplier for higher and decrease bands.
• Minimal Band Vary (CBBLevelMin): Minimal allowed vary between higher and decrease Bollinger Bands (used as a volatility filter).
• Most Band Vary (CBBLevelMax): Most allowed vary between bands (used to exclude overly unstable situations).

How It Works:

This filter measures the distance between the higher and decrease bands on the chosen timeframe. If the band width falls inside the specified min/max thresholds, then the breakout sign is taken into account legitimate.

Instance:

• CBBPeriod = 20, CBBDev = 2.0, CBBLevelMin = 30, CBBLevelMax = 120
• If Bollinger Band width = 85 pips → passes the filter
• If Bollinger Band width = 15 pips or 150 pips → filtered out

This ensures breakouts are solely thought-about when volatility is inside a wholesome vary — not too compressed (low volatility) or too expanded (excessive threat of mean-reversion).

The above indicator may be present in MT4/MT5 Terminal. To higher perceive how the above customary indicators operate, you possibly can add them on to your chart in MT4 or MT5. This lets you visually observe how the EA’s confluence logic interacts with Shifting Averages, ADX, Bollinger Bands  and ADR in actual time in your to formulate your personal setting.

11. Common Settings

These settings management the final habits and logging of the EA.

• Magic Quantity (MagicNumber):
  Distinctive identifier assigned to the EA’s trades. This ensures the EA solely manages its personal trades and avoids conflicts with different EAs.
  Instance: MagicNumber = 1970 → All trades from this EA will carry this magic quantity.
• EA Remark (EaOrderComment):
  A customized remark connected to every order positioned by the EA. This may also help in figuring out trades within the terminal or throughout journal/debug overview.
  Instance: EaOrderComment = “AIO Breakout” → All trades will embody this remark.
• Chart Remark Swap (ChartComment):
  true – The EA shows dynamic commerce or strategy-related feedback on the chart.
  false – Disables chart feedback.
• Debug Message Swap (DebugSwitch):
  true – Allows detailed logs within the Specialists and Journal tabs for debugging or evaluation.
  false – Disables additional debug messages to scale back litter.

12. Visible Settings

These settings management how the EA seems on the chart throughout buying and selling or backtesting. Use these settings to reinforce the visibility and readability of chart annotations.    This built-in indicator doesn’t have an effect on the field/vary setting.

• Field Shade (RangeColor): Defines the visible colour of the principle vary field. Notice that if Field Vary Filter is activate and the field vary/measurement doesn’t meet the filter standards, the field seems as boadered, not crammed.
• Cease Trades Shade (StopColor): The colour of the horizontal line that reveals the place trades cease.
• Cancel Pending Shade (CancelColor): The colour used to show the cancel pending orders line.
• Day Open Shade (DayOpenColor): The road colour marking the day’s open worth.
• Higher Field Shade (UpperBoxColor): Shade of the higher line of the breakout field.
• Decrease Field Shade (LowerBoxColor): Shade of the decrease line of the breakout field.
• Present Data (ShowInfo): Present or conceal the EA’s standing and particulars on the chart.
• Textual content Measurement (TextSize): Units the dimensions of the displayed font on the chart.
• Textual content Shade (TextColor): Defines the font colour of displayed info.
• Field Shade (BoxColor): Background colour of the knowledge field.

13. Commerce Classes Indicator
These settings enable the EA to show visible markers on the chart that point out the beginning of key buying and selling classes. This helps merchants acknowledge optimum breakout home windows and intervals of low or excessive volatility primarily based on session timing.

• Allow Commerce Classes Indicator (TradeSessionsIndicatorSwitch): Activates or off the show of buying and selling session markers. If enabled (true), session labels will seem on the chart.
• Tokyo Session Begin Hour (JP_Start_Hour): Units the beginning time (hour) for the Tokyo session, typically related to decrease volatility and generally used to type the breakout vary (RBO technique).
• London Session Begin Hour (LD_Start_Hour): Units the hour when the London buying and selling session begins. This can be a widespread opening level for breakout alternatives, particularly in OBO.

• New York Session Begin Hour (NY_Start_Hour): Units the hour of the New York session begin. It’s typically linked to excessive volatility and overlaps with London.
• Textual content Spacing (Spacing): Adjusts the vertical spacing between session label texts. Helpful for holding chart show clear and readable when a number of classes are proven.

Thick line denotes beginning of a session and skinny line denotes ending of a session.

Settings for brokers with server timezone in GMT+2/3, for instance ICMarkets  is:
Tokyo Buying and selling Session Beginning Hour = 2
London Buying and selling Session Beginning Hour = 10
New York Buying and selling Session Beginning Hour = 15

Some brokers are utilizing UTC as buying and selling server timezone and a few may be others. You must discover out your dealer server timezone and set the required above values.

14. Backtest

These settings management the habits of backtests. Use these choices to hurry up assessments or scale back execution time whereas sustaining logical habits.

• Quick Backtest (FastBacktest):
• T-Sort: Use T-type quick backtesting logic.
• S-Sort:  Use S-type quick backtesting logic.
• Quick Backtest Off: Disable quick backtest optimizations.
• T-type Interval (TInt): Specifies the interval between check occasions throughout T-type testing, from 3 and above.  Larger variety of this produce sooner backtest even with each actual ticks.