NinjaTrader indicators: what they do, and which ones are worth adding

Indicators on NinjaTrader are written in NinjaScript, which is C# with a set of platform classes on top. They are compiled, not interpreted: the platform builds them into an assembly the first time and runs the compiled code after that.

That matters in one practical way. A compiled indicator can do per-tick work — reading each trade as it prints, separating buys from sells, holding state across a session — at a speed that keeps up with a fast market. Most of the difference between a simple overlay and an order flow tool is how much of that per-tick work it does.

It also means an indicator is real code running in your platform. A badly written one can slow a chart down, throw exceptions when the data feed hiccups, or fail to compile — and when a source-code indicator fails to compile, every source-code indicator on the machine disappears from the list at once, because they are compiled together into one assembly. That single behaviour explains most "my indicators vanished" reports.

Nearly every indicator is doing one of five things. Naming the job first makes the buying decision much simpler, because you stop comparing tools that were never alternatives to each other.

Trend and momentum tools are all calculations on price. They are useful and they are also, by construction, one step behind: they describe what price has already done. Nothing in that family can tell you whether a move had size behind it.

Volume and order flow tools are the ones reading a different input. Volume says how much changed hands; order flow separates the side that had to pay up from the side that was sitting there waiting. That is a genuinely separate piece of information, and it is the family we build for.

Support and resistance tools sit in between. Drawn from price alone they are guesses about where a reaction might happen; drawn from volume they are a record of where reactions actually did happen.

Two tools used consistently beats five. The most common failure we see is adding a second indicator to explain why the first one was wrong, and then a third.

NinjaTrader 8 ships with a large set of standard indicators, and they are genuinely usable. If you are learning to read a market, start there. You will find out whether a way of looking at the chart suits you before spending anything.

Free third-party scripts from forums and public repositories are a different proposition. Many were written for NinjaTrader 7 or early 8 builds and never updated. The common failure modes are not subtle: no exception handling, so a feed interruption or a session rollover throws; assumptions about bar indexing that break under Tick Replay; and compile errors on current builds, which — see above — take every other source indicator down with them.

None of that makes free tools worthless. It makes them appropriate for learning and simulation, and risky in front of live capital, which is a different question from whether they cost money.

Paid does not automatically fix it either. What you are paying for is that someone is still maintaining the thing against new platform builds — so the question worth asking a vendor is when they last shipped an update, not what the indicator claims to predict.

NinjaTrader 8.1 changed enough underneath that some indicators compiled against older 8.0 builds produce assembly errors or trigger safe mode on load. Vendor DLLs are the usual case, because they were compiled once against whatever the platform looked like at the time.

Two 8.1 conveniences are worth knowing about because they change how a busy chart is managed: data box labels can be styled so you can tell overlapping values apart, and indicators can be hidden and shown without removing them from the chart.

If an indicator you rely on stops appearing after a platform update, the useful diagnostic is not the Output window — it truncates. Read the log and trace files under your NinjaTrader 8 folder. The first real error is usually several lines above whatever the Output window shows you, and it is often not in the indicator you suspect.

An indicator can be installed correctly, load without error, and still be showing you something other than what you think. Two platform settings account for most of it.

Calculate. An indicator set to On bar close updates once per bar. For a moving average or a trend filter that is the right choice — it is cheaper and the answer does not change mid-bar.

For anything reading inside the bar — delta, footprint, imbalance, anything separating buying from selling — On each tick is not an optimisation, it is a requirement. On bar close, those tools cannot see the activity they exist to measure, and they will not warn you. They will just be wrong quietly.

Tick Replay. Enabled under Tools ▸ Options ▸ Market Data, it makes historical bars available tick by tick instead of as finished candles. Without it, a tool that reconstructs bid/ask detail has nothing to reconstruct it from, so historical bars come back empty or flat while live bars look correct.

It is expensive: loading a long history tick by tick takes real time and memory. In practice the limit is how much history you are willing to wait for, which is why it is off by default.

How you install depends on what the vendor gave you, and the two cases are handled differently.

A NinjaScript archive (source code, usually a .zip built by the exporter) goes through Tools ▸ Import ▸ NinjaScript Add-On. The platform unpacks the source and recompiles everything.

Compiled vendor DLLs do not go through Import at all. If you try, NinjaTrader answers "Selected file was made from an older, incompatible version of NinjaTrader or is not a NinjaScript archive." That message is correct and the file is fine — a folder of DLLs simply is not a NinjaScript archive. They are copied in by hand.

The install problems that come up most — a failed installer, a missing demo connection, an import that throws an error — are answered on our FAQ page.

The worry is reasonable and the answer is structural. NinjaTrader compiles the .cs source files in bin\Custom together into one assembly, but it loads .dll files in that folder as they are. Copying a DLL in does not touch a single source file, so it cannot break the compile.

On a working machine we measured, bin\Custom held 173 source indicators alongside eleven vendor DLLs from four different vendors, some dating back to 2021, coexisting without trouble.

The one real conflict would be two vendors publishing an identically named type. Ours live under the ICF.* namespace, which makes that close to impossible — and it is a risk that exists equally with Import.

ICF Market is an approved vendor in the NinjaTrader Ecosystem and a UK-registered company. We work on one family: volume and order flow. We do not make trend indicators, and there are good free ones already.

One pack is on sale today — three profiling tools that answer the "where is value" question. A footprint indicator is in development. The other views described above we do not currently sell, and this page will say so until that changes.