Pine Script Bar-Close Entry Guard

Forces all entries to fire only on confirmed bar closes — eliminating repainting so your backtest results match live automated trading exactly.

Free snippet · Pine Script v5 · Works on TradingView free plan

Copy//@version=5
// calc_on_every_tick=false is the key setting — signals only fire on confirmed bar closes.
// This prevents repainting: what you see in backtests is exactly what executes live.
strategy("Bar-Close Entry Guard", overlay=true, calc_on_every_tick=false)

// ── Indicators ───────────────────────────────────────────
ema9  = ta.ema(close, 9)
ema21 = ta.ema(close, 21)

// barstate.isconfirmed = true only on the final tick of a closed bar
longCondition  = ta.crossover(ema9, ema21)  and barstate.isconfirmed
shortCondition = ta.crossunder(ema9, ema21) and barstate.isconfirmed

// ── Entries ───────────────────────────────────────────────
if longCondition
    strategy.entry("Long", strategy.long)
    strategy.exit("Long Exit", "Long", profit=20, loss=10)

if shortCondition
    strategy.entry("Short", strategy.short)
    strategy.exit("Short Exit", "Short", profit=20, loss=10)

// ── Visuals ───────────────────────────────────────────────
plot(ema9,  color=color.new(color.blue,  20), linewidth=1)
plot(ema21, color=color.new(color.orange, 20), linewidth=1)

Why repainting destroys automation results

The most common complaint from traders who automate Pine Script strategies is that the live performance looks nothing like the backtest. Repainting is almost always the cause.

Here is how it happens: TradingView's default strategy setting is calc_on_every_tick=true. This means Pine Script recalculates on every price movement within a bar. An EMA crossover can appear, trigger a backtest signal, and then disappear — all before the bar closes. In the Strategy Tester, that signal gets recorded as if it fired, but in live trading, the crossover never actually occurred on a completed bar.

The fix is two lines of code:

1. calc_on_every_tick=false in the strategy() declaration — recalculation only happens on bar closes.
2. barstate.isconfirmed on every entry condition — an explicit gate that is only true on the final tick of a completed bar.

Together, these ensure that every signal your strategy fires in backtesting corresponds to a real, finalized bar close — the same point in time where TradersPost or any other automation bridge would receive and execute the alert.

How the two-layer protection works

How to add this to your existing strategy

1. Find your strategy() declaration at the top of your script.
2. Add calc_on_every_tick=false to it: strategy("My Strategy", overlay=true, calc_on_every_tick=false)
3. On every entry condition (longCondition, shortCondition), append and barstate.isconfirmed.
4. Run a fresh backtest. If your results change significantly, your original strategy was repainting — the new results are the true historical performance.

Frequently Asked Questions

Related