Pipsgrowth EX12030 MultiIndicatorConfluence

Pipsgrowth EX12030 MultiIndicatorConfluence ships with the same retry-wrapper plumbing the rest of the EX12 family uses, and nothing else. The 111-line source is a starting skeleton — identity inputs, three CTrade retry helpers, empty OnInit/OnDeinit/OnTick stubs, and a header brief that names a 12-layer architecture the file does not implement. Anyone attaching it to a live chart with default inputs will see the EA register, accept ticks, and never place, modify, or close a single position. That is not a bug; it is the deliverable. The file is meant to be forked, not run.

The input block is two declarations long. InpMagic defaults to 22212030, a number that follows the EX12 family convention: the prefix 22212 is the family ID, the suffix 030 is this specific EA's slot. Sibling EAs use 22212010, 22212020, 22212027, 22212028, 22212029 and so on, so two EX12 EAs running on the same account can coexist without their position-management code stomping on each other's tickets. InpTradeComment defaults to the literal string "Psgrowth.com Expert_12030" and is the comment that would appear in the deal-history field on any order the developer eventually adds. Neither input has any effect on the current build. The retry wrappers do not call SetExpertMagicNumber, and there is no code path that reads InpTradeComment. Both are placeholders that the developer is expected to wire up when they add the entry layer.

The three functions are the only executable surface in the file. TryClose_EX12030, TryClosePartial_EX12030, and TryModify_EX12030 are driven by a per-EA CTrade instance declared at file scope as g_trade_wrappers_EX12030. The naming pattern — wrappers suffixed with the magic number — is reused across the family, and it is what lets two EX12 EAs share a chart without colliding on the global CTrade object. Each helper attempts the operation up to three times before giving up. The close wrappers (full and partial) sleep 200 milliseconds between attempts and treat four retcodes as transient: TRADE_RETCODE_REQUOTE, TRADE_RETCODE_TIMEOUT, TRADE_RETCODE_PRICE_OFF, and TRADE_RETCODE_PRICE_CHANGED. The modify wrapper sleeps 100 milliseconds and accepts only two: TRADE_RETCODE_REQUOTE and TRADE_RETCODE_TIMEOUT. The asymmetry is deliberate. A close that gets a PRICE_CHANGED reply is still trying to close at market — the broker is telling the EA the price moved, which is exactly when retrying makes sense. A modify that gets PRICE_CHANGED is the broker suggesting a different SL or TP than the EA requested, and retrying tends to push stale levels back into the order. Flattening this asymmetry — for example by making the modify wrapper retry on PRICE_CHANGED — usually produces positions whose stops are repeatedly clobbered with old values. Anyone extending the file should keep the four-versus-two split as-is.

The header brief names a 12-layer architecture the file does not implement: REGIME, SIGNAL, ENTRY, CONFIRM, NO-TRADE, CAPITAL CAP, RISK, SIZING, MANAGE, EXIT, SCALING, OnTester. The vocabulary is consistent across the EX12 family. REGIME classifies the market state (trend, range, volatility regime). SIGNAL reads the raw indicator output. ENTRY is the trigger that fires a trade. CONFIRM is a second-pass filter — ADX above threshold, volume above average, that kind of thing. NO-TRADE is the gate that blocks entries when spread, slippage, or session is wrong. CAPITAL CAP is the absolute position ceiling. RISK is per-trade risk in percent. SIZING is the lot calculation that turns the risk number into a concrete volume. MANAGE is the trailing-stop, break-even, and dynamic-lock-profit module. EXIT is the close logic. SCALING is the add-to-winner or pyramid module. OnTester is the OnTester() function that produces the optimization fitness score. In EX12030 every one of those layers is a label in the brief, not code in the file. There are no indicator handles — zero — and no signal logic that would feed them.

The three event handlers are empty by design. OnInit returns INIT_SUCCEEDED with a blank body — no iMA or iRSI handles created, no SetExpertMagicNumber call, no timer registration. OnDeinit takes the standard const int reason parameter and returns without acting. OnTick is three lines including the comment delimiter and the closing brace. A working 12-layer EA would normally seed OnInit with the indicator handles the SIGNAL layer needs, populate OnTick with a per-tick decision loop that reads those handles, runs the signal through the regime and confirm gates, sizes the lot, and dispatches the resulting order through the retry wrappers, and clean up in OnDeinit. EX12030 does none of that. The wrapper functions are present, but nothing in the file calls them, and that is the point: the developer is supposed to drop the entry code into OnTick and reach for TryClose_EX12030, TryClosePartial_EX12030, and TryModify_EX12030 from their position-management code without having to write the retry plumbing from scratch.

For a trader evaluating EX12030, the honest summary is that there is no strategy here. Backtesting the file over any date range on any symbol produces zero trades, because OnTick never asks for one. The file is a reference starting point — useful for a developer who wants a known-compiling 12-layer skeleton with the EX12 retry semantics already in place, useful as a teaching artifact for someone learning how the family structures its CTrade wrappers and identity inputs, and useful as a baseline for any code-generation workflow that needs a clean compile to seed from. It is not a turnkey multi-indicator confluence system. The EAs in the same family that do wire the 12 layers into a working strategy are EX12027, EX12028, and EX12029; EX12030 is what those files would look like if you stripped out everything except the boilerplate.

The 100-dollar minimum balance and XAUUSD M5-H1 default pair in the EA's metadata are inherited from the family default, not from this file's behavior. EX12030 does not consume margin because it does not place orders, so the minimum-balance figure is a placeholder for the developer to keep or override. The M5-H1 designation is the timeframes the indicator stack is most likely to be tuned for once one is added, since the rest of the EX12 family is built around those bars. Until then, those numbers are suggestions about what the file would be calibrated for, not constraints on what the empty skeleton does.