Skip to content

Work on an Existing Indicator

What this Workflow Does

The Work on Existing Indicator workflow helps you make targeted changes to an existing indicator.

It is designed for modifying code you already have, rather than creating a new indicator from scratch.

You can use it to:

  • Fix bugs or incorrect behaviour
  • Add new features or signal logic
  • Adjust calculations or conditions
  • Improve performance where needed
  • Extend an existing indicator without rebuilding it

This workflow focuses on safe, controlled changes to your existing code.


Supported Platforms

You can submit indicators from:

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

If the indicator is not written for cTrader, Xen may advise that conversion is required before changes can be applied properly in cTrader.


When to Use This Workflow

Use this workflow when:

  • You already have an indicator and want to change it
  • You want to fix a bug or logic issue
  • You want to add alerts, filters, or outputs
  • You want to refine or extend an existing indicator

Do not use this workflow when:

  • You want to create a completely new indicator from scratch
  • You want to convert a non-cTrader indicator into cTrader code as a separate task
  • You only want analysis without making changes

For those cases, use:

  • Build an Indicator
  • Convert an Indicator

What You Should Provide

For best results, include:

  1. Full source code
    Paste or upload the complete indicator file.

  2. Requested change
    Clearly explain what you want to modify, fix, add, or remove.

  3. Context (optional)
    Explain what the indicator is intended to do, or where the current behaviour is wrong.

Examples:

  • “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.”

How to Interact with Xen

Be specific about the change you want.

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.”

Less useful requests include:

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

The more precise your request, the better the result.


What Xen Will Do

Xen will:

  • Read the existing indicator code
  • Preserve the original structure where possible
  • Make targeted modifications based on your request
  • Return updated code or focused code changes, depending on the selected mode

Xen will aim to avoid unnecessary rewrites and unrelated changes.


What Xen Will Not Do

Xen will not:

  • Rebuild the indicator from scratch unless required
  • Change unrelated parts of the code without reason
  • Guess major changes if your request is unclear

If your request is too vague, Xen will ask what you want changed before editing the indicator.


Common Changes You Can Request

Common update requests include:

  • Add alerts
  • Add filters
  • Change calculations
  • Fix repainting issues
  • Improve signal timing
  • Add extra plots or outputs
  • Adjust parameter behaviour
  • Fix compile or logic errors

Before submitting your request:

  • Make sure you provide the full indicator source code
  • State exactly what you want changed
  • Mention any known issues or expected behaviour

If the indicator is from another platform and needs adapting for cTrader first, use the Convert an Indicator workflow instead.