Build & releaseBuilds & releases

The short version used in deploy package descriptions (the current package uses MT5 Build 6230). Details are in each section below.

flowchart LR
  B21["1.41.4 b21<br/>2bbd135 · 71dac5f<br/>previous production"]
  B211["1.41.4 b21.1<br/>77b12cd<br/>HOTFIX, not deployed"]
  L1["1.42 b1<br/>1967099<br/>EA Link"]
  L2["1.42 b2<br/>51b2864<br/>DEV, Close all"]
  L3["1.42 b3<br/>ff0e30e<br/>heartbeat"]
  L5["1.42 b5<br/>c9145f8<br/>manual init"]
  L6["1.42 b6<br/>3fc37ea<br/>force_dir"]
  L7["1.42 b7<br/>663082f<br/>PRODUCTION, force_add"]
  T22["b22"]
  T23["b23"]
  T24["b24"]
  T25["b25"]
  T26["b26"]
  T27["b27"]
  T28["1.41.4 b28<br/>0eee481<br/>TEST"]
  P22["1.41.5 b22<br/>588aeec<br/>PARKED"]
  B21 --> B211 --> L1 --> L2 --> L3 --> L5 --> L6 --> L7
  B21 -- "test line" --> T22 --> T23 --> T24 --> T25 --> T26 --> T27 --> T28
  B21 -- "StrongMove branch" --> P22

All three branches start from production b21. The hotfix → 1.42 branch contains none of the features of the b22–b28 test line or of 1.41.5.

Run in Git Bash or cmd — do not use PowerShell's >, because it corrupts binary files:

After attaching the EA, check that the panel title shows GoldenRobber v1.41.4 (b21).

• Per-EA remote config: URL /easupported/goldenrobber + its own secret token; the EA pushes its config_schema to the web itself.
• Hot-reload of 14 keys: manual_init, single_round, strong_bypass, strong_tf, strong_require_sr, lot_balance_enable/trigger/target, hedge_enable/after_trades/lot_percent, weekend_protect_enable/max_net_lot/balance_enable.
• Manual Init: OFF / Only BUY / Only SELL (no Auto yet).
• Telemetry payload = the whole Info Panel (including the Spread line), viewable at /admin/easupported/goldenrobber/account/{id}.
• The heartbeat runs in OnTimer → the panel and heartbeat do not depend on ticks.

v1.41.4-pass58-easupported-goldenrobber-29082026.set (pass58 + per-EA URL). The bearer token is typed in by hand and never committed.

The stable config for 1.42 b3 is v1.42.b3-pass58-12092026.set — see Stable config.

Forked from b21 (71dac5f) → it has none of the b22–b28 features (Auto, PivotGuard…). Files: GoldenRobber-1.41.4-b21.1.mq5 / .ex5.

Deploy: the 1.41.4 deploy package (GoldenRobber-Pass58_v1_41_4-Vantage-build-6182.zip) has a chart01.chr pointing to Experts\GoldenRobber-1.41.4.ex5. To package b21.1, rename GoldenRobber-1.41.4-b21.1.ex5 → GoldenRobber-1.41.4.ex5 when putting it into the zip (or edit name=/path= in the .chr). After attaching, check that the panel title contains (b21.1).

• Files: GoldenRobber-1.42.mq5 + the shared include Include/EaLink.mqh. Trading logic, heartbeat parser, tmap and leader election are unchanged from b21.1.
• Admin Apply/Clear on /admin/easupported/{slug} → fxconsole publishes to Redis → monitor/EaLinkBroker sends a cfg signal → the EA immediately pulls its config over the HTTPS heartbeat → applied within ≈ ≤1s.
• New inputs: InpLinkMode (HTTP only / HYBRID default), InpLinkHost (empty = host of InpCloudMyApiDomain), InpLinkPort (9607). Slug + token come from the existing inputs.
• The panel gains a Link: UP ... / Link: DOWN, retry Ns / Link: AUTH FAIL: ... line.
• Server side must be in sync: fxconsole (endpoint /api/internal/ea-link/key, notify after Apply/Clear, Link badge) + container fxconsole-ea-link-broker + port 9607 opened (OVH + IPFire). If the broker is not running the EA still works like b21.1 (periodic HTTP) and the panel shows Link: DOWN.
• Protocol details + the standard for new EAs: EA integration standard §9 (EA Link), §16 (compliance checklist) — source EA-HOTRELOAD-STANDARD.md.

• Problem: every Init decision sits inside the M1 if (isNewBar) branch, so InpWaitAfterCloseSec / InpInitCooldownSec below 60 seconds have no real effect — the EA still waits for the next bar (0-60 s). Any value from 1 to 59 behaves the same.
• Why only for Manual Init: the bar gate exists to read closed-candle signals (IsClosedCandleGreen, M3 trend MA, M30/H1 wick, H1 ADX). But manual_init = Only BUY / Only SELL bypasses every direction filter, so that reason no longer applies.
• What b4 does: with manual_init = BUY/SELL and no open positions, Init is evaluated on every tick. Unchanged: InTradingWindow, both time gates, MinPips / SingleRound, the Pause / Close all guards, and the scalp-leak guard when ExposureScale pushes the lot down to minLot.
• How to spot it: the log line [ManualInit] init không chờ nến (BUY|SELL): Ns sau lần đóng cuối; orders carry the |init_manual comment.
• Automatic mode untouched: manual_init = OFF behaves exactly like b3; the pass58 backtests ran with InpManualInit=0, so they still hold.
• Risk: manual init has no filter holding it back — it can open a round right before a reversal, and the round rate rises sharply with a low cooldown. Turn it off when you stop watching.

