BUSTER CALL — the Operator's Manual, and your own ARMADA relay in ten minutes

BUSTER CALL is live on the MQL5 Market: https://www.mql5.com/en/market/product/193070

BUSTER CALL is the EA that does not trade — it BRAKES. One chart, the whole account guarded: a daily loss limit built for prop-firm rules, an equity kill-switch with a patrol, per-EA jails, a news lockdown, and a built-in trade copier that runs over infrastructure YOU own.

This post carries the two things every operator needs beyond the EA itself:

1. THE OPERATOR'S MANUAL — the full 78-page PDF, attached at the bottom of this post, free.

2. THE RELAY FILES + SETUP GUIDE — everything the remote copier needs, step by step.

PART 1 — THE OPERATOR'S MANUAL (78 pages, free download)

The PDF is attached at the bottom of this post. Written for humans, not for lawyers: master setup in 9 steps, follower in 6, a full prop-firm playbook for the DAY GUARD, every input explained, every panel colour decoded, every screenshot from a live terminal — and a Reference part that states plainly where every protection's edges are. Read section 7 (THE DAY GUARD) before you arm the daily dial on a funded account, and section 13 to drill the guardian in the Strategy Tester before you ever need it live.

PART 2 — YOUR OWN ARMADA RELAY, IN TEN MINUTES

The relay files (worker.js + wrangler.jsonc + README) are in the ZIP attached at the bottom of this post.

Read this only if you chose REMOTE — copying between two computers in different places. If both accounts run on the same computer or the same VPS, use LOCAL and skip all of this: LOCAL needs no relay, no account, no internet and no setup at all.

WHAT A RELAY ACTUALLY IS

A relay is a mailbox on the internet. Your master drops a message in; your follower checks the mailbox and takes it out. That is the whole job. It never sees your broker, never holds your password, never places a trade — and could not trade on your behalf even if someone broke into it. You need one because two computers in different places cannot hand files to each other directly. That mailbox is YOURS: you make it, you own it, nobody else uses it, and it costs nothing.

WHAT YOU NEED

- A free Cloudflare account — cloudflare.com, email and password, no card asked for.

- Node.js — free from nodejs.org, download the LTS button, click Next until done. You never open it; it just needs to exist. Install it BEFORE opening the command window.

- The two relay files from the ZIP below — worker.js and wrangler.jsonc — copied into a new folder, for example C:\my-relay\

- Ten minutes. Once.

DO NOT CHANGE ANYTHING INSIDE THE TWO FILES. They are a matched pair. The worker name, the class name and the migration tag inside wrangler.jsonc are how your relay finds its own database — change the name and your next deploy silently starts a NEW, EMPTY relay: every master identity, every feed, every follower token gone, with no error anywhere. Edit neither file.

STEP 1 — open a command window in that folder. Open the folder in Windows Explorer, click the address bar, type cmd, press Enter. A black window opens, already pointed at your folder.

STEP 2 — connect it to your Cloudflare account. Type: npx wrangler login — your browser opens and asks to allow it; click Allow. The first time it may ask "Ok to proceed? (y)" — type y, Enter. On a VPS with no browser, wrangler prints the link — open it on any device. You can also do this whole section from your own PC: the relay is not tied to the machine that deployed it.

STEP 3 — put your relay online. Type: npx wrangler deploy — two things it may ask the first time, neither a problem. "You need to register a workers.dev subdomain": open dash.cloudflare.com, Workers and Pages, pick any word (it becomes the middle of your address, permanently), run the command again. "More than one account available": copy the ID of the account you want from the list it printed, type set CLOUDFLARE_ACCOUNT_ID=that-id, Enter, deploy again. After a few seconds it prints an address like https://armada-relay.something.workers.dev — THAT ADDRESS IS YOUR RELAY. Copy it and keep it. It is now running, permanently.

