
OI: AVMA Candles
Clean candles + unified labels from multiple closed-source engines. Powered by AVMA + SAND + Bungee (Unified).
Candle colouring and unified buy/sell labels driven by three closed-source engines working together — built to keep charts clean while improving timing and context.
Built for readable states and repeatable workflows — not indicator overload.
Designed to improve timing and decision quality while keeping the chart clean.
Sensible controls grouped logically — start with defaults, then tune for your market and session habits.
Access is managed via originalindicators.com — purchase, submit your TradingView username, and you’ll be added to the invite-only list.
Candle colouring to reflect the dominant state
Optional background tint (context layer)
Unified labels when engines align (reduced noise vs single-source signals)
Use candle colour as your baseline bias.
Use background/context tint to avoid trading against the wider state.
Act on labels only when they align with your session plan and structure.
If you’re getting too many labels: reduce sensitivity / enable guards / filter sessions.
Best for
- Keeping charts minimal while still getting structure + timing
- Trend-following and pullback entries with context
- Traders who like ‘state’ + ‘trigger’ workflows
Not ideal for
- Over-trading in low volume chop (use regime/participation filters)
- Treating labels as unconditional entries (they’re confirmations, not permission slips)
- Module toggles (run it minimal first)
- Label density / sensitivity (reduce noise)
- Visual overrides (keep it readable on your chart theme)
Avoid over-tuning early
Start with defaults, learn the states, then tune for your main market and session habits. The edge comes from consistent execution, not constant parameter chasing.
Will this replace my whole system?
It can, but it’s designed to slot into a workflow: state first, trigger second, management third.
What’s the point of ‘unified’ labels?
Confluence without clutter — you get fewer, higher-quality moments instead of constant blinking lights.
Works across assets and timeframes — best used as a decision layer alongside your execution model.
Get Access