NOVA SHIELD EA

MQL5 Experts

Job finished

Execution time 21 hours
Feedback from customer
Good job
Feedback from employee
Thanks so much!!!!!

Specification

Platform: MT5 ==> With Source. Experienced Dev required. EA Written for Exness XAUUSD

Platform: MT5 
Version: Final


1. System Overview

NovaShield EA is a Directional Trend Grid Trading System.
The EA trades in only one direction, determined exclusively by the EMA trend:

  • If price is above the 200 EMA → EA opens BUY-only trades

  • If price is below the 200 EMA → EA opens SELL-only trades

All modules—entries, martingale, pyramiding, break-even, trailing, and protection—must strictly follow this direction.


2. Indicator Filters

2.1 EMA Trend Filter (Directional Control)

EMA Period = 200 EMA Shift = 5 Method = Exponential Applied Price = Close

Directional Rule:

If Close > EMA200AllowedDirection = BUY_ONLY If Close < EMA200AllowedDirection = SELL_ONLY


2.2 RSI Filter

RSI Period = 5 Applied Price = Close Overbought Level = 80 Oversold Level = 20

Used for additional entry filtering if RSI filtering is enabled.


2.3 EMA Distance Filter

EnableEmaDistanceFilter = true/false MaxEmaDistancePips = 300

If the price is farther than the allowed distance → no new trades.


3. Entry Logic

A new position is allowed only if ALL filters pass:

  • EMA direction filter

  • Spread filter

  • Time session filter

  • News filter

  • RSI filter (optional)

  • EMA distance filter (optional)

  • Anti-order-spam delay (developer must implement)

Initial Lot

InitialLot = 0.01


4. Position Management Engines

NovaShield EA uses two engines, both strictly following the EMA direction:

  • Martingale Averaging Down Engine

  • Pyramiding Averaging Up Engine


4.1 Martingale Engine (Averaging Down)

Parameters

EnableMartingale = true MartingaleDistancePips = 35 MartingaleMaxOrders = 1000 EnableMartingaleRsiFilter = false

Three-Phase Lot Scaling

Phase Levels Lot Multiplier
Phase 1 Level 2–35 ×1.1
Phase 2 Level 36–100 ×1.0
Phase 3 Level 101+ ×1.1

Martingale Condition

If floating loss ≥ MartingaleDistancePips → Open a new trade in the SAME direction → Lot size = previous_lot × multiplier_of_current_level

Note:

  • Pip calculation must adapt to symbol Digits (XAUUSD vs XAUUSDc).

  • EA must never open opposite-direction martingale.


4.2 Pyramiding Engine (Averaging Up)

Parameters

EnablePyramiding = true PyramidingTriggerPips = 30 PyramidingMultiplier = 1.0 PyramidingMaxOrders = 100

Pyramiding Condition

If the FIRST position's profit ≥ PyramidingTriggerPips → Open a new position in SAME direction → Lot = previous_lot × 1.0 (fixed)


5. Safety & Protection Systems

5.1 Group Break-Even

EnableGroupBEP = true GroupBEP_MinOrders = 1 GroupBEP_Trigger = 15 pips GroupBEP_LockPips = 10 pips

When total floating profit ≥ Trigger →
Move SL of all positions to +10 pips.


5.2 Group Trailing Stop

EnableTrailing = true TrailingTrigger = 80 pips TrailingDistance = 20 pips

When total floating profit ≥ 80 pips → activate group trailing.


5.3 Global Equity Protection (Cut-Loss Shield)

EnableCutLoss = true CutLossEquity = 20000.0

If account equity ≤ CutLossEquity:
→ Close ALL orders immediately
→ Block new entries until equity rises above threshold.


6. Trading Filters

6.1 Time Session Filter

EnableTimeFilter = true StartHour = 09:00 EndHour = 17:00

Outside this window → no new trades.


6.2 Spread & Slippage Filter

EnableSpreadFilter = true MaxSpreadPips = 20.0 EnableSlippageFilter = false MaxSlippagePoints = 30

If spread > MaxSpreadPips → block entry.


6.3 Leverage Filter

EnableLeverageFilter = true RequiredLeverage = 2000

If account leverage < RequiredLeverage → block entry.


6.4 High-Impact News Filter

EnableNewsFilter = true PauseBeforeNewsHrs = 2 PauseAfterNewsHrs = 1

During the news lock window:

  • No new trades

  • No martingale

  • No pyramiding

  • Break-Even / Trailing / SL / Cut-Loss still active

News Source:
MQL5 built-in Economic Calendar (recommended)


