AuroraSync MT4 Trade Copier
- Yardımcı programlar
-
Thorsten Fuehrmann
Founder of the Aurora Trading Suite.
My mission is to bridge the gap between institutional logic and automated trading. I don't believe in "Black Box" algorithms. I believe in documented transparency, multi-layer confluence, and capital protection as a priority. - Sürüm: 2.3
- Etkinleştirmeler: 5
AuroraSync — The MT4 Trade Copier That Gets Safety Right
------------------------------------------------------------
Copies trades locally between MT4 terminals — event-driven, not state-mirrored. No DLLs, no cloud service, no subscription. Built from a real incident where a standard copier closed positions across four live accounts.
------------------------------------------------------------
Full Description
The Problem With Other Trade Copiers
Most trade copiers work by state mirroring: on every tick, they compare the current state of the master terminal to the slave and derive what action to take. Simple, right?
Too simple.
When the master's connection drops briefly and OrdersTotal() returns 0, a state-mirror copier concludes that all positions were closed — and closes them on the slave. This is not a theoretical risk. It happened. On live accounts, with real money.
AuroraSync was built in direct response to that incident.
------------------------------------------------------------
The AuroraSync Principle: Event-Driven Commands
AuroraSync does not mirror states. It sends explicit commands:
| Event | What is sent |
| Position opened | OPEN command — symbol, type, lots, SL, TP |
| SL/TP changed | MODIFY command — new SL/TP values |
| Position closed | CLOSE command — only when ticket is found in History WITH CloseTime confirmed |
A CLOSE command is never inferred from the absence of a position. It is only sent when the master has positively verified the close in its trade history. That distinction is everything.
------------------------------------------------------------
Double-Lock Duplicate Protection
Even if a slave receives a command twice, it will never open duplicate positions:
- GlobalVariable lock: AS2S_<AccountNumber>_<Ticket> — set on first OPEN, never removed
- Order comment lock: "AS:<MasterTicket>" embedded in the order comment — independent second layer that survives GlobalVariable loss
Both locks must simultaneously be absent for a duplicate to occur. In practice, this does not happen.
------------------------------------------------------------
Session ID: Protection Against Restart Errors
Every master instance generates a unique session ID on startup (Unix timestamp). This ID is written into every command file header. The slave uses it to immediately detect: is this a genuine new command, or did the master restart and the file was reset from zero?
Without the session ID, a master restart could, in the worst case, be misread as a data gap — triggering follow-on commands that were never intended.
------------------------------------------------------------
Scalping Safety
When a position is opened on the master but the slave executes it with delay, the entry price on the slave can be significantly worse than the master's original. AuroraSync calculates:
Deviation = | SlaveBid - MasterEntry | / StopDistance
If this deviation exceeds the configurable threshold S_MaxEntryDevR, the position is not copied. A skipped entry is better than a catastrophic one.
------------------------------------------------------------
Technical Architecture
Master MT4 Terminal
│
▼
Common Files (CSV)
on local PC / VPS
│
┌────┴────┐
▼ ▼
Slave 1 Slave 2 (... Slave N)
MT4 MT4
- All terminals on one PC or VPS — no network overhead
- Communication via Common Files — the only DLL-free, serverless method with true persistence
- No cloud, no external server, no third-party dependency
- No DLLs — runs on any MT4 without special permissions
------------------------------------------------------------
Parameters
Master:
| Parameter | Description |
| M_Lots | Fixed lot size (0 = proportional) |
| M_Prefix | Broker symbol prefix (e.g. "m.") |
| M_Suffix | Broker symbol suffix (e.g. ".+") |
| M_Magic | Magic number filter (0 = all) |
| M_Comment | Comment filter |
Slave:
| Parameter | Description |
| S_Lots | Fixed lot size (0 = proportional to master) |
| S_RiskFactor | Proportional scaling factor |
| S_Prefix / S_Suffix | Broker symbol mapping |
| S_MaxEntryDevR | Max entry deviation (× stop distance) |
| S_MaxSlippage | Max allowed slippage in points |
| S_AutoRecon | Automatic reconciliation check (true/false) |
------------------------------------------------------------
What AuroraSync Does NOT Do
- Not a network copier (no cross-VPS or LAN operation without shared file system)
- No built-in risk management or position sizing calculator
- No strategy tester support (requires live terminal environment)
- No MT5 version
------------------------------------------------------------
System Requirements
- MetaTrader 4
- All terminals on one PC or VPS sharing the MQL4/Files/Common directory
- No additional broker, cloud service, or subscription required
------------------------------------------------------------
Tested On
- Windows VPS (standard configuration)
- Up to 4 simultaneous MT4 terminals (1 Master + 3 Slaves)
- Live trading, multiple months
------------------------------------------------------------
Why No MT5?
MT4 offers decisive advantages for this use case: cleaner order model, reliable Global Variables as kill-switch mechanism, straightforward pending order behavior, and broader broker support for prop firm accounts. AuroraSync is built for MT4 and stays MT4.
------------------------------------------------------------
About the Developer
AuroraSync is part of the Aurora Framework family by Thor_Vig — a trader and MQL4 developer who builds his own tools for live deployment on real accounts. Everything published on MQL5 Market has been tested on live accounts for weeks before release.
------------------------------------------------------------
Changelog
| Version | Changes |
| 2.04 | Scalping safety (MaxEntryDevR), DST bug fixed: TimeLocal → TimeGMT |
| 2.03 | Session ID mechanism introduced |
| 2.02 | Dual-lock duplicate protection |
| 2.01 | First public release candidate |
| 2.00 | Complete rewrite after the reconnect incident |
------------------------------------------------------------
Price
USD 99 (introductory price — limited to first buyers)
One-time payment — no monthly fees, no activation limits.
------------------------------------------------------------
Copyright © Thor_Vig | Aurora Framework | MQL4
