NinjaTrader 8 Strategy Builder: Building a Futures Strategy Without Code

A rule you can say in one sentence is a candidate for automation, but whether it makes money is a separate question, and the Strategy Builder answers the first one faster than the second. NinjaTrader 8's Strategy Builder lets you assemble a strategy from conditions and actions without writing NinjaScript, then generates the code for you. It's a good way to find out cheaply that an idea doesn't work.

Opening it

In the NinjaTrader 8 desktop Control Center, open the New menu and choose Strategy Builder. It walks you through a wizard: pick indicators, define the conditions that trigger an entry and an exit, set the actions, add a stop loss and profit target, and review the strategy's properties. When you finish, it generates a NinjaScript strategy that you can open in the NinjaScript Editor and read. Reading the generated code is worth doing once, because it shows exactly what orders the strategy submits. The official NT8 help guide at NinjaTrader's NT8 documentation is the authority on the wizard's current screens, since the layout can change between releases.

A simple example: 9 and 21 EMA crossover

1. Name the strategy and add a 9 period EMA and a 21 period EMA as indicators.
2. Set the long entry condition: the 9 EMA crosses above the 21 EMA.
3. Set the action: enter long at market for 1 contract.
4. Add the short side: the 9 crosses below the 21, enter short at market.
5. Set a stop loss and a profit target in ticks or dollars.
6. Finish the wizard to generate the strategy.

Before you test, check the strategy's Calculate setting. Whether it evaluates on bar close or on each tick changes when signals fire, and a backtest on one setting won't match live behavior on the other.

Backtesting it

Open the Strategy Analyzer from the Control Center New menu. Choose the strategy, the front-month contract (named by month and year, such as ES followed by the current expiry), a data series, and a date range. You'll need historical data loaded for that contract. Futures backtests should use the front-month contract, and a suspiciously short history usually means a broken contract roll merge rather than a data limit. Set slippage and a commission value that match what you'd actually pay, because the default of zero flatters every result.

Friction matters more than most first backtests admit. Hypothetically, a $4 round-turn commission plus one tick of slippage each way on ES ($25) costs about $29 per trade. If a crossover strategy trades 5 times a day for 20 sessions, that's 100 trades and $2,900 of friction. A strategy has to earn that before it earns anything.

Look at net profit after costs, the largest drawdown, the average trade and the trade count. Don't lean on a single metric, and don't treat an in-sample result as proof. A backtest on the same data you used to pick the settings is a description of that data. A small count of trades isn't an edge either: 30 trades is not a statistically proven edge. A moving average crossover on a short intraday timeframe often struggles when price chops sideways, which is why it makes a good first test, since you learn how a plain rule behaves before you add ideas to it.

From backtest to SIM

If a result survives costs and a separate stretch of data, the next step is running it on SIM from the Strategies tab in the Control Center. Two things are easy to confuse here. Selecting a SIM account for the strategy is one step, and connecting to a Playback connection to replay historical data is another. One doesn't imply the other. After a run, review the Trade Performance report. SIM is useful for checking that orders, stops and targets behave as coded, but it doesn't reproduce live fills, queue position or what you feel when real money is at stake. 50 SIM trades is not live proof.

Where the Strategy Builder runs out

I'd check the help guide for what your version supports before assuming a limit. The ones I'd plan around are filters that need a second timeframe, logic with several phases such as waiting for a setup, then a trigger, then managing the trade, and position sizing that depends on equity or volatility. If you need any of those, that's the point to move to NinjaScript, either by editing the generated code or writing the strategy yourself. A fixed contract count can also hide risk: 1 ES contract is $50 a point, while 1 MES is $5 a point, so choose the product deliberately.

Automation also isn't available on every firm's accounts, so check the rules of any evaluation or funded account before running a strategy on it. If you want to see how the YMI bots are specified, read the Marty bot specs. Bot access is part of the Pro membership, not Intro or VIP.