Thunderbird EA

명시

1. The idea of the trading system is as follows: market entries are performed when MACD's main and signal lines intersect in the current trend direction.

2. Trend is determined based on the Exponential Moving Average with the specified period (InpMATrendPeriod). If the current EMA value is greater than the previous one, the trend is seen as growing (ema_current > ema_previous). Alternatively, if current EMA is below the previous one, the trend is considered to be falling (ema_current< ema_previous).

3. Trading Signals:

  • Buy signal: the main MACD line crosses the signal line upwards (macd_current>signal_current && macd_previous<signal_previous).
  • Sell signal: the main MACD line crosses the signal line downwards (macd_current<signal_current && macd_previous>signal_previous). The below figure shows Buy and Sell cases.


4. Positions are closed at opposite signals: Buy positions are closed at Sell signals, and Sell positions are closed at Buy signals.

5. Positions are opened at the market price, when a new bar emerges. The Expert Advisor is to be tested using Open prices, so there is no need to add functions for disabling operations inside the bar.

6. Additional filters for opening a position:

The absolute value of MACD's main line will be used to filter out weak signals: the signal is only confirmed if this value is greater than open_level (in points). Signal confirmation conditions are as follows:

  • Confirmation of a buy signal: Abs(macd_current)>open_level
  • Confirmation of a sell signal: macd_current>open_level

7. Additional filters for closing a position:

The absolute value of MACD's main line will also be used to confirm position closure: the signal is confirmed if this value is greater than close_level (in points). Close signal confirmation conditions are as follows:

  • Confirmation to close Buy positions — macd_current>close_level
  • Confirmation to close Sell positions — Abs(macd_current)>close_level

8. Close by Take Profit — during position opening, a Take Profit level is set at a fixed distance from the open price, specified in points. The value is set in the InpTakeProfit input parameter.

9. Position management

TrailngStop is used to protect profit. Stop Loss is set if profit in points exceeds the value specified in the InpTrailingStop parameter. If the price continues to move in the profit direction, Stop Loss should be trailed at the given distance. Stop Loss cannot be moved towards the loss direction, i.e. the Stop Loss value cannot be increased. If none of protective orders (Take Profit or Stop Loss) triggers, the position should be closed by an opposite signal. No other position exit methods are available.


What is contained in the Requirements Specification?

Trading idea

Describe the general underlying idea in the first part of the Requirements Specification. Example: "If the price approaches the resistance level twice and rolls back from it, the next time it is likely to break resistance." Here you can add a chart with the resistance/support lines, indicators and explanatory notes. Exact numbers or calculation algorithms are not required in the idea description. So, in this example we do not need to explain how to determine:

  • resistance level,
  • level breakout,
  • the concept of "is likely to".

Some abstraction at the initial stage will help focus on the idea rather than on technical details. This way you can generate multiple modifications of your trading strategy by replacing or combining strategy blocks, indicators and filters. With the common general idea, you will use different input parameters for your trading robots.

Next, you need to describe all terms and concepts contained in the idea description. If trend is important for your strategy, clearly define what indicator should be used to determine the trend direction and strength. The numerical characteristics of these definitions form the basis of Expert Advisor's input parameters, and can be optimized in the Strategy Tester. So, the first section of the Requirements Specification is "The Trading Idea".

Terms and definitions

It is recommended to create a separate section in the Requirements Specification for explaining related terms and definitions. Explain terms in separate paragraphs. Use bold font to highlight the key concepts of your trading strategy. Where applicable, you may add an image. Input parameters of the desired EA can be written in italics


응답함

