Precision Entry Pro EA V1

MQL5 Experts

Specification

PRECISION ENTRY PRO EA V1
MT5 EXPERT ADVISOR REQUIREMENTS SPECIFICATION

PROJECT NAME:
Precision Entry Pro EA V1

PLATFORM:
MetaTrader 5 (MT5)

LANGUAGE:
MQL5


1. PROJECT OBJECTIVE

I want a simple, reliable and fully automated MT5 Expert Advisor based on the following trading concept:

TREND → MARKET STRUCTURE → FIBONACCI RETRACEMENT → PRICE ACTION CONFIRMATION → ENTRY → STOP LOSS → TAKE PROFIT.

The purpose of V1 is to create the core trading engine first.

The EA must NOT use martingale, grid trading, averaging down, or increasing lot size after losses.

The EA must wait for the required conditions before opening a trade.


2. TRADE DIRECTION

The EA must support:

- Buy only
- Sell only
- Buy and Sell

Input:

TradeDirection

Default:
Buy and Sell


3. TIMEFRAME

Default entry timeframe:

M15

The timeframe must be configurable.

The EA must evaluate signals using CLOSED candles.

The EA must not enter simply because an unfinished candle temporarily meets the conditions.


4. TREND FILTER

Use two Exponential Moving Averages:

Fast EMA = 50
Slow EMA = 200

BUY TREND CONDITION:

- Price is above the 200 EMA
- 50 EMA is above the 200 EMA

SELL TREND CONDITION:

- Price is below the 200 EMA
- 50 EMA is below the 200 EMA

The EMA periods must be configurable.

Input:

FastEMA = 50
SlowEMA = 200

Also include:

EnableTrendFilter = true/false


5. MARKET STRUCTURE

The EA must identify a recent valid swing high and swing low.

Use a configurable lookback period.

Default:

SwingLookback = 50 candles

The EA must use the recent meaningful swing high and swing low for the Fibonacci calculation.

The developer should use a clear and deterministic swing-detection method.

Please document exactly how the swing high and swing low are identified.

The EA must not change the Fibonacci anchors randomly from tick to tick.


6. FIBONACCI BUY SETUP

For a bullish setup:

1. Identify a valid swing low.
2. Identify the subsequent swing high.
3. Calculate Fibonacci retracement from the swing low to the swing high.
4. Wait for price to retrace into the Fibonacci zone.

Primary entry zone:

50.0% to 61.8%

The EA must NOT buy simply because price touches the Fibonacci zone.

A price-action confirmation is required.


7. FIBONACCI SELL SETUP

For a bearish setup:

1. Identify a valid swing high.
2. Identify the subsequent swing low.
3. Calculate Fibonacci retracement from the swing high to the swing low.
4. Wait for price to retrace into the Fibonacci zone.

Primary entry zone:

50.0% to 61.8%

The EA must NOT sell simply because price touches the Fibonacci zone.

A price-action confirmation is required.


8. BUY PRICE-ACTION CONFIRMATION

After price enters the 50%-61.8% Fibonacci zone, the EA must wait for bullish confirmation.

For V1, use the following confirmation:

A bullish rejection candle OR bullish engulfing candle must close while price is in or has interacted with the Fibonacci zone.

Then the EA waits for price to break the HIGH of the confirmation candle.

BUY ENTRY:

Open a BUY when the confirmation candle high is broken.

The confirmation candle must already be closed.

No BUY should be opened if the required confirmation did not occur.


9. SELL PRICE-ACTION CONFIRMATION

After price enters the 50%-61.8% Fibonacci zone, the EA must wait for bearish confirmation.

For V1, use:

A bearish rejection candle OR bearish engulfing candle must close while price is in or has interacted with the Fibonacci zone.

Then the EA waits for price to break the LOW of the confirmation candle.

SELL ENTRY:

Open a SELL when the confirmation candle low is broken.

The confirmation candle must already be closed.

No SELL should be opened if the required confirmation did not occur.


10. CONFIRMATION SETTINGS

The EA should have:

EnableBullishEngulfing = true
EnableBearishEngulfing = true
EnableRejectionCandles = true

If possible, allow the user to choose:

ConfirmationMode:
- Engulfing only
- Rejection only
- Either

Default:

Either


11. STOP LOSS

For BUY:

Place Stop Loss below the relevant swing low.

