FreelanceSections

Modification of Existing EA | Adding OR/ELSE IF Functions to Existing EA.

MQL4 Indicateurs Experts

Tâche terminée

Temps d'exécution 9 jours
Commentaires du client
A pleasure to work with, very patient and understanding & would have no problem working with Maxwell again.
Commentaires de l'employé
I appreciate and am honored working with you. I look forward to more endeavors. Thank you.

Spécifications

I have an algorithm which is based on candlestick formations - specifically the hammer candle formation. 

Previously, the algorithm only executed short positions on bearish hammers & long positions on bullish hammers.

Now, however, I'm wanting to introduce inverse hammers, but keeping the wicks in the same positions (i.e., extended lower wicks for short positions and extended upper wicks for long positions)

It's not so much the interpretations of the global & local declarations themselves that are the issue, but it's the placement of the brackets that needs to be altered, as well as maybe introducing the "OR" or "ELSE IF" logic but I'll leave that up to you.

The instructions I'm needing it to follow - in layman’s terms - is the following:

"If '(BarTime != Time[0])' is true,
then assess if '(hammerHeadClose < hammerHeadOpen)' is True.
If (hammerHeadClose < hammerHeadOpen) is True, then assess if all of it's child statements are true. 
If all of its child statements are also True, then execute a position.

Alternatively (OR/ELSE IF) if '(hammerHeadClose > hammerHeadOpen)' is true, 
then assess if all of it's child statements are true.
If all of its child statements are true, then execute a position”.  

Therefore, if(BarTime != Time[0]) must always be TRUE, but dependant on weather  '(hammerHeadClose < hammerHeadOpen)' or '(hammerHeadClose > hammerHeadOpen)' will determine which set of child statements will be assessed to determine if a poition should be open.

Obviously (hammerHeadClose > hammerHeadOpen) & (hammerHeadClose < hammerHeadOpen) are mutually exclusive criteria (the closing price can either be above the opening or below the opening - doji's aren't allowed), there is no point in the EA assessing the child statements under (hammerHeadClose > hammerHeadOpen) when (hammerHeadClose < hammerHeadOpen) and visa-versa.

To put it another way "if(BarTime != Time[0]), assess "if(hammerHeadClose > hammerHeadOpen)". 
If "if(hammerHeadClose > hammerHeadOpen)" is FALSE (for example), go straight to if(hammerHeadClose < hammerHeadOpen) and assess all child statements here".

I hope this helps, if you need any clarification, let me know. 

The code in question is on line 315 (short position criteria) and line 795 (long position criteria).

I have enclosed documentation for the EA which includes the explanations to the Global Declarations which you will come across.


if(BarTime != Time[0])
     
     {
     
       if((hammerHeadClose < hammerHeadOpen)

         && (bearHammerHead >= Transform(candleBodyLength,2))
         && (bearHammerHandle!=0 && (bearHammerHead / bearHammerHandle) <= hammerHandlePct)
         && (bullRetracementCandle!=0 && (bearHammerHead / bullRetracementCandle) <= hammerHeadPct)
         && (bullRetracementCandle!=0 && (initialTrendBearCandle / bullRetracementCandle) <= retracePercentage)
         && (bullRetracementCandle >= Transform(candleBodyLength,2))
         && (trendFast < trendSlow)
         && (momentumFast < momentumSlow)
         && (NewBar)
         && (spread <= MaxSpread)
         && (hourOfDay >= startingHour && hourOfDay < endingHour)
         && (OrdersTotal()== 0))
         
       if((hammerHeadClose > hammerHeadOpen)

         && (bullHammerHead >= Transform(candleBodyLength,2))
         && (bearHammerHandleInv!=0 && (bullHammerHead / bearHammerHandleInv) <= hammerHandlePct)
         && (bullRetracementCandle!=0 && (bullHammerHead / bullRetracementCandle) <= hammerHeadPct)
         && (bullRetracementCandle!=0 && (initialTrendBearCandle / bullRetracementCandle) <= retracePercentage)
         && (bullRetracementCandle >= Transform(candleBodyLength,2))
         && (trendFast < trendSlow)
         && (momentumFast < momentumSlow)
         && (NewBar)
         && (spread <= MaxSpread)
         && (hourOfDay >= startingHour && hourOfDay < endingHour)
         && (OrdersTotal()== 0))
 
         {

         bool OpenShort = OrderSend(.....);

         /*----------code----------*/   
        /*----------code----------*/    
        /*----------code----------*/    

         }

}

Dossiers :

MQ4
stop_hammertime_canat_touch_this.mq4
197.1 Kb
PNG
Slide1.PNG
15.5 Kb
PNG
Slide2.PNG
15.7 Kb

Répondu

