Existing Expert Advisors

Choose Existing Expert Advisor when you have MQL5 EA source to change. Add the complete current file through Share source code before sending the request. Use the version you actually compile and test rather than an excerpt from an older conversation.

MQL4 belongs in Converting Strategies. A compiled .ex5 file cannot replace editable .mq5 source. If the EA depends on custom headers or indicators, explain those dependencies and provide the relevant source when needed to understand the change.

Add the current codebase

Use Current codebase for the main EA and load or paste its full source. Check the filename and attachment before sending. Put the change request in the composer so the program and requested behaviour remain distinct.

After adding the main source, additional roles become available. Merge functionality into the current codebase supplies behaviour to incorporate. Use only as example code gives a reference without making it the target. Explain which feature to borrow and how its inputs or trading rules should interact with the main EA.

Request a bounded change

Describe the new behaviour and what must be preserved. For example: “Add a maximum spread input in points and reject new entries above it. Keep entries, sizing, stops and open-position management unchanged.” Give a default value and explain whether the rule affects existing trades.

For a bug, supply the symbol, timeframe, inputs, event time and what happened compared with your expectation. Journal messages can help. A specific duplicated entry or missed exit gives Xen something to inspect; “it does not trade properly” leaves the problem undefined.

Replace and retest the file

Use the complete revised source. Keep the earlier tested version, compile the replacement and repeat the test that demonstrated the original behaviour. Check the requested change and the rules that should have remained intact.

If you edit locally between requests, update the source supplied to Xen. The browser cannot know about a MetaEditor change. Use History for useful revisions and Requirements Verification when several changes need checking against the specification.

Fix compiler errors in this task

After attaching the current source, choose Check Compile Errors to inspect MetaEditor diagnostics without changing the file. If source errors are found, Fix Errors prepares the complete source and diagnostics in the same task. Choose Send to request the correction with your selected model. A check that could not complete is not proof of a source error; retry it or compile locally in MetaEditor.

Generated source also receives a build check. If automatic repair leaves errors, choose Continue repair and send the prepared request within your current task. For behaviour bugs, describe the expected result and the observed result, then retest the corrected file under the same conditions.