FreelanceSections

MT5 Expert Advisor - Multi-Timeframe Price Action Strategy (CP/BOS/Engulfing)

MQL5 Experts Forex Trading robot/indicator debugging Strategy optimization

Tâche terminée

Temps d'exécution 14 jours

Spécifications

# Project Specification — MT5 Expert Advisor "Prince Strategy"

## Project Goal

Develop an Expert Advisor (trading robot) for MetaTrader 5 that automates a price-action trading strategy based on candlestick patterns across multiple timeframes. The robot must work on the forex.com broker.

---

## 1. Traded Instruments

The robot must trade the following 4 forex pairs:
- GBPUSD
- EURUSD
- NZDUSD
- AUDUSD

**Important note:** For backtesting, MT5 tests one pair at a time. The robot should therefore be designed to work on the symbol of the chart it is attached to (recommended approach), or reliably handle all 4 pairs if technically feasible.

---

## 2. Strategy Architecture: Multi-Timeframe (Top-Down) Approach

The strategy uses a sequence of two timeframes:

| Step | Timeframe | Role |
|------|-----------|------|
| Bias analysis | H1 (or M30) | Determine market direction |
| Confirmation & entry | M15 (or M5) | Confirm and enter the trade |

Both the bias timeframe and the confirmation timeframe must be configurable as inputs (H1/M30 for bias, M15/M5 for confirmation).

---

## 3. Determining the BIAS (on H1/M30)

The bias (bullish or bearish direction) is determined by ONE of the following 3 patterns:

### 3.1 — Continuation Pattern (CP)

A bullish CP consists of **exactly 3 candles**:
- **B1** (oldest): bullish candle
- **B2** (middle): bearish candle, very small
- **B3** (most recent): bullish candle

**Validity conditions for the bullish CP:**
1. B3 must **fully engulf the body of B2** (B3's body must exceed B2's body, not just equal it)
2. B3 must **not be significantly smaller than B1** (B3 can be equal to or larger than B1 — this is accepted)
3. The **upper wick of B2 must not exceed the high of B3**
   - The upper wick of B2 MAY exceed the high of B1 (accepted)
   - The lower wick of B2 MAY exceed the low of B1 (accepted)
   - The lower wick of B2 MAY exceed the low of B3 (accepted)
   - ONLY the upper wick of B2 exceeding the high of B3 invalidates the CP

**The bearish CP is the exact mirror** (B1 bearish, B2 bullish very small, B3 bearish engulfing B2).

**Special cases:**
- A CP can break a zone (support/resistance) OR form "in open space" (no key level). Both cases are valid.
- On the bias timeframe (H1/M30), B3 can be long without issue.

### 3.2 — Engulfing

A bullish engulfing consists of **2 candles**:
- **B1**: bearish candle (size does not matter)
- **B2**: bullish candle that engulfs **B1's body AND B1's UPPER wick**
  - The high of B2 must exceed the high of B1 (body + upper wick)
  - The **lower wick does NOT matter** (B1's lower wick may extend below B2 — this is accepted)

**The bearish engulfing is the exact mirror:**
- **B1**: bullish candle (size does not matter)
- **B2**: bearish candle that engulfs **B1's body AND B1's LOWER wick**
  - The low of B2 must go below the low of B1 (body + lower wick)
  - The **upper wick does NOT matter** (B1's upper wick may extend above B2 — this is accepted)

**Clarification (important):** Engulfing does NOT require engulfing both wicks. Only the wick in the direction of the bias must be engulfed (lower wick for a bearish engulfing, upper wick for a bullish engulfing). The opposite wick is irrelevant.

### 3.3 — Break of Structure (BOS)

The BOS is the break of a nearby support/resistance level (not a distant one).

**Bearish BOS:**
- Identify the **close of the last bearish candle** that formed the support
- The market may consolidate near this level (several candles)
- A candle that **closes below this close** = confirmed BOS

**Invalidation condition:**
- If the breakout candle has a **wick that is too large** in the opposite direction, the BOS is invalid
- Precise rule: if the wick (lower wick for a bearish BOS, upper wick for a bullish BOS) is **larger than the body** of the breakout candle, the BOS is rejected
- A wick slightly larger than the body is tolerated, but an exaggerated wick invalidates it

**Bullish BOS = exact mirror.**

**Difference between CP and BOS:**
- CP = exactly 3 candles
- BOS = several candles (consolidation) then a breakout

**"Nearby" level:** The BOS is drawn on the most recent structure closest to the current price, not on a distant level.

---

## 4. CLEAN TRAFFIC (mandatory filter)

Clean traffic is the free space between the setup and the target. If the traffic is not clean, the setup is NOT taken, even if the bias is valid.

### 4.1 — Candle obstacles (base rule)

**Definition (bearish case):**
- In the space between the setup and the target, there must be NO **closes of bearish candles** that would form a support (obstacle)
- In other words: **no bearish candle in the traffic** (a bearish candle indicates a correction = creation of an obstacle)

**Bullish case = exact mirror**: no bullish candle (close forming resistance) in the traffic.

**Observation timeframe:** clean traffic is observed on the bias timeframe (H1/M30).

**Note:** The trader does not use pip-based measurement for distance — it is visual. The developer should propose a logic (for example: number of clean candles before the first obstacle).

### 4.2 — Old support/resistance levels as obstacles (additional rule)

Beyond candle obstacles, **old support/resistance levels** in the path are ALSO obstacles, **including FLIPPED levels** (a former support that becomes resistance, or a former resistance that becomes support). These levels can push price back and make the trade fail, even when the candle path itself is clean.

**Important — how an obstacle behaves:**
- An obstacle **BLOCKS** the trade as long as it is **NOT broken**.
- Once price **breaks** through an obstacle, that obstacle **no longer counts**.
- If another obstacle remains further ahead in the path, we must **WAIT** until price breaks it too before taking the trade.
- **This rule only applies WHEN there are obstacles in the path.** Very often there is NO obstacle at all (clean path, or levels far away) — in that case the trade is taken directly, nothing to wait for.

**Difficulty (to be solved with the developer):** The trader identifies these support/resistance levels **VISUALLY**, from experience. He cannot give an exact mathematical rule for them. The developer should **propose an automated method to approximate these levels** (for example: recent zones where price reacted or reversed multiple times). This will be tested on the DEMO version and refined together, stage by stage.

---

## 5. CONFIRMATION and ENTRY (on M15/M5)

Once the bias is validated on H1/M30 with clean traffic:

### 5.1 — Draw the reference line (confirmation line)

The confirmation line is drawn on the **wick of the LAST candle of the bias pattern**. The exact candle depends on which pattern produced the bias:
- if bias = **CP** → line on **B3's wick** (high of B3's wick for a bullish bias, low of B3's wick for a bearish bias)
- if bias = **Engulfing** → line on **B2's wick** (the engulfing candle)
- if bias = **BOS** → line on the **breakout candle's wick**

The confirmation process below works **the SAME WAY** regardless of which bias pattern was used — only the candle used to draw the line changes.

### 5.2 — Wait for the break of the intermediate resistance/support
- If price reaches the close of a candle (resistance in the bullish case), wait for it to break before taking the setup

### 5.3 — Drop to M15 (or M5) and look for confirmation

Confirmation is done **only via CP or BOS** (NOT via engulfing), according to 2 scenarios:

**Scenario 1:** Price breaks the reference line directly with a CP or BOS on M15.

**Scenario 2:** Price breaks the line WITHOUT showing a CP, then forms a CP or BOS **within a maximum of 2 candles after the break**.

**Important confirmation conditions:**
- The confirmation must NOT touch the obstacle. If the obstacle is touched, there is no more space → skip the trade. (Unless the M15 confirmation breaks that obstacle, then it is valid.)
- The **B3 of the confirmation CP must NOT be too long** on M15/M5 (unlike on H1/M30), because the Stop Loss would be too large.
- For BOS confirmation: the correction before the BOS must not be exaggerated, and price must not consolidate too long before breaking.

---

## 6. TRADE MANAGEMENT

| Parameter | Value |
|-----------|-------|
| **Entry** | At the close of B3 (of the confirmation) |
| **Stop Loss** | Slightly below the low of B3 (bullish case) / above the high of B3 (bearish case). Buffer configurable in pips (e.g. 3-5 pips) |
| **Take Profit** | Risk/Reward of 1:1 (TP at the same distance as SL) |

---

## 7. RISK MANAGEMENT

| Parameter | Value |
|-----------|-------|
| Risk per trade | 1% of capital |
| Simultaneous trades | Maximum 1 trade per pair (so max 4 simultaneous trades across the 4 pairs) |
| No 2 trades on the same pair at the same time | Yes |

---

## 8. PROGRESSIVE MONEY MANAGEMENT

The lot size must evolve progressively based on results ("symmetric progressive" method):
- Base lot calculated on 1% of capital
- After each **winning trade**: the lot increases by one step (e.g. +0.01)
- After each **losing trade**: the lot decreases by one step (e.g. -0.01)
- The lot never goes below the minimum base lot
- Safety: the lot must never exceed a configurable maximum risk (e.g. 5% of capital)

---

## 9. DESIRED CONFIGURABLE PARAMETERS

The developer should expose at least the following inputs:
- Bias timeframe (H1/M30) and confirmation timeframe (M15/M5)
- Risk per trade (%)
- Risk/Reward ratio
- Stop Loss buffer (pips)
- Lot increment/decrement (money management)
- Maximum risk (%)
- Pattern detection thresholds (candle size ratios for the CP, lookback bars for the BOS, etc.) to allow fine-tuning after backtesting

---

## 10. EXPECTED DELIVERABLES

1. The commented `.mq5` source file
2. The compiled `.ex5` file
3. A functional backtest on the 4 pairs showing a coherent number of trades (the trader estimates around 2-3 setups per day per pair on average)
4. Installation and usage documentation

---

## 11. NOTES FOR THE DEVELOPER

- The strategy relies on visual judgment (wick size, "clean traffic"). Some rules will need to be translated into adjustable numeric thresholds, to be fine-tuned together after the first backtests.
- The trader can provide annotated screenshots of each pattern to visually clarify each rule. Available annotated screenshots: valid bearish CP, invalid bearish CP, valid bearish BOS, bearish engulfing, clean traffic (open path), old support/resistance levels as obstacles (support became resistance), obstacles that must be broken before entry, and two full confirmation examples (H1 bias → M15 entry, both bullish and bearish).
- Priority: the robot should take trades faithful to the described logic, with selectivity to be refined afterwards.

---

*Specification document prepared for the development of an MT5 EA based on a multi-timeframe price-action strategy.*

Répondu

1
Développeur 1
Évaluation
(111)
Projets
183
25%
Arbitrage
24
17% / 75%
En retard
16
9%
Gratuit
2
Développeur 2
Évaluation
(17)
Projets
21
19%
Arbitrage
5
40% / 40%
En retard
0
Gratuit
3
Développeur 3
Évaluation
(614)
Projets
718
33%
Arbitrage
46
48% / 41%
En retard
15
2%
Chargé
4
Développeur 4
Évaluation
(62)
Projets
90
29%
Arbitrage
24
13% / 58%
En retard
7
8%
Travail
5
Développeur 5
Évaluation
(319)
Projets
566
35%
Arbitrage
82
30% / 45%
En retard
204
36%
Travail
6
Développeur 6
Évaluation
(33)
Projets
36
33%
Arbitrage
5
0% / 80%
En retard
0
Travail
Publié : 2 codes
7
Développeur 7
Évaluation
(3)
Projets
4
0%
Arbitrage
0
En retard
0
Gratuit
8
Développeur 8
Évaluation
(9)
Projets
16
19%
Arbitrage
2
0% / 50%
En retard
3
19%
Travail
9
Développeur 9
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
10
Développeur 10
Évaluation
(551)
Projets
839
61%
Arbitrage
33
27% / 45%
En retard
24
3%
Gratuit
Publié : 1 code
11
Développeur 11
Évaluation
(3)
Projets
3
33%
Arbitrage
0
En retard
0
Chargé
12
Développeur 12
Évaluation
(3)
Projets
1
0%
Arbitrage
5
0% / 100%
En retard
0
Gratuit
13
Développeur 13
Évaluation
(18)
Projets
24
33%
Arbitrage
3
33% / 67%
En retard
3
13%
Gratuit
14
Développeur 14
Évaluation
(1)
Projets
1
0%
Arbitrage
1
0% / 100%
En retard
0
Gratuit
15
Développeur 15
Évaluation
(15)
Projets
20
25%
Arbitrage
2
50% / 0%
En retard
4
20%
Travail
16
Développeur 16
Évaluation
(83)
Projets
95
32%
Arbitrage
9
22% / 56%
En retard
5
5%
Travail
17
Développeur 17
Évaluation
(25)
Projets
32
19%
Arbitrage
6
33% / 33%
En retard
4
13%
Travail
18
Développeur 18
Évaluation
(1)
Projets
1
0%
Arbitrage
0
En retard
0
Gratuit
19
Développeur 19
Évaluation
(55)
Projets
92
24%
Arbitrage
8
75% / 13%
En retard
44
48%
Gratuit
20
Développeur 20
Évaluation
(25)
Projets
31
13%
Arbitrage
13
0% / 77%
En retard
9
29%
Travail
21
Développeur 21
Évaluation
(2674)
Projets
3413
68%
Arbitrage
77
48% / 14%
En retard
342
10%
Gratuit
Publié : 1 code
22
Développeur 22
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
23
Développeur 23
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
24
Développeur 24
Évaluation
(65)
Projets
81
57%
Arbitrage
6
67% / 17%
En retard
1
1%
Occupé
25
Développeur 25
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
26
Développeur 26
Évaluation
(1)
Projets
8
88%
Arbitrage
0
En retard
0
Gratuit
27
Développeur 27
Évaluation
(184)
Projets
317
24%
Arbitrage
23
35% / 13%
En retard
23
7%
Gratuit
Publié : 3 codes
28
Développeur 28
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
29
Développeur 29
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
30
Développeur 30
Évaluation
(21)
Projets
27
7%
Arbitrage
9
33% / 33%
En retard
1
4%
Travail
31
Développeur 31
Évaluation
(13)
Projets
22
41%
Arbitrage
8
0% / 50%
En retard
3
14%
Gratuit
32
Développeur 32
Évaluation
(2343)
Projets
2948
63%
Arbitrage
124
44% / 26%
En retard
429
15%
Travail
33
Développeur 33
Évaluation
(78)
Projets
246
74%
Arbitrage
7
100% / 0%
En retard
1
0%
Gratuit
Publié : 1 article
34
Développeur 34
Évaluation
(10)
Projets
12
58%
Arbitrage
0
En retard
0
Gratuit
35
Développeur 35
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
36
Développeur 36
Évaluation
(45)
Projets
53
57%
Arbitrage
2
100% / 0%
En retard
1
2%
Gratuit
Publié : 5 codes
37
Développeur 37
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
38
Développeur 38
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
39
Développeur 39
Évaluation
(4)
Projets
4
25%
Arbitrage
0
En retard
0
Gratuit
40
Développeur 40
Évaluation
(50)
Projets
51
8%
Arbitrage
0
En retard
0
Gratuit
41
Développeur 41
Évaluation
(50)
Projets
64
20%
Arbitrage
11
27% / 55%
En retard
5
8%
Gratuit
42
Développeur 42
Évaluation
(16)
Projets
35
23%
Arbitrage
4
0% / 50%
En retard
2
6%
Travail
43
Développeur 43
Évaluation
(366)
Projets
449
55%
Arbitrage
23
57% / 17%
En retard
30
7%
Travail
44
Développeur 44
Évaluation
(59)
Projets
92
42%
Arbitrage
4
0% / 100%
En retard
3
3%
Travail
45
Développeur 45
Évaluation
(258)
Projets
269
29%
Arbitrage
1
100% / 0%
En retard
3
1%
Travail
Publié : 2 codes
46
Développeur 46
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
47
Développeur 47
Évaluation
(119)
Projets
169
38%
Arbitrage
9
78% / 22%
En retard
15
9%
Gratuit
48
Développeur 48
Évaluation
(10)
Projets
14
43%
Arbitrage
0
En retard
3
21%
Gratuit
49
Développeur 49
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
50
Développeur 50
Évaluation
(259)
Projets
304
76%
Arbitrage
13
77% / 0%
En retard
5
2%
Chargé
51
Développeur 51
Évaluation
(52)
Projets
63
40%
Arbitrage
15
27% / 60%
En retard
1
2%
Gratuit
52
Développeur 52
Évaluation
(1)
Projets
0
0%
Arbitrage
1
0% / 100%
En retard
0
Gratuit
53
Développeur 53
Évaluation
(271)
Projets
553
50%
Arbitrage
57
40% / 37%
En retard
227
41%
Travail
54
Développeur 54
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
55
Développeur 55
Évaluation
Projets
0
0%
Arbitrage
1
0% / 100%
En retard
0
Gratuit
56
Développeur 56
Évaluation
(13)
Projets
20
45%
Arbitrage
6
33% / 17%
En retard
2
10%
Travail
Publié : 7 articles, 35 codes
57
Développeur 57
Évaluation
Projets
1
0%
Arbitrage
0
En retard
0
Gratuit
58
Développeur 58
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
59
Développeur 59
Évaluation
(298)
Projets
478
40%
Arbitrage
105
40% / 24%
En retard
82
17%
Chargé
Publié : 2 codes
60
Développeur 60
Évaluation
(8)
Projets
8
0%
Arbitrage
2
50% / 0%
En retard
1
13%
Travail
61
Développeur 61
Évaluation
(19)
Projets
27
11%
Arbitrage
11
9% / 55%
En retard
12
44%
Gratuit
62
Développeur 62
Évaluation
(13)
Projets
20
40%
Arbitrage
1
0% / 100%
En retard
1
5%
Gratuit
63
Développeur 63
Évaluation
Projets
0
0%
Arbitrage
0
En retard
0
Gratuit
Commandes similaires
ThunderGold Scalper – funktional ähnlicher Gold-Scalping-EA für MT5 30+ USD
Ich möchte einen professionellen Expert Advisor (EA) für MetaTrader 5 entwickeln lassen, der sich funktional am ThunderGold Scalper orientiert. Instrument: XAUUSD / GOLD Zeitrahmen: M15 Plattform: MetaTrader 5 / MQL5 Der EA soll eine eigene, nachprogrammierte Strategie verwenden und keine geschützten Quellcodes oder proprietären Dateien des Originalprodukts kopieren. Gewünschte Funktionen: automatischer Handel auf
XAGUSD MT5 Automated Trading Expert Advisor 30 - 200 USD
I need a fully automated Expert Advisor (EA) written in MQL5 for MetaTrader 5. The EA must work directly inside MT5 and must NOT require TradingView, PineConnector, webhooks, or another external connector to place trades. Trading Instrument Primary symbol: XAGUSD (Silver) My broker may display the symbol as XAGUSD-ECN, so the EA should work with the broker’s available XAGUSD symbol. Main entry timeframe: 5-minute
RECHERCHE DÉVELOPPEUR MQL5 — PARTENARIAT 50/50 30+ USD
RECHERCHE DÉVELOPPEUR MQL5 — PARTENARIAT 50/50 Objectif : développer un EA de trading automatisé en 11 jours maximum pour participer à plusieurs concours de trading démo. Je recherche un développeur MQL5 expérimenté, capable de développer, tester et optimiser un EA proprement, avec une vraie maîtrise de la gestion du risque. CONCOURS VISÉS 🥇 XM — Weekly Demo Contest - Concours récurrent - Prize pool annoncé : 25 000
GoldTrade EA 89+ USD
//+------------------------------------------------------------------+ //| XAUUSD Wolfe + SMC Quick Profit EA | //| MT5 / MQL5 | //+------------------------------------------------------------------+ #property strict #include <Trade/Trade.mqh> CTrade trade; //================================================================== // INPUTS //================================================================== //--- General
Trading view indicator fixing 30+ USD
can you help me with I have an indicator that I built and I work with PickMyTrade. The entries come through the alerts I get from Trading View . Trading View needs to send an alert and PickMyTrade executes a trade at that exact same second. Now, I have a problem in Trading View with the synchronization between the alert and the signal. I have a box that I built for a trade. It needs to output the box and get an
Looking for a developer in NinjaTrader For coding 30+ USD
Looking for a developer in NinjaTrader For coding Inst - ES,NQ Chart type - Tick, range, volume & time Brief- Fib levels mapped on chart which act as entries, tgts and stops all based on candle close. (Maybe) use MACD for filtering direction. Daily manual input of the TWO fib Anchor levels is part of the strategy. I need a well experienced developer to bid and before biding check the attached file well. the PDF and
Simple EA with Very High Sniper Assertiveness and Low RRR ( 0.06:1, 0.1:1, 0.3:1) (1-3 TRADES PER DAY) 30+ USD
1- The EA must h ave a unique strategy specialized on make trades with very very low RRR, so basicaly risking 1475$ to make 100$, with an ammount adjustable of trades per day. (This is very important that i wish in 100 trades, it makes a maximum of 10 trades of mistake, maybe less...) 2- The EA must have the strategy specialized on INDEX CFD. 3- The EA must make each trade with more than 3 minutes, and less than 12h
Modification of an existing MQL5 EA TH-05 30 - 300 USD
I Have an existing Mql5 Expert advisor (source code), I want a professional programmer to help me Modify the EA... so that it can stop taking new trades once it Gets to a Pacific Lots Size or Floating loss
EA LOTS SIZE MODIFICATION !!! 30 - 300 USD
I Have an existing Mql5 Expert advisor (source code), I want a professional programmer to help me Modify the EA... so that it can stop taking new trades once it Gets to a Pacific Lots Size or Floating loss
The Ultimate Trading Bot 30+ USD
take your time better make it for days and have good bot than never benefits both of us. Make the bot have zero errors and backtest it for a 2 year period

Informations sur le projet

Budget
30 - 200 USD
Délais
à 10 jour(s)