The platform I’ve been using and building on since NT6.5. Setup, troubleshooting, and what makes it work.
In Part 3, we laid the groundwork for our Better Moving Average (BMA) indicator — setting up the file structure, building inputs for multiple moving average types, and wiring up the core logic. But identifying the average is only half the story. In this post, we’re diving into trend detection. 📉📈 You’ll learn how to:…
It’s been a while since I’ve posted here. Life stuff, personal stuff, family stuff—you know, all the stuff. But I’m hoping to get back into a rhythm again. Not daily (let’s be real), but at least once a week. And yes, I will finally finish the series I started forever ago. Probably. In the meantime,…
If you’ve ever wanted to track live trades, monitor bid/ask changes, or build a tool that reacts faster than a bar can form, OnMarketData() is where the action begins. Unlike OnBarUpdate(), which reacts to completed bars, OnMarketData() responds to every change in Level I market data — including bid, ask, and last price updates. That…
Debugging is one of the most underrated skills when it comes to writing NinjaScript indicators. You can have the cleanest code in the world, but if the logic isn’t behaving how you expect—or worse, it’s silently failing—you’ll find yourself stuck staring at a chart wondering what went wrong. In NinjaTrader, debugging isn’t quite the same…
You finally got your custom indicator to compile. You drop it on the chart, ready to feel like a genius—aaaand 💥 Unhandled exception in OnBarUpdate(). If you’ve ever had NinjaTrader slap you with one of those cryptic errors or freeze your backtest halfway through, you’re not alone. The good news? There’s a simple tool built…
In the last post, we walked through our plan for the Better Moving Average (BMA) — an indicator that lets you switch between multiple moving average types using a single dropdown. Now it’s time to start building. This post focuses on laying the foundation — getting our files created, our workspace organized, and the core…
When you’re building indicators or strategies in NinjaScript, you’ll often find yourself needing to repeat an action—like checking the last 10 bars for a pattern, scanning through a list of values, or cleaning up old draw objects. That’s where loops come in. Loops let you automate repetitive tasks inside your code, saving you from writing…
In the last post, we kicked things off with the big idea: build a better moving average indicator—one that adapts to your logic, reflects it visually on the chart, and gives you full control over how it behaves. But before we start writing code, we need a blueprint. Rushing into NinjaScript without a plan is…
In the world of automated trading and indicator building, logic is everything. Whether you’re trying to trigger a signal when price crosses above a moving average or avoid double entries during a trend, NinjaScript uses one tool more than almost any other: the bool. Booleans (true or false values) are how NinjaTrader scripts think. Combine…
👋 So… you’ve used moving averages. And let’s be honest—they’re fine. Maybe useful. Maybe just noise. Maybe you’ve got an EMA or HMA on your chart that turns green or red when price crosses over. Maybe you’ve tried tweaking someone else’s code, hoping to make it fit your style. But what if you could actually…
Notifications
