Pipsgrowth EX12012 MultiIndicatorConfluence

Average Force zero-cross, Andean Oscillator envelope, and MACD direction all need to align before this EA will fire a single trade on XAUUSD M5. The architecture is a four-clause confirmation system: nothing is placed unless every leg agrees.

The Average Force component is a smoothed Force Index computed inside GetSignal() as a simple moving average of iForce(). The default reads InpForcePeriod=20 bars of raw force, then averages the last InpForceSmooth=9 readings to produce AF(1) and AF(2). The function does not use the InpForceMethod input for the smoothing — that parameter is declared but unused in the current build, and the SMA path is what actually runs. The signal only cares whether AF crossed zero on the latest bar: AF(2) below zero and AF(1) above zero is the bull trigger, the opposite is the bear trigger.

The Andean Oscillator is built from scratch in CalculateAndeanOscillator(). With InpAndeanPeriod=50 the function walks back 3×50 = 150 bars from the requested shift, seeds the bull envelope with the close at that seed point, then iterates forward applying alpha = 2 / (period + 1) = 2/51 ≈ 0.0392. On each step the bull leg uses MathMax(close, open) — a proxy for bullish bar extension — and the bear leg uses MathMin(close, open). When the new value exceeds the current envelope, the envelope jumps to the new high; otherwise it decays exponentially toward the new low. The output is two envelope series whose relationship (bull > bear or bear > bull) defines the oscillator's directional bias.

The third leg is a standard iMACD(12, 26, 9) main line. The header brief lists Stochastic as a fourth confirmation, but the code never instantiates iStochastic. The actual fourth clause is the slope of the MACD main line itself. For a long, both md_main_1 and md_main_2 must be positive AND md_main_1 must be greater than md_main_2 — i.e. the MACD is rising while above zero. Sell is the mirror: both values negative and the more recent value lower than the older one.

Combining the four clauses in GetSignal() produces a buy iff: AOS_bull > AOS_bear on shift 1, AF(2)<0 AND AF(1)>0, MD(2)>0 AND MD(1)>0, AND MD(2)<MD(1). Sell is the strict negation across all four. The signal is then handed to OnTick(), which calls CheckPyramidSafety() before any CTrade.Buy/CTrade.Sell fires. InpReverseSignal=false by default; flipping it to true swaps the buy and sell branches, which can be useful when gold's regime is mean-reverting rather than trending.

Trade management is split across three independent modules. Lot sizing in GetLotSize() defaults to 1% of account balance (InpRiskPercent=1.0) per trade, computed as risk_money / (sl_points × tick_value_per_point), then snapped to the broker's lot step and capped at InpMaxLotSize=10 lots. Setting InpRiskPercent=0 falls back to InpFixedLot=0.01 — also the broker minimum that takes over when risk-based sizing underflows.

Stop loss and take profit are fixed-point inputs rather than ATR-derived despite what the file header implies: InpStopLoss=500 points and InpTakeProfit=1000 points, giving a hard 1:2 risk-to-reward geometry. Slippage is capped at InpSlippage=30 points via m_trade.SetDeviationInPoints().

The safe-pyramid module, CheckPyramidSafety(), is the most distinctive design choice. With InpUsePyramid=true the EA permits up to InpMaxPyramidTrades=3 simultaneous positions on the same symbol, all sharing magic 22212012. Three preconditions gate every additional entry: (a) all existing positions must be in the same direction as the new signal — opposing-direction exposure is rejected outright, which means the EA cannot be net long and net short at the same time; (b) each existing position must have a stop loss set on the trade server; (c) the distance from entry to stop must be at least InpPyramidMinProfit=100 points. That last rule is the safety hinge — the EA will not pyramid into a position whose stop is below the entry. New entries must also be at least InpPyramidMinDist=200 points from the most recent entry price. With InpUsePyramid=false the EA collapses to a strict one-position-at-a-time mode.

Profit protection runs in ManageProfitLock(). When InpUseProfitLock=true and a position has gained at least InpLockTrigger=300 points, the EA moves the stop to InpLockDistance=100 points behind the current bid/ask — but only when the implied movement exceeds InpLockStep=50 points. The effect is a step-ratchet: tiny fluctuations under 50 points do not trigger constant modifications, but once the lock has stepped up, it never steps back down. This is a simpler design than a swing-based or ATR-based trail; the developer is trading smoothness-of-modification for a hard floor on locking.

The time filter (IsTradingTime()) defaults to InpStartTime="08:00" and InpEndTime="20:00" server time, with InpUseTimeFilter=true. Outside this window the EA updates the dashboard with "Market Closed" and does not place new orders. InpCloseAtEnd=false by default, so existing trades are allowed to run past 20:00 unless the user flips it. The clock comparison supports overnight windows by branching when start > end.

Order execution uses the standard CTrade wrapper with SetTypeFilling(ORDER_FILLING_FOK), magic 22212012, and 30-point slip deviation. Close and modify operations go through TryClose_EX12012() and TryModify_EX12012() retry helpers — three attempts with 200ms sleep on REQUOTE/TIMEOUT/PRICE_OFF/PRICE_CHANGED for close, and 100ms sleep on REQUOTE/TIMEOUT only for modify. PRICE_CHANGED is not retried in modify — an asymmetric design. New-candle gating in OnTick() uses a static last_bar timestamp so signals are evaluated exactly once per M5 bar open, not on every tick.

What this EA does NOT do is as important as what it does. There is no news filter, no daily-loss cap, no equity-percent-of-balance guard, no consecutive-loss cooldown, no max-trades-per-day limit, no weekly loss cap, no regime classifier, no ATR minimum filter, no ADX filter, no volume spike detector, no higher-timeframe trend confirmation, and no dry-run flag. The signal is the only source of edge; the safety stack is purely trade-management hygiene. OnTester is not defined, so backtest fitness is the platform default.

In practice, what traders observe is an EA that takes relatively few but tightly-conditioned trades on XAUUSD M5 during the European and US active trading hours. When gold trends, the four-clause combination tends to catch the second or third push of a directional move, and the 1:2 R:R plus step-trail handles the post-entry management. When gold chops, the filter rejects most setups and trade count drops sharply. The safe-pyramid module means trends can scale exposure up to 3 lots, but only when each layer is at least 100 points secured — the EA will not add to a losing position just because price moved 200 points against it.

The most common configuration issue users hit is the slippage cap: 30 points is too tight during high-volatility XAUUSD moments (NFP, FOMC, the London and Geneva gold fixes), and a 500-point SL with 30-point slip tolerance can fill hundreds of points away from the requested price in fast markets. For brokers with wider spreads or higher rejection rates, lifting InpSlippage to 50 or 80 is reasonable. The InpAndeanPeriod default of 50 is also worth examining — pushing it to 30 tightens the envelope and produces more signals, while pushing it to 80 widens it and produces fewer but more durable signals. InpForceSmooth at 9 with InpForcePeriod at 20 is a balance point; lowering the smooth to 5 makes the AF zero-cross noisier, raising it to 14 delays entries by one or two bars.