Install, Examine & Stop Expert Advisors

Differentiate EA, Indicator and Script

An EA automates analysis and, if necessary, trade actions according to its programmed rules. An indicator is typically used for display or evaluation. A script performs a specific task; the filename alone does not follow what effect it has. MT4 belongs to MQL4, MT5 to MQL5.

Preparation as an editorial checklist: record the origin and version number; request the required icons, time zone, account model, parameters, external services and the intended stop sequence. If the description is missing, a reproducible test is hardly possible.

Install an externally supplied program

1. Choose a suitable platform and a separate demo work environment.
2. Using File → Open Data Folder to determine the actual data folder of the current installation.
3. For MT4, a suitable EA program in the area MQL4/Experts, for MT5 in MQL5/Experts. Indicators belong in the corresponding indicators range. Procure Market products via the intended Market installation route.
4. Update or restart platform in the navigator. For source code, check the appropriate MetaEditor compilation and messages.
5. Start EA on the scheduled chart; read and save input parameters. Trade release initially deactivated.

EX4 and EX5 are different executable formats. Renaming a file does not port a code. Missing dependencies or an inappropriate license can also not be solved by renaming.

Targeted allocation of permissions

For MT5, EA-specific trade clearance and general platform clearance must match. A started program can therefore be visible without being allowed to act. The settings contain separate options for DLL imports, web accesses and behavior when changing accounts or profiles.

Our rule: granting rights only according to a specific documented requirement. A DLL call is additional executable code; a permitted web access connects the program to a named service. In the test protocol, record which rights were actually necessary.

First check behavior, then release

1. Store parameters and program version.
2. Run a small traceable run in the tester; check journal for errors.
3. In demo forward operation with suitable small sizes, observe when and why orders are created.
4. Compare orders sent, execution and actual position.
5. Observe restart and connection interruption during demo operation; document unexpected duplicates or orphan positions.

This work sequence is an editorial test method. It does not prove future profitability and does not replace verification of the code. Limit protocols and errors

Turn off automation and check account

Deactivate trade clearance and remove the affected program from the chart if it should not continue to run. Then check open positions and pending orders separately. A deactivated EA does not automatically close it. Existing server-side stops must be checked separately.

In VPS operation, stop the actually running instance or update its settings. A local counter says nothing about whether another entity is still acting. In a generic VPS, local and remote instances can run simultaneously. Copying service and exit

Sources & scope

Check the evidence.

1. MT4 · Automation

   MQL4 programs and terminal automation.

   Open the source ↗
2. MT4 · Navigator

   Manufacturer assistance also contains historical references. Only specific operating functions are taken over.

   Open the source ↗
3. MT5 · EA and indicators

   Program launch, parameters and trading permissions.

   Open the source ↗
4. MT5 · Settings

   EA rights, notifications and signals; version-dependent options.

   Open the source ↗

Deepening Expert Advisors

Technique, Strategy Types, Grid Lab and Trust Test