MT4 Liquidity Sweep EA

Specification

Requirements Specification for Asian Range Breakout EA

1. Introduction

This document outlines the functional and technical requirements for the Asian Range Breakout Expert Advisor (EA) for MetaTrader 4 (MT4). The EA identifies a trading range during a specified time window (Asian Range) and executes trades based on specific breakout conditions.

2. Functional Requirements

2.1 Asian Range Identification

  • The EA must define the Asian Range based on a time window specified by the user.

  • Default range: 19:00 EST to 24:00 EST.

  • The user must be able to configure the start and end hours in the input parameters.

  • The EA must account for Daylight Saving Time (DST) in EST and adjust accordingly.

  • The Asian Range High and Low should be determined based on the highest and lowest price between the defined start and end hours.

2.2 Entry Conditions

  • Long Trade Entry:

    • A long position must be entered when a candle wicks below the Asian Range Low but closes above it.

    • The trade must be executed at the close of the triggering candle.

  • Short Trade Entry:

    • A short position must be entered when a candle wicks above the Asian Range High but closes below it.

    • The trade must be executed at the close of the triggering candle.

  • The EA should execute trades based on the timeframe of the chart it is running on (e.g., 15-minute timeframe means candles are 15-minute).

2.3 Stop Loss (SL) & Take Profit (TP)

  • The Stop Loss (SL) should be set below the low of the wick candle for long trades and above the high of the wick candle for short trades.

  • The user must be able to define a buffer in pips to adjust the SL beyond the wick level.

  • The SL must be at least 5 pips. If the calculated SL is smaller, it must be overridden to 5 pips.

  • The Take Profit (TP) should be set based on a Risk-to-Reward Ratio (RRR) specified by the user.

    • TP = Entry Price + (Risk × Risk-to-Reward Ratio) for long trades.

    • TP = Entry Price - (Risk × Risk-to-Reward Ratio) for short trades.

2.4 Position Sizing Based on Account Balance

  • The EA must provide an option for position sizing based on a fixed lot size or a percentage of account balance.

  • The user must be able to define a percentage of the account balance to risk per trade (e.g., 1%).

  • If SL is hit, the total loss should equal the specified percentage of the account balance.

  • The EA must dynamically calculate the trade lot size based on the user-defined risk percentage and the distance of SL from the entry price.

3. Technical Requirements

3.1 MetaTrader 4 Compatibility

  • The EA must be developed in MQL4.

  • The EA should work on any currency pair and timeframe.

  • The EA should use Magic Numbers to distinguish its trades.

  • The EA should allow for user-defined inputs:

    • Asian Range Start & End Hours (EST)

    • Lot Size

    • Slippage

    • Magic Number

    • Stop Loss Buffer (pips)

    • Minimum Stop Loss (pips)

    • Risk-to-Reward Ratio

    • Risk Percentage of Account Balance

3.2 Broker Time & DST Handling

  • The EA must adjust for broker time zone differences.

  • The EA must handle Daylight Saving Time (DST) automatically based on North American DST rules:

    • DST starts on the second Sunday of March.

    • DST ends on the first Sunday of November.

  • The EA must calculate the correct broker time adjustments based on whether DST is active.

3.3 Trade Execution & Risk Management

  • The EA must place orders with defined slippage.

  • The EA should avoid duplicate trades by ensuring that it does not enter multiple trades on the same signal.

  • The EA should manage active trades independently and avoid interference with manual trades.

4. Performance & Logging

  • The EA should log key events and errors for debugging purposes.

  • The EA should handle unexpected broker rejections or execution errors gracefully.

  • The EA should include basic debugging logs for identifying potential issues in execution.

5. Future Considerations

  • Potential addition of trade filtering conditions such as trend filters, volatility filters, or time-based restrictions.

  • Implementation of partial take profit or trailing stop mechanisms for optimizing profits.

6. Acceptance Criteria

  • The EA correctly identifies the Asian Range based on the user’s configured time.

  • The EA enters long and short trades as per the defined conditions.

  • The EA correctly calculates SL and TP based on the rules provided.

  • The EA correctly adapts to DST changes.

  • The EA does not interfere with manual trades.

  • The EA correctly calculates position sizing based on either fixed lot size or risk percentage of account balance.



Responded