7. Order Execution Flow (For Developer)

OnTick: 1. Check Spread 2. Check Time Filter 3. Check Leverage 4. Check News Lock 5. Determine EMA Direction: If Close > EMA → BUY_ONLY If Close < EMA → SELL_ONLY 6. Entry: If no open positions: Apply RSI filter (optional) Apply EMA distance filter (optional) If all conditions valid → open trade in trend direction 7. Martingale: If floating loss ≥ MartingaleDistance: If total orders < MartingaleMaxOrders: open martingale order (same direction) 8. Pyramiding: If first order profit ≥ PyramidingTrigger: open pyramid order (same direction) 9. Risk Management: Apply Group Break-Even Apply Group Trailing Apply Equity Cut-Loss


Hidden Stop Loss (Stealth SL) – Technical Specification (Add-on)

Purpose

A hidden stop-loss system that closes trades internally without placing SL values on the server, preventing brokers from hunting visible stops.


Hidden SL Module – Parameters

EnableHiddenSL = true/false HiddenSL_Pips = X (e.g., 300 pips) HiddenSL_CheckEvery = 1 second (or OnTick)


Hidden SL – Operational Logic

Hidden SL should:

  1. NOT set any visible SL on orders sent to the server.
    → All SL logic must be internal inside the EA.

  2. Continuously check floating loss:

If (Current Floating Loss in pips ≥ HiddenSL_Pips) → Close the individual position immediately
  1. “Pips” must be calculated using the correct Digits of the symbol (XAUUSD vs XAUUSDc).

  2. The module must work independently of:

  • Break-even

  • Trailing stop

  • Equity Cut Loss

  1. Applies to every single order individually:

Each trade has its own internal Hidden SL threshold.

  1. Should NOT trigger during:

  • News Lock

  • Time Filter lock
    (because those filters block entries, not exits)

Hidden SL must always remain active to protect the account.


Hidden SL – Example Logic (Pseudocode)
for each order in Orders: profitPips = CalculatePips(order.open_price, current_price) if (EnableHiddenSL == true) if (profitPips <= -HiddenSL_Pips) CloseOrder(order)

Interaction With Other Modules

Works alongside:

  • Martingale Engine

  • Pyramiding Engine

  • EMA Direction filter

  • Group BE & Trailing

  • Equity Cut-Loss shield

Priority:

If multiple exit conditions trigger simultaneously:

  1. Equity Cut Loss (highest priority)

  2. Hidden SL

  3. Group BE / Trailing Stop

  4. Take Profit


Notes for Developer
  • Must NOT send SL to server.

  • Must NOT modify SL value through OrderModify.

  • Close trades only through internal logic.

  • Must avoid repeated close signals (add small cooldown per order).

  • Works on OnTick (recommended) or timer.

8. Developer Notes

  • Must handle pip/point calculations correctly depending on symbol Digits

  • Must implement retry logic for OrderSend/OrderModify errors

  • Must use SymbolInfo* functions (no deprecated MarketInfo)

  • Must prevent order spamming (minimum tick/time delay between trades)

  • Must ensure compatibility with real ticks & backtesting

  • All trade operations must strictly follow EMA directional filter



Responded

