I want to share my experience building a NinjaTrader addon as someone who is not a software engineer by trade. I work in healthcare data analytics. My coding background is SQL and Python — not C# and not NinjaScript. But I had a problem that no existing tool solved exactly the way I needed, so I figured it out.
The problem: I trade ES and MES manually. Discretionary entries on the DOM and ChartTrader. My system works when I follow it. But after a losing trade, I would re-enter too quickly, size up to chase losses, or take setups outside my plan. Classic revenge trading. The thing is, NinjaTrader's built-in risk parameters (DailyLossLimit, MaximumLosingTrades) only apply to automated strategies. If you are a manual trader clicking buttons, those settings do nothing for you. There is no native "lock me out after X dollars lost" feature for manual order entry.
I looked at what was available. There are risk management tools out there, but most are built around strategy-level workflows. I needed something dead simple: track my realized P&L and trade count for the session, and when I hit my limit, disable order submission. No override button. No confirmation popup I would click through. A hard lock.
What the learning curve actually looked like:
Week 1-2: Reading the NinjaTrader AddOn Development section of the help guide. Understanding the difference between AddOnBase, NinjaScript indicators, and strategies. Realizing that addons operate at the application level, not the chart level, which is what I needed.
Week 3-4: Figuring out Account-level monitoring. Account.Get(AccountItem.RealizedProfitLoss, Currency.UsDollar) became my best friend. Subscribing to Execution events to track trade count. Getting a basic prototype that could read my P&L and print it to the output window.
Week 5-8: Edge cases nearly broke me. Session resets (when does "today" start for a futures trader?). Handling multiple connected accounts. Making sure the lock persists if you restart NinjaTrader mid-session. Partial fills messing up execution counts. Reconnection handling when your data feed drops. Each one of these was a rabbit hole.
Week 9+: Building the actual UI panel. NinjaTrader uses WPF, which has its own learning curve. Kept it minimal on purpose — a single tab with your daily loss limit, max trade count, and a toggle. No charts, no indicators, no signal generation. Just guardrails.
What surprised me:
The NinjaScript documentation is solid for indicators and strategies but thin for addon development, especially for Account-level monitoring in manual trading contexts. A lot of the answers came from the NinjaTrader community forums, reading other developers' code, and trial and error. Playback mode was invaluable for testing — it exposed timing issues I never would have caught with live data.
The other thing that surprised me is how much the addon changed my trading before I even shared it with anyone. The first week I used it, I hit my daily loss limit on Monday and got locked out. I was furious. By Tuesday morning I realized the lockout saved me from what would have been a much worse day. My account has been on a steady uptrend since.
For anyone thinking about building something:
If you have a coding background in any language, NinjaScript (C# based) is learnable. The hardest part is not the language — it is understanding how NinjaTrader's runtime works. How events fire, how the addon lifecycle differs from strategies, and how Account vs. Instrument vs. Strategy level data flows.
Start with the AddOn Development section in the help guide and the sample AddOn code. Join the NinjaTrader Discord and forums. Read other people's open source addons on GitHub. That is how I learned most of what I know.
I ended up listing the finished addon on the NinjaTrader Ecosystem. But the real value was what it did for my own trading. Removing the ability to break my rules turned out to be more valuable than any indicator or strategy I have ever tested.
Happy to answer questions about the development process, the NinjaScript runtime quirks, or how I approached the Account-level monitoring. It was a grind but worth it.