Magic Number Registry

Magic numbers are usually picked by hand, one EA at a time, with no record of which numbers are already spoken for. On a terminal running several EAs at once, or across a team sharing EAs on the same account, two of them eventually end up on the same magic number - and everything downstream that filters "my own orders" by magic number quietly starts touching someone else's trades. This script is a planning tool, not a live scanner: it never reads open orders or trade history. It only reads and writes its own registry file, one row per EA, holding a name, a start magic, a range size, an end magic, the date it was registered and a free-text note. Register mode either allocates the next free block automatically (right after the highest end magic already registered) or checks a specific requested start against every existing range and refuses outright if it would overlap - it never silently reassigns a colliding request to somewhere else. Check mode looks up a single magic number and reports which registered EA (if any) owns it, including the case where more than one overlapping entry claims it, which means the registry itself already has a collision worth fixing. Whether an EA actually uses the magic numbers it was allocated is up to whoever wires the resulting InpMagicStart-style value into that EA's own input - the registry has no way to enforce that from outside, and does not claim to. Notes and limitations - The registry is a plain CSV that can be hand-edited. A hand-edited overlap between two ranges is detected and reported by Check mode (it reports every matching entry, not just the first), but Register mode only actively prevents a NEW overlap - it does not repair one that already exists in the file. - Registering the same EA name twice is refused; release the existing entry first if it genuinely needs to be re-registered with a different range. - This tool has no connection to live trading. It does not verify that an EA is actually using the magic numbers registered for it, and cannot - that link only exists inside the EA's own code. - A malformed or blank line in a hand-edited registry file is skipped silently when the file is loaded, on the basis that a partially-edited file should not crash the tool, but this means a badly mistyped row can disappear from the registry the next time anything is registered or released (which rewrites the whole file from the entries it could parse).

Script · MT4 · v1.0 · Free

Tags: Alerts · MT4 Script · MQL4 Source Code

MQL4 & MQL5 scripts · PolyMaria