1
Developer 1
Rating
(2)
Projects
3
0%
Arbitration
8
13% / 88%
Overdue
1
33%
Free
2
Developer 2
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
3
Developer 3
Rating
(329)
Projects
515
19%
Arbitration
35
46% / 31%
Overdue
34
7%
Working
4
Developer 4
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
5
Developer 5
Rating
(4)
Projects
9
11%
Arbitration
11
18% / 64%
Overdue
4
44%
Free
6
Developer 6
Rating
(78)
Projects
246
74%
Arbitration
7
100% / 0%
Overdue
1
0%
Free
Published: 1 article
7
Developer 7
Rating
(230)
Projects
241
78%
Arbitration
0
Overdue
0
Working
8
Developer 8
Rating
(161)
Projects
208
61%
Arbitration
10
80% / 0%
Overdue
0
Free
Published: 1 code
9
Developer 9
Rating
(171)
Projects
195
42%
Arbitration
13
8% / 54%
Overdue
9
5%
Free
Published: 3 codes
10
Developer 10
Rating
(12)
Projects
9
33%
Arbitration
11
0% / 100%
Overdue
2
22%
Free
11
Developer 11
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
12
Developer 12
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Working
13
Developer 13
Rating
(322)
Projects
499
67%
Arbitration
5
40% / 0%
Overdue
4
1%
Free
Published: 8 codes
14
Developer 14
Rating
(461)
Projects
488
70%
Arbitration
6
67% / 0%
Overdue
2
0%
Working
15
Developer 15
Rating
(574)
Projects
945
47%
Arbitration
309
58% / 27%
Overdue
125
13%
Free
Similar orders
MT5 EA Developer – London Opening Strategy + 3-Hour Rule I’m looking for an experienced MQL5/MT5 EA developer to build an automated XAUUSD London Opening Strategy . Strategy Requirements Use the London session opening as the main setup. Primary setup is based on the first completed M15 candle . If the M15 setup is valid, execute the defined trade. If the M15 setup is not satisfied , activate a 3-hour fallback rule
I need a professional AI-assisted Forex trading Expert Advisor (EA) for MetaTrader 5. The EA should not be based on a simple single indicator strategy. I want a robust multi-factor trading system that can analyze market conditions, trend, momentum, volatility, price action and risk before entering a trade. Requirements: Forex trading on MT5 Automated analysis and trade execution Dynamic entry and exit decisions Stop
Hey guys, I’ve got an MT4 HFT EA that’s showing strong results on an IC Markets demo account, and I'm looking to move it over to MT5. Does anyone have a solid MT5 version that performs well on IC Markets? Having the source code (MQL5) included would be awesome. Thanks for any leads
Let’s use Chart M3. Stochastic 8,3,3. 85/15 trigger for sell stochastic >85, and the reversal move need to engulf the last bar for 1 point. SL over the engulfed bar. Same trigger for buys… Stochastic <15, engulfed bar by 1 point = entrance. SL under the engulfed bar… more details as soon we start to work on it
Freelance Task — EA Recovery Layer Hello. I have a ready-made MQL5 EA. The signals, SL/TP and lot calculation should essentially not be touched. I need a recovery system added. I am not a programmer — below is how the robot should behave. What stays Entry only from an EA signal. Stop-loss is not a new signal. Trailing is already built into my EA — recovery does not implement its own trailing. If trailing is disabled
Should be as it but no alarms, also we need to add a deep search so he can see all the preves candles and a memory function so its not slowing down the indicator. for higher time frames daily 4h 1h around 365 days and for lower time frames we do up to 20k bars but both flexible so i can change it later. the memory is important so the indicator is not always recalculating everything when a new candle shows especially
Creating a bot using the Parabolic indicator with a simple interface.. I want a bot that uses the Parabolic SAR indicator only, with these orders attached to it. Boot name : HEMIN .FX Magic number : 000000 …………………………………………………. Trade behavior : regular OR inverse OR only long "buy" OR only short "sell" Timeframe : ………… Period: ……… ………………………………………………….. Lot size : ……………… Break even in points : …
Project: Fix & Schedule My Dual Fibo Standard Fibonacci Bot I have an existing MQ4 expert advisor called "Dual Fibo Standard Fibonacci". It needs to process 1,000 clients. Right now it runs blindly with no schedule and takes way too long. I need you to optimize it so it runs like a professional business with a 50-100 batch printed stamp copy progress log. Please reply with your numbers for this simple layout: * Phase
Hi, I need an experienced NinjaTrader 8/NinjaScript developer to finish or rebuild an automated futures strategy, ideally by the end of this week. I already have the complete TradingView Pine Script reference strategy, an existing ~2,000-line NinjaScript implementation, Playback logs, and known historical benchmark trades. MOST IMPORTANT REQUIREMENT: TRADINGVIEW ↔ NINJATRADER PARITY. The Pine Script is the reference
I need a custom MQL5 indicator for MetaTrader 5. The indicator must automatically print entry, stop loss, and take profit zones on the chart using dots. A critical requirement is that these dots must be non-lagging and absolutely non-repainting. Additionally, the indicator needs to identify and display current supply and demand zones. Please provide the mq5 source code and the ex5 file upon completion

Project information

Budget
50+ USD