Skip to main content

Build Conditions, Plots, and Alerts in Pineify

A condition editor expresses when a rule is true. In Pineify's visual workflow, you select calculations and comparisons, combine them with boolean operators, and use the resulting condition for plots, alerts, or strategy rules.

Open Visual Pine Editor and follow the application link to your workspace. For current interface navigation, use the Pineify manual.

State conditions and crossing events​

A comparison such as fast EMA being above slow EMA can remain true for several bars. A crossover identifies a transition from not-above to above. Choose the operation that matches your intended rule.

Combine conditions with AND when all must be true, and OR when either is sufficient. Group conditions explicitly when mixing operators; changing their grouping can change which bars trigger.

Earlier visual condition editor

A complete boolean example​

This independent Pine example shows the calculation behind three combined state conditions. It does not claim that the condition predicts profitable trades.

//@version=6
indicator("Combined Conditions Example", overlay=true)
[macdLine, signalLine, histogram] = ta.macd(close, 12, 26, 9)
rsiValue = ta.rsi(close, 14)
average = ta.sma(close, 20)
condition = macdLine > signalLine and rsiValue < 30 and close > average
plotshape(condition, title="Combined condition", style=shape.circle, location=location.belowbar)

The history-dependent calculations run on every bar. The marker shows a true state on each qualifying bar; it is not restricted to the first bar of a new state.

Display the condition​

Use the condition as the boolean input for a shape, character, or other supported conditional plot. Give the marker a meaningful title and choose a position that does not obscure prices.

Earlier conditional plot configuration

Copy the generated code into TradingView, compile it, and inspect several marked and unmarked bars. If the output differs from your intention, review the inputs, timeframes, comparison directions, and AND/OR grouping.

Configure alert behavior​

Choose whether the condition should be evaluated during the open bar or only after confirmation. Values can cross a threshold and reverse before the bar closes; a live alert and a later historical marker may then differ.

Use the alert type actually exported by the script: a named alertcondition() or Any alert() function call for alert() calls. TradingView account features and alert capacity still apply. Combining conditions in one script does not bypass those limits.

A running TradingView alert uses a snapshot of the script and inputs at creation. Recreate it after relevant changes. Consult TradingView's alert documentation for the execution details.

Evaluate a trading rule separately​

Visual markers help inspect the logic, but they are not a substitute for explicit entries, exits, costs, and position sizing. Adding another confirmation condition can remove both losing and winning signals; it does not guarantee fewer false signals or a better result.

Use Create Your First Strategy when moving from condition inspection to a reproducible simulation.