Pipsgrowth EX12035 MultiIndicatorConfluence

EX12035 puts Ichimoku Kinko Hyo at the centre of the decision tree and bolts a cascade of five optional confirmation filters on top of it. The primary signal is the Tenkan-sen / Kijun-sen cross: a buy trigger requires Tenkan-sen (period 9 by default) to be above Kijun-sen (period 26) on the current bar AND to have been at or below Kijun-sen on the previous bar — that is, a fresh upside cross, not a continuation. The mirror condition fires a sell. This cross is the only mandatory gate. Everything else is a toggle.

The five optional filters are wired as a stack of UseXxxFilter boolean inputs. With them all enabled (the default), a buy has to clear: (1) Chikou Span above bid, (2) Senkou Span A above Senkou Span B (bullish Kumo cloud), (3) bid above both cloud boundaries (price above cloud), (4) current tick volume at least MinVolumeMultiplier (default 1.5) times the 20-bar average, (5) MACD main line above signal line on bar 0 with a cross on bar 1 (MACD 12/26/9), and (6) RSI(14) sitting between 50 and the overbought level (70 default). Each of these five can be switched off individually. With most off, the EA degrades to a pure Tenkan/Kijun crossover, which makes it useful both for traders who want the full Ichimoku confluence filter chain and for traders who want to A/B test the impact of removing individual gates.

The Chikou filter deserves a frank note. The source carries an honest in-code comment that the implementation compares Chikou to the current bid rather than to the price 26 periods ago as a textbook Ichimoku interpretation would. So enabling UseChikouFilter adds a regime gate — Chikou must be above current price for buys, below for sells — but it is not a strict historical Chikou confirmation. The author flagged the shortcut in the code; we flag it here. If you want textbook Chikou discipline, keep the filter off and add your own higher-timeframe Chikou check on the chart.

Position management is deliberately simple. The EA holds one position per side per symbol, magic-numbered 22212035. OnTick runs the cross + filter check; if a buy fires and no buy is currently open, it first closes any open sell via CloseSellPositions() (raw OrderSend with 3-point slippage) and then opens the buy via OpenBuy() with the same fixed lot. The reverse flow mirrors this for sells. SL and TP are attached to the order at entry: 100 points and 200 points by default, a 1:2 risk-to-reward. There is no dynamic SL ratchet, no breakeven move, no scaling-in or pyramiding, no partial close, no time-based exit. The only way a position leaves is SL hit, TP hit, or a fresh cross in the opposite direction.

Lot sizing is fixed at the LotSize input (0.1 default). There is no risk-percentage mode, no balance-based scaling, and no minimum-lot fallback ladder — change LotSize and the EA trades that many lots per entry. The LotSize, StopLoss, TakeProfit, MagicNumber, Slippage, and InpTradeComment group is the only place to tune position economics; everything else is signal logic.

The source declares a CTrade g_trade_wrappers_EX12035 and three retry helpers — TryClose_EX12035, TryClosePartial_EX12035, and TryModify_EX12035 — that handle REQUOTE, TIMEOUT, PRICE_OFF and PRICE_CHANGED with 200ms backoff on close and 100ms on modify, up to three attempts. None of these are called from OnTick; the entry and close paths go through raw OrderSend and a single GetLastError print. The wrappers sit in the file as scaffolding for future partial-close or trailing-stop work but are inert in the current build. Anyone reading the source should treat the file as a single-shot signal architecture, not as a fault-tolerant one — the retry layer is present but not in the call graph.

The EA is portable. The default symbol is XAUUSD with M5 as the suggested timeframe; the header lists FX majors and metals as portable targets and the timeframe range as M5 to H1. Indicators are created in OnInit only for the filters that are enabled — iIchimoku is always created, iMACD and iRSI are conditional on their respective UseXxxFilter booleans, and the volume buffer is only set up when UseVolumeFilter is on. OnDeinit releases whatever handles were allocated. There is no IsNewBar gate — every tick recomputes the signal from the latest two bars of each enabled indicator, which keeps the logic responsive on M5 but is more CPU-hungry than a once-per-bar scheduler.

The honest expectations paragraph: a fully filtered EX12035 on XAUUSD M5 with 1.5x volume filter and 1:2 R:R will produce a low trade frequency — Ichimoku crosses with all five gates aligned are uncommon, and the volume floor alone eliminates most quiet-session setups. Trade frequency in backtest is closer to a swing system than a scalper. Win rate, given the 1:2 R:R and the multi-filter discipline, tends to print below 50% on most symbols — the system is built to let winners run to the 200-point TP while the SL cuts losers short, so the edge is in the asymmetry, not in the hit rate. Filter toggles will materially change both frequency and drawdown profile; UseVolumeFilter = false roughly doubles trade count, and disabling the cloud filter pulls the EA into mean-reversion-like behaviour during chop because the cross fires inside flat Kumo. The recommended path is to leave all five filters enabled for live trading and only disable them in research to isolate which gate is doing the work.