For SELL:

Place Stop Loss above the relevant swing high.

Include an adjustable safety buffer.

Default:

SLBuffer = 5 pips

The EA must calculate the correct price distance according to the symbol's point/tick specifications.

The developer must ensure the EA respects the broker's minimum stop distance.


12. TAKE PROFIT

V1 should use Risk/Reward based Take Profit.

Default:

Risk/Reward = 1:2

Example:

If the distance between entry and Stop Loss is 20 pips:

BUY:
SL = 20 pips
TP = 40 pips

SELL:
SL = 20 pips
TP = 40 pips

Input:

RiskReward = 2.0

The Risk/Reward ratio must be configurable.


13. RISK MANAGEMENT

The EA must support percentage-based risk.

Default:

Risk per trade = 1%

The EA must calculate the lot size automatically from:

- Account equity/balance
- Risk percentage
- Stop Loss distance
- Symbol tick value
- Symbol tick size
- Broker minimum lot
- Broker maximum lot
- Broker lot step

Input:

RiskPercent = 1.0

The user must also have an option to use fixed lot size.

Input:

LotMode:
- Risk Percent
- Fixed Lot

Default:

Risk Percent


14. MAXIMUM OPEN TRADES

V1 should allow only one open trade per symbol and Magic Number by default.

Input:

MaxOpenTrades = 1

The EA must not continuously open multiple trades from the same setup.


15. DUPLICATE SIGNAL PROTECTION

Once a setup has triggered a trade, the EA must not repeatedly enter the same setup.

A new trade should require a new valid Fibonacci setup and new confirmation.

This is important to prevent multiple entries from the same signal.


16. MAXIMUM SPREAD

Include a spread filter.

Input:

MaxSpreadPoints

Default value can be recommended by the developer based on the symbol, but it must be configurable.

If spread is above the configured maximum:

DO NOT OPEN A NEW TRADE.

Existing trades should not automatically be closed just because the spread increases.


17. TRADING HOURS

Include an optional trading-session filter.

Inputs:

EnableTradingHours = true/false
StartHour
EndHour

The EA must use broker/server time.

If the current time is outside the configured trading session, the EA must not open new trades.

Existing trades may continue to be managed normally.


18. BREAK-EVEN

V1 should include a simple optional break-even function.

Input:

EnableBreakEven = true/false

Default:

false

If enabled:

When price reaches +1R:

Move Stop Loss to entry price.

Include optional buffer:

BreakEvenBuffer


19. TRAILING STOP

For V1:

Trailing stop should be OPTIONAL.

Default:

Disabled.

If implemented, use a simple fixed-distance trailing stop.

Input:

EnableTrailingStop
TrailingStopPoints

The trailing stop must never increase risk after a trade has been opened.


20. DAILY LOSS PROTECTION

Include a basic daily loss protection feature.

Inputs:

EnableDailyLossLimit = true/false
DailyLossLimitPercent

Default:

Disabled unless configured.

If the configured daily loss limit is reached:

- Do not open additional trades for the rest of the trading day.
- Existing trades should continue to be managed normally.

The developer must clearly define how the trading day is calculated using broker/server time.


21. MAGIC NUMBER

The EA must have a unique configurable Magic Number.

Default:

MagicNumber = 26001

The EA must manage only positions belonging to its Magic Number and symbol.

It must not interfere with manually opened trades or trades from another EA.


22. TRADE COMMENT

All trades opened by the EA should have a recognizable comment:

Precision Entry Pro V1


23. EXECUTION

The EA must check before placing an order:

- Trading is allowed.
- Symbol is tradeable.
- Spread is acceptable.
- Lot size is valid.
- Stop Loss is valid.
- Take Profit is valid.
- Broker stop-level requirements are respected.

If an order fails, the EA must report the relevant error in the Experts/Journal log.

The EA must not create duplicate trades after an execution error.


24. BROKER COMPATIBILITY

The EA must correctly handle different:

- Digits
- Point sizes
- Tick sizes
- Tick values
- Minimum lots
- Maximum lots
- Lot steps
- Stop levels

The developer must not hard-code Forex assumptions that would cause incorrect lot calculations.


25. SYMBOLS

V1 should be designed to work with:

- EURUSD
- GBPUSD
- XAUUSD

The EA should be coded generically so it can be attached to other compatible symbols.

