MT5 Expert Advisor Phase 1 — Active Development

Paksa Hunter Pro

Native MT5 Expert Advisor — SMC, 3CS, Order Blocks, FVG & Adaptive Market Intelligence

13 Pipeline Stages
3-Leg TP System
7 Market States
0 DLL Required
Active Development
Market Forex Majors, Gold (XAUUSD), Synthetic Indices
Platforms MetaTrader 5 (Native), Exness, XM Trading, Any MT5 Broker
MQL5 Native No DLL No Python No Server ALGLIB ML (Planned) One EX5 File
Get Early Access
Overview

Paksa Hunter Pro is a native MetaTrader 5 Expert Advisor that translates a documented Smart Money Concepts trading methodology into a deterministic, auditable, risk-governed execution system. No Node.js. No Python. No DLL. No external server. One EX5 file — attach it to your MT5 chart and it runs entirely inside MetaTrader 5.

The EA is built around the principle that Observation ≠ Signal ≠ Trade. A detected market pattern never automatically becomes an order. Every setup candidate passes a 13-stage authorization pipeline — market structure, liquidity, zones, setup detection, confluence, news gate, volatility gate, spread gate, risk governor, execution validation, OrderCheck, and OrderSend — before a single lot reaches the broker.

The architecture explicitly distinguishes 7 market context states (NORMAL, PRE_NEWS, NEWS_SHOCK, POST_NEWS, VOLATILITY_EXPANSION, VOLATILITY_DECAY, NORMALIZATION) and adapts its behavior to each. The EA is designed for prop-firm compliance, VPS operation, and MQL5 Market distribution.

Decision Pipeline

Every trade candidate passes through every stage. Any stage can reject and record why.

01
Market Structure (HH/HL/LH/LL)
02
Trend Direction Gate
03
S&D / OB / FVG Location
04
Setup Detection (3CS/Sweep/Reversal)
05
Momentum Confirmation
06
News Regime Verification
07
Spread & Volatility Gate
08
Position & Exposure Check
09
Price / SL / TP Calculation
10
Margin & Risk Computation
11
Risk Governor Authorization
12
Execution Governor Validation
13
OrderCheck u2192 OrderSend

Every stage can reject the candidate and record the reason. No-trade is a valid terminal state. The system records rejection reasons — not just the absence of an order. Duplicate protection: one order per SetupId, no retries on rejected setups.

How It Compares

Typical MT5 EAPaksa Hunter Pro
Indicator crossover = trade 13-stage pipeline u2014 any stage can reject and record why
Fixed stop loss in points Dynamic SL from structure: OB low, sweep wick, zone boundary + buffer
No news awareness u00b115 min blackout + Tier-1 u00b130/45 min + PROP_COMPLIANCE u00b12 min mode
Blows up on spread spikes (gold rollover) Hard spread gate + rollover blackout + Friday cutoff
Loses TP stage on VPS restart TP stage restored from MT5 deal history u2014 no repeated partial closes
Requires DLL or external server 100% native MQL5 u2014 no DLL, no Python, no server, one EX5
Fails prop-firm rules Breach-aware sizing, daily DD lock, max DD lock, PROP_COMPLIANCE news mode
Averages down (martingale) No martingale, no grid, no hedging abuse u2014 ever
Single take-profit TP1 (34%) + TP2 (33%) + TP3 (33%) with break-even and trailing
No audit trail Full decision lineage: SetupId, retcode, reason codes, deal matching

Problems Paksa Hunter Pro Solves

Your EA breaches the prop firm daily loss limit

Breach-aware sizing calculates whether the new trade's worst-case loss plus all existing open risk would exceed the remaining daily allowance. If it would, the lot size is trimmed or the trade is refused. One trade cannot breach the limit. Daily DD lock persists across VPS restarts via MT5 Global Variables.

Gold spreads spike to 50 pips at rollover and your EA trades into it

