Documentation
Documentation
Getting a tool onto a chart is the easy half. This is the other half: what each reference is, and why it is computed the way it is. A tool you can’t explain is one you can’t take responsibility for.
Every calculation, not every checkbox
A parameter list is not documentation.
Most indicator documentation tells you which setting turns a feature on. That is a menu, not an explanation. It leaves you able to operate the tool and unable to say what it means.
Ours is written the other way round. For every reference a tool draws, the documentation states what it is, how it is computed, when it updates, and what it does not tell you. That last one matters as much as the rest: knowing the boundary of a reference is what stops you reading meaning into it that was never there.
This is the practical side of refusing to ship a black box. If we ask you to put a level on your chart, we owe you the rule behind it — see what we don’t do.
Reference by tool
The full reference for each tool lives on its own page, alongside the breakdown of what the tool is for.
- ADP X
- In development 75% — documented when it ships
- MGI HUD X
- Full breakdown · reference in progress
- MGI ICT
- In development 99% — documented when it ships
- DOM HUD X
- In development 70% — documented when it ships
- PlayBook Coach X
- In development 75% — documented when it ships
- Rejection Zone X
- In development 75% — documented when it ships
- TTR X
- In development 80% — documented when it ships
- IB VBAR X
- In development 90% — documented when it ships
- Bias HUD Live X
- In development 50% — documented when it ships
- Tape Reader Live X
- In development 70% — documented when it ships
- Market Auction Live X
- In development 60% — documented when it ships
- Wyckoff X
- In development 50% — documented when it ships
The per-reference documentation is being written. Until it is published, questions about how a specific level is computed are answered directly by email — ask, and the answer you get will be the one that ends up in the documentation.
Where a tool needs particular calibration for a particular use, that belongs in the tool’s own documentation rather than here.
When something does not work
The install-time problems — the tool not appearing in the indicator list, a compile error on import, an empty chart after loading — are covered at the end of Setup, where you will already be when they happen.
Two things are worth knowing before you start debugging anything:
Check these first
- A tool missing from the indicator list is almost always a missed restart. Close NinjaTrader completely, not just the chart.
- A compile error on import usually means an older version of ours is still installed, or another add-on declares the same name. Remove the previous version, then import again.
Anything that is not an install problem — a level that looks wrong, a figure that does not match what you expect, the platform lagging with the tool on the chart — is a support question, and we would rather hear about it than not.
Asking for help
Email support@makedgelab.com. Reproducing a problem is most of the work of fixing it, so the more of this you can include, the faster it moves:
Include if you can
- Your NinjaTrader 8 version.
- The instrument and the chart timeframe.
- What you were doing when it happened.
- Whether it was live data, Market Replay or a simulated feed.
- A screenshot, if the problem is something you can see.
What we can answer: how a tool computes something, why a reference behaves the way it does, anything about installing, updating or running it.
What we cannot: what you should do in a position. We build software; we are not financial advisers, and nothing we publish is a personal recommendation. The risk disclosure sets out why that line exists.
Not covered here yet?
This documentation is being written alongside the tools, and the gaps above are marked rather than hidden. If you need something that is not here, asking is the fastest way to get it — and the fastest way for it to end up on this page.