Pipsgrowth EX16032 Trend

EX16032 sits in a different category from every other EA in the EX16xxx lineup. It does not open positions, does not read indicators, does not scan for patterns, and does not gate trades by spread, session, or account equity. The entire program is a passive position manager — a utility that sits on a chart and watches every open position on the account, filters by magic number, and applies a pip-based trailing stop plus an optional chart-line virtual stop-loss and take-profit system. The header's '12-layer architecture' label describes the family template, not this EA's actual function. The wired layers in the source are two: MANAGE (the trailing stop) and EXIT (the virtual stop-loss and virtual take-profit).

The signature design choice is magic-number routing. The MagicNumbers input is a string of comma-separated longs — the default is "22216032", but the operator can pass in any number of upstream EAs at once by listing their magics: "22216001,22216002,22216024,22216030" for example. On OnInit, ParseMagicNumbers() StringSplits the string on commas, trims each token with StringTrim(), converts to long, and stores the result in the global magicNumbersArray[]. IsOurMagicNumber() then does a linear scan over the array on every position check. The intent: a single instance of EX16032 can trail positions opened by multiple signal EAs simultaneously, without ever touching positions opened by other EAs on the same account or by the same EAs running on other symbols.

The trailing stop itself runs in TrailingStop(), which OnTick calls on every price change. The function walks PositionsTotal() in reverse so removals do not disturb the loop, selects each position with positionInfo.SelectByIndex(i), and skips any position whose magic is not in the watched list. For positions that survive the filter, the logic is a textbook pip-step trail. TrailStartPips (50 pips default) is the activation distance — the position must move at least that far in profit before any trailing starts. TrailStopPips (20 pips default) is the trailing distance — once activated, the stop is held at currentPrice plus-or-minus trailStop. TrailStepPips (10 pips default) is the minimum increment — the stop is only ratcheted forward if the new stop is at least trailStep beyond the existing one, which prevents a flood of modify requests on every tick.

pipValue is computed once at OnInit as (SymbolInfoInteger(_Symbol, SYMBOL_DIGITS) % 2 == 1) ? _Point * 10 : _Point — that single expression handles 5-digit FX pairs (1.23456), 4-digit FX pairs (1.2345), 3-digit XAUUSD brokers (1234.567), and 2-digit metal quotes (1234.56) in one branch. The same EA can therefore manage a portfolio of XAUUSD positions, EURUSD positions, and XPTUSD positions without manual pip adjustments per symbol.

The math is straightforward but worth tracing. For a long: if currentPrice - openPrice >= trailStart, the trailing activates. The new stop is computed as NormalizeDouble(currentPrice - trailStop, digits). If a stop already exists, the code checks (currentPrice - trailStop) > currentStop — the new stop must be strictly tighter than the existing one. If the new stop is too close (less than trailStep away), the code bumps the new stop to currentStop + trailStep so it advances by at least one step. For a short, every comparison flips: openPrice - currentPrice >= trailStart, the new stop is currentPrice + trailStop, and the advance check is currentStop - newStop < trailStep. The modify is sent only if newStop != currentStop, going through the 3-attempt TryModify_EX16032() wrapper, which retries on REQUOTE, TIMEOUT, PRICE_OFF, and PRADE_CHANGED with 100ms backoff before giving up.

The virtual stops mechanism is the second major feature. When EnableVirtualStops is true, OnTick calls VirtualStopsDriver("listen") on every tick. The driver scans all OBJ_HLINE objects on the chart, filters to those whose name starts with # and has length at least 5, and whose color is clrRed (virtual SL) or clrBlue (virtual TP). The name is then parsed: the last 2 characters must be sl or tp, and the substring between # and sl or tp is the position ticket. The operator draws two horizontal lines named #12345678 sl (red) and #12345678 tp (blue) and the driver picks them up automatically.

