Installing a PBT Bot in NinjaTrader: The Import Wizard Steps Most Traders Rush Before Going Live

"No coding required" gets taken too literally. Traders hear it, picture a single download-and-go step, and treat the NinjaTrader import process like installing a phone app. It isn't. NinjaTrader 8 handles each PBT bot as a NinjaScript add-on, and the import wizard has a handful of steps that quietly determine whether the bot runs clean or throws compile errors the first time you try to attach it to a chart.

Here's the setup sequence worth doing right, start to finish.

Close every chart window first

This is the step almost everyone skips. NinjaTrader won't fully reload a NinjaScript add-on while a chart window referencing it is still open — you'll import the bot, get a "successful" message, and then watch it fail to compile or simply not show up in the Strategies list. Close all chart windows before you ever touch Control Center > Tools > Import > NinjaScript Add-On. It takes ten seconds and it's the difference between a clean import and a half hour of "why isn't my bot showing up" troubleshooting.

From there, point the import wizard at the .zip file for the bot — ORB, Snapback, Scalper, 10 EMA, NR7, or Volume Spike, whichever of the 15 automated strategies you're adding. NinjaTrader will compile it in the background. Watch the Log tab in Control Center, not just the popup — a successful import still throws warnings sometimes, and those warnings tell you whether an indicator dependency didn't come through.

Find it, don't assume it

Once the import finishes, the bot won't attach itself anywhere. Open a chart for the instrument you actually trade, go to the Strategies tab, and look for it in the list by name. New traders sometimes attach the wrong variant of a bot name after importing an update, because NinjaTrader doesn't overwrite an old version automatically — it can leave both versions in the list. If you're reinstalling or updating a bot you've already got, check for duplicates before you enable anything.

Match the chart before you touch the inputs window

Every PBT bot expects a specific timeframe and instrument setup — this is the same chart template matching we've covered before, and it matters more at install time than any other point, because the inputs window inherits whatever's already on the chart. Attach the strategy to the wrong timeframe and the default parameters won't mean what you think they mean. Get the chart right first, then open the Strategies dialog to configure inputs.

Respect the firm's rules in the inputs window, not just your own preference

This is where setup turns into a risk decision. The inputs window controls position size, stop distance, and daily trade limits — and those numbers have to fit inside whatever evaluation or funded account you're running the bot against. Apex, Lucid, BluSky, and TakeProfit each set their own daily loss limits and drawdown rules, and the bot doesn't know which firm you're with. It'll run whatever size you type in. Pull up your account's daily loss limit before you set position size, not after a bad session tells you the hard way.

Enable it in Sim101 before you enable it live

Toggle the strategy to "Enabled" against a Sim101 account first and watch at least a few sessions. You're not testing whether the bot works — the backtest data already covers that. You're confirming the ATM Strategy bracket is firing the stop and target you configured, that the connection to your data feed is stable, and that the strategy actually behaves the way the Strategies tab says it will. A bot that looks enabled and a bot that's actually placing orders are two different things until you've watched it do it.

Only then flip it live

Once Sim101 confirms the brackets and the connection are solid, switching the account in the Strategies dialog from Sim101 to your live or funded account is the last step — not the first one. Everything before it is setup. This part is just a dropdown.

Get the import, the chart match, and the Sim101 check right once, and every bot you add after that follows the same five minutes. Skip any of them, and you're troubleshooting a "broken" bot that was never actually broken — it was just installed in a hurry.