MTF and Repainting

This page exists because the indicator's timing behavior is one of its main trust boundaries.

The short version is simple:

• each slot can read another timeframe
• each slot decides for itself whether to use settled or still-forming requested-context values
• one stack can mix both postures

That is why a single yes-or-no answer to "does it repaint?" is not the right way to think about this tool.

When to stop reading and reset the stack

If this topic still feels slippery, go back to a smaller baseline before you keep tuning:

• keep the stack on one symbol
• keep active slots on confirmed mode first
• compare one confirmed slot and one live-forming slot only after the baseline feels stable

This matters because timing confusion compounds quickly once weighting, alternate symbols, and hidden slots get involved.

Start with the hard rule

An enabled slot must use a timeframe at or above the chart timeframe.

Practical consequences:

• a 5m slot on a 15m chart will fail
• a blank TimeFrame: inherits the chart timeframe
• the shipped 5 / 15 / 60 baseline is only valid as-is on a 1m or 5m chart

If the script errors on first load, check slot timeframes before you assume something deeper is wrong.

What On Bar Close? actually changes

Each slot has its own timing choice.

When On Bar Close? is on

That slot uses the last settled requested-context values.

In practice, this means:

• the slot is steadier
• the slot lines up more cleanly with what you later see in history
• the slot also reacts later

When On Bar Close? is off

That slot can use the current still-forming requested-context values.

In practice, this means:

• the slot can respond sooner
• the slot can move while the requested bar is still building
• the slot may not finish the requested bar where it looked intrabar

Earlier is not the same thing as better. It is a different trust posture.

Why this matters more in a stack than in a single line

In a single MTF line, confirmed-versus-live is already a meaningful choice.

In this indicator, the choice gets more important because:

• several slots can use different timeframes
• several slots can use different timing posture
• those slots can then be summarized into one blended pair

That means the pane can look unified while the timing assumptions underneath it are mixed.

What alerts do and do not change

All alertconditions in this script are evaluated on chart bar close.

What that means:

• a slot configured for still-forming requested-context behavior can move earlier inside the bar
• the alert tied to that behavior still waits for chart bar close

So if an alert "felt late," the real question may not be "are alerts broken?" It may be:

• was the slot still forming during the bar
• did the chart bar close after the slot had already moved
• was I expecting intrabar alert timing from a close-gated alert surface

A good mental model

Use this mental model when you are working with MTF slots:

• timeframe decides where the slot is looking
• On Bar Close? decides how settled that look must be before the slot reports it
• blend weight decides how much that slot matters in the summary

Those are three different decisions. Keep them separate.

How to verify the timing behavior yourself

The safest way to build trust is to compare two otherwise identical slots.

Replay test

1. duplicate one slot's symbol, timeframe, source, and smoothing into a second slot
2. leave the first slot on On Bar Close?
3. turn the second slot off On Bar Close?
4. keep both visible
5. step through replay while the requested timeframe bar is still building

What you should notice:

• the live-forming slot can move before the requested bar settles
• the confirmed slot waits for the settled version of that read
• the gap between them becomes more obvious when the requested timeframe is meaningfully higher than the chart timeframe

Live-chart test

1. choose one higher-timeframe slot
2. duplicate it
3. keep one confirmed and one live-forming
4. watch them during a still-open requested bar

This test is less controlled than replay, but it still makes the tradeoff concrete.

When confirmed mode is usually the better starting point

Use confirmed mode first when:

• you are learning the indicator
• you want the chart and the manual examples to line up more closely
• you are building a baseline stack
• you want cleaner comparison between current and historical behavior

When live-forming mode may be worth testing

Test live-forming mode when:

• you understand the settled baseline already
• earlier information would materially change your workflow
• you are willing to observe the tradeoff instead of assuming it
• you are ready to document which slots are allowed to be less settled

Mixed timing stacks: use with intent

Mixed stacks are allowed. They are not automatically bad.

They become risky when you forget that:

• the blend can summarize both settled and still-forming slots together
• a smooth summary can hide which slot is actually moving first
• alignment can include live-forming slots too

If you are going to mix timing posture, write down which slots are allowed to do it and why.

Common mistakes

Mistake: asking for a yes-or-no repaint answer

Better question:

• which slots are confirmed, and which are still forming

Mistake: turning live-forming mode on everywhere

Better approach:

• test it on one slot first
• decide whether the earlier information is actually useful

Mistake: assuming the default baseline is always valid

Better approach:

• check chart timeframe first
• adapt or disable conflicting slots before you start reading the pane

What to remember under pressure

• MTF is not the problem by itself; unexamined timing assumptions are
• confirmed mode is steadier and later
• live-forming mode is earlier and less final
• the stack can mix both
• the blend can summarize both

Where to go next

• Workflows: see how timing posture fits into actual stack design
• Troubleshooting: fix timeframe errors and timing misunderstandings
• For the Geeks: get the deeper mental model for how per-slot requested-context behavior shapes trust

Visual placeholder: Side-by-side replay sequence showing two identical higher-timeframe slots, one confirmed and one live-forming, with notes on when each line is allowed to move.