FAQ
Because at least one enabled slot timeframe is below the current chart timeframe.
Written By AxiomCharts
Last updated About 3 hours ago
FAQ
Why did the indicator throw an error as soon as I added it?
Because at least one enabled slot timeframe is below the current chart timeframe.
The default stack starts at 5 / 15 / 60, so a higher-timeframe chart can load into an immediate conflict. Raise or disable the conflicting slot first, then read the chart.
Is On Bar Close? global or per slot?
It is global in this build.
That means all active slots switch between confirmed and live-forming higher-timeframe behavior together. The docs treat the code as the source of truth here.
Does hiding a slot remove it from the blend?
No.
Hiding only removes the drawing. If the slot stays enabled and has a non-zero weight, it can still shape the blend and affect alignment logic.
What does a zero-weight slot actually do?
A zero-weight slot leaves the blended calculation, but it can still:
- draw its own envelope
- support slot-level alerts
- affect all-slots-above and all-slots-below alignment if it is enabled and valid
That makes zero weight useful for diagnostic layers.
Which basis type should I start with?
Start with one familiar basis type across the first stack.
If you already have a house preference, use that. If you do not, start with SMA or EMA, then learn what the stack is doing before you compare less familiar options.
The first goal is not "find the smartest basis." It is "build a stack I can explain and verify."
Can I mix an alternate ticker into the blend?
Yes, the indicator allows it. The better question is whether you should.
That can be useful in a carefully designed workflow, but it raises the interpretation burden because the alternate symbol is being remapped into chart price space. If you are new to the tool, keep cross-ticker slots at zero weight first and verify them on a separate chart.
Is the alternate-ticker slot showing the other market's raw price?
No.
The slot's Bollinger envelope is calculated on the other symbol, then remapped into the chart symbol's price region. That is useful for one-chart context. It is not literal price equality.
Why do alerts still wait for the chart bar to close if the stack is using live-forming higher-timeframe data?
Because those are 2 different timing layers.
- stack trust mode decides whether the slots read last-closed or still-forming higher-timeframe values
- alert logic decides when TradingView is allowed to mark the condition true
In this indicator, alerts wait for the chart bar to close even if the stack is reading live-forming higher-timeframe values.
Does All BB Slots Above Basis mean the trade is confirmed?
No.
It means price is above every enabled slot basis with a valid value. That can be useful context, but it is still only one chart condition inside a larger workflow.
Can the blended band replace the rest of the stack?
It can summarize the stack. It should not replace understanding the stack.
If you stop knowing which slots are shaping the blend, the summary has already become more authoritative than it deserves.
Can this indicator replace my process?
No, and it should not try to.
Axiom BB Lite can make a process easier to structure, monitor, and verify. The process still has to belong to you.