XAUUSD must receive particular attention because its contract specifications and point/tick values can differ from Forex pairs.


26. DASHBOARD

A simple optional chart dashboard is requested.

Display:

Precision Entry Pro V1

Trend:
Bullish / Bearish / Neutral

Current Price

Fibonacci Zone:
Active / Inactive

Spread

Risk %

Open Trades

EA Status:
Trading / Waiting / Outside Session

The dashboard can be basic.

It must not interfere with trading performance.


27. ALERTS

For V1, alerts should be simple and optional.

When a valid setup appears:

- Optional MT5 alert
- Optional push notification

When a trade opens:

- Optional notification

Inputs:

EnableAlerts
EnablePushNotifications


28. NO NEWS FILTER IN V1

Do NOT implement an external news service in V1.

The news filter can be considered for V2.

This keeps V1 simpler and reduces external dependencies.


29. NO MULTI-TIMEFRAME FILTER IN V1

V1 should use one configurable trading timeframe.

Multi-timeframe analysis can be added in V2 after the basic system has been properly tested.


30. NO MARTINGALE

Absolutely no:

- Martingale
- Recovery multiplier
- Increasing lot size after a loss
- Grid
- Unlimited averaging
- Loss recovery system

Lot size must remain based on the configured risk-management rules.


31. SIGNAL FREQUENCY

The EA should evaluate the strategy once per newly formed candle rather than repeatedly generating the same signal on every tick.

Tick-level monitoring may be used only for execution/management after a valid setup has been identified.

This is to reduce duplicate signals and make the strategy behavior easier to test.


32. STRATEGY LOGIC SUMMARY

BUY:

1. New candle forms.
2. Check trend.
3. 50 EMA must be above 200 EMA.
4. Price must be above the 200 EMA.
5. Identify valid bullish swing low and swing high.
6. Calculate Fibonacci retracement.
7. Wait for price to enter 50%-61.8% zone.
8. Wait for bullish rejection OR bullish engulfing confirmation.
9. Confirmation candle must close.
10. Wait for price to break confirmation candle high.
11. Calculate Stop Loss.
12. Calculate lot size according to risk percentage.
13. Calculate Take Profit at configured R:R.
14. Check spread and trading filters.
15. Open BUY.
16. Manage Break-Even if enabled.
17. Manage trailing stop if enabled.


SELL:

1. New candle forms.
2. Check trend.
3. 50 EMA must be below 200 EMA.
4. Price must be below the 200 EMA.
5. Identify valid bearish swing high and swing low.
6. Calculate Fibonacci retracement.
7. Wait for price to enter 50%-61.8% zone.
8. Wait for bearish rejection OR bearish engulfing confirmation.
9. Confirmation candle must close.
10. Wait for price to break confirmation candle low.
11. Calculate Stop Loss.
12. Calculate lot size according to risk percentage.
13. Calculate Take Profit at configured R:R.
14. Check spread and trading filters.
15. Open SELL.
16. Manage Break-Even if enabled.
17. Manage trailing stop if enabled.


33. DEFAULT SETTINGS

Please use these default settings for V1:

EA Name:
Precision Entry Pro V1

Timeframe:
M15

Fast EMA:
50

Slow EMA:
200

Swing Lookback:
50

Fibonacci Entry Zone:
50% - 61.8%

Risk:
1%

Risk/Reward:
1:2

SL:
Swing-based + 5 pip buffer

Max Open Trades:
1

Break-Even:
Disabled

Trailing Stop:
Disabled

Daily Loss Limit:
Disabled

Trading Hours:
Configurable

Spread Filter:
Enabled

Confirmation:
Bullish/Bearish Engulfing OR Rejection Candle


34. TESTING REQUIREMENTS

The developer must test the EA using MT5 Strategy Tester.

Testing should be performed on historical data before delivery.

At minimum test:

EURUSD
GBPUSD
XAUUSD

Recommended timeframe:

M15

The developer should provide the tester report/results showing:

- Initial deposit
- Net profit/loss
- Number of trades
- Win rate
- Profit factor
- Maximum drawdown
- Gross profit
- Gross loss
- Average win
- Average loss

The developer must not claim that historical backtest results guarantee future profits.


35. VISUAL TESTING

Please perform visual testing in MT5 Strategy Tester where possible.

I want to verify that:

- Fibonacci levels are placed correctly.
- Entries occur only after confirmation.
- BUY entries follow BUY rules.
- SELL entries follow SELL rules.
- Stop Loss is placed correctly.
- Take Profit is placed correctly.
- No duplicate trades are opened.


36. SOURCE CODE

The final delivery must include:

1. .mq5 source code
2. Compiled .ex5 file
3. Any required supporting files
4. Default .set file
5. Installation instructions
6. Input/settings explanation
7. Backtest report

The .mq5 source code must be editable in MetaEditor.

The EA must compile without errors.


37. CODE QUALITY

The developer must provide clean and understandable MQL5 code.

Please avoid unnecessary external libraries or DLLs.

No hidden trading logic.

No hidden account restrictions.

No undisclosed external services.

Any external dependency must be disclosed before implementation.


38. ACCEPTANCE TEST

The project will be considered complete when the EA demonstrates all of the following:

- Compiles successfully.
- Opens valid BUY trades.
- Opens valid SELL trades.
- Correctly identifies the trend.
- Correctly calculates Fibonacci levels.
- Correctly detects the configured confirmation.
- Waits for the confirmation candle to close.
- Enters on confirmation breakout.
- Correctly calculates Stop Loss.
- Correctly calculates Take Profit.
- Correctly calculates risk-based lot size.
- Respects maximum open trades.
- Respects maximum spread.
- Respects trading hours.
- Prevents duplicate entries.
- Break-Even works when enabled.
- Trailing stop works when enabled.
- Daily loss protection works when enabled.
- Magic Number works correctly.
- Does not interfere with other trades.
- Strategy Tester runs successfully.


39. IMPORTANT

This EA is a mechanical implementation of the rules above.

The developer must not add additional entry conditions, indicators, martingale, grid, averaging, or other trading logic without my approval.

If any requirement is technically ambiguous, please ask before implementing it rather than making a major assumption.

The objective of V1 is a clean, testable core version of Precision Entry Pro EA.

Future features such as:

- Multi-timeframe confirmation
- News filter
- Advanced market

Responded

