GoldenRobber 1.42 · build b2

Trading logic (init, DCA, TP, Tia, hedge, lot balance) is unchanged from production b21. This build does not contain Manual Init Auto, PivotGuard (b22–b28) or StrongMove fakeout-exit (1.41.5). See the build lineage.

Choose Close all (close EA orders + pause) under Manual Init on /admin/easupported/goldenrobber, or set InpManualInit=5 in the .set file.

Previously the EA only received a new config on its next HTTP heartbeat (a 10–30 second cycle). From 1.42 the EA keeps an extra connection to EaLinkBroker so it is notified as soon as an admin clicks Apply or Clear.

1. The admin clicks Apply or Clear on the easupported page.
2. fxconsole notifies EaLinkBroker; the broker sends a “config changed” signal to exactly that account.
3. The EA reads the signal within 200 ms, then calls the HTTPS heartbeat to fetch the new config.
4. The EA applies the config and logs [EaLink] cfg rev=… đã áp trong N ms ("applied in N ms"). It usually takes under 1 second.

The Link connection carries only the signal, never config values or the token; values always travel over certificate-verified HTTPS. If the broker is down or the network drops, the EA keeps trading and receives config on the heartbeat cycle as before.

The slug and token come from the existing InpCloudMyApiDomain and InpCloudBearerToken, so b21 / b21.1 .set files can be reused without edits.

Every GoldenRobber build shares the goldenrobber web page. A build that does not understand a value ignores it and keeps its previous value; it does not fall back to OFF.

1. Open TCP port 9607 on the OVH firewall and port-forward it on IPFire to the Docker host.
2. On the server run git pull origin main, then bash deploy.sh. The script creates the EaLinkBroker .env and fills in the DB connection from fxconsole.
3. Check that docker logs fxconsole-ea-link-broker contains the line settings DB: on, and that /admin/settings shows version 2026.09.12.3 or later.

1. Copy GoldenRobber-1.42.ex5 into the MQL5\Experts folder.
2. Remove the running EA from the chart, then attach 1.42 reusing the current .set file. Do not use F7 while the EA is attached. If MT5 shows the LiveUpdate dialog, choose Later.
3. Check the panel: title GoldenRobber v1.42 (b2), Server: CONNECTED, Link: UP. The easupported page shows a Link badge for the account.
4. Test on a demo account: Apply manual_init = Pause; the log must show hot-reload từ server: 0 -> 4 within about 1–2 seconds; Clear to return to OFF.

The current deploy .zip still points to GoldenRobber-1.41.4.ex5. Installing 1.42 in bulk through vps-agent requires repackaging.

• DEV build: compiled with 0 errors and 0 warnings but not yet run on demo or live.
• Close all has no confirmation dialog on the web yet.
• Close all only closes orders when ticks arrive; at the weekend it waits until the market opens.
• The seconds on the Server: line are based on the last quote time, so they freeze while the market is closed. The Link: line is not affected.
• In a backtest with InpManualInit=5, the panel does not update during Close all.
• The web page shows the option list of the build that sent the most recent heartbeat, so with mixed builds the Close all option is sometimes missing.

Remove 1.42 from the chart and re-attach GoldenRobber-1.41.4 b21 (production) or b21.1. Reuse the same .set file; MT5 ignores the Link inputs. EaLinkBroker can be stopped on its own with docker compose down in monitor/EaLinkBroker without affecting other services. Recovering the b21 binary: Builds & releases, section 2.

Technical details: Builds & releases, section 2c (RELEASES.md) and EA integration standard §9 (EA-HOTRELOAD-STANDARD.md).