FAQ

Why did the script throw an error as soon as I added it?

At least one enabled slot timeframe is lower than the chart timeframe. The default stack uses 5, 15, and 60, so it will fail on higher chart timeframes unless you raise or disable the conflicting slot. Start by checking TimeFrame: on every enabled slot.

Why is a hidden slot still affecting the indicator?

Because hidden is not the same thing as disabled. Hide MA 0x Plot only removes the line from view. The slot can still stay active for:

• the blend, if its weight is above 0
• slot alerts
• full-slot alignment

If you want the slot gone from logic, disable it instead.

Why did setting a slot weight to zero not remove that slot from all alerts?

Because weight controls blend participation, not slot existence. A weight-zero slot is ignored by the blended pair, but it can still:

• plot
• change state
• fire slot alerts
• count toward all-slots bullish or bearish alignment

If you want the slot gone from those surfaces too, disable it.

What actually changes when I turn one slot's On Bar Close? off?

That slot shifts from confirmed requested-context behavior to live-forming requested-context behavior. That means the slot can move sooner, but its value is less final until the requested bar closes. In this Pro build, the switch is local to that slot, so the rest of the stack can stay confirmed if you want it to.

Does this indicator repaint?

The useful answer is more specific than yes or no. If a slot's On Bar Close? is on, that slot uses confirmed requested-context values. If it is off, that slot can follow still-forming requested-context values. So the real question is not "Is it pure?" The real question is "Which active slots are confirmed and which ones are still forming right now?"

Do I need all 10 slots?

No. The indicator can support up to 10 slots, but very few workflows improve because all 10 are active from the start. Most readers are better served by:

• the three-slot baseline
• one added slot at a time when it has a real job
• one optional zero-weight diagnostic slot
• one alternate-symbol slot only when that relationship already matters to the workflow

Which MA 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, keep it simple with something like EMA or SMA, then learn what the stack is doing before you start comparing more specialized families. The right first goal is not "find the smartest MA." It is "build a stack I can explain and verify."

What does a blank TimeFrame: mean on a parked slot?

If you enable a slot with a blank TimeFrame:, it falls back to the chart timeframe. That can be useful, but it is not a substitute for deciding what job that slot is supposed to do. The safer posture is:

• enable the slot
• confirm what timeframe it is actually using
• then decide whether that is the role you want

Can I mix another ticker into the stack and treat that as confirmation?

No. You can treat it as context. The mixed-symbol slot is designed to make cross-symbol comparison more workable inside one bounded pane. That is useful. It still does not prove causality, leadership, or a reliable confirmation relationship by itself.

Why did master smoothing make the pane look better but feel later?

Because master smoothing adds another smoothing pass to the blended pair after the raw blend already exists. That can calm the summary. It can also add lag. If the smoother version looks cleaner but makes the workflow harder to use honestly, turn it back off.

Why is the blend bullish when all-slots bullish is not firing?

Because those are different conditions. The blend is a weighted summary. All-slots bullish requires every enabled slot with valid data to agree. One lower-weight or weight-zero slot can still block alignment while the blend stays bullish.

Should I trust the blend first or alignment first?

Trust neither by default. First trust your ability to explain the slot stack. After that:

• use the blend when you want a weighted summary
• use alignment when your workflow actually needs all enabled slots to agree

If you cannot say which job you need, the safer move is to keep reading the slots directly for a while longer.

Should I start with mixed symbols, uneven weights, and live-forming slots right away?

Probably not. The cleaner first path is:

1. same-symbol baseline
2. legal timeframes
3. confirmed slots
4. visible active slots
5. default weights

Once that feels predictable, the more advanced features become much easier to use without telling yourself stories.