Modification of Existing EA | Adding OR/ELSE IF Functions to Existing EA. - MQL5.community 프리랜싱 서비스에서 기술 지표을(를) 개발하기 위한 주문 - 예산: 30+ USD - MQL4

작업 종료됨

실행 시간 9 일

고객의 피드백

A pleasure to work with, very patient and understanding & would have no problem working with Maxwell again.

피고용인의 피드백

I appreciate and am honored working with you. I look forward to more endeavors. Thank you.

설명

명시

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----------*/    

         }

}

파일:

MQ4

stop_hammertime_canat_touch_this.mq4

197.1 Kb

PNG

Slide1.PNG

15.5 Kb

PNG

Slide2.PNG

15.7 Kb

응답함

등급

(169)

프로젝트

204

30%

중재

40% / 44%

기한 초과

무료

등급

(3)

프로젝트

중재

0% / 100%

기한 초과

25%

무료

등급

(155)

프로젝트

239

70%

중재

67% / 33%

기한 초과

무료

등급

(213)

프로젝트

316

34%

중재

37% / 40%

기한 초과

102

32%

작업중

등급

(298)

프로젝트

478

40%

중재

105

40% / 24%

기한 초과

17%

로드됨

게재됨: 2 코드

등급

(5)

프로젝트

18%

중재

기한 초과

27%

무료

등급

(42)

프로젝트

30%

중재

17% / 75%

기한 초과

13%

무료

비슷한 주문

I am looking for an experienced MQL5 developer to build a robust XAUUSD scalping Expert Advisor for MetaTrader 5. The EA should focus on consistent risk management, controlled drawdown, high-quality trade filtering, precise entries and exits, configurable stop loss and take profit, spread and volatility protection, trading-session filters, and reliable execution. I need the strategy to be fully backtestable and

1. General Overview: I am looking for an experienced developer to build (or debug/optimize) an MQL5 Expert Advisor. The EA will primarily trade Gold (XAU/USD) and US Indices (US30, US100). 2. Platform & Broker Requirements: Platform: MetaTrader 5 (MQL5) Broker: Must be fully compatible with XM Broker execution. Account Types: Must support both Standard and Micro lot sizing seamlessly. 3. Technical & Skill

I will pay 2500 to 10000 USD (negotiable) for one MT5 Expert Advisor, built properly. One robot done right, not a batch of cheap jobs. I have a strategy I believe in and a rough draft robot I built myself. The logic is there. The execution is not. That last part is outside my expertise, which is why I am hiring instead of continuing on my own. I am open to feedback on the strategy itself. If you see something in it

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

//+------------------------------------------------------------------+ //| AdvancedPriceAction.mq5 | //| Copyright 2026, Trading Strategy AI | //+------------------------------------------------------------------+ #property copyright "Trading Strategy AI" #property version "1.00" #property strict #include <Trade\Trade.mqh>

I will pay 10k (negotiable) for an EA for existing MT5 that generates a minimum of 5% or higher a month consistently Please send demo version with optimal settings so I can test, if it performs in a strategy tester i will also need option to forward test it in a demo account. Developer should be willing to demonstrate how efficient the robot is, Once you send me the demo, I will test the EA on a real-time account

I need an experienced MQL5/MT5 developer to review, correct, complete, and backtest an existing XAUUSD (Gold) news-trading Expert Advisor called LuxNewsEA. The EA is based on a documented trading strategy and I will provide the full strategy booklet, existing .mq5 source code, and the original video/interview explaining the strategy. The developer should first audit the strategy against the video, especially the

Hi, can you define entry conditions based on 100 or 200 trades? If you need more history, i can give you more trades. It is EURUSD with great results! If you can do it, contact me

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+ USD

상세내용의 질
결과 확인의 질
능력과 커뮤니케이션 스킬