Alerts

Ten alert conditions in three groups. Every alert is evaluated on confirmed chart bars only. Every alert reports a state — K above or below D, or every enabled slot in the same K-vs-D direction — not a transition. Nothing fires on the 0, 100, 50, or the dashed 20 and 80 lines.

That is the short version. The rest of this page explains what each alert says, what it deliberately does not say, and what to expect when you wire these in TradingView's alert interface.

The ten conditions

Per-slot (six total)

• Stoch 01 Is Bullish — slot 01's K is above slot 01's D on a confirmed chart bar.

• Stoch 01 Is Bearish — slot 01's K is below slot 01's D on a confirmed chart bar.

• Stoch 02 Is Bullish / Stoch 02 Is Bearish — same two states for slot 02.

• Stoch 03 Is Bullish / Stoch 03 Is Bearish — same two states for slot 03.

Each per-slot alert fires based on that slot's own K-vs-D relationship. Once the slot's D value is available, it is the same relationship that drives the slot's line color — full tone is bullish, faded is bearish — so a per-slot alert and the slot's color on the same confirmed bar should agree. During warm-up, slot color can fall back to a midline rule while D is still unavailable; do not treat that early color fallback as an alert state.

A disabled slot does not fire its per-slot alerts. The alertcondition is still declared on the indicator for wiring purposes in TradingView, but it will never trigger while the slot is disabled. Enabled-but-zero-weight slots and enabled-but-plot-hidden slots fire their per-slot alerts normally — weight and plot visibility do not gate alert evaluation. Only Enable Stoch 0N does.

Blend (two total)

• Blended Stoch Is Bullish — blended K is above blended D on a confirmed chart bar.

• Blended Stoch Is Bearish — blended K is below blended D on a confirmed chart bar.

These fire on the blend pair's own K-vs-D relationship. Same logic as the per-slot alerts, applied to the weighted blend you configured. They fire independently of whether Plot Blended K/D is on or off — hiding the blend visuals does not disable the blend computation or the blend-based alerts. If you turned off the plot for visual reasons and are confused about why a blend alert is still firing, that is the intended separation between display and logic.

When no slot is contributing to the blend (every enabled slot is warming up with na K values, or every enabled slot has weight 0), the blended K and D are both na, and neither blend alert can fire on that bar.

Alignment (two total)

• All Stoch Slots Bullish — every enabled slot with a non-na K has K above D on a confirmed chart bar.

• All Stoch Slots Bearish — every enabled slot with a non-na K has K below D on a confirmed chart bar.

This is the alert that deserves a careful read.

The alignment tally counts every enabled slot with a non-na K. It does not look at weights. An enabled slot with weight 0 — an observer slot, in the sense used in Workflows — still counts toward alignment. A slot with plot hidden still counts. A disabled slot does not count.

The alignment alert is reporting K-vs-D state across the enabled slots that are currently contributing evidence. It is not reporting breadth across independent observations. If the three slots share source, K length, and MA families — differing only by timeframe — the alignment alert is closer to a trend-persistence detector than to a three-way vote. It is one measurement sampled at three cadences, and the alignment holds for as long as the trend does.

And because Base only has three slots total, a single misconfigured or unintended slot carries a third of the alignment tally. The damage per slot is larger than it would be on a pack with ten slots, where one misconfigured slot is a tenth of the tally. On Base, alignment is a coarse instrument. Treat it accordingly.

A quick test before you rely on the alignment alert on your current configuration: can you describe, in one sentence, what makes each of your three slots report something different? If slot 01 and slot 02 only differ by timeframe and share everything else, the alert is seeing two close-to-duplicate measurements and one distinct one — a two-slot vote with a bystander. If all three only differ by timeframe, the alert is one measurement voting three times. That is the configuration the alert is most likely to fire misleadingly on, because trending instruments produce long runs of alignment on duplicated slots regardless of whether anything meaningful changed.

That caveat is not a flaw in the alert. The alert is doing exactly what the code says it does. The caveat is about how you read the alert. Limitations and Trust Boundaries walks the full alignment trap as its opening section.

Confirmation gating

Every alert is gated by barstate.isconfirmed — evaluated only on confirmed chart bars. That is a deliberate choice. Alerts do not fire on bar-in-progress ticks.

The subtlety: the gate is about the chart bar, not the slot's higher-timeframe bar. A 60m slot running with On Bar Close? = false can still carry intra-bar-evolving values across multiple confirmed chart bars, because the chart bars are completing while the 60m slot bar is still open. Under that configuration, per-slot alerts on slot 03 can fire on chart bars whose state may still revise as the 60m bar continues to form.

Two mode/behavior pairs to carry forward:

• On Bar Close? = true: each slot is working with its previous higher-timeframe bar's values. Alerts fire on confirmed chart bars against those previous-close values. The values do not revise across chart bars inside the same higher-timeframe bar.

• On Bar Close? = false: each slot is working with the live higher-timeframe bar's values. Alerts fire on confirmed chart bars against whatever the slot shows at that chart bar's close, which is still an intra-bar read for the slot if the higher-timeframe bar is still open.

MTF and Repainting treats this in more detail. If you are about to wire alerts and you do not yet have a firm grip on the bar-close switch, that is the page to read first.

State, not transition

Every alert on this indicator is level-based. "Bullish" means K is above D. "Bearish" means K is below D. There is no transition condition.

Practically: when you wire an alertcondition in TradingView and set it to fire on every match, Stoch 01 Is Bullish will fire on every confirmed chart bar for which slot 01's K sits above its D. If slot 01 sits in its bullish state for forty bars, the alert fires forty times.

That is not a bug. It is the design of the alertcondition. If you want a cross-style transition alert — "just crossed bullish" — you need external state tracking or a separate tool built for that transition. The blended K and D are plotted, so blend-pair crossover workflows have visible series to work from. Per-slot D lines are not plotted on Base, so a per-slot K-vs-D transition is not something you can derive from the visible slot K plot alone. The indicator does not pretend it has transition alerts.

The same is true for the alignment alerts. All Stoch Slots Bullish fires on every confirmed chart bar for which every enabled non-na-K slot is in its bullish state. If the alignment holds for a twenty-bar run, the alert fires twenty times — not once on the bar alignment became true.

This level-based design cooperates well with TradingView's only once and once per bar close options. A reader who wants one alert per bar uses once per bar close. A reader who wants a single alert at the moment alignment became true uses an external flag in their TradingView alert workflow.

Alerts deliberately not wired

Five classes of alert are not present on this indicator, and the absence is a design choice, not a gap. Some can be built from plotted lines in TradingView; others require external state or a separate script because Base does not plot every internal series.

No native crossover or crossunder alerts on slot K-vs-D state, on the blended pair, or on the midline. The level-based per-slot bull/bear alerts carry the K-vs-D information. A reader who wants a single blended-pair "just crossed" alert has plotted blended K and D to work with. A reader who wants per-slot K crossing its own D needs a surface that exposes the slot D line or tracks the prior state externally.

No threshold alerts on the 80 or 20 reference lines. These lines are reference zones. Nothing in the indicator fires on them. A reader who wants an alert when a line crosses 80 wires it in TradingView on top of the plotted lines.

No native divergence alerts. Divergence detection across any of these lines is external work. Base does not implement one.

No alignment-transition alerts. There is no "All Slots Just Turned Bullish" condition. All Stoch Slots Bullish reports state, not transition. If you want the moment alignment became true, you derive it externally from the state alert.

No saturation alerts. No alert fires at 0, 100, 95, 5, or any level the user might configure. Saturation is context, not signal — see Visuals and Logic.

Hidden alert placeholders

The indicator plots two numbers at display.none so they can be referenced from TradingView alert message templates without drawing anything on the pane: Active Bullish Count and Active Bearish Count. These are the counts of enabled, non-na-K slots that are currently in their bullish or bearish state respectively.

If you write an alert message like Bull count: {{plot("Active Bullish Count")}}, Bear count: {{plot("Active Bearish Count")}}, the alert payload will include the counts as numbers at the moment the alert fired. Useful for downstream tooling that wants the counts in addition to the state booleans.

These are not themselves alertconditions. They are data surfaces available to any alertcondition you wire on top of the indicator.

Wiring patterns that hold up

A few patterns worth knowing, not as recommendations but as context for what the alert surface supports cleanly.

• State alert as a visual confirmation. Wire one per-slot alert on each slot with once per bar close and use the alert payload to mark the chart visually. Each slot's alert reports the current K-vs-D color state at bar close; it is not limited to the bar where the color changed.

• Blend alert as a regime flag. Wire Blended Stoch Is Bullish with once per bar close as a regime flag. The flag updates on every confirmed chart bar. A downstream consumer can hold the latest state as a signal.

• Alignment alert as a differentiation check. Wire both All Stoch Slots Bullish and All Stoch Slots Bearish on the differentiated three-slot stack described in Workflows, not on three identical slots. The alert means more when the slots are doing different work.

• Per-slot alerts on an observer slot. Enable slot 03, set its weight to 0, keep its plot visible. Wire Stoch 03 Is Bullish and Stoch 03 Is Bearish as higher-timeframe context alerts while the blend is being driven by slots 01 and 02. Remember that slot 03 still counts toward alignment.

Cross-references

• If an alert is firing more often than you expected: Troubleshooting.

• If you are wiring alerts and have not yet chosen a stance on On Bar Close?: MTF and Repainting.

• For the color logic behind the per-slot and blend alerts: Visuals and Logic.

• For the alignment trap in full: Limitations and Trust Boundaries.