1
개발자 1
등급
(15)
프로젝트
19
16%
중재
5
40% / 40%
기한 초과
0
무료
2
개발자 2
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
3
개발자 3
등급
(25)
프로젝트
33
24%
중재
3
33% / 33%
기한 초과
4
12%
작업중
4
개발자 4
등급
(313)
프로젝트
559
35%
중재
80
31% / 44%
기한 초과
203
36%
무료
5
개발자 5
등급
(250)
프로젝트
460
26%
중재
140
20% / 59%
기한 초과
100
22%
작업중
6
개발자 6
등급
(1)
프로젝트
2
0%
중재
0
기한 초과
1
50%
무료
7
개발자 7
등급
(77)
프로젝트
243
74%
중재
7
100% / 0%
기한 초과
1
0%
무료
게재됨: 1 기고글
8
개발자 8
등급
(17)
프로젝트
19
26%
중재
0
기한 초과
3
16%
무료
9
개발자 9
등급
(638)
프로젝트
859
48%
중재
29
38% / 17%
기한 초과
63
7%
작업중
10
개발자 10
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
11
개발자 11
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
12
개발자 12
등급
(1)
프로젝트
0
0%
중재
4
0% / 75%
기한 초과
0
무료
13
개발자 13
등급
(1)
프로젝트
1
0%
중재
0
기한 초과
0
무료
14
개발자 14
등급
(7)
프로젝트
7
0%
중재
6
0% / 83%
기한 초과
1
14%
무료
15
개발자 15
등급
(44)
프로젝트
53
38%
중재
8
13% / 38%
기한 초과
8
15%
작업중
16
개발자 16
등급
(22)
프로젝트
29
3%
중재
4
25% / 0%
기한 초과
3
10%
작업중
17
개발자 17
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
18
개발자 18
등급
(1)
프로젝트
8
88%
중재
0
기한 초과
0
무료
19
개발자 19
등급
(298)
프로젝트
477
40%
중재
105
40% / 24%
기한 초과
81
17%
로드됨
게재됨: 2 코드
20
개발자 20
등급
프로젝트
0
0%
중재
1
0% / 0%
기한 초과
0
무료
게재됨: 7 기고글
21
개발자 21
등급
(162)
프로젝트
288
35%
중재
18
22% / 61%
기한 초과
42
15%
작업중
22
개발자 22
등급
(45)
프로젝트
91
13%
중재
34
26% / 59%
기한 초과
37
41%
무료
23
개발자 23
등급
(10)
프로젝트
14
43%
중재
0
기한 초과
3
21%
무료
24
개발자 24
등급
(12)
프로젝트
12
17%
중재
2
0% / 50%
기한 초과
1
8%
무료
25
개발자 25
등급
(574)
프로젝트
945
47%
중재
309
58% / 27%
기한 초과
125
13%
무료
비슷한 주문
Gold Precision Pro 30 - 100 USD
I want the indicator to be built professionally and carefully because the strategy is strong, but it requires advanced and clean programming. The indicator should work mainly on XAUUSD M15 and should generate more than 2 high-quality signals per day, ideally around 2 to 4 signals maximum, without flooding the chart. The logic must not be random. Each signal must be based on: HTF Bias from H1/H4, Liquidity Sweep
FINAL EA STRATEGY DOCUMENT (Chandelier Exit + EMA Breakout System) ------------------------------------ CORE INDICATOR - Chandelier Exit (MAIN LOGIC) - ATR Period: Editable (Default 22) - ATR Multiplier: Editable (Default 3) IMPORTANT: - ATR must NOT be shown as a separate indicator - ATR must be used ONLY internally inside Chandelier Exit - All SL & trailing must strictly follow Chandelier Exit line
Super scalper 30 - 200 USD
Articles 1 How to create Requirements Specification for ordering a trading robot 28 MetaQuotes 225 289 Table of Contents Prerequisites for ordering a trading robot Why is it important to have a well-prepared Requirements Specification? Requirements Specification examples What is contained in the Requirements Specification? Where do I get Requirements Specification if I can't create it? Terms to use How to write an
i have a tradingview simple indecator of 40 lines of code ,i want it to convert it into mt5 EA strategy details given below AUTOMATED TRADING STRATEGY Multi-Lot Execution & Dynamic Trailing Stop Logic System Architecture & Operational Rules Trading Bot Strategy Profile Entry Conditions Buy Logic • • • Wait for Buy Signal candle. Confirmation: Future candle must break the signal high. Execution: Open 2 orders of 0.01
Situation: Please contact me privately so I can provide the source code for review. Thank you. Project Overview: I have developed a high-frequency trading (HFT) EA that performs consistently in demo environments and passes most prop-firm requirements. While short live phases showed profitability, the results were not reproducible over time. My primary goal is stable live performance on retail accounts , not just
"I need an MT5 EA based on price action — liquidity sweep + hammer/shooting star reversal strategy. TREND: Identified by HH/HL for uptrend, LL/LH for downtrend on selected timeframe. No trade in ranging conditions. BUY SETUP: In uptrend, price retraces to swing low zone, wicks below it (liquidity sweep), hammer forms (lower wick min 2x body, closes above swept low). Buy stop entry at hammer high. SL below hammer
EA SPECIFICATION SHEET OBJECTIVE: Build a transparent, non-martingale, non-grid breakout EA for XAUUSD that trades only high‑quality breakouts during London + New York sessions. 1. TRADING INSTRUMENT - XAUUSD only - MT4 platform - 5‑digit ECN broker 2. CORE STRATEGY LOGIC (BREAKOUT + CONFIRMATION) A trade is allowed ONLY when ALL conditions are true: - Candle closes beyond previous high/low (no wick breakouts) -
I am looking to develop a custom Expert Advisor (EA) for MetaTrader (MT4/MT5) based on a defined technical analysis strategy and flexible risk management rules. The EA should operate on a chart and timeframe that I manually specify, with the ability to adapt its behavior dynamically when the timeframe is changed. Core Strategy Logic The EA will execute trades based on predefined technical analysis zones
I need a professional MT5 Expert Advisor (EA) built with clean, modular code. This is an advanced strategy combining liquidity concepts, controlled DCA, hedge protection, and strict risk management. Core Requirements: Entry Logic (ALL must align): Liquidity sweep (Previous Day High/Low breakout and return) EMA50 and EMA200 trend alignment Higher timeframe bias (H1 or H4) RSI confirmation Bollinger Band entry Filters
I need a professional MQL5 developer. BEFORE I SHARE ANY DETAILS: 1. You must sign a PERPETUAL NDA with no expiration date 2. NDA includes €100,000 penalty for any breach 3. I require full .mq5 source code ownership 4. Developer must have 500+ completed jobs, 4.9+ rating Budget: €1500 EUR Duration: 14 days Start your application with "RULER" to prove you read this

프로젝트 정보

예산
30+ USD