Navy: getting started

What Navy is

Navy is the language of indicators on the Wintrading charts.

• A script is an indicator like the built-in ones: on the price chart or in its own pane, with a legend, settings and alerts.
• Written like TypeScript, runs like Pine Script: once per bar, every value a series with history.
• The built-in library (Trend Cloud, Ichimoku, Supertrend, RSI Pro…) and every script in My scripts and Community are written in it.

Next: your first indicator, core concepts, what a script draws, the reference.

Bar by bar: how a script runs

The script's top level runs once per bar, starting from the oldest bar.

• close, volume… are the values of the bar being run; close[1] — the bar before.
• The live bar re-runs on every update, its state first rolled back: var counts the bar once, an object drawn on it is redrawn, not copied.
• History equals live: the same result either way. Older bars, another coin or timeframe — the history runs again.
• barstate.islast — the live bar; barstate.isconfirmed — its last run; barstate.ishistory — a closed bar.

//@navy 2.0
indicator('Bars and updates')

var bars = 0      // var: kept from bar to bar, rolled back before every update of the live bar
bars += 1
varip runs = 0    // varip: kept between the updates of the live bar too
runs += 1

plot(bars, { title: 'Bars', color: color.blue })
plot(runs, { title: 'Runs', color: color.orange })

On the live bar runs keeps growing: varip is never rolled back.

What a script looks like

A complete indicator: an EMA colored by the trend, labels on the crosses, an alert.

• //@navy 2.0 first (else NV1001), then exactly one overlay('…') or indicator('…'): its title names the script.
• Outputs — plot, hline, fill, bgcolor, marker.*, alert — stay at the top level, never inside if or a loop: their value changes per bar, na draws nothing.
• Comments //, /* … */; a ; at a line's end is optional.

Your first indicator

Five minutes, no AI. Saving your own scripts needs Pro (the trial counts).

1. Open the editor: the indicator window → My scripts → Open editor. Paste:

   //@navy 2.0
   overlay('My first indicator')
   
   plot(ta.sma(close, 20), { title: 'SMA 20', color: color.orange, width: 2 })

2. Add to chart (Ctrl+Enter): saved under its overlay('…') name, an orange line appears; errors are under Problems.
3. Two EMAs and a cloud: Update on chart shows the new code at once, before saving.

   //@navy 2.0
   overlay('My first indicator')
   
   const fastLen = input.int('Fast', 9, { min: 1 })
   const slowLen = input.int('Slow', 21, { min: 1 })
   const fast = ta.ema(close, fastLen)
   const slow = ta.ema(close, slowLen)
   
   const a = plot(fast, { title: 'Fast', color: color.orange, width: 2 })
   const b = plot(slow, { title: 'Slow', color: color.blue, width: 2 })
   fill(a, b, { color: fast > slow ? color.new(color.teal, 0.15) : color.new(color.red, 0.15) })

4. Signals and alerts — the whole script:

   //@navy 2.0
   overlay('My first indicator')
   
   const fastLen = input.int('Fast', 9, { min: 1 })
   const slowLen = input.int('Slow', 21, { min: 1 })
   const fast = ta.ema(close, fastLen)
   const slow = ta.ema(close, slowLen)
   
   const a = plot(fast, { title: 'Fast', color: color.orange, width: 2 })
   const b = plot(slow, { title: 'Slow', color: color.blue, width: 2 })
   fill(a, b, { color: fast > slow ? color.new(color.teal, 0.15) : color.new(color.red, 0.15) })
   
   // Signals: computed at the top level, on every bar
   const up = ta.crossover(fast, slow)
   const down = ta.crossunder(fast, slow)
   marker.below(up, 'Buy', { shape: 'label', color: color.teal })
   marker.above(down, 'Sell', { shape: 'label', color: color.red })
   alert(up, '{{ticker}}: fast EMA crossed above the slow one at {{close}}', { freq: 'close' })
   alert(down, '{{ticker}}: fast EMA crossed below the slow one at {{close}}', { freq: 'close' })

5. Save (Ctrl+S). Fast and Slow are now in the settings window (the gear in the legend).

Where a script runs and who sees it

• In your browser, in a thread next to the chart; nothing is computed on a server.
• Only where it is on (Coins, the heatmap, the constructor, the trend screener); its data loads only while it reads it.
• Safely: the chart's data and the language only — no page, no network. Too long a loop or too much memory stops the script, not the chart (limits).

• A new script is private: My scripts, your account.
• Publish it: after a review it is in Community — anyone can add it, vote, copy it; the code is open (Publishing).

Navy and Pine Script

Runs like Pine, written like TypeScript: TradingView code does not run as is — ChatGPT or Claude ports it in a minute (Scripts → From TradingView).

• Accepted as they are: shape.labelup, size.small, plot.style_stepline, linewidth, line.style_dashed, array.new_float(), array.push(a, x), line.set_xy1(l, x, y), var line l = na, [a, b] = f(), double-quoted strings, the same input title in different groups.
• Navy adds: Wintrading's data — vol.*, liq.*, oi.*, fp.*, book.*, walls.*; second timeframes on Binance futures; security() that does not repaint by default.

Writing with AI

ChatGPT or Claude get the Navy reference from the same compiler: answers usually compile the first time.

• One thing, with what to tune: «EMA 50 and 200, a cloud between them, lengths in the settings».
• Name the data and the place: «long liquidations», «the nearest density», «the 4h trend»; «on the price chart» or «in a pane».
• Ask for a marker or label on the signal, and an alert.
• Errors → Copy the errors for the AI or Fix with AI, into the same chat.
• The Navy reference (.txt) for a chat; steps: Create with AI, From TradingView.

The editor and its keys

Opens from My scripts → Open editor or a script's Open in the editor; saving, updating and problems: Scripts → The editor.

• Checks as you type with the chart's compiler: Compiled · 3 ms or the number of errors.
• Completes names, Wintrading's too (liq., walls.…); help on hover; parameters inside the brackets.
• Quick fixes for typical mistakes (Pine's :=, an if without brackets, a misspelled name); a color swatch by every color; folding in the margin.

On a Mac: Cmd for Ctrl; redo — Cmd+Shift+Z; completion stays Ctrl+Space.