How to Handle NinjaTrader 8 Indicator Import Conflicts (When You Have the Source)

🤔 The Problem

You’re trying to import or update a custom indicator in NinjaTrader 8—and boom, you hit a compilation error.

Common reasons?

• A method signature changed in the updated version.
• An existing script is using a now-outdated version.
• Properties or methods were renamed or removed.

If you have the source code of the conflicting indicator or strategy, there's a fast, safe way to move forward.

✅ The Fix: Exclude Now, Fix Later

1. Open NinjaScript Editor

Go to Tools > NinjaScript Editor.

2. Exclude the Conflicting Script

In the NinjaScript Explorer (right-hand panel):

• Right-click the file that’s causing the issue (e.g., TdjDonchianFlagRangeBreakoutV2)
• Click “Exclude From Compilation”

This prevents NinjaTrader from compiling that file. Now you can finish your import.

3. Import the New Indicator

Go to Tools > Import > NinjaScript Add-On and select your .zip file.

With the problematic script excluded, the import should complete without errors.

4. Check What Changed

Once imported, consult the documentation for the updated indicator.

Look for:

• New or changed method parameters
• Removed or renamed methods/properties
• New required setup steps

5. Update the Old Script

Open the excluded script and update it to reflect the new method signature.

Before:

TdjDonchianFlagPoleSetup(someArg1, someArg2);

After:

TdjDonchianFlagPoleSetup(someArg1, someArg2, newRequiredArg3);

6. Re-Include and Compile

• Right-click the file in NinjaScript Explorer
• Select "Exclude From Compilation" again to toggle it back on for compilation
• Hit F5 to compile

Fix any remaining errors and recompile until you're clean.

🚨 Caution

Just because the indicator compiles doesn’t mean it works the same.

Backtest again.

• Entries may shift.
• Stop-loss behavior may change.
• Parameter logic may be completely different.

🧪 Pro Tip

Always back up your workspace and original .cs files before importing updates. If something breaks, you can restore your working version.

✅ Recap

• Exclude broken scripts from compilation
• Import your update
• Compare documentation and method changes
• Fix the script manually
• Recompile and test

Don’t skip the test phase—even a small method change can ripple through your whole strategy.