STEP 4 — check it is really alive. This must be the black cmd window — if the window is blue or the tab says PowerShell, type cmd and Enter first (PowerShell's curl is a different program). Paste on one line, replacing YOUR-ADDRESS with the whole address wrangler printed (it already starts with https://):

curl -s -i -X POST YOUR-ADDRESS/rest/v1/rpc/armada_fetch -H "apikey: ARMADA-RELAY-PUBLIC-2026-EDGE-GATE-01" -H "Content-Type: application/json" -d "{\"p_token\":\"PROBE-000000000000000000000000\"}"

The last line you want is exactly: "ERR|token refused" — that LOOKS like an error and it is the CORRECT answer. You asked your relay about a mailbox key it has never seen, and it correctly refused. That one sentence proves the whole chain: TLS, the key gate, routing, the database, the reply format.

If instead you got — Invalid API key: the apikey line was mistyped; retype it, one long value, no spaces. Not Found: the /rest/v1/rpc/armada_fetch part got mangled, or the address already had a path on it. URL rejected or nothing: the address is wrong, usually https:// typed twice. A page full of HTML: the deploy has not spread yet; wait a minute, try again.

Run this probe from the same part of the world as your MASTER terminal — this first request decides where your relay physically lives, and it stays there.

STEP 5 — tell MetaTrader it may talk to your relay. On EACH terminal: Tools, Options, Expert Advisors, tick Allow WebRequest for listed URL, and add your address exactly as wrangler printed it. MetaTrader contacts no address that is not on this list, and gives no warning when it blocks one. Not optional.

STEP 6 — point BUSTER CALL at it. On each terminal, put your address into Relay address. Leave Relay public key exactly as you found it — it is not a password, it is the same for everybody, and your relay expects that exact value. PASTE THE ADDRESS ONLY — nothing after .dev. A /rest/... left on the end from step 4's clipboard still looks valid, still turns the panel green, and then never finds the feed.

STEP 7 — mint a fresh token for your follower. Mailbox keys belong to the mailbox that made them — a token from a different relay means nothing to yours. Type the follower's name into the mint field on the master, press OK, read the token from the journal, hand it to the follower, clear the field. The manual's section 30 walks it with screenshots.

BOTH TERMINALS MUST POINT AT THE SAME RELAY. A master on one relay and a follower on another will never find each other, and nothing will look broken — the follower simply reports no feed, quietly, forever. If a pair goes silent after any change, check the address on both sides first.

WHAT IT COSTS

Nothing. Cloudflare gives every account 100,000 free requests a day; one master + one follower at the shipped 2000 ms settings uses about 86,400 of that. Planning more than one follower? Set poll and heartbeat to 5000 on both sides (about 34,560/day — room for three followers). Raising the heartbeat does NOT slow your trades: a fill publishes instantly on its own event; the heartbeat only paces the idle keepalive.

OPTIONAL HARDENING, ONCE IT RUNS

npx wrangler secret put PEPPER — mixes a private value into how master identities are derived, so a dump of the database is useless without it. Bind it BEFORE registering your master: binding it later changes every identity, and every follower token must then be re-minted.

HONEST, AS ALWAYS

The relay stores your account login and balance (the frame header — a follower needs them for pairing and lot scaling), your trade frames, the token list, and a HASH of every key and token — never the full values. A fully compromised relay could forge frames; it could NOT recover your keys or tokens, could not touch your broker login, and every copy it might suggest still has to pass your ceilings, your drift gate, your News Shield and your trip line. The blast radius ends at your own dials — and the relay is yours, on your own account, so its security is in your hands rather than a stranger's.

There is no uptime guarantee, from us or from Cloudflare's free tier. A relay outage reads as a dead transmitter on every follower: with the default orphan policy they HOLD what they have, and your phone is told. The guardian, the News Shield and the LEGION jails run entirely inside your terminal and never notice a relay outage at all.

Questions? Ask in the comments on the product page — and drill the demo in the Strategy Tester before you trust anything live. The manual shows you exactly how.

BUSTER CALL — the guardian your EAs answer to.