Skip to content

Modify an Existing cTrader Indicator

What this Workflow Does

The Work on Existing Indicator workflow allows you to make targeted changes to an indicator you already have. It is designed for modifying, fixing, or extending existing code rather than creating something new from scratch.

This workflow is useful when you want to correct behaviour, refine logic, or add features without rebuilding the entire indicator. The focus is on making controlled, minimal changes while preserving the original structure wherever possible.

Supported Platforms

You can submit indicators from several platforms, including:

  • cTrader (C#)
  • MT4 and MT5 (MQL4, MQL5)
  • TradingView (Pine Script)
  • NinjaTrader
  • Other structured trading platforms

If the indicator is not written for cTrader, Xen may recommend converting it first before applying changes. This ensures that modifications are made on a compatible code base.

When to Use This Workflow

Use this workflow when you already have an indicator and want to change or improve it. This may include fixing bugs, adjusting calculations, adding alerts, or extending the logic.

Do not use this workflow if you are building a completely new indicator or converting an indicator from another platform. In those cases, use a build or conversion workflow instead.

What You Should Provide

For best results, always provide the full source code of the indicator. Partial snippets are not sufficient, as Xen needs the complete file to apply changes safely. You should also clearly describe what you want to change and, if possible, explain the current behaviour and what should happen instead.

Examples of useful requests include:

  • “Add alert conditions when the signal changes direction.”
  • “Fix the logic so it does not repaint.”
  • “Add a moving average filter to reduce false signals.”
  • “Change the output so bullish and bearish signals use separate plots.”

Clear instructions lead to more accurate results.

How to Interact with Xen

Be specific about the change you want. Xen performs best when the request is focused and clearly defined.

Good requests include:

  • “Add pop-up and sound alerts.”
  • “Change the calculation to use EMA instead of SMA.”
  • “Fix the signal so it only triggers on bar close.”
  • “Add a trend filter using a 200 period moving average.”

Avoid vague requests such as:

  • “Improve this.”
  • “Make it better.”
  • “Change the logic.”

If the request is unclear, Xen will need to ask for clarification before making changes.

What Xen Will Do

Xen will analyse the existing indicator code and apply targeted modifications based on your request. It will aim to preserve the original structure and avoid unnecessary rewrites. Depending on the selected mode, Xen may return a full updated file or focused code changes with guidance on where to apply them.

What Xen Will Not Do

Xen will not rebuild the indicator from scratch unless it is necessary. It will also avoid changing unrelated parts of the code or making assumptions about major changes. If your request is too broad or unclear, Xen will ask for more detail before proceeding.

Common Changes You Can Request

Typical updates include adding alerts, filters, or additional outputs, adjusting calculations, fixing repainting issues, improving signal timing, or resolving compile and logic errors.

Before submitting your request, make sure you provide the full indicator source code and clearly state what needs to change. Mention any known issues or expected behaviour to help guide the update. If the indicator is from another platform and needs to be adapted for cTrader first, use the Convert an Indicator workflow before making modifications.