The maximum spread gate blocks execution when Spread > InpMaxSpreadPoints. The rollover blackout prevents new entries around the daily close and reopen. The Friday cutoff stops new entries before the weekend. All configurable per symbol with gold-appropriate defaults in the PropFirm preset.

Your EA forgets its TP stage after a VPS restart

The TP stage is restored from MT5 deal history after any restart, timeframe change, symbol change, or terminal kill. The EA identifies its own close deals by magic number and DEAL_REASON_EXPERT. An unfinished close order defers the rebuild. No repeated partial closes. No lost final legs.

The MQL5 Market rejects your EA for DLL imports or invalid stops

No DLL imports. Filling mode is auto-detected from the symbol (IOC u2192 FOK u2192 RETURN). Stop distances are validated against the broker's TRADE_STOPS_LEVEL and TRADE_FREEZE_LEVEL before submission. Volume is normalized to the broker's minimum, maximum, and step. OrderCheck runs before every OrderSend.

Your EA trades during NFP and blows the prop firm account

News Filter v2 supports PROP_COMPLIANCE mode: all EA-initiated operations (TP partial closes, break-even, trailing, opposite-signal closes) are frozen within u00b12 min of high-impact events. Pending orders are cancelled before the window opens. Calendar health check fails closed when zero events are detected.

You cannot tell why your EA did not trade

Every rejection is recorded with a reason code: which stage blocked it, what the measured value was, and what the threshold was. The dashboard shows the last decision and rejection reason. The journal records SetupId, symbol, state, action, reason, and retcode for every candidate.

Operating Modes

PH_MODE_MANUAL

Autonomous entry disabled. Operator submits risk-calculated BUY/SELL orders via dashboard ticket with OrderCheck dry-run preview.

PH_MODE_AUTO

Full autonomous evaluation, risk validation, entry submission, and trade lifecycle. All 13 pipeline stages active.

PH_MODE_MIXED

Strategy trades autonomously while operator can place manual trades or trigger manual overrides (BE, Close All).

KILL SWITCH

Halts all automated trading immediately, sets persistent lock, flattens all managed positions. Survives restarts.

7 Market Context States

The EA explicitly distinguishes these states — they are descriptive, not automatic trade signals.

NORMAL

Standard conditions u2014 full 13-stage pipeline active, all setups evaluated

PRE_NEWS

High-impact news approaching u2014 new entries blocked, pending orders cancelled

NEWS_SHOCK

News event active u2014 all execution blocked, no opens or closes

POST_NEWS

Post-news reaction u2014 selective re-entry after spread and volatility normalize

VOLATILITY_EXPANSION

ATR/Baseline > threshold u2014 entry gate active, no new positions

VOLATILITY_DECAY

Volatility normalizing u2014 cautious re-entry evaluation with tighter criteria

NORMALIZATION

Market returning to normal u2014 standard pipeline resuming after confirmation

Configuration Presets

Pre-built .set files for common trading scenarios. Load and go.

Paksa_PropFirm_SafeCapital
FTMO/The5ers compliant u2014 daily DD lock ON, max DD lock ON, breach-aware sizing, PROP_COMPLIANCE news mode, spread gate ON
PaksaHunterPro_Balanced
Balanced risk/reward for standard live accounts u2014 1% risk per trade, all safety gates enabled
PaksaHunterPro_Aggressive
Higher risk tolerance for experienced traders u2014 2% risk, wider TP targets, trailing after TP1
Paksa_Gold_Optimized_M15
XAUUSD M15 u2014 gold-appropriate spread settings, rollover blackout, Tier-1 news u00b130/45 min windows
Paksa_Forex_Majors_H1
Major Forex pairs on H1 u2014 session-filtered, standard news u00b115 min, conservative lot sizing

Algorithmic trading involves substantial risk of loss. Past performance does not guarantee future results. Paksa Hunter Pro is a technical system, not financial advice. Always validate with paper trading before live deployment.

Get Started

Ready to trade smarter with Paksa Hunter Pro?

Contact us to request early access or learn more about how Paksa Hunter Pro can work for your trading strategy.