MTF and Repainting

This page exists because the main trust boundary in Axiom BB Lite is not cosmetic. It is behavioral.

Written By AxiomCharts

Last updated About 3 hours ago

MTF and Repainting

This page exists because the main trust boundary in Axiom BB Lite is not cosmetic. It is behavioral.

Multi-timeframe Bollinger overlays can look calm on history and still behave differently live if the script is reading a higher-timeframe bar before that bar has closed. This indicator gives you a direct switch for that tradeoff, but it applies to the whole stack, not one slot at a time.

If you skip this page, it becomes much easier to build habits around a chart behavior you did not actually mean to trust.

The 2 modes

On Bar Close?

What the stack reads

What you gain

What you give up

On

The last closed higher-timeframe values for every active slot

Better alignment between history and live behavior

Earlier updates from still-forming higher-timeframe bars

Off

The current still-forming higher-timeframe values for every active slot

Earlier awareness of what the higher timeframe is doing right now

A weaker trust boundary because the stack can shift before the higher-timeframe bars close

If you only remember one thing from this page, make it this:

Earlier is not the same as safer.

Before you change the mode

Ask yourself 2 questions:

  1. Do I want earlier context, or do I want cleaner history-to-live consistency?

  2. Will I still remember the whole stack is live-forming once the chart starts looking normal again?

If the answer to the second question is no, stay with confirmed mode for now.

What repaint means here

In this indicator, repaint risk is not a vague accusation. It is a specific behavior.

When On Bar Close? is off:

  • active slots can change while their higher-timeframe candles are still forming

  • the stack can look smoother in hindsight than it felt live

  • alternate-ticker remapping also follows the live-forming higher-timeframe read

When On Bar Close? is on:

  • the stack waits for the last closed higher-timeframe values

  • the chart gives up some speed

  • the tradeoff is usually worth it when you want history and live reading to line up more closely

A five-minute verification drill

Run this once before you build habits around live-forming mode.

  1. Open a lower chart timeframe that can legally request a higher slot timeframe.

  2. Keep one slot on a clearly higher timeframe than the chart.

  3. Watch the stack with On Bar Close? enabled during a still-forming higher-timeframe candle.

  4. Note that the slot stays anchored to the last closed higher-timeframe read.

  5. Turn On Bar Close? off.

  6. Watch the same unfinished higher-timeframe candle again.

  7. Notice whether the active slots or the blended band shift before the higher-timeframe candle is finished.

What you are trying to learn is not whether one mode is morally better. You are trying to learn which tradeoff your workflow can actually carry without self-deception.

If you cannot see a meaningful difference yet, that is a good reason to keep confirmed mode a little longer.

What does not change when you turn it off

These points are commonly missed:

  • each enabled slot still has to respect the chart-timeframe compatibility rule

  • the alert system still waits for the chart bar to close

  • the stack is still your chosen source, basis type, length, weight, and symbol mix

So the mode switch changes the trust posture, not the whole identity of the workflow.

When confirmed mode is usually the better default

Stay with confirmed mode when:

  • you are still learning the indicator

  • you care about cleaner history-to-live consistency

  • you are building alerts around higher-timeframe structure

  • you want your stack to behave in a more reproducible way

When live-forming mode might be worth testing

Test live-forming mode when:

  • you know exactly why earlier higher-timeframe feedback matters to your process

  • you are prepared to verify the behavior in replay or live observation

  • you are willing to accept that the chart can look less stable while the higher-timeframe candles are open

Even then, test it with a simple stack first.

Misuse to avoid

The common mistake is not turning confirmed mode off. The common mistake is turning it off and then continuing to read the chart as though nothing about trust changed.

That usually shows up as:

  • treating the live-forming stack like hindsight-clean evidence

  • forgetting that alerts still wait for chart-bar close

  • using live-forming mode on a cross-ticker workflow before you have verified the remap behavior

A healthy sentence to be able to say

"This stack is earlier because I turned confirmed mode off, so I trust it for early context only, not for hindsight-clean interpretation."

That kind of sentence keeps the tool in the right place. It turns uncertainty into a named condition instead of a hidden one.

Visual placeholder: Side-by-side chart captures of the same stack with On Bar Close? on and off during one unfinished higher-timeframe candle, with notes marking where the live-forming mode can move before the close.