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 active 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 per slot in this build. That means one active slot can stay confirmed while another is allowed to use live-forming higher-timeframe values. The docs treat the code and planning artifacts as the source of truth here.

When should I leave On Bar Close? on?

Leave it on when you are still learning the indicator, when you care about cleaner history-to-live consistency, or when you are building a workflow that becomes harder to verify once timing gets mixed. Turning it off is not wrong. Turning it off too early is where most confusion starts.

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 family should I start with?

Start with one familiar family 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."

Once I change Type:, is it still a normal Bollinger Band?

It still looks like a Bollinger layout, but the basis behavior underneath it changes with the family you chose. If Type: is no longer SMA, stop describing that slot like nothing material changed. The familiar visual grammar is still there. The basis behavior is not the same.

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 band 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 some slots are using live-forming higher-timeframe data?

Because those are two different timing layers.

• slot timing decides whether that slot reads 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 part of the stack is using 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.

How many basis families are available in the pro build?

The current build exposes 21 basis families through Type:. That breadth is there to support adaptation, not to pressure you into using all of it.

Can this indicator replace my process?

No, and it should not try to. Axiom BB Pro can make a process easier to structure, monitor, and verify. The process still has to belong to you.