Alerts

This page explains what the alert conditions mean and what they do not mean.

That matters because alert overload usually comes from one of two mistakes:

• treating state alerts like one-time events
• forgetting that chart-bar confirmation and higher-timeframe confirmation are not the same thing

There is a third mistake worth naming too: wiring alerts around a stack you still cannot explain. Alerts help most when they call you back to a chart state you already understand.

What alert families the script exposes

Per-slot state alerts

• MA 01 Is Uptrend
• MA 01 Is Downtrend
• MA 02 Is Uptrend
• MA 02 Is Downtrend
• MA 03 Is Uptrend
• MA 03 Is Downtrend

These tell you the current slot state exists on the confirmed chart bar.

Per-slot change alerts

• MA 01 Trend Change
• MA 02 Trend Change
• MA 03 Trend Change

These tell you the slot state flipped on the confirmed chart bar.

Blend alerts

• Blended MA Is Uptrend
• Blended MA Is Downtrend
• Blended MA Trend Change

These apply the same state-versus-change distinction to the blended summary line.

Full-alignment alerts

• All MA Slots Uptrend
• All MA Slots Downtrend

These only care whether all enabled slots with valid values point the same way.

State alert versus change alert

This is the first distinction to get right.

If you want a prompt that tells you the chart entered a new condition, start with Trend Change.

If you want a prompt that checks whether a condition is true at bar close, use the state alerts more carefully and make sure you understand how your alert frequency is configured on the TradingView side.

What "bar-close gated" means here

Every alert condition in the script waits for the chart bar to close.

That is a useful filter. It cuts down on intrabar noise from the chart timeframe.

It does not mean:

• the higher timeframe is automatically confirmed
• live-forming higher-timeframe behavior stops mattering
• the chart can no longer surprise you

If On Bar Close? is off, the stack can still be using still-forming higher-timeframe values even though the alert waits for the chart bar to close.

The timing rule to remember

Use this sentence as a check:

"Alerts confirm on the chart bar. Slot timing still depends on the stack's global higher-timeframe mode."

That is why MTF and Repainting belongs in the learning path before heavy alert use.

A practical way to start

If you are new to the indicator, begin with one of these:

• one slot Trend Change alert
• one Blended MA Trend Change alert
• one All MA Slots Uptrend or All MA Slots Downtrend alert

That gives you a cleaner review prompt than turning on every state alert at once.

If you cannot yet answer which slots are shaping the blend or whether the stack is confirmed or live-forming, stop there and fix that first. Adding more alerts will not solve that confusion.

When each alert family is most useful

Alert habits that usually age badly

• enabling every slot state alert before you know which slots matter to you
• turning On Bar Close? off, then forgetting the whole stack is now live-forming
• assuming a blend alert tells the same story as full alignment
• using alerts as commands instead of prompts to review the chart state

The calmer posture is better: let alerts call you back to a chart you can already explain.

Hidden count plots

The script also exposes hidden series for active up-count and active down-count.

Those may support more advanced alert workflows, but the exact placeholder behavior in the live TradingView alert surface was not verified in this manual run. Treat them as optional advanced tooling, not as a core part of the alert workflow until you have checked the alert dialog yourself.

A simple verification drill

1. Create one slot Trend Change alert.
2. Create one slot Is Uptrend alert on the same slot.
3. Watch how they behave across several chart-bar closes.
4. Then compare one blend alert to one full-alignment alert.

What you are checking:

• change alerts and state alerts are not interchangeable
• blend and alignment are related, but not identical
• chart-bar-close gating does not erase the higher-timeframe timing choice

From here, go to Workflows if you want to build calmer alert habits, or Limitations and Trust Boundaries if you want to keep alert confidence from outrunning what the stack can justify.

Visual placeholder: Alert-setup walkthrough showing one slot change alert, one blend change alert, and a callout explaining chart-bar-close gating versus the global On Bar Close? timing mode.