EA Deployment Checklist Runner
Every item this checklist covers has caused a real live-trading mistake on its own, and none of them announce themselves as an error - they all look, on the surface, like a perfectly normal running EA. AutoTrading quietly toggled off after a restart. A demo preset attached to the live account out of habit, or the reverse. A symbol the broker has paused trading on for the day. A freshly attached chart whose history is still syncing in the background. One input hand-edited during testing and never changed back before go-live. Any one of these silently changes what the EA actually does compared to what was tested and approved, and the first sign of trouble is usually a trade that should not have happened. This script runs all five checks in one pass and prints a plain PASS/FAIL line for each, plus a single GO/NO-GO verdict at the end, so a deployment gate takes one script run rather than five separate manual checks spread across different dialogs. The most detailed check is the last one: it loads an approved baseline .set file and the currently-attached EA's own exported .set file (via the terminal's own Inputs dialog "Save" button), compares every parameter by name, and lists exactly which ones differ rather than a bare Yes/No - a mismatch is only actionable if it says which input moved and what it changed to. Notes and limitations The preset comparison only works against a .set file the EA's Inputs dialog itself exported - this script has no way to read another program's live input values directly, since MQL4 has no such introspection API. If InpCurrentSetFile does not exist yet, that check fails with a clear message telling you to export it first, rather than silently passing. "Symbol is tradeable" reads the modern SYMBOL_TRADE_MODE property; it reports full trading, long-only, short-only, close-only or disabled, but it cannot see broker-side restrictions that are not exposed through that property (e.g. an account-level restriction rather than a symbol-level one). This tool only reports; it does not enable AutoTrading, does not attach or detach any EA, and does not change any input itself. A GO verdict means the checks it knows how to run all passed - it is not a substitute for reviewing the strategy, its risk settings and its recent backtest results before deploying capital.
Script · MT4 · v1.0 · Free
About EA Deployment Checklist Runner
EA Deployment Checklist Runner is a script for MetaTrader 4. It can alert you with a pop-up, sound, email or push message. It has 6 settings, such as Expected account, Expected server and Min bars required. MQL source code included.
Files in the download: DeploymentChecklistRunner.mq4, DeploymentChecklistRunner.txt.
Settings
| Setting | Default | What it does |
|---|---|---|
| Expected account | 0 | Expected account number (0 = skip check) |
| Expected server | Expected server name, exact match (blank = skip check) | |
| Min bars required | 1000 | Minimum bars required on this chart's timeframe |
| Approved set file | approved.set | Approved baseline .set (in MQL4\Files) |
| Current set file | current.set | Currently attached EA's exported .set (in MQL4\Files) |
| Compare set files | true | Compare approved vs current .set (turn off if not exported yet) |
How to install
- Download the ZIP from your PolyMaria library and unzip it.
- In MetaTrader 4 open File → Open Data Folder, then go to MQL4 → Scripts.
- Copy the .mq4 file(s) there. Put any .mqh files in MQL4 → Include.
- Open the .mq4 file in MetaEditor and press Compile (F7) if MetaTrader does not show it.
- Drag the script onto a chart to run it once.
Tags: Alerts · MT4 Script · MQL4 Source Code