1
Developer 1
Rating
(111)
Projects
184
25%
Arbitration
25
16% / 76%
Overdue
16
9%
Free
2
Developer 2
Rating
(287)
Projects
359
29%
Arbitration
37
27% / 65%
Overdue
10
3%
Working
3
Developer 3
Rating
(17)
Projects
21
19%
Arbitration
5
40% / 40%
Overdue
0
Free
4
Developer 4
Rating
(319)
Projects
572
35%
Arbitration
83
31% / 45%
Overdue
207
36%
Working
5
Developer 5
Rating
(437)
Projects
647
53%
Arbitration
35
63% / 20%
Overdue
7
1%
Working
6
Developer 6
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
7
Developer 7
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
8
Developer 8
Rating
(22)
Projects
30
40%
Arbitration
8
25% / 38%
Overdue
2
7%
Busy
Published: 8 articles, 35 codes
9
Developer 9
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
10
Developer 10
Rating
(2)
Projects
2
0%
Arbitration
1
0% / 100%
Overdue
0
Free
11
Developer 11
Rating
(9)
Projects
16
19%
Arbitration
2
0% / 50%
Overdue
3
19%
Loaded
12
Developer 12
Rating
(465)
Projects
815
49%
Arbitration
75
21% / 51%
Overdue
142
17%
Free
13
Developer 13
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
Published: 1 code
14
Developer 14
Rating
(20)
Projects
26
38%
Arbitration
3
33% / 67%
Overdue
3
12%
Free
15
Developer 15
Rating
(2)
Projects
3
67%
Arbitration
0
Overdue
0
Working
Published: 2 codes
16
Developer 16
Rating
(624)
Projects
731
34%
Arbitration
48
52% / 40%
Overdue
14
2%
Working
17
Developer 17
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
18
Developer 18
Rating
(1)
Projects
1
0%
Arbitration
0
Overdue
0
Free
Published: 2 codes
19
Developer 19
Rating
(74)
Projects
98
57%
Arbitration
5
80% / 20%
Overdue
4
4%
Loaded
20
Developer 20
Rating
Projects
0
0%
Arbitration
1
0% / 100%
Overdue
0
Free
21
Developer 21
Rating
(3)
Projects
3
67%
Arbitration
0
Overdue
0
Free
Published: 6 articles, 1 code
22
Developer 22
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
23
Developer 23
Rating
(10)
Projects
12
33%
Arbitration
0
Overdue
2
17%
Working
Published: 1 code
24
Developer 24
Rating
(13)
Projects
23
39%
Arbitration
8
0% / 50%
Overdue
4
17%
Free
25
Developer 25
Rating
(212)
Projects
275
21%
Arbitration
25
52% / 16%
Overdue
0
Working
26
Developer 26
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
Published: 4 codes
27
Developer 27
Rating
(11)
Projects
18
33%
Arbitration
0
Overdue
1
6%
Working
28
Developer 28
Rating
(16)
Projects
30
40%
Arbitration
3
33% / 67%
Overdue
7
23%
Working
Similar orders
​ Indicators: Fast MA (Period 10, Exponential) and Slow MA (Period 50, Exponential). ​ Buy Signal: When Fast MA crosses above Slow MA. ​ Sell Signal: When Fast MA crosses below Slow MA. ​ Risk Management & Parameters: ​Customizable Lot Size (Default: 0.01). ​Stop Loss (SL) and Take Profit (TP) in pips. ​Trailing Stop options. ​Max Spread filter. ​ Platform: MetaTrader 5 (MQL5)
A robot 30+ USD
Je souhaite trouver un développeur pour réaliser ce travail et effectuer les paiements via cette application. Je m'engage à ne communiquer avec les candidats que par cette application, y compris par messageries tierces, correspondance personnelle ou courriel. Je comprends que toute personne ne respectant pas ces conditions sera interdite de publier des commandes sur la plateforme Freelance
I am looking for an experienced MQL5/MT5 developer to develop a custom Expert Advisor based on a complete technical architecture already prepared by the client. This is not a request to design a trading strategy from scratch . The strategy architecture, entry/exit concepts, filters, risk-management requirements and testing requirements are already documented. The main responsibility will be MQL5 development
EAs 100+ USD
To apply, you must already have your EA running on an active MT5 trading account connected to the market. The account must have genuine trading history that can be independently reviewed and verified. EA Requirements 1. Prop-Firm Compatible Risk Management - The EA must include daily and overall drawdown protection. - Required inputs: "MaxDailyLoss = 5%" "MaxTotalDrawdown = 10%" - Once either limit is
Strategy 40 - 60 USD
yo i have a strategy i would really like to turn into a signal bot basically please this is very technical and serious to me the strategy needs more time 1 time frame and the bot most be 100% accurate
Ready to use bot 100+ USD
seller must provide the following to be considered... i will answer to all who fit this description, and can purchase more than 1 EA... - brief strategy description - overall EA expectancy - 1 week limited trial version, with whatever settings you consider best (can be blocked on demo, i don't really care) - investor password from a reputable broker (if history is available... live / demo, same thing, doesn't really
I want you to develop a professional HFT trading robot for MT5/MQL5 , initially focused on XAUUSD . The robot should be designed for high-speed tick-level trading , analyzing real-time bid/ask movement, spread, tick velocity, momentum, volatility, price acceleration and short-term market microstructure to identify very short-term opportunities. The core strategy should be capable of opening 5–10+ positions in a
can you help me use a Tickblaze Algo NRBO on the NT platform? I have it somewhat set up, but I have other questions about running it & knowing how to operate it in NT. Thank you if anyone have experience in this kindly bib and let do it asap
I need a fully automated custom Expert Advisor for MetaTrader 5 (MQL5). The EA is intended for use on a The5ers $100,000 2-Step prop-firm account. IMPORTANT DELIVERY REQUIREMENT: I must receive the complete editable .mq5 source code as well as the compiled .ex5 file. Compiled-only delivery is NOT acceptable. The EA must be coded specifically for this project and must not copy trades, use external trading signals or
I've got a Pine Script from Trading View. I need help from a programmer who can help with optimising the strategy by 1) Adding a couple of further rules 2) Redesign the trading alert arrows & colours I need, please, a programmer who is 1) Good at Pine language 2) Has excellent after-job support (not for free though) 3) Possess the ability to work with others. 4) Able to deliver the job at the shortest possible time

Project information

Budget
50 - 150 USD
Deadline
from 5 to 10 day(s)

Customer

Placed orders1
Arbitrage count0