FreelanceBölümler

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

MQL5 Uzmanlar Forex Trading robot/indicator debugging Strategy optimization

Şartname

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

Yanıtlandı

1
Geliştirici 1
Derecelendirme
(107)
Projeler
175
25%
Arabuluculuk
23
13% / 78%
Süresi dolmuş
16
9%
Çalışıyor
2
Geliştirici 2
Derecelendirme
(15)
Projeler
19
16%
Arabuluculuk
5
40% / 40%
Süresi dolmuş
0
Serbest
3
Geliştirici 3
Derecelendirme
(599)
Projeler
693
33%
Arabuluculuk
43
47% / 44%
Süresi dolmuş
12
2%
Çalışıyor
4
Geliştirici 4
Derecelendirme
(62)
Projeler
90
29%
Arabuluculuk
24
13% / 58%
Süresi dolmuş
7
8%
Çalışıyor
5
Geliştirici 5
Derecelendirme
(317)
Projeler
564
35%
Arabuluculuk
81
31% / 44%
Süresi dolmuş
204
36%
Serbest
6
Geliştirici 6
Derecelendirme
(33)
Projeler
36
33%
Arabuluculuk
5
0% / 80%
Süresi dolmuş
0
Çalışıyor
Yayınlandı: 2 kod
7
Geliştirici 7
Derecelendirme
(1)
Projeler
1
0%
Arabuluculuk
0
Süresi dolmuş
0
Çalışıyor
8
Geliştirici 8
Derecelendirme
(7)
Projeler
13
15%
Arabuluculuk
2
0% / 50%
Süresi dolmuş
3
23%
Çalışıyor
9
Geliştirici 9
Derecelendirme
Projeler
0
0%
Arabuluculuk
0
Süresi dolmuş
0
Serbest
10
Geliştirici 10
Derecelendirme
(545)
Projeler
830
62%
Arabuluculuk
33
27% / 45%
Süresi dolmuş
23
3%
Serbest
Yayınlandı: 1 kod
11
Geliştirici 11
Derecelendirme
Projeler
0
0%
Arabuluculuk
0
Süresi dolmuş
0
Serbest
12
Geliştirici 12
Derecelendirme
(3)
Projeler
1
0%
Arabuluculuk
5
0% / 100%
Süresi dolmuş
0
Serbest
13
Geliştirici 13
Derecelendirme
(12)
Projeler
18
17%
Arabuluculuk
3
33% / 67%
Süresi dolmuş
3
17%
Serbest
14
Geliştirici 14
Derecelendirme
(1)
Projeler
1
0%
Arabuluculuk
1
0% / 100%
Süresi dolmuş
0
Serbest
15
Geliştirici 15
Derecelendirme
(12)
Projeler
16
25%
Arabuluculuk
1
0% / 0%
Süresi dolmuş
4
25%
Çalışıyor
16
Geliştirici 16
Derecelendirme
(77)
Projeler
87
30%
Arabuluculuk
9
11% / 56%
Süresi dolmuş
4
5%
Yüklendi
17
Geliştirici 17
Derecelendirme
(25)
Projeler
31
19%
Arabuluculuk
5
40% / 40%
Süresi dolmuş
4
13%
Çalışıyor
18
Geliştirici 18
Derecelendirme
(1)
Projeler
1
0%
Arabuluculuk
0
Süresi dolmuş
0
Serbest
19
Geliştirici 19
Derecelendirme
(55)
Projeler
92
24%
Arabuluculuk
8
75% / 13%
Süresi dolmuş
44
48%
Serbest
20
Geliştirici 20
Derecelendirme
(25)
Projeler
31
13%
Arabuluculuk
13
0% / 77%
Süresi dolmuş
9
29%
Serbest
21
Geliştirici 21
Derecelendirme
(2669)
Projeler
3402
68%
Arabuluculuk
77
48% / 14%
Süresi dolmuş
342
10%
Serbest
Yayınlandı: 1 kod
22
Geliştirici 22
Derecelendirme
Projeler
0
0%
Arabuluculuk
0
Süresi dolmuş
0
Serbest
23
Geliştirici 23
Derecelendirme
Projeler
0
0%
Arabuluculuk
0
Süresi dolmuş
0
Serbest
24
Geliştirici 24
Derecelendirme
(48)
Projeler
62
56%
Arabuluculuk
4
75% / 25%
Süresi dolmuş
1
2%
Çalışıyor
25
Geliştirici 25
Derecelendirme
Projeler
0
0%
Arabuluculuk
0
Süresi dolmuş
0
Serbest
26
Geliştirici 26
Derecelendirme
(1)
Projeler
8
88%
Arabuluculuk
0
Süresi dolmuş
0
Serbest
27
Geliştirici 27
Derecelendirme
(184)
Projeler
317
24%
Arabuluculuk
23
35% / 13%
Süresi dolmuş
23
7%
Serbest
Yayınlandı: 3 kod
28
Geliştirici 28
Derecelendirme
Projeler
0
0%
Arabuluculuk
0
Süresi dolmuş
0
Serbest
29
Geliştirici 29
Derecelendirme
Projeler
0
0%
Arabuluculuk
0
Süresi dolmuş
0
Serbest
30
Geliştirici 30
Derecelendirme
(19)
Projeler
24
8%
Arabuluculuk
9
33% / 33%
Süresi dolmuş
1
4%
Yüklendi
31
Geliştirici 31
Derecelendirme
(12)
Projeler
21
43%
Arabuluculuk
8
0% / 50%
Süresi dolmuş
3
14%
Serbest
32
Geliştirici 32
Derecelendirme
(2327)
Projeler
2930
63%
Arabuluculuk
124
44% / 26%
Süresi dolmuş
429
15%
Çalışıyor
33
Geliştirici 33
Derecelendirme
(77)
Projeler
244
74%
Arabuluculuk
7
100% / 0%
Süresi dolmuş
1
0%
Serbest
Yayınlandı: 1 makale
34
Geliştirici 34
Derecelendirme
(6)
Projeler
7
71%
Arabuluculuk
0
Süresi dolmuş
0
Serbest
Benzer siparişler
Expert MQL5 Developer Needed for Prop Firm-Ready EA 30 - 200 USD
I am looking for an experienced MQL5 developer to build a robust, high performance Expert advisor (EA) designed specifically for passing and managing funded accounts.The primary focus is to make some good money and also focus on risk management, consistent equity growth
Expert Advisor based on EMA crosses and successful trading principles needed 50+ USD
Expert Advisor (EA) Requirements – MT5 (MQL5) Project Overview Develop an automated Expert Advisor (EA) for MetaTrader 5 based on EMA crossover signals combined with strict risk management and trade management principles. The EA must be optimized for Forex pairs and indices and should operate automatically without manual intervention. Entry Conditions Buy Setup Fast EMA crosses above Slow EMA. Current candle closes
REQUEST FOR MT4 EXPERT ADVISOR DEVELOPER (XAUUSD MULTI-TIMEFRAME SWING EA) 30 - 1000 USD
SUBJECT: REQUEST FOR MT4 EXPERT ADVISOR DEVELOPER (XAUUSD MULTI-TIMEFRAME SWING EA) Dear Developer, I am looking to hire an experienced Meta Trader 4 (MQL4) Expert Advisor developer to build a custom Expert Advisor for XAUUSD (Gold). This project is based on a structured multi-timeframe swing trading system using market structure analysis. PROJECT OVERVIEW The Expert Advisor must be designed to trade XAUUSD using a
Modify a (Pruning) Grid EA 30+ USD
MT5 Expert Advisor Development Project Overview I am looking for an experienced MQL5 developer to build a custom MetaTrader 5 Expert Advisor based on a grid-cycle trading framework. This is not a standard grid EA . The system combines: Session-based trade initiation Multi-filter signal generation Dynamic grid management Advanced basket management State-machine-driven trade lifecycle management Dynamic take-profit
MT5 Expert Advisor Development – Heikin Ashi EMA Pullback Strategy 30 - 350 USD
Need an MT5 EA coded in MQL5. Strategy uses internally calculated MT5 Heikin Ashi candles, EMA 9 and EMA 21 on M1 USDJPY. Fixed lot size 12.20. One trade at a time. 40-point stop loss. Exit after 3 consecutive opposite Heikin Ashi candles. I have a detailed strategy document and video examples of valid and invalid entries. Videos linked show MT5 IOS but custom EA code will be used for windows MT5
Trading view indicator merge and buy sell signal create ....dashboard 30 - 50 USD
Two trading view indicator merge and specific area show entry and SL/TP....DASHBOARD SHOW 1YEAR. UMBER OF ORDER AND WIN/LOSS PROFIT% etc.The trading view indicator name will be under me............and I will tell you condition for A+ setup...and normal....based on that condition signal will create
Advanced Forex Expert Advisor-fully automated system 200 - 300 USD
I require a custom EA and an accompanying custom indicator built in MQL5 for Meta Trader 4/5. The EA must be fully automated (Algo Trading); Telegram-Signal-Linked and named 'AMK Fx'
MT5 XAUUSD Order Block and Liquidity Expert Advisor 30 - 200 USD
Use the H4 timeframe to determine the main trend direction. Identify valid order blocks on the H1 timeframe. Identify liquidity zones and liquidity sweeps. Wait for M15 confirmation before opening a trade. Only take buy trades in bullish market conditions and sell trades in bearish market conditions. Risk a fixed percentage of account balance per trade (user adjustable). Automatically calculate lot size based on
MC Trader's 30+ USD
If Buy: it must Buy when a conformation is done Bye the candle that would be a bullish engolfing candle or after liqudity swip or when sellers has stepped down the market and the market regains energy and trand upwards, it's stop loss must be below the Buy position and it's take profit must be at the top of all candles
Telegram bot upgrade and options trading feature 30+ USD
i am looking to upgrade my trading telegram bot and add live data to it and also make it linked to a dashboard where i can trace the users who register in my bot and pay and make them go in my private channel and manages the expiry date of each user

Proje bilgisi

Bütçe
30 - 200 USD
Son teslim tarihi
to 10 gün

Müşteri

Verilmiş siparişler1
Arabuluculuk sayısı0