1
Developer 1
Rating
(21)
Projects
27
7%
Arbitration
9
33% / 33%
Overdue
1
4%
Working
1
Developer 1
Rating
(328)
Projects
514
19%
Arbitration
35
46% / 31%
Overdue
34
7%
Working
2
Developer 2
Rating
(45)
Projects
46
24%
Arbitration
34
9% / 85%
Overdue
10
22%
Free
2
Developer 2
Rating
(59)
Projects
73
60%
Arbitration
4
75% / 25%
Overdue
1
1%
Loaded
3
Developer 3
Rating
(62)
Projects
90
29%
Arbitration
24
13% / 58%
Overdue
7
8%
Working
3
Developer 3
Rating
(1)
Projects
2
0%
Arbitration
1
0% / 100%
Overdue
0
Free
Published: 2 codes
4
Developer 4
Rating
(47)
Projects
67
37%
Arbitration
5
40% / 40%
Overdue
1
1%
Free
4
Developer 4
Rating
(144)
Projects
186
41%
Arbitration
24
58% / 21%
Overdue
13
7%
Free
5
Developer 5
Rating
(510)
Projects
977
74%
Arbitration
27
19% / 67%
Overdue
100
10%
Free
Published: 1 article, 6 codes
5
Developer 5
Rating
(169)
Projects
180
46%
Arbitration
3
33% / 33%
Overdue
1
1%
Working
6
Developer 6
Rating
(32)
Projects
42
43%
Arbitration
2
100% / 0%
Overdue
4
10%
Free
7
Developer 7
Rating
(78)
Projects
246
74%
Arbitration
7
100% / 0%
Overdue
1
0%
Free
Published: 1 article
8
Developer 8
Rating
(2)
Projects
3
0%
Arbitration
1
100% / 0%
Overdue
0
Free
9
Developer 9
Rating
(2672)
Projects
3408
68%
Arbitration
77
48% / 14%
Overdue
342
10%
Free
Published: 1 code
10
Developer 10
Rating
(2)
Projects
3
0%
Arbitration
0
Overdue
0
Free
11
Developer 11
Rating
Projects
0
0%
Arbitration
0
Overdue
0
Free
12
Developer 12
Rating
(318)
Projects
565
35%
Arbitration
81
31% / 44%
Overdue
204
36%
Free
13
Developer 13
Rating
(22)
Projects
29
34%
Arbitration
4
50% / 25%
Overdue
5
17%
Working
Similar orders
Online Ordering System para sa Milk Tea Shop* *1. Layunin ng Project* Gumawa ng website at mobile app kung saan makaka-order ang mga customer ng milk tea online. Para hindi na pumila at para mas madali i-track yung mga orders. *2. Mga Kailangan / Features* - *Para sa Customer:* - Mag-register at mag-login gamit ang email at number - Makita ang menu na may picture, presyo, at description - Makapag-customize ng
Hi there developer, I need someone who can create an trading ea that place order in points using an. Vps with an stop loss in 2 point behind the order price automatically it close order in 1 point if the market reverse
I am looking for a highly experienced developer to build a professional, commercial-grade trading indicator for MT4/MT5. I am not looking for a basic indicator or a modified public script. I need a custom solution based on real market logic with high-quality coding standards. Requirements 100% Non-Repainting indicator. Accurate Entry signals. Automatic Stop Loss placement based on real market structure. Automatic
I need a custom MT5 Expert Advisor (MQL5) for XAUUSD. Strategy: 1. Trend Filter (H1) - EMA 20, EMA 50 and EMA 200. - Buy only when EMA20 > EMA50 > EMA200 and price is above EMA200. - Sell only when EMA20 < EMA50 < EMA200 and price is below EMA200. 2. Confirmation (M15) - M15 trend must confirm the H1 trend before taking any trade. 3. Entry (M5) - Wait for price to pull back to EMA20 only. - After touching EMA20, wait
Mac200 50+ USD
I need a Trend following Bot. Here we took entries by looking at two indicator which are 200 period ema and 12 26 9 MacD. Rules for entry exit are: Buy trade: When market is above 200 ema and MacD Line cross over the signal line and this cross over happened below the zero line of MacD indicator. We simply put Buy trade. Sell trade: When market is below 200 ema and MacD line crosses below the signal line and this
I I would like to create a trading robot based on 2 ema crossing. The robot is pretty simple, it should open buy position when fast ema cross slow ema and vise versa. Also it should use martingale after the loss position. It should has expiration period inside the code and alerts l
Iconic Boy 300 - 400 USD
Am looking for a bot to trade .so that I can be able to trade and become very successful and make some profit so that I cannot sleep on a empty stomach
MT5 Global Stop Loss & Take Profit Manager for Manual Trades I need an Expert Advisor (EA) for MetaTrader 5 that manages ONLY existing manual trades. GENERAL REQUIREMENTS - Works only on the current chart symbol (example: XAUUSD). - Supports Hedging accounts. - Detects all manually opened market positions. - Never opens trades automatically. - Never closes trades automatically. - Never places pending orders. - Never
Supply and Demand EA 50 - 250 USD
I need a SnD EA. Prefer coder who has previous experience coding SnD EA. PO are based on (CHoCH or BoS) and 3EMA, order block (from my TradingView indicator), area based on Fibonacci. SL options are based on fix pips or zone size; CL is based on candle closing. TP1 and TP2 options are based on fix pips or fix ratio. Canceling PO is based on market structure or Fibonacci. Money management are based on fix volume or
Hi MQL5 Community, With over 10 years of live market experience as a Quantitative & Trading System Developer, I specialize in building robust, highly scalable Expert Advisors (EAs), custom indicators, and automated architectures. I’ve recently put together a comprehensive showcase demonstrating my flagship Modular Multi-Engine Architecture , designed to bring institutional-grade logic and real-time telemetry into

Project information

Budget
30 - 100 USD