Open New > Strategy Builder in NinjaTrader Desktop inside your Ninja Mobile Trader VPS to create a rule-based NinjaScript strategy. We specialize in hosting NinjaTrader on Windows, so your scripts, indicators and Desktop setup stay together when you connect from a PC, Mac, phone or tablet.
Build on a larger screen, then return to the same hosted installation from another supported device. With Windows licensing included and 24/7 VPS support, NMT gives you a central place to maintain that development workspace.
Build the rule before testing its results#
NinjaTrader’s point-and-click Strategy Builder generates NinjaScript from the conditions and actions you select. This guide covers creating and compiling that script. Our Strategy Analyzer guide covers historical testing once the strategy exists.
An ATM template is a separate position-management configuration. Saving one does not create a programmable NinjaScript strategy.
Work in a supported simulation setup with live execution and copier routes excluded. Before changing an established installation, preserve it with our NinjaTrader backup procedure.
Create a named Builder strategy#
Follow the Builder screens in your remote Windows installation:
- From the Control Center, choose New > Strategy Builder and select New Strategy.
- Give it a descriptive name and description, such as PracticeRule01.
- Review Default properties, including the calculation mode. More properties exposes further settings.
- Add only the extra series your design needs under Additional data.
- Define adjustable settings under Inputs and Variables.
- Create the rule in Conditions and Actions, then review Stops and Targets if your design submits orders.
- Select Finish to compile. The separate Compile button is available during editing.
Keep the first version small enough that you can explain each condition and action.
Translate one condition into the interface#
A condition answers a true-or-false question. As an interface exercise, use the documented price-comparison controls:
- On Conditions and Actions, add a condition.
- Select Price > Close on each side.
- Choose the greater comparison.
- Keep the left side on the current bar and set the right side’s Bars ago to 1.
- Confirm with OK.
This compares the current close with the previous bar’s close. For the practice rule, choose a drawing action from the Actions window, with no order-management action. You can learn how a condition maps to an action before designing entries and exits.
When combining rules, check whether all conditions must be true or any one is sufficient. Compare compatible values: a numeric indicator value and a true-or-false expression are different types.
Write down the intended behavior#
Use this worksheet alongside the Builder, then check the completed rule against it:
| Decision | Record before compiling |
|---|---|
| Inputs | Which values should be adjustable, and what each means |
| Comparison | Left value, operator, right value and each bar offset |
| Group logic | Whether all conditions or any condition can trigger the action |
| Action | The exact drawing or order action you selected |
| Expected result | One situation that should trigger it and one that should not |
| Revision | The script name and the change made since the previous version |
A precise rule record makes it easier to spot an accidental setting change when returning to the workspace later.
Keep an editable version#
View Code shows the generated NinjaScript. Unlock Code switches to code editing and prevents subsequent editing of that script in the Builder.
Keep a Builder version before taking that step: select the saved script in the strategy dropdown and use save as to create a separately named copy. Include NinjaScript files in a suitable backup archive to preserve custom scripts.
Resolve compilation, then move to validation#
A successful compile confirms that the code builds; it does not establish the strategy’s trading behavior or profitability.
NinjaTrader’s compile-error guide explains that compilation includes all NinjaScript files. Inspect the error list’s filename, description and code before assuming the new rule is responsible. Keep the backup and capture those details for the relevant script developer instead of deleting unrelated files.
After compilation, use the existing Strategy Analyzer procedure for a defined historical test, followed by supported simulation checks. Keep live routing excluded while validating your rules. Before later operating automation on the VPS, follow our strategy continuity checklist for application, connection and recovery requirements.
Build your NinjaTrader workspace on NMT
Keep your scripts, installed tools and Windows Desktop setup in one hosted workspace you can reach across supported devices.