• How to read it: the seconds give it away — :00 = M1 bar open (old path), :10 = exactly InpWaitAfterCloseSec=10 (b4 branch). One hit out of five.
• Root cause: ExecuteInitRoundNow still has a guard after the manual-init side forcing — if (g_singleRoundMode) { if (!g_singleRoundAllowSell) allowSell = false; }. The two flags g_singleRoundAllowBuy/Sell are only computed inside the if (isNewBar) block. While a round is open, every M1 bar pushes the flag of the very side being traded to false (round not maxed on adds + cross-round MinPips sees a same-side position next to price). Once the round closes, b4's tick branch reads those stale false flags → blocked, silently, until the next bar opens a round the old way.
• Why R310 slipped through: R309 lived entirely inside one minute; the single bar boundary it met (04:27:00) landed exactly when the position closed, so canOpenNewRound=false skipped the single-round block and the flags stayed true from 04:26:00.
• b5 fix (1): re-assert g_singleRoundAllowBuy/Sell = true right before the call. The branch only runs with nPos==0, and the bar path with no open positions reaches the same conclusion (both sides ready) and skips cross-round MinPips (that block only runs when nPos>0) — so this restates its conclusion rather than loosening any guard.
• b5 fix (2,3): add the two caller-level gates b4 missed — ShouldBlockInitForWeekend() and Sideway BlockInit. pass58 disables both, so today's behaviour is unchanged.
• b5 fix (4): a throttled (60s) [ManualInit] bị chặn … log line, because b4 stayed silent when blocked.
• Automatic mode untouched: every change lives inside the g_manualInit == BUY/SELL branch. The pass58 backtest runs InpManualInit=0, so +$332k / 38% DD still stands.
• Verify after deploy: set manual_init = Only SELL, let a round live across at least two M1 bars, then close it. The next round must open exactly 10 seconds after the close (on a second other than :00) tagged init_manual.

Problem: in b5, manual BUY/SELL forces the direction of every Init while it stays on. With SELL forced in a rising market, init_pivot and init_gap (opened while positions exist) also come out as SELL, and no BUY Init can open at all. One hand-placed seed skews the whole automatic strategy.

b6: adds the InpManualForceDirection input (default false), hot-reloadable via the manual_force_dir key (bool) on /admin/easupported/{slug}. It only matters while manual_init = Only BUY / Only SELL.

• Code: one guard, GR_ManualForceApplies() (manual BUY/SELL and (empty basket or force_dir on)), replaces the three reads of g_manualInit in ExecuteInitRoundNow: the neutral-trend skip, the P-leg label and the allowBuy/allowSell override.
• Unchanged: the every-tick init_manual path, adds (always trend-following), Pause / Close all, and automatic mode (manual_init = OFF). The pass58 backtest runs InpManualInit=0, so it still holds.
• No fxconsole change needed: the web renders keys from the schema the EA pushes, so manual_force_dir appears after b6's first heartbeat.
• Deployment note: the default is false, so an account with manual BUY/SELL on behaves differently from b5 as soon as it runs b6. Turn manual_force_dir on in the web to keep the b5 behaviour.
• How to spot it: panel title GoldenRobber v1.42 (b6); the Hot Reload line shows forceDir=ON|OFF while the web overrides it; log [ManualInit] force direction hot-reload: OFF -> ON.
• Verify after deploy: manual = Only SELL, force_dir OFF, positions open, M3 trend up and price near a pivot support → a BUY Init (init_pivot) must open if the BUY side is ready. Turn force_dir on → only SELL Inits.

Problem: manual init only forces the direction of Inits. Adds always follow the M3 trend (UP adds BUY only, DOWN adds SELL only), so after you have called the trend and forced SELL, the EA still adds BUYs to the round whenever M3 turns up.

b7: adds the InpManualForceAddDirection input (default false), hot-reloadable via the manual_force_add key (bool). It only matters while manual_init = Only BUY / Only SELL, and is independent of manual_force_dir.

