strategy-config-safe

To safely update NinjaTrader strategy parameters, only modify defaults within State.SetDefaults and avoid touching OnBarUpdate or execution code. This isolation prevents unintended changes to runtime logic while adjusting inputs like StopLossATRMultiplier or ATRPeriod.

The correct workflow for changing NinjaScriptProperty attributes involves four steps: identify the parameter zone in State.SetDefaults, perform pre-update validation, apply the safe change, and conduct post-update validation. This ensures parameter relationships remain valid and auditable.

NinjaTrader strategy parameter updates cause unintended execution changes when edits extend beyond State.SetDefaults into runtime logic like OnBarUpdate. Keeping modifications isolated to parameter defaults defined with NinjaScriptProperty prevents altering execution paths.

Validation rules for NinjaTrader ATR multipliers require Target2 multiplier to exceed Target1, and StopLossATRMultiplier must remain positive. These relationship checks ensure parameter configurations stay within safe boundaries during State.SetDefaults updates.

You can change ORWindowMinutes and Target multipliers without affecting live execution by restricting edits to State.SetDefaults. After updating, compile the strategy and run Strategy Analyzer on historical data to perform a controlled simulation before live deployment.

Limitations of updating parameters in State.SetDefaults include the inability to modify runtime execution logic or OnBarUpdate behavior. This approach strictly covers user-configurable parameters like ATRPeriod and StopLossATRMultiplier, requiring separate handling for any logic changes.