1
Développeur 1
Évaluation
(169)
Projets
204
30%
Arbitrage
25
40% / 44%
En retard
12
6%
Gratuit
2
Développeur 2
Évaluation
(3)
Projets
4
0%
Arbitrage
2
0% / 100%
En retard
1
25%
Gratuit
3
Développeur 3
Évaluation
(155)
Projets
239
70%
Arbitrage
3
67% / 33%
En retard
20
8%
Gratuit
4
Développeur 4
Évaluation
(211)
Projets
313
34%
Arbitrage
63
37% / 38%
En retard
100
32%
Chargé
5
Développeur 5
Évaluation
(296)
Projets
475
40%
Arbitrage
105
40% / 24%
En retard
80
17%
Occupé
Publié : 2 codes
6
Développeur 6
Évaluation
(5)
Projets
11
18%
Arbitrage
0
En retard
3
27%
Gratuit
7
Développeur 7
Évaluation
(42)
Projets
47
30%
Arbitrage
12
17% / 75%
En retard
6
13%
Gratuit
Commandes similaires
Simplebot 30+ USD
#include <Trade/Trade.mqh> CTrade trade; input double LotSize = 0.1; input int FastMA = 10; input int SlowMA = 20; int fastHandle, slowHandle; // Initialize indicators int OnInit() { fastHandle = iMA(_Symbol, PERIOD_CURRENT, FastMA, 0, MODE_SMA, PRICE_CLOSE); slowHandle = iMA(_Symbol, PERIOD_CURRENT, SlowMA, 0, MODE_SMA, PRICE_CLOSE); return(INIT_SUCCEEDED); } void OnTick() { double fastMA[2]; double
Indicator 250+ USD
Looking for an all in one buy sell indicator I'm looking for a strategy too as part of the project I'm willing to pay well but I will want to test it before proceeding with contract. I'm looking for a developer that is skilled motivated open for future projects... if you aren't one of those do us a favor and just don't respond
Ea for MACD ...& charting 30 - 50 USD
Im after a person to copy, exactly MACD in TRADINGVIEW to use on MT5. Ive tryed alot of the apps available...Tradingview works for me. Im also after a person to make a real time chart, overlayed on the delayed chart Thanks
Pullbacks simple indicator 30+ USD
need a dots marking of a simple rules pullback indicator. in the .tpl file look at 28 Jan 2026, TF M5 basically it is just overlaping lows or highs of the previous candle price. there are 2 scenario to accomodate: 1. simple pullbacks 2. pullbacks with inside bar and outside bar involved
Some one creates an ea based on this heikein ashi smothed indicator 30 - 200 USD
buy condition when blue color appears sell condition when yellow color appears close all buys when there is a sell order close all sells when there is a buy order
Collaboratore MetaTrader 5 - Ottimizzazione algoritmi 500 - 1500 USD
Società di investimento con attività tra Sanremo e Monaco ricerca un giovane collaboratore con esperienza nell’utilizzo avanzato di MetaTrader 5. Si richiede la conoscenza della lingua italiana e inglese. Attività Il collaboratore si occuperà di: • eseguire backtest di strategie di trading su MT5 • effettuare ottimizzazioni parametri tramite Strategy Tester • analizzare risultati e robustezza delle strategie •
Custom Aggressive XAUUSD MT5 Basket Scalping EA (M1/M5/M15) with Momentum Continuation 30 - 50 USD
I am looking for an experienced MT5 developer to build a custom, aggressive XAUUSD scalping EA with structured basket management and momentum continuation logic. This is not a generic EA — it requires careful architecture and proper risk control. Key Requirements: Instrument & Timeframes: XAUUSD only M1 execution chart M5/M15 for directional bias and structure context Execution & Basket Logic: Aggressive basket-style
Fast Scalping EA for Multiple Pairs and Gold 30+ USD
​1. Project Overview ​ Asset: XAUUSD (Gold) ​ Timeframe: M1 (1-Minute) for execution; M5/M15 for trend filtering. ​ Objective: Execute high-frequency scalps during peak liquidity (London/NY overlap) to capture 10–30 pip movements with high precision. ​ Core Logic: The "Poverty Bot" strategy relies on Mean Reversion combined with Momentum Burst (Price Action + RSI/EMA filters). ​2. Strategy Logic (The "Poverty"
In need of a programme to create a buy and sell indicator with simple moving Average 30 - 40 USD
Simple MA indicator with buy and sell arrow with a push notification. Conditions for buy or sell should be when price breaks above or below the MA and then retraced back to the MA creating a HH/HL or LH/LL then the buy/sell signal arrow should be at the reversal candle that forms the HL/HH. And on indicator window1 RSI cross over MA and the RSI line
EA features are working correctly, complete the remaining 30+ USD
Hi, I hope you doing Greate, Let me share details , so the original EA already working but you can check and verify everything fine.First you verify that all original EA features are working correctly then add a user dashboard showing the number of detected zones, buy sell both none status, and an on off button. also ensure mitigated zones disappear properly and that trades follow the zone rules, and integrate the

Informations sur le projet

Budget
30+ USD