• Still enforced: MinPips 34 from the round reference, 8 adds / side / round, 60-second cooldown, lot 0.1 × 1.5ⁿ capped at 0.5, ExposureScale, the price-zone limit, FlashCrash.
• Code: each branch (DCAPos and DCANeg) snapshots baseAddBuy/baseAddSell right before the direction filters, then GR_ApplyManualForceAdd() after the Choppy block overrides them per the manual side. The schema gains a bool key, plus the heartbeat parser, hot_keys revert and the forceAdd=ON|OFF panel entry.
• Unchanged: Inits (including manual_force_dir), closing, Pause / Close all, and automatic mode (manual_init = OFF) → the pass58 backtest still holds.
• Risk: with force_add on, the other side gets no counterweight adds. Force the wrong side and losing positions can only be unwound by Tia / Global TP.
• Verify after deploy: manual = Only SELL, force_add ON, a round holding SELLs, M3 trend up, price falls another 34 pips below the lowest SELL → a SELL add must open; price rises 34 pips above the reference → no BUY add. Flag change log: [ManualInit] force add direction hot-reload: OFF -> ON.

• Bug fixed (D1): CloudSyncPulse timed the heartbeat with TimeCurrent() — the last quote time, which freezes while the market is closed or has no ticks → the EA stopped sending HTTP heartbeats; /admin/easupported/{slug} showed Offline all weekend, and leader election and HTTP hot-reload did not update.
• b3: the interval is measured with GetTickCount64() (g_lastCloudSyncMs); TicketMapSaveImmediate stamps the same clock; the self-promote-to-leader check when both clouds fail and the panel line Server: CONNECTED (Ns ago) use the age of g_hbOkMs → the heartbeat runs every InpCloudSyncIntervalSec even without ticks.
• Input comments corrected: InpCloudMyApiDomain must be the product URL .../easupported/{slug}; InpManualInit BUY/SELL only skips the side-selecting filters inside the order-opening step and still passes the shared gates (neutral trend, sideway, pivot while positions are open, two-sided wick).
• Trading logic unchanged from b2. Compiled with 0 errors and 0 warnings; running in production on live accounts.

• New inputs (absent in b21): InpManualInitAutoTF, InpManualInitAutoMAPeriod, InpManualInitAutoConfirmBars, InpManualInitAutoPivotGuard.
• Hot-reload of 18 keys: adds manual_auto_tf, manual_auto_ma_period, manual_auto_confirm_bars, manual_auto_pivot_guard.
• Detailed docs: section 8d. Manual Init of the old README (README/index.html before it was split into pages); in these docs see Workflow & logic.

1. The schema on the web flips back and forth. config_schema is stored per EA product, not per account → the /admin/easupported/goldenrobber page shows the schema of whichever account sent the most recent heartbeat. The manual_auto_* keys appear and disappear; sometimes the Pause option (b21.1) is shown, sometimes the Auto option (b28).
2. A build that does not understand a value ignores it and keeps its previous value (it does not fall back to OFF):
   • manual_init = Auto (3) applied to b21 / b21.1 → ignored.
   • manual_init = Pause (4) applied to b21 / b28 → ignored → that account STILL inits. Pausing everything via a global override only works once every account runs b21.1.
   • An account in SELL that receives an unknown value stays in SELL. To turn it off, choose OFF.
3. Cross-loading .set files: a b28 .set loaded into b21 → MT5 ignores inputs that do not exist (safe). A b21 .set loaded into b28 → the new inputs take their defaults (Auto stays off because InpManualInit=OFF). A .set with InpManualInit=4 loaded into a build without Pause → invalid; re-check the panel after loading.

• Forked from b21 → it has none of the Auto features of b22–b28.
• Input InpStrongMoveFakeoutExit (hot key strong_fakeout_exit): closes an init_strong round when the next candle closes back inside the range it broke.
• Backtest 2023–2026 (run on $200k capital, expressed in absolute $ because of fixed lots): profit −$33,769 (−9%) versus plain StrongMove; DD almost unchanged ($242k vs $246k); exposure 52.7 → 48.5 lots.
• Not yet tested on 2020–2026 — the period needed to learn whether it prevents account blow-ups.
• Data: backtest/new-backtest/v1.41.4-pass58-29082026/StrongMove/*strong_fakeout_exit*

Reviewed on 2026-09-10, not fixed:

• ResultRetcode() is never read; deviation is hardcoded to 30 points, filling hardcoded to IOC.
• A failed Add DCA is retried on every tick (order spam); a timed-out order can lead to a duplicate open.
• Global TP (pass58 = $10) closes every position without re-checking → slippage on a large book can turn +$10 into a loss.
• Tia computes its budget from planned profit and does not subtract slippage on the winning side.
• No block on opening orders when the spread widens.
• Virtual TP does not run while MT5 is disconnected.

Server side (independent of the EA build): fxconsole v2026.09.04.1 stops rewriting tmap_entries when the map is unchanged — fixes the ~3 GB/day binlog growth (see TMap disaster recovery).

1. Full-range backtest (at least 2023–2026; 2020–2026 recommended as well) — a hotfix that does not change trading logic (like b21.1) may skip this step.
2. Trial run on a demo account or a small live account.
3. Compile, commit the .ex5, record the commit hash.
4. Roll out VPS by VPS: remove the EA from the chart and drag it back on (F7 while the EA is attached does not load the new binary); if MT5 shows the LiveUpdate dialog, choose Later.
5. Check the panel title shows the right build; the web page lists every hot-reload key.
6. Update Quick lookup and section 1 of RELEASES.md (and this page).