The driver validates each candidate via positionInfo.SelectByTicket(ticket) and IsOurMagicNumber(positionInfo.Magic()) — a virtual stop is ignored if the position is closed, missing, or has a magic outside the watched list. For valid pairs, the driver reads the line's price, computes the polarity from position type (BUY = +1, SELL = -1), and checks if price has crossed the level. A long's virtual SL fires when level is at or below the bid; the virtual TP fires when level is at or above the bid; for shorts the comparisons flip. askbid is read from SymbolInfoDouble for the position's actual symbol, so a manager running on a multi-symbol account reads the correct bid or ask for each position.

The VirtualStopTimeout input (default 0, meaning disabled) adds a delay. If a long's bid drops to the red SL line and VirtualStopTimeout is greater than zero, the EA does NOT close immediately. Instead, it records the current TimeLocal() in the mem_to[] array indexed by ticket, prints "#<ticket> timeout of <N> seconds started", and continues. On subsequent ticks, while TimeLocal() - mem_to[index] is still within VirtualStopTimeout, the close is suppressed. Once the timeout expires, the next touch closes the position. The timeout applies only to virtual SL, not virtual TP. TryClose_EX16032 does the actual close, and on success the driver deletes both the #<ticket> sl and #<ticket> tp horizontal lines from the chart.

The cleanup path handles stale objects. If positionInfo.SelectByTicket(ticket) fails or the magic is not ours, the driver treats the object as orphaned and ObjectDelete(0, name) removes it. Otherwise the lines persist until either the close fires or the operator removes them by hand. The "set" / "modify" / "clear" / "partial" command paths in VirtualStopsDriver are alternative entry points an external script could use to programmatically create or update the lines — none are called from inside this EA, but the API is there for tooling.

The header claims a 12-layer architecture (REGIME, SIGNAL, ENTRY, CONFIRM, NO-TRADE, CAPITAL CAP, RISK, SIZING, MANAGE, EXIT, SCALING, OnTester). Counting only the wired layers in the source: MANAGE is the trailing stop, EXIT is the virtual SL / TP. That is two. REGIME, SIGNAL, ENTRY, CONFIRM, NO-TRADE, CAPITAL CAP, RISK, SIZING, SCALING, and OnTester are all absent. The EA has zero indicator handles — no iRSI, no iMA, no iBands, no iATR. The '12-layer stack' label in the description string is a family-template inheritance that does not describe this EA's actual function.

The seven inputs split into two groups. The Trailing Stop Parameters group is the heart: TrailStartPips=50, TrailStopPips=20, TrailStepPips=10, EnableVirtualStops=true, VirtualStopTimeout=0. The Identity group is the routing: MagicNumbers="22216032", InpTradeComment="Psgrowth.com Expert_16032". pipValue and magicNumbersArray are global-scope; trade, positionInfo, and orderInfo are the CTrade / CPositionInfo / COrderInfo objects the EA uses to talk to MT5. The helpers are minimal: ArraySearch() does a linear scan for a ulong in a ulong[], StringTrim() wraps the MQL string-trim pair, and the three TryXxx_EX16032 retry wrappers. TryClosePartial_EX16032 is defined but never referenced — dead code inherited from the family template.

The deployment context is what makes this EA useful. The strategy EAs in the EX16xxx family all open positions with hard-coded magic numbers, hard-coded SL/TP, and no trailing logic. EX16032 sits on top of them. The operator launches EX16032 on the same chart, sets MagicNumbers to the comma-separated list of EAs to manage, and EX16032 takes over the stop management: it applies a 50 / 20 / 10 pip trail to every open position whose magic is in the list, and lets the trader draw virtual TP lines on the chart that the EA will close on when price hits them. The 50-pip activation distance and 20-pip stop distance are sized for XAUUSD M5 volatility; the same values applied to a slow pair would trail too tight and clip the trend. This is a portfolio-level utility rather than a trade-entry bot: it does not generate signals, does not filter setups, does not size positions. It applies a single mechanical policy — trail with X/Y/Z pips, close at the chart's virtual TP if a line is present — to every position whose magic it has been told to watch.