Update an EA without losing your settings

A saved settings file and a compiled EA are separate files. Replacing one does not automatically prove the other still matches. An update is easier to manage when the old version remains available for comparison.

Save a small rollback folder

Keep the original MQ5, EX5, settings and release notes together. Name the folder with the version and date. Avoid overwriting the only copy while a terminal is still using it.

Compare the input interface

Review renamed inputs, changed defaults and altered enum meanings. A setting that loads without an error can still mean something different after a design change. Use the new parameter guide as the reference.

Confirm the loaded build

Check the intended terminal’s data folder and the initialisation log. Compile from the intended source if you modified it. Multiple broker installations can otherwise make it look as though an update had no effect.

Keep the next step simple

Install one version at a time and retain the old report as a reference. MQLume packages include documentation so you can see what you received and keep your own modifications organised.

Reference and further reading

Start with a free editable EA project · Explore MQLume source code

Back to top