프리랜스섹션

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

MQL5 EA Forex Trading robot/indicator debugging Strategy optimization

작업 종료됨

실행 시간 14 일

명시

# 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.*

응답함

1
개발자 1
등급
(111)
프로젝트
183
25%
중재
24
17% / 75%
기한 초과
16
9%
무료
2
개발자 2
등급
(17)
프로젝트
21
19%
중재
5
40% / 40%
기한 초과
0
무료
3
개발자 3
등급
(614)
프로젝트
718
33%
중재
46
48% / 41%
기한 초과
15
2%
로드됨
4
개발자 4
등급
(62)
프로젝트
90
29%
중재
24
13% / 58%
기한 초과
7
8%
작업중
5
개발자 5
등급
(319)
프로젝트
566
35%
중재
82
30% / 45%
기한 초과
204
36%
작업중
6
개발자 6
등급
(33)
프로젝트
36
33%
중재
5
0% / 80%
기한 초과
0
작업중
게재됨: 2 코드
7
개발자 7
등급
(3)
프로젝트
4
0%
중재
0
기한 초과
0
무료
8
개발자 8
등급
(9)
프로젝트
16
19%
중재
2
0% / 50%
기한 초과
3
19%
작업중
9
개발자 9
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
10
개발자 10
등급
(551)
프로젝트
839
61%
중재
33
27% / 45%
기한 초과
24
3%
무료
게재됨: 1 코드
11
개발자 11
등급
(3)
프로젝트
3
33%
중재
0
기한 초과
0
로드됨
12
개발자 12
등급
(3)
프로젝트
1
0%
중재
5
0% / 100%
기한 초과
0
무료
13
개발자 13
등급
(18)
프로젝트
24
33%
중재
3
33% / 67%
기한 초과
3
13%
무료
14
개발자 14
등급
(1)
프로젝트
1
0%
중재
1
0% / 100%
기한 초과
0
무료
15
개발자 15
등급
(15)
프로젝트
20
25%
중재
2
50% / 0%
기한 초과
4
20%
작업중
16
개발자 16
등급
(83)
프로젝트
95
32%
중재
9
22% / 56%
기한 초과
5
5%
작업중
17
개발자 17
등급
(25)
프로젝트
32
19%
중재
6
33% / 33%
기한 초과
4
13%
작업중
18
개발자 18
등급
(1)
프로젝트
1
0%
중재
0
기한 초과
0
무료
19
개발자 19
등급
(55)
프로젝트
92
24%
중재
8
75% / 13%
기한 초과
44
48%
무료
20
개발자 20
등급
(25)
프로젝트
31
13%
중재
13
0% / 77%
기한 초과
9
29%
작업중
21
개발자 21
등급
(2674)
프로젝트
3413
68%
중재
77
48% / 14%
기한 초과
342
10%
무료
게재됨: 1 코드
22
개발자 22
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
23
개발자 23
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
24
개발자 24
등급
(65)
프로젝트
81
57%
중재
6
67% / 17%
기한 초과
1
1%
바쁜
25
개발자 25
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
26
개발자 26
등급
(1)
프로젝트
8
88%
중재
0
기한 초과
0
무료
27
개발자 27
등급
(184)
프로젝트
317
24%
중재
23
35% / 13%
기한 초과
23
7%
무료
게재됨: 3 코드
28
개발자 28
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
29
개발자 29
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
30
개발자 30
등급
(21)
프로젝트
27
7%
중재
9
33% / 33%
기한 초과
1
4%
작업중
31
개발자 31
등급
(13)
프로젝트
22
41%
중재
8
0% / 50%
기한 초과
3
14%
무료
32
개발자 32
등급
(2343)
프로젝트
2948
63%
중재
124
44% / 26%
기한 초과
429
15%
작업중
33
개발자 33
등급
(78)
프로젝트
246
74%
중재
7
100% / 0%
기한 초과
1
0%
무료
게재됨: 1 기고글
34
개발자 34
등급
(10)
프로젝트
12
58%
중재
0
기한 초과
0
무료
35
개발자 35
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
36
개발자 36
등급
(45)
프로젝트
53
57%
중재
2
100% / 0%
기한 초과
1
2%
무료
게재됨: 5 코드
37
개발자 37
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
38
개발자 38
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
39
개발자 39
등급
(4)
프로젝트
4
25%
중재
0
기한 초과
0
무료
40
개발자 40
등급
(50)
프로젝트
51
8%
중재
0
기한 초과
0
무료
41
개발자 41
등급
(50)
프로젝트
64
20%
중재
11
27% / 55%
기한 초과
5
8%
무료
42
개발자 42
등급
(16)
프로젝트
35
23%
중재
4
0% / 50%
기한 초과
2
6%
작업중
43
개발자 43
등급
(366)
프로젝트
449
55%
중재
23
57% / 17%
기한 초과
30
7%
작업중
44
개발자 44
등급
(59)
프로젝트
92
42%
중재
4
0% / 100%
기한 초과
3
3%
작업중
45
개발자 45
등급
(258)
프로젝트
269
29%
중재
1
100% / 0%
기한 초과
3
1%
작업중
게재됨: 2 코드
46
개발자 46
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
47
개발자 47
등급
(119)
프로젝트
169
38%
중재
9
78% / 22%
기한 초과
15
9%
무료
48
개발자 48
등급
(10)
프로젝트
14
43%
중재
0
기한 초과
3
21%
무료
49
개발자 49
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
50
개발자 50
등급
(259)
프로젝트
304
76%
중재
13
77% / 0%
기한 초과
5
2%
로드됨
51
개발자 51
등급
(52)
프로젝트
63
40%
중재
15
27% / 60%
기한 초과
1
2%
무료
52
개발자 52
등급
(1)
프로젝트
0
0%
중재
1
0% / 100%
기한 초과
0
무료
53
개발자 53
등급
(271)
프로젝트
553
50%
중재
57
40% / 37%
기한 초과
227
41%
작업중
54
개발자 54
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
55
개발자 55
등급
프로젝트
0
0%
중재
1
0% / 100%
기한 초과
0
무료
56
개발자 56
등급
(13)
프로젝트
20
45%
중재
6
33% / 17%
기한 초과
2
10%
작업중
게재됨: 7 기고글, 35 코드
57
개발자 57
등급
프로젝트
1
0%
중재
0
기한 초과
0
무료
58
개발자 58
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
59
개발자 59
등급
(298)
프로젝트
478
40%
중재
105
40% / 24%
기한 초과
82
17%
로드됨
게재됨: 2 코드
60
개발자 60
등급
(8)
프로젝트
8
0%
중재
2
50% / 0%
기한 초과
1
13%
작업중
61
개발자 61
등급
(19)
프로젝트
27
11%
중재
11
9% / 55%
기한 초과
12
44%
무료
62
개발자 62
등급
(13)
프로젝트
20
40%
중재
1
0% / 100%
기한 초과
1
5%
무료
63
개발자 63
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
비슷한 주문
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

프로젝트 정보

예산
30 - 200 USD
기한
로 10 일