Pipsgrowth EX16079 Trend

Pipsgrowth EX16079 ships as a 119-line MetaTrader 5 file with the file name Pipsgrowth_com_EX16079_ZoneRecovery_XAUUSD_5M.mq5, magic 22216079, and a header block that promises a "zone-based recovery" engine plus a "full 12-layer stack." The on-disk source, however, is a stripped skeleton: a single market buy on the first tick that the EA encounters an empty position list, three retry helpers that are never called, and no indicator handles, no session gate, no drawdown switch, no partial-close logic, and no recovery loop. This page is written about what the file actually contains, not what the description line claims it should contain. Anyone evaluating EX16079 needs to know that before they attach it to a live chart.

The OnTick function is fourteen lines. It refreshes the symbol with mysymbol.RefreshRates(), checks PositionsTotal(), and if no position is open it sends a market buy at the current ask with trade.Buy(InpStartLot, _Symbol, mysymbol.Ask(), 0, tp, InpTradeComment). The TP is computed inline as mysymbol.Ask() + InpProfitPoints * mysymbol.Point() — there is no stop loss, no break-even, no trailing, no opposite-side close on a bearish candle, no time-based exit, no second-leg averaging. After that one buy, the function returns. The next tick repeats the same check; if PositionsTotal() is zero again, it opens another buy. If the position is still open, the function does nothing. There is no OnTimer and no OnTradeTransaction override.

The header comment between the +--- lines documents an intended recovery scheme — "If Buy goes against by ZonePoints, Open Sell with higher lot. Loop until Profit" — but that scheme is not implemented. InpZonePoints is declared as an input (default 200) and is read by no code path. InpProfitPoints is the only input that the OnTick actually consumes. The 12-layer architecture claimed in the #property description is similarly not wired: there is no regime classifier, no signal layer, no risk layer, no safety stack, no OnTester formula, no news filter, no session window. The file is closer to a behavior template for a future zone-recovery EA than a finished one.

Five inputs are declared. InpStartLot (double, default 0.01) is the fixed lot for every market buy. InpZonePoints (int, default 200) is the intended but unused spacing for the recovery grid. InpProfitPoints (int, default 200) is the take-profit distance in raw price points (200 points = 20 pips on a 5-digit XAUUSD quote, or 2 whole dollars on a 2-digit quote). InpMagicNumber (int, default 22216079) is set on the trade object in OnInit via trade.SetExpertMagicNumber(). InpTradeComment (string, default "Psgrowth.com Expert_16079") is attached to every order. Two sinput const string separator inputs (GroupTrade, GroupIdentity) only act as visual dividers in the Inputs panel and have no runtime effect.

The three functions after OnTick — TryClose_EX16079, TryClosePartial_EX16079, TryModify_EX16079 — are stock wrappers around trade.PositionClose, trade.PositionClosePartial, and trade.PositionModify. Each runs up to three attempts and only retries on the standard transient retcodes (TRADE_RETCODE_REQUOTE, TRADE_RETCODE_TIMEOUT, TRADE_RETCODE_PRICE_OFF, TRADE_RETCODE_PRICE_CHANGED); on the close helpers the backoff is 200ms per attempt, on the modify helper 100ms. They are defined but not referenced from OnTick, OnInit, OnDeinit, or anywhere else in the file — they are dead code, present in case a future revision wires them into a position-management layer. As shipped, they do nothing.

Risk profile is the most important section. With SL = 0 the trade has no per-trade stop, and the only exit is the fixed TP at +200 points. On XAUUSD M5 the 200-point TP equates to roughly $2.00 per 0.01 lot, which is small relative to the maximum adverse excursion a gold trade can run in a five-minute bar — gold can move several dollars inside a single candle on a news spike. Lot size is fixed at 0.01 regardless of balance, there is no per-trade risk percentage, no daily loss cap, no equity-curve guard, no max-drawdown kill switch, and no max-positions cap. The minimum recommended deposit is $100, which is the smallest tier the catalog lists and reflects the 0.01-lot entry; with SL = 0 the broker's stop-level check (SYMBOL_TRADE_STOPS_LEVEL) is the only thing keeping the TP at a sane distance from the ask, but a stop-level check is not a risk check.

If you attach EX16079 to an XAUUSD M5 chart with default inputs and a $100 account, the backtest will produce one open buy at the start of every contiguous flat period, with a +200-point TP and no protective stop, and a long string of stopped-out-by-Friday-flatten or terminal-margin-call outcomes during sustained downtrends. The file is useful as a starting scaffold for someone who wants to write their own zone-recovery system, but it is not deployable as-is on a funded account, and the header's "full 12-layer stack" claim should be read as roadmap text rather than implemented feature set.

For context, a real zone-recovery implementation typically carries four things this file does not: an entry signal (often a counter-trend reversion trigger around a moving average or a Bollinger band touch), a hard stop on the initial order sized to the same InpZonePoints it then uses as the recovery spacing, a recovery ladder that opens an opposite-side position at InpZonePoints adverse with a lot multiplier (often 1.5x to 2.0x) until the basket breaks even, and a basket take-profit that closes all legs together. EX16079 declares InpZonePoints and uses the word "recovery" in its filename and header, but the OnTick body contains none of those four pieces — only the very first leg of the strategy (an entry) without any of the protective or recovery machinery that would justify the label. The file should be read as a stub that documents the intended state machine in comments, not as a working implementation of it.