Magic Number Collision Checker
Check user-entered Expert Advisor magic-number assignments for exact duplicates inside the same account or terminal scope. Cross-scope reuse is shown separately, and the page never connects to MetaTrader.
Enter EA assignments
Use a consistent label for each account or terminal namespace. A collision means two entered EAs share one magic number inside the same normalized scope.
Use one EA assignment per row. Labels must be unique inside each scope.
Magic-number audit
MT Execution Utilities 1.0.0.
| EA label | Scope | Magic number | Status | Global uses |
|---|
How the collision check works
Cross-scope reuse = Same number entered in more than one normalized scope
Scope and EA labels trim leading and trailing whitespace, collapse repeated spaces and compare without letter-case differences.
The next available number scans upward from the entered suggestion start and excludes every magic number in the complete entered sample.
Worked example from the audited fixture
Enter four assignments: London Breakout and Swing Trend both use magic number 12001 on Primary VPS; London Breakout Copy uses 12001 on Backup VPS; and Asia Range uses 12002 on Backup VPS. The checker reports one same-scope collision group containing the two Primary VPS rows, one number reused across scopes, one fully unique row, and 12000 as the next unused number from the entered suggestion start.
How to interpret the result
Only the duplicate inside Primary VPS is a collision under this model. The Backup VPS use of 12001 is shown separately because it is in another entered namespace. The suggestion 12000 is unused only within these four rows—not proof that every EA, terminal or account is free of that identifier.
Assumptions and limits
- Only the rows you enter are checked; no MQ4, MQ5, EX4, EX5, order history or terminal state is inspected.
- Scope is a user-defined namespace and must be applied consistently across every relevant EA.
- Cross-scope reuse is informational rather than a same-scope collision.
- The conservative positive 32-bit range does not represent every identifier value accepted by every platform API.
- A unique magic number does not prevent conflicts caused by symbols, comments, order filters, copy systems or faulty EA logic.
Frequently asked questions
- It is an identifier an Expert Advisor can attach to trading requests or orders so program logic can distinguish its activity.
- Two or more entered EA rows using the same exact magic number inside the same normalized account or terminal scope.
- A number used in two deliberately separate scopes is not the same entered-scope collision, but seeing the reuse can still help with inventory control.
- This planner uses positive identifiers so zero is not silently treated as a planned EA identifier. Check the exact conventions in your own code.
- No. It analyzes only the rows entered in the browser.
- That depends on their filtering and management logic. This page flags the duplicate but cannot certify EA behavior.
- It is unused only in the entered sample. You must compare it with every relevant EA, terminal and account configuration.
- No. Identifier separation does not verify execution logic, risk controls, broker compatibility or strategy performance.
Sources and methodology
- MQL5 Reference — Order Properties — Official ORDER_MAGIC property definition and EA-identification purpose.
- MQL5 Reference — MqlTradeRequest — Official request structure containing the magic EA identifier and requested volume.
- MQL4 Reference — OrderSend — Official MQL4 order-request function and magic identifier parameter.
Continue MT4 / MT5 planning
Verify symbol and account rules
Confirm the exact account entity, platform, symbol specification, volume rules and copier or EA settings before using an entered plan.
Risk and affiliate disclosure: Leveraged forex and CFD trading can result in substantial losses. These are affiliate links, so ForexMT4Indicators.com may receive compensation if you register or trade through them, at no additional cost to you. Availability and terms vary by jurisdiction and broker entity.