MTF and Repainting

This page exists because the indicator is only as trustworthy as your understanding of its timing behavior.

Written By AxiomCharts

Last updated About 1 hour ago

MTF and Repainting

This page exists because the indicator is only as trustworthy as your understanding of its timing behavior.

Multi-timeframe tools often get misused in one of two ways:

  • the trader assumes every historical reading behaved exactly the same way live
  • the trader treats any live-forming movement as scandal instead of a timing choice

Neither reaction helps. The useful question is simpler:

"Is this slot reading confirmed requested-context values, or am I choosing to watch that requested bar while it is still forming?"

That distinction matters because the pane can stay visually calm while the active slots are carrying very different timing assumptions underneath it.

The first hard rule

Every enabled slot timeframe must stay at or above the chart timeframe.

That means:

  • a 5m slot is legal on a 1m or 5m chart
  • a 5m slot is not legal on a 15m chart

If you violate that rule, the script throws a runtime error. That is not a bug. It is the guardrail telling you the stack no longer makes sense in the current chart context.

What On Bar Close? actually changes

This Pro build uses a slot-by-slot timing switch.

That means one active slot can be confirmed while another is live-forming.

ModeWhat that slot readsWhat you gainWhat you must not forget
OnConfirmed requested-context valuesA calmer trust posture and a live view that stays closer to the historical pictureThat slot will react later
OffStill-forming requested-context valuesEarlier movement from that requested contextEarlier does not mean final, and alerts still wait for confirmed chart bars

When On Bar Close? is on

That slot uses the last confirmed value from its requested symbol and timeframe context.

Practical meaning:

  • the slot waits for the requested bar to finish
  • the historical view and the live experience stay closer together
  • the slot is slower to react, but easier to trust

When On Bar Close? is off

That slot can use the current still-forming value from its requested symbol and timeframe context.

Practical meaning:

  • the slot can move sooner
  • the slot can change before the requested bar is final
  • the live experience is more responsive, but less settled

Neither mode is fake. They answer different timing questions.

Why this is a trust boundary

The indicator does not become more honest simply because one slot updates earlier. It also does not become more useful simply because a slot waits longer.

You are choosing between:

  • earlier information with less finality
  • later information with more stability

That is why On Bar Close? belongs in your method, not only in your settings.

What "repainting" means here

In this manual, repainting is not a moral label. It is a behavior difference between still-forming and confirmed values.

For this tool, the most important version of that difference is:

  • confirmed requested-context slot behavior versus
  • still-forming requested-context slot behavior

If you keep that sentence in mind, the whole topic gets calmer.

The part that catches people: mixed timing inside one stack

Because timing is per slot in this build, one stack can quietly carry:

  • confirmed short-term context
  • live-forming higher-timeframe context
  • confirmed outside-symbol context
  • live-forming outside-symbol context

The blend can still look neat while those inputs are not equally settled.

That is why the safest first posture is:

  • keep the active baseline slots confirmed
  • learn what the stack looks like in one trust mode first
  • only then introduce one live-forming slot on purpose

Alerts are still chart-bar-close gated

This is the nuance that catches people.

Even when one slot's On Bar Close? is off and that slot can update sooner, the alert conditions are still checked on confirmed chart bars.

That means two things can both be true:

  • the slot value can move during the requested higher-timeframe bar
  • the alert still waits for the chart bar to close before it fires

So "live-forming timing" and "instant alerts" are not the same thing.

A clean replay test

If you want to verify the timing behavior without guessing, use this drill:

  1. Open a chart at 1m or 5m.
  2. Keep one active slot on a clearly higher timeframe such as 15 or 60.
  3. Copy that slot's symbol, timeframe, baseline, and Slow settings into another unused slot.
  4. Leave one of the two slots confirmed.
  5. Turn the other slot live-forming.
  6. Watch both while the requested higher-timeframe bar is still unfinished.
  7. Note how the confirmed slot holds the settled read while the live-forming slot can still move.

What you are verifying is not whether one mode is morally better. You are verifying what kind of object each slot is showing you.

What usually gets misread

"The indicator repainted, so it must be deceptive"

Not necessarily. If you chose live-forming requested-context behavior for that slot, you chose a value that was allowed to keep evolving.

"Confirmed mode is always better"

Not necessarily. Confirmed mode is safer for trust and review. It can also be later than your workflow wants.

"Turning one slot live only affects that slot, so the blend is still clean"

Not necessarily. The blend can now summarize slots that do not share the same timing posture.

"If the alert fired late, the MTF logic must be broken"

Often the real answer is simpler: the slot was allowed to move earlier, but the alert still waited for the chart bar to confirm.

A sensible first-use posture

If the indicator is still new to you:

  • keep the three baseline slots confirmed
  • learn the stack in confirmed mode first
  • add alerts only after that mode feels predictable
  • test one live-forming slot later, on purpose

That order protects comprehension. It also reduces the chance that you start trusting speed more than you trust process.

What to verify before you leave this page

You should be able to answer these without guessing:

  • Which active slot has the lowest timeframe on your chart?
  • Which active slots are confirmed right now?
  • Would a blended shift and an alert always happen at the same instant?

If the answer to the last question is still "yes," read the alerts page next.

One more good check:

  • If you duplicated one slot and changed only On Bar Close?, could you explain why the two versions might disagree before the requested bar settles?

Where to go next

  • Go to Alerts if you need the notification timing explained cleanly.
  • Go to Quick Start if you want to rerun the first sanity checks.
  • Go to Limitations and Trust Boundaries if this page made the indicator feel a little more complex than you expected.

Visual placeholder: Replay sequence showing two otherwise identical slots, one confirmed and one live-forming, plus one callout noting that chart alerts are still checked on confirmed chart bars.