Alerts

Twenty-four alert conditions ship with this indicator. Every one of them is a state observation on a confirmed chart bar, not a transition event and not an entry signal. That distinction is the first thing this page teaches, because it changes how the alerts should be wired and what they will and will not tell you.

State vs. transition — why it matters

A transition alert fires on the moment something flips. A state alert fires as long as the state holds. These 24 conditions are all the second kind. MACD 01 Is Bullish does not mean "slot 01 just turned bullish." It means "slot 01 is bullish right now, on the chart bar that just closed." Wire it with "Once Per Bar Close" in TradingView and it will fire every confirmed chart bar while the state remains true. That is deliberate. If you want true per-slot transition behavior, you need separate transition logic; this indicator plots the slot fast line, but the per-slot slow line used for the bullish/bearish state is internal, not a plotted line you can cross against in TradingView's generic alert builder.

The bar-close gate

Every alertcondition is gated by barstate.isconfirmed on the chart timeframe. In practice:

• Alerts only fire when the chart bar closes. No intra-bar firings, regardless of chart timeframe.

• This gate is independent of each slot's On Bar Close? setting. On Bar Close? controls what the slot reports; the chart-bar gate controls when the alert fires. Two layers, two switches, no interaction beyond what each one does in its own layer.

• If you need the distinction sharpened, MTF & Repainting walks it with a two-posture verification.

If you want a one-shot alert that fires once after it is armed, TradingView's "Only Once" mode on the same condition is the quickest way there. Treat it as a one-shot notification, not a reusable transition detector that resets every time the state changes.

The 24 conditions

Grouped by family. Names are exactly as they appear in TradingView's alert dialog.

Per-slot bullish / bearish (20)

For each of the ten slots, two conditions:

• MACD 01 Is Bullish — slot 01's fast is above slot 01's slow on the confirmed chart bar.

• MACD 01 Is Bearish — slot 01's fast is below slot 01's slow on the confirmed chart bar.

• MACD 02 Is Bullish / MACD 02 Is Bearish

• MACD 03 Is Bullish / MACD 03 Is Bearish

• ...through MACD 10 Is Bullish / MACD 10 Is Bearish.

The "bullish" / "bearish" phrasing is about the slot's internal fast-vs-slow posture, not a claim about the market. Slot 03 can be bullish by its own definition while slot 01 is bearish by its own, and neither is telling you anything about where price is headed — only where each slot's normalized MACD sits relative to its own normalized signal right now.

One concrete implication: per-slot alerts fire for every enabled slot whose values have formed, regardless of whether the slot is steering the blend. A slot set to weight 0 is still alert-active. That is intentional — it is how "observer" slots work.

Blended (2)

• Blended MACD Is Bullish — the blended fast is above the blended slow on the confirmed chart bar.

• Blended MACD Is Bearish — the blended fast is below the blended slow on the confirmed chart bar.

Two details worth internalizing:

• The blend is a weighted average of the fast/slow/histogram across enabled, non-zero-weight slots. If every enabled slot has weight 0, the blend is na and the blend alerts cannot fire.

• If master smoothing is enabled, the blend alerts read the smoothed blended fast and slow. That is a lagging read by construction. A blend alert on a heavily smoothed pane is not an early signal; it is a late one. This is covered in Limitations & Trust Boundaries under master smoothing.

Alignment (2)

• All MACD Slots Bullish — every enabled slot whose values are not na is on the bullish side of its own signal on the confirmed chart bar.

• All MACD Slots Bearish — same, bearish.

Two things to understand about this count:

• Weight does not matter. A slot enabled with weight 0 still participates in the alignment count. If you add an observer slot, expect it to join the tally.

• Source overlap does matter. Ten slots that share source and lengths and differ only in timeframe produce alignment that reflects the persistence of one underlying convergence story, not ten independent agreements. When this alert fires on a slot set that has not been deliberately differentiated, treat it as information about correlation, not as consensus. This is the pack's lead misuse warning; Limitations & Trust Boundaries opens with it.

What this indicator does not alert on

This matters as much as what it does, because absent features are honest boundaries, not oversights:

• No native crossover or crossunder alerts. There is no MACD 01 Cross Above Signal condition. Per-slot signal lines are not plotted, so a generic TradingView cross alert cannot directly compare this indicator's plotted slot fast against that slot's internal signal. Use the shipped state alerts, write custom transition logic, or use another plotted MACD if your workflow requires literal per-slot crosses.

• No native histogram alerts. The four-state histogram color is rich information, but there is no alert for "histogram just flipped from faded green to full green" or "histogram crossed above 50." Build those in TradingView against the histogram plot if you need them.

• No native overbought / oversold alerts. The 70 and 30 reference lines are visual brackets, not trigger thresholds. The pane does not behave like RSI, and wiring OB/OS alerts into the script would pretend otherwise.

• No cross-asset divergence alerts. There is no "chart slot is bullish and cross-asset slot is bearish" condition. If you want to monitor a regime split between the chart instrument and a cross-asset slot, wire two separate per-slot alerts and compare externally.

Each absence is a decision. The indicator is a multi-context MACD workbench, not a signal service. Bolting crossover or OB/OS alerts on as natives would blur that boundary.

A practical wiring note

TradingView's alert dialog supports several trigger modes. The ones that make sense for state alerts:

• Once Per Bar Close. Fires every confirmed chart bar while the state holds. Useful as a monitoring feed.

• Only Once. Fires once after the alert is armed, then goes quiet. Useful for "tell me the first time this state appears and don't keep monitoring it with this alert."

• Once Per Bar. Fires on the first bar where the state becomes true within a bar. Because these alerts are gated by barstate.isconfirmed, this mode behaves equivalently to "Once Per Bar Close" for this indicator.

Avoid intra-bar modes on these conditions. They will not fire intra-bar because of the gate, and setting them that way only obscures what is happening.

Reading an alert when it fires during a live session

The moment an alert fires on your phone is not the moment the pack is written for. It is written for the moment ten seconds later, when you are staring at the chart and deciding what, if anything, to do. The discipline around that moment is most of the value the alert layer provides.

Three habits worth keeping.

First, name the alert. Out loud if you can. "MACD 03 Is Bullish on SPY 5. That is my 60-minute slot on SPY, still bullish on the bar that just closed." This reads trivial, and it is the habit that prevents the most common kind of alert-triggered mistake — acting on a name that turned out to mean something other than what you remembered. "Bullish" here means the slot's fast is above its slow on the most recent confirmed chart bar. It does not mean "price is up," it does not mean "buy," and the word "bullish" does not confer any of those meanings no matter how many times the alert fires.

Second, check what you expected to be true. If you wired the alert as part of a specific workflow — a curated three-slot alignment, a cross-asset regime split, or a blend-crossed-its-signal transition using the plotted blended lines — then the alert fired in the context of that workflow's other evidence. Look at the rest of it. If the alignment alert is firing but the pane itself has a mild blend and slot lines that disagree about fast-vs-slow, the alignment is genuine (every enabled slot is on the same side of its own signal) but the conviction is softer than the alert name implies. That is not a malfunction. It is what alignment looks like when the slots have less to say.

Third, decide before you act whether the alert changed anything. If the answer is "this is the fifteenth time MACD 01 Is Bullish has fired in the last hour and I have not acted on any of them," then firing number sixteen does not carry new information. The monitoring feed serves a different purpose from the decision trigger, and conflating the two is how state alerts turn into over-trading. If you want an alert that only speaks when something changes, use one-shot alerting with care or build true transition logic outside these shipped per-slot conditions.

That discipline is easy to describe and hard to keep. The volume of alerts this indicator can emit on a busy day — twenty-four conditions, each capable of firing once per confirmed chart bar — can wear down a reader who tries to respond to each one. Reduce the wiring to the alerts you have a real use for. An alert you will ignore is worse than no alert, because it costs attention to decline.

Where to go next

For the mental model behind the bullish/bearish wording and what slot fast vs. slot slow means, Visuals & Logic. For why the alignment alert deserves care, Limitations & Trust Boundaries. For wiring alerts into named setups, Workflows. For alerts that fire every bar when you expected transitions, Troubleshooting.