50 EMA WITH RSI CONFIRMATION

Specifiche



Scenario 1:



Breakout, Retest, and Engulfing Candle Cross Entry

1. **Price Breaks Above/Below the 50 EMA:** - The EA should identify when the price breaks above (for buy) or below (for sell) the 50 EMA.

2. **Retest of the Breakout Level:** - After the breakout, the EA should wait for the price to return and test the breakout level TEST SHOULD BE WITH BEARISH CANDLE IF CASE BULLISH AND TEST WITH BULLSIH CANDLE IF CASE BEARISH (above or below the 50 EMA).

3. **Engulfing Candle Formation:** - The EA should detect the formation of a bullish (for buy) or bearish (for sell) engulfing candle after the retest of the breakout level.

4. **Entry Trigger (Candle Cross):** - The EA should place a trade when the next candle crosses above the high (for buy) or below the low (for sell) of the engulfing candle. ---


#### Scenario 2: Breakout of 50 EMA Without Retest

1. **Price Breaks Above/Below the 50 EMA:** - The EA should detect when the price breaks above (for buy) or below (for sell) the 50 EMA. At the time of the breakout, RSI should be above 50 for a buy or below 50 for a sell.
2. **No Retest of the 50 EMA:** - If there is no retest of the 50 EMA, the EA should proceed with the next step.
3. **Next Candle Crosses Breakout Candle by X Pips:** - The EA should enter the trade when the next candle crosses the high (for buy) or low (for sell) of the breakout candle by a user-defined number of pips (e.g., 5 pips). 4. **Stop Loss (SL) Placement:** - The EA should set the SL below the low of the breakout candle for a buy, or above the high of the breakout candle for a sell. --- ### SL and TP Management for EA 1. **Risk Management:** - The EA should open the initial trade with 1% of the account balance as risk. 2. **Martingale Strategy:** - If the trade hits the SL, the EA should open a new trade with an increased lot size (Martingale) to recover the loss and still target profit. 3. **Take Profit (TP) Management:** - The TP should be user-defined, e.g., targeting 5% of the account balance, and the EA should manage TP and SL accordingly for both risk and reward.


Con risposta

1
Sviluppatore 1
Valutazioni
(454)
Progetti
718
34%
Arbitraggio
35
69% / 9%
In ritardo
22
3%
In elaborazione
2
Sviluppatore 2
Valutazioni
(43)
Progetti
66
12%
Arbitraggio
12
58% / 42%
In ritardo
1
2%
Gratuito
3
Sviluppatore 3
Valutazioni
(22)
Progetti
21
10%
Arbitraggio
4
25% / 75%
In ritardo
0
Gratuito
4
Sviluppatore 4
Valutazioni
(64)
Progetti
83
28%
Arbitraggio
9
33% / 56%
In ritardo
9
11%
Gratuito
Pubblicati: 1 codice
5
Sviluppatore 5
Valutazioni
(11)
Progetti
15
20%
Arbitraggio
6
0% / 100%
In ritardo
3
20%
Gratuito
6
Sviluppatore 6
Valutazioni
(62)
Progetti
90
29%
Arbitraggio
24
13% / 58%
In ritardo
7
8%
In elaborazione
7
Sviluppatore 7
Valutazioni
(458)
Progetti
485
70%
Arbitraggio
6
67% / 0%
In ritardo
2
0%
In elaborazione
8
Sviluppatore 8
Valutazioni
(1)
Progetti
2
0%
Arbitraggio
0
In ritardo
1
50%
In elaborazione
9
Sviluppatore 9
Valutazioni
(106)
Progetti
129
25%
Arbitraggio
23
30% / 52%
In ritardo
8
6%
Gratuito
10
Sviluppatore 10
Valutazioni
(460)
Progetti
802
48%
Arbitraggio
73
19% / 52%
In ritardo
140
17%
In elaborazione
11
Sviluppatore 11
Valutazioni
(443)
Progetti
570
37%
Arbitraggio
106
39% / 33%
In ritardo
17
3%
Gratuito
12
Sviluppatore 12
Valutazioni
(5)
Progetti
8
13%
Arbitraggio
3
0% / 33%
In ritardo
2
25%
Gratuito
Pubblicati: 1 codice
13
Sviluppatore 13
Valutazioni
(39)
Progetti
54
61%
Arbitraggio
2
50% / 50%
In ritardo
0
Gratuito
14
Sviluppatore 14
Valutazioni
(85)
Progetti
174
44%
Arbitraggio
3
100% / 0%
In ritardo
5
3%
Gratuito
Pubblicati: 1 codice
15
Sviluppatore 15
Valutazioni
(3)
Progetti
4
0%
Arbitraggio
4
25% / 75%
In ritardo
1
25%
Gratuito
16
Sviluppatore 16
Valutazioni
(318)
Progetti
565
35%
Arbitraggio
81
31% / 44%
In ritardo
204
36%
Gratuito
17
Sviluppatore 17
Valutazioni
(77)
Progetti
245
74%
Arbitraggio
7
100% / 0%
In ritardo
1
0%
In elaborazione
Pubblicati: 1 articolo
18
Sviluppatore 18
Valutazioni
(2672)
Progetti
3406
68%
Arbitraggio
77
48% / 14%
In ritardo
342
10%
Gratuito
Pubblicati: 1 codice
19
Sviluppatore 19
Valutazioni
Progetti
0
0%
Arbitraggio
0
In ritardo
0
Gratuito
20
Sviluppatore 20
Valutazioni
(258)
Progetti
266
29%
Arbitraggio
0
In ritardo
3
1%
In elaborazione
Pubblicati: 2 codici
21
Sviluppatore 21
Valutazioni
(271)
Progetti
553
50%
Arbitraggio
57
40% / 37%
In ritardo
227
41%
In elaborazione
22
Sviluppatore 22
Valutazioni
(16)
Progetti
22
14%
Arbitraggio
8
38% / 63%
In ritardo
6
27%
Gratuito
23
Sviluppatore 23
Valutazioni
(8)
Progetti
8
0%
Arbitraggio
2
50% / 0%
In ritardo
1
13%
In elaborazione
24
Sviluppatore 24
Valutazioni
Progetti
1
0%
Arbitraggio
4
0% / 50%
In ritardo
0
In elaborazione
25
Sviluppatore 25
Valutazioni
(174)
Progetti
233
61%
Arbitraggio
3
33% / 33%
In ritardo
6
3%
Gratuito
Pubblicati: 1 codice
Ordini simili
Professional MT5 Expert Advisor – Multi-Engine Trading Framework Description I'm looking for an experienced MQL5 developer to build a professional MetaTrader 5 Expert Advisor. This is not a simple indicator-based EA. The system should be designed using a modular architecture with a strong focus on maintainability, optimization, and future scalability. The first version should include the following features. Market
Looking for an MT5 Expert Advisor developer with: Minimum 1 year of verified activity on the MetaTrader Market Positive, real user reviews Ability to build EAs without Bollinger Bands Fully configurable parameters (risk, filters, SL/TP, trading hours) Free test version available before any payment Clear communication and ongoing support If you meet these requirements, please send your MQL5 profile or portfolio
Akram boushaba 30 - 500 USD
مرحبا كيف حالكم انا اكرم مهتم بالتداول احاول ان اصمم برنامج روبوت قادر على التداول من تلقاء نفسه من يمكنه ان يساعدني او يعلمني كيف استطيع فهل ذلك وسأكون ممتناً له وشكرا لكم
MetaTrader In-App Trade Alerts An existing MetaTrader terminal is already running on my side, but its account is kept hidden for privacy reasons. I need a specialist to wire up native in-app notifications so that every time a position is opened or later closed I see an immediate pop-up inside the platform—no emails or SMS, just the built-in alert window (and the usual MT push to mobile if that comes automatically
EA Crafter 500+ USD
Act as a professional Quantitative Developer and Risk Manager. I want to build a systematic trading strategy rulebook that prioritizes capital preservation and statistical edge over raw performance. Please generate a structured trading strategy using the following framework: 1. ASSET CLASS & TIMEFRAME: - Asset: [e.g., Apple (AAPL), Bitcoin (BTC), or EUR/USD] - Timeframe: [e.g., 5-minute, 1-hour, Daily] 2. CORE
JOB TITLE: XAUUSD ONLY MQL5 Strategy Developer Needed To Improve Existing MT5 EA Winrate JOB DESCRIPTION: I already have a working MetaTrader 5 Expert Advisor with a fixed set file and existing trading logic. The strategy is based on Volume Profile / Delta bias, ATR-based TP/SL, ATR deviation filtering, ATR trade spacing, break-even after TP1, and TP lock management. I am looking for an experienced MQL5 / trading
أحتاج إلى مستشار خبير لمنصة MetaTrader 5 (MT5) مصمم كآلة حالة محدودة (FSM). يجب أن ينفذ أوامر السوق فقط بناءً على مستويات أسعار يحددها المستخدم. يجب ألا يستخدم أي مؤشرات أو تحليل فني أو أوامر معلقة أو ذكاء اصطناعي أو قرارات تداول تلقائية. يجب أن ينفذ المستشار الخبير ببساطة تسلسلًا محددًا مسبقًا لمستويات الأسعار كما يحددها المستخدم تمامًا، مع إدارة دقيقة للحالة، ودورة نشطة واحدة في كل مرة، ومعالجة الفجوات السعرية،
Message me please for the investor login. You will replicate the ea and I shall tell u some things about it, I am not paying over $100. You should have great skills. The EA can handle any market and shall not blow the account
Мне нужен простой торговый бот, написанный исключительно на Python. Бот должен подключаться к терминалу MetaTrader 5 через официальную библиотеку Python "MetaTrader5". Объем кода невелик (около 250 строк). КРИТИЧЕСКИ ВАЖНЫЕ ТРЕБОВАНИЯ: 1. НЕТ КОДА MQL5: Весь проект должен быть написан только на Python. 2. ВНЕШНЯЯ КОНФИГУРАЦИЯ: У бота должен быть внешний конфигурационный файл (config.ini или settings.json). Я должен
Dashboard Backtest 30 - 500 USD
Hello, I have a question. Is it possible to create an offline version of MetaTrader for backtesting multi-timeframe dashboards? Specifically, I would like the dashboard to receive historical data from multiple timeframes (such as M1, M5, M15, H1, and H4) during a backtest and operate exactly as it does in live trading. Is this technically possible, or do MetaTrader's backtesting limitations prevent this

Informazioni sul progetto

Budget
50+ USD