Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Most likely you have a conflict with the special bartype number, the way Ninja assigns bar types. You've probably got another add-on bar type using the same number.
I haven't used Ninja in forever and a day, so can't remember exactly how to fix this. Open the .cs inside your bin/custom/type folder for this bar type and near the top should be a fairly obvious definition for the 'number' for this bar type.
Or just wait for someone else to tell you more precisely how to do it.
I just "discovered" Kase bars on TS and I think it's largely a song of unrealized potential.
For larger range bars, the differences between Kase and simple Range bars is negligible. I usually have to conduct a sanity check when backtesting to ensure that I had no fills in gaps, but that's easy enough to do on larger range bars because the gaps almost exclusively ocurr between electronic close and open.
The "potential" of these bars is considerable given the ability to make the target input a variable.
Imagine if you could construct a range bar based off some variable (ATR, volitility, oscillators, etc).
"A dumb man never learns. A smart man learns from his own failure and success. But a wise man learns from the failure and success of others."