Existing Indicators

Select Existing Indicator for an MQL5 indicator that needs a change. Add complete current source through Share source code, then describe the modification in the composer. This keeps the real calculation as the starting point instead of recreating it from appearance.

Use conversion for MQL4 or another platform's indicator. A screenshot can explain a display issue but cannot replace the source required by an Existing task. Describe custom includes or other indicators that the program uses.

Choose the source role

Attach the main indicator as Current codebase. Additional source can then supply functionality to merge or an example to follow. Identify the exact calculation, alert or drawing feature required from an attachment, rather than asking Xen to combine everything indiscriminately.

If an EA reads the indicator, specify buffer indexes, input order and signal values that must stay compatible. A visual change can look correct while breaking a robot that depends on those outputs. Include that integration in the request so it can be preserved.

Describe the chart problem

Give the symbol, timeframe, inputs and bar demonstrating the issue. For a missing arrow, identify the condition that should produce it. For repeated alerts, explain the current frequency and the required frequency. For a wrong value, provide a calculation example.

Attach a supported image when placement or colour is the concern. Explain which elements should change and which calculations must remain fixed. If a historical signal appears only after later candles arrive, clarify the confirmation timing before requesting a repainting change.

Check the revised indicator

Compile and compare the revised source with the previous version on the same chart and inputs. Reload it, change timeframe and inspect historical bars. Confirm alert timing and check that chart objects do not accumulate unexpectedly.

Retest any EA integration as well. Keep a local copy or pinned snapshot of the known working version before another change. Using Code in MetaTrader covers installation, and Image Uploads explains visual references.

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.