The home screen

An icon rail down the left edge, the working pages beside it that run edge to edge (with Themes, Licence and Help at the bottom), and nothing that leaves your computer.

How a page is laid out

Each page is a header with its title and main action, a thin bar of controls (a filter, a range, tabs), then two panes that scroll on their own: a list or filters on the left, the detail or figures on the right. Nothing floats in a card in the middle of the screen. Figures meet at ruled lines. Pages that are mostly reading, such as Licence and Help, sit in one centred column instead.

New session

The + at the top of the rail opens a small menu: Backtesting session, Prop firm challenge, or Import data. The first two open the new session form. If you have not imported any market data yet, they take you to the import wizard instead.

Into a session and back

Press Resume on a session to open it in the replay window. Exit session in the title bar saves it and brings you back here, to the page you left.

Dashboard

The page that opens first. The pane on the left holds your most recently used session, ready to resume; the right-hand side is how it is going.

Pick up where you left off

The top of the left pane shows the session you last worked on, with its profit and loss, win rate, trade count and a small balance curve. Resume opens it; Analytics opens the analytics page narrowed to that one session. At the bottom of the pane are three shortcuts: a backtesting session, a prop firm challenge, and importing data.

With no sessions yet the page shows three short steps instead: bring in price data, start a session, trade and review.

Performance

The two controls in the bar under the header narrow every figure on the right. All / Backtesting / Prop firm picks the kind of session. The range picks Lifetime, or only sessions you worked on in the last 30 or 7 days.

If any trades have not been reviewed, an amber banner says how many and takes you to the Trades page. Below are four charts: hours invested by month, win rate by month, trades by market session (with each session's hours on your data's clock) and trades by symbol. Hours are grouped by the month a session was last worked on, which is an approximation when a session spans several months.

Recent sessions

Under the latest session, the eight most recent as rows, each with its profit and loss and a 3 px mark on the left edge (green or red). Click one to open it on the Sessions page.

Sessions

Every saved session in a list on the left, newest first; the one you pick fills the right-hand side.

Search by name, symbol or strategy; filter to backtesting or prop firm; sort by recently used, oldest, best P&L, most trades or name.

A row in the list

• The name and profit and loss, the symbol and the market dates the replay has covered, the trade count and win rate, and how many trades are still to review.
• A 3 px mark on the left edge says how it is going: green or red by profit and loss, and for a challenge green when passed, red when failed, blue while it is running. There are no coloured dots.

Its pane

• Resume opens it in the replay window. Analytics opens analytics for just this session.
• Rename, Start a copy (a new session on the same data and balance) and Delete.
• Share as image saves a picture of the results to post or send: net profit and loss, return, win rate, profit factor, maximum drawdown, the trade count and the equity curve. It is marked as simulated trading, and holds nothing else about you.

The details

Below the actions you get the strategy and description (edit them and press Save), net profit and loss, profit factor, expectancy and time invested, the equity curve, monthly and daily performance, and the latest trades five at a time. The pencil beside a trade opens that session with the trade's journal entry showing.

Trades

All your closed trades in one table.

Use the same filters as analytics (type, asset, side, outcome, tags, grade, session, strategy, market session, day, time, timezone and date), the search box, and the To review button, which shows only trades you have not marked as reviewed. Click a column heading to sort by it.

Each row shows when the trade closed, its session, symbol, side and lots, profit and loss, R, how long it was held, its grade, its first two tags, and a tick if it is reviewed. Click a row (or press Enter on it) to open that session with the trade's journal entry open. Export CSV saves exactly the rows you are looking at.

Data and the clock

A price file has times but no time zone, so the app has to be told which clock they are on.

It matters because anything defined in real time depends on it: which market session a trade belongs to (London, New York, Asia), and what hour and weekday it falls on. If your file is in Kenyan time (UTC+3), then 15:30 in the file is 12:30 UTC, which is New York. Read as if it were UTC, the same trade would look like London's afternoon.

Choosing it

• When you import, the confirm step asks What clock are these times on? The default is Kenya (UTC+3, no daylight saving). The list is grouped by region, with 37 zones: UTC, a MetaTrader broker's server time (GMT+2 in winter, +3 in summer), fixed GMT+2 or GMT+3 for brokers that never change, and cities across Africa, Europe, the Americas, the Middle East and Asia, and the Pacific, from Lagos and Johannesburg to Chicago, Hong Kong and Auckland.
• MetaTrader exports are usually in the broker's server time, not your own. If unsure, compare the first rows of the file with a chart you trust.
• Data imported earlier has no clock recorded, so it is assumed to be Kenyan. Open New session, find Data clock in the left pane, and set it to the right zone. It says when it is only an assumption.

Changing it later

Changing the clock never touches the candles: the digits in the file are the same either way, only their meaning is corrected. It is saved with the dataset, so every session, chart and analytics view on that data follows at once. Nothing needs re-importing.

What it changes

Panels and menus on the chart

Everything that opens over the chart follows one of two shapes, so it is always clear what you are looking at.

Edge panels

Indicators (I), Objects (D), Chart layout (L) and a chart's Properties (right-click the chart, Properties) are panels down the right edge of the window. They start under the toolbar, so the playback controls stay reachable beside them, they have no dimming backdrop, and the chart stays live: change a colour and watch the candles change. Esc, the × or a click anywhere outside closes one, as a popup would.

• Indicators: a search box, tabs for All, Favorites and My scripts, and a list; click a row to add it (the star pins it). Saved templates and the field to save the current set are pinned at the bottom.
• Objects: every drawing, grouped by chart, each with a remove button and a Clear all.
• Chart layout: chart type, how context panes sit, the theme, the all-charts colours (candles, wicks, and the bid and ask lines) and grid, the trading sessions to shade, and the context panes themselves.
• Properties: colours, volume, grid and session shading for just that chart, with a button to go back to the app-wide look.

Chart types

The chart type button on the toolbar offers Candles, Hollow candles (a rising body left empty), Bars (OHLC), Line, Area, Heikin Ashi, Renko and Range bars. Orders and fills always use the real prices, whatever the chart shows.

• Renko lays a brick each time the close moves one box on, and turns only when it moves a box past the other end. Quiet stretches draw nothing.
• Range bars each span the same height from high to low; a new one opens where the last closed. The last one is still forming.
• Both are built from the candles already shown, so they never read ahead, and indicators on the chart are worked out from them. The box or range size is in the chart type menu, as a price, per symbol; left empty it is worked out from the first candles. They follow each candle's open, high, low and close, so the finer the chart's timeframe (M1, or seconds on tick data), the truer they are.
• On these two the time axis shows dates only: a bar's time only says when it formed.

The colour swatches open a palette of ten shades for each colour, with a hex field for any other.

Dialogs

Jump to date (G), Save template and the Keyboard list (?) are small centred dialogs with an action bar. Esc or a click outside closes them.

The order ticket

The floating Buy and Sell box keeps its shape: price on each button, a lot stepper between them, and a chevron (Z) to expand it into the full ticket with Market, Pending and OCO. It is drawn with the same square structure and 6 px controls as the rest, and can still be dragged by its grip.

Trading a position box

A Long Position or Short Position box (Forecasting tools) can become a real order. Select it and press Enter, or press Place order on its toolbar:

• The ticket turns into the box's plan: you type the risk in money (it starts at 1% of the balance) and it shows the lots that risk buys, the entry, stop and target, and the risk to reward. The plan's lines can still be dragged.
• Enter again, or Place order, places it with its stop and target attached: at market when the entry is at the current price, otherwise as a limit or stop order on the right side. The order's own lines then take the box's place.
• Esc cancels, and the box is back as it was.

Left as a drawing, a box plays its own trade on the chart: a candle any part of the box covers counts, including one its left or right edge cuts through.

Right-click menu and indicator settings

The chart's right-click menu shows the shortcut beside Indicator List and Object List, and ticks the toggles that are on. Add price alert at sets an alert at the price you clicked: playback stops when a bar reaches it. Refresh chart redraws that chart from scratch without touching your session, drawings or settings; use it if a chart ever goes blank. The app also does this by itself when the chart library reports a drawing error. An indicator's gear (in the legend, top left of the chart) opens a compact settings card with the same rows as every other panel.

Themes

Every colour in the app, and the chart's, defined in one place. The Themes page is at the bottom of the rail.

Using one

Click a theme in the list. The whole app changes at once, the chart included, and the choice is remembered. There are five built in: Ink (true black with amber, the default), Graphite (dark), Daylight (light), Midnight (blue-tinted dark) and Paper (warm light with dark ink outlines and a green accent). In a session, the theme list is also in Chart layout.

Making your own

1. Pick the theme closest to what you want and press Make a copy (or New from this theme).
2. Change any colour: type a hex value or click the swatch for a palette. Everything updates as you go, this page included, and it is saved as you go.
3. The colours are grouped: Surfaces (recessed, ground, raised, pressed), Lines, Text, Accent and signals (accent, profit, loss, caution), six Chart series colours, and the Chart itself (background, candles, wicks, grid).
4. Tints behind coloured text, the stop and target lines and the focus ring are worked out from these, so changing the accent changes everywhere it shows.

Legibility

A panel on the page checks the pairs that matter against recognised contrast ratios: primary text 7:1, other text 4.5:1, and accent, profit, loss and caution colours 3:1, all against the ground, plus the outline colour. A failing row is marked in amber with its ratio, so you can see a problem before you live with it. It advises; it never blocks.

Share and keep

Export writes a theme to a .theme.json file; Import reads one. An imported file is checked: a colour that is missing or not a hex value is replaced by the matching colour from the light or dark base, so a damaged file cannot leave anything invisible. The built-in themes are fixed; delete only removes your own.

Built-in indicators

Open Indicators (I) and search by name, ticker or family (rsi, bill williams, ma). Each one's gear sets its periods, source and colour.

• On the price: simple, exponential, weighted, smoothed and Hull moving averages; Bollinger, Keltner and Donchian channels; Envelopes; VWAP; Pivot Points; Parabolic SAR; Supertrend; Ichimoku; the Alligator; Fractals; ZigZag; and the session and ICT tools (see Session and ICT tools).
• In their own pane: RSI, MACD, Stochastic, ATR, ADX, CCI, Standard Deviation, OBV, Volume, Awesome Oscillator, Williams %R, Momentum and the Money Flow Index.

They follow MT5's definitions, so the numbers match what you know. A few are worth knowing:

• Fractals appear two bars after the high or low, when those bars have closed, as on a live chart.
• ZigZag's newest leg follows the price until the next turn confirms it; every earlier point stays where it is.
• Momentum is MT5's form: the price as a percentage of the price n bars ago, so 100 is no change.
• Envelopes' deviation is a percentage of the average (0.1 is 0.1%).
• Awesome Oscillator, MACD's histogram and Volume are bars: the oscillator green when it rose from the bar before and red when it fell, MACD green above zero, volume by its own candle.

Volume profile

How much traded at each price, as bars across the chart. Four kinds, all built only from bars the replay has shown.

The four kinds

• Volume Profile Visible Range (an indicator): the bars on screen, docked at the right edge (or the left). It redraws as you scroll or zoom, so it always describes what you are looking at.
• Session Volume Profile (an indicator): one profile per day, or per week, standing at the start of its own session. The newest 40 are drawn.
• Fixed range volume profile (a drawing, under Forecasting → Volume-based): drag across the bars you want. It stays on those bars.
• Anchored volume profile (a drawing, same place): click a bar. It covers that bar to the newest and grows as the replay plays.

Reading one

• The point of control (amber line) is the price with the most volume.
• The value area is the band round it holding 70% of the volume, drawn stronger, with its high and low as dashed lines. The indicators' gear sets the percentage and the number of rows.
• Green is volume on up candles and red on down candles. The gear can turn that off for one colour.
• Naked points of control (Session Volume Profile, on by default): a dashed amber line from each earlier session's point of control to the right edge, for as long as price has not traded back through it. Those are the levels a session left behind untested.

Session and ICT tools

The levels and zones price-action traders mark by hand, drawn for you as the replay goes. Open Indicators (I) and search for the tool, or type ict to see them all.

Each one only reads candles the replay has already shown. A swing counts once the bars after it have closed, and a gap only fills when a bar has traded through it, so what you see on a bar is what you would have seen live. Each tool's gear sets what it shows.

The tools

• Previous Day, Week and Month High/Low: yesterday's high and low (PDH, PDL) held across today, and the same for last week (PWH, PWL) and last month (PMH, PML). Today's are solid and tagged at the right edge; earlier days are dashed. On Monday the previous day is Friday. Last week and last month come from your data's daily bars, so they are there from the first candle of a session.
• Session Ranges: a box round each session's high and low (Sydney, Tokyo, London, New York), each in its own city's hours, so daylight saving is handled. Tokyo is the Asian range.
• ICT Kill Zones: the Asia (20:00 to 00:00), London (02:00 to 05:00), New York (07:00 to 10:00) and London close (10:00 to 12:00) windows, on New York's clock.
• Fair Value Gaps: three-candle gaps, green up and red down. A gap stays until a bar trades all the way through it. The gear sets how many are shown, and can show filled ones, faded.
• Market Structure (BOS / CHoCH): a line from the swing to the candle that closed beyond it. BOS (solid) is a break with the trend; CHoCH (dashed) is the first break against it. Swing length is how many bars each side a swing must beat.
• Order Blocks: for each break of structure, the last opposite candle before the move. A block holds until a candle closes through its far side.
• Average Daily Range: the average high-to-low range of the last 14 days, in pips, projected from today's low (ADR↑) and today's high (ADR↓). Near one, the day has already moved about as far as usual.
• Equal Highs and Lows (Liquidity): two or more swing highs (EQH, red) or swing lows (EQL, green) at about the same price, where stops tend to rest. A dot marks each swing and a dashed line holds the level until a bar trades beyond it; then it is swept, and stays faded and dotted (untick Show swept levels to hide those). Match within is how close the swings must be, as a fraction of the average bar range (0.2 by default); swing length as above.

Trading sessions on the chart

See at a glance which market was open when each candle formed. Right-click the chart and tick Trading sessions.

The sessions

Each session is shaded in its own colour behind the candles, with its name at the top when there is room. Where two are open at once, such as London and New York in the afternoon, the overlap gets a colour of its own, a little stronger, so the busiest hours stand out.

Tokyo, London and New York are shown at first. Pick which ones in Chart layout, under Trading sessions, which also lists today's hours for each on your data's clock.

Daylight saving

Hours are kept in each city's own time, so they move with its daylight saving and not with yours. London and New York change on different dates in spring and autumn, so for a week or two each year their overlap is an hour longer or shorter than usual; the shading shows that. Sydney's summer is the northern winter, so it moves the other way. Weekends are never shaded.

Your data

The Data page in the rail lists every dataset you have imported.

Each row shows the symbol and name, the dates it covers, the number of one-minute bars, any gaps found when it was imported, its size on disk, and the sessions that use it. The Clock drop-down sets which time zone its times are in, the same setting as in Data and the clock.

Deleting a dataset

Delete asks first, then removes the dataset and its prepared timeframes from this computer. A dataset that a session uses, as its main instrument or one of its others, cannot be deleted: delete those sessions first, or keep it. To get the data back later, import the file again.

Help, backup and privacy

The Help page, at the bottom of the rail, shows the app's version and gathers what you need when something goes wrong or you change computers.

Getting help

• Send feedback opens an email to support with the version in the subject.
• Copy diagnostics puts a short report on the clipboard to paste into that email: the app version, your system, how many sessions and datasets you have, and the recent log. It holds no trades, prices or names.
• Show log file opens the folder with the app's log. It records errors and crashes on this computer only, and keeps itself small.

Updates

The app asks whether a new version exists a few seconds after it starts. When one does, a band on the home screen says so: Install and restart downloads it, checks its signature, installs it and opens the new version; Later hides the band until the next start. It never interrupts a session. Check for updates on this page asks at any time. Updating keeps your sessions, data and licence.

Backup and moving computers

Back up everything asks for a folder and copies into it, as one new folder, your sessions, journal and screenshots, datasets, scripts, templates and settings. Restore from a backup reads such a folder back, on this computer or another. Restoring adds what the backup holds and replaces files with the same name; nothing that exists only on this computer is deleted.

Privacy

Everything stays on this computer. The app goes online only to check your licence key (the key and a device code, nothing else) and to ask whether a new version exists. No trades, prices or usage are ever sent.

Open-source notices

The page lists the open-source software the app is built on, with each licence. Charts are drawn with TradingView Lightweight Charts™.

Play only some sessions

Practise the hours you actually trade. Pick the market sessions to play, and the replay skips everything else, quickly.

Choosing sessions

• In New session, tick Play only these sessions: Asia, London, New York and Off-hours. The hours beside each are on your data's clock, so for Kenyan-clock data New York reads 15:00 to 00:00. Nothing ticked plays every bar.
• During a session, the clock button at the right end of the playback bar (it shows a code such as NY) opens the same choices, so you can change your mind without restarting.
• The skip button beside it, or N, leaves the current session at once and lands just before the next one opens.

What a skip does

A skip is not a jump over unseen history. Every skipped bar still runs through the engine, so stops, targets, pending orders and a challenge's limits act on it exactly as if you had watched it. Only the drawing and the waiting are skipped, and playback stops by itself at the end of the data.

A trade still open when the session ends

Starting a session

Choose Backtesting or Prop firm challenge at the top, fill in the basics, and start.

• Market data: shown when you have more than one dataset.
• Name and Starting balance.
• Strategy: optional, but it is what lets analytics compare strategies across sessions.
• More instruments: optional, up to three; each is tradable, sharing the one balance. Pick one and a field for the next appears. Each symbol gets its own chart window, with a tab in the strip under the charts (XAUUSD,H1, EURUSD,H1 and so on), next to any timeframe windows you open. One shows at a time: click a tab, or a symbol in the title bar, to bring it to the front, and the ticket trades that symbol. The side by side and stacked buttons show them all at once; then click a chart to trade it (it is outlined, and its tab lit), and its maximize button to see it alone for a moment.
• The charts share one clock: all move together as the replay plays, and all are on the same timeframe, which the picker of any of them changes for the whole session. A bar of another symbol is shown only once it has closed, so none of them ever shows a moment the replay has not reached. Scroll or zoom one and the others show the same stretch of time; the crosshair is shared too.
• Play only these sessions: replay just New York, say, and skip the rest; see Play only some sessions.
• Data clock: the time zone the file's times are in. It decides which market session a trade falls in; see Data and the clock.
• Trading costs: slippage and variable spread, below. Both are remembered for the next session.
• Start from: a date and time inside your data. Blank starts at the beginning.

Trading costs

• Slippage (in pips) is added against you on every fill that takes the price there is: market orders, stop orders, a stop-loss being hit, and closing by hand. Limit orders and take-profits fill at their own price, as they do at a broker. 0 is none. Half a pip to a pip is a fair figure for a major pair outside news.
• Variable spread widens the instrument's spread the way a retail feed does: three times from 16:30 to 18:00 New York (the daily rollover, when spreads blow out) and one and a half times from 18:00 to 03:00 (the quiet Asian hours). The rest of the day it is the quoted spread. It follows New York's clock, so US daylight saving moves it. The ask line, the order ticket and open positions all show the spread in force on the current bar.

Your data's own spread

When the file you import has a spread column, every bar keeps its own spread and fills use it, minute by minute: a short's stop is tested against the ask that minute really had. The import preview shows a Spread column and says so. That real spread wins over variable spread; the spread you type in the import is then only for a bar that has none.

• MT5's History Center (Symbols, Bars, Export) writes a <SPREAD> column. It is read as it is.
• The TradeOnReplay export script writes one too, from this version. If you installed the script before, use Install MT5 exporter script in the import (under Or import directly from MetaTrader 5) again to get the new one, restart MT5, then export again.
• Files with no spread column (Dukascopy, most others) use the spread you give, and variable spread if you turn it on.

Both are saved with the session, so resuming one keeps its costs. A trade's entry and exit prices include them, and so does every figure built from them.

The basics are on the left. For a challenge, the whole rulebook is on the right, with the profit target, maximum loss and daily loss limit typed as a percentage of the account. See Starting a challenge.

Replaying a trade, and copying a session

Replay this trade in the journal (or Replay in the History table) opens this form pre-filled to start at that trade's entry bar with the future hidden again. Start a copy on a session does the same with that session's balance and strategy.

In a replayed trade, a bar under the toolbar holds the original trade (its side, entry time, lots, stop and target) and, as you trade it again, your retake's result beside it with the difference from the original's. It only compares: it places nothing for you, so the bars ahead stay unseen.

Bringing in price data

The app replays from one-minute bars. Import a file once and it is kept on this computer; every session you start from it reads the same data.

Trying it first: DEMO/USD

A new install opens with DEMO/USD, a practice market the app makes for you on the first start: two years of one-minute bars that move like a real currency pair, with quiet and busy hours and closed weekends. Press Try it now on DEMO/USD on the dashboard to start a session on it at once. Its prices are made up, so use it to learn the app, then bring in real data to backtest. It is on UTC, so the session shading lines up. You can delete it on the Data page.

Where the data comes from

• MetaTrader 5: the importer can install a small script into your terminal. Run it on the chart you want, choose how far back to go, then press Refresh and the export appears in the list. A calendar of news events comes with it.
• Dukascopy, free: in the import wizard, Open Dukascopy's data page opens their historical data export in your browser. Pick the instrument and dates, choose 1 minute, Bid and the GMT time zone, and download the CSV (they may ask you to sign in for free). Then choose the file in the wizard. Its first column says "Gmt time", so the app sets the clock to UTC by itself.
• A file you already have: choose a CSV from HistData, Binance, TradingView, your broker, or anywhere else. Tab, comma and semicolon files are all detected, and so is a decimal comma.

The app does not download market data for you. Free sources such as Dukascopy allow personal downloads under their own terms, so you fetch the file in your browser and the app reads it.

Adding newer data to a dataset

Import a newer file for an instrument you already have and, on the confirm step, set Save as to Add to that dataset. Bars at minutes it does not have yet are added and every timeframe is rebuilt; minutes it already has are kept as they are, and the result says how many of each. The file must be on the same clock as the dataset; the wizard tells you if it is not.

What the importer reads

Column names are matched loosely (time, Gmt time, open_time, timestamp and date with time all work). With no header row the order is date, time, open, high, low, close, volume.

A date that does not exist (a 13th month, 30 February) is refused, never turned into a plausible-looking timestamp. Rows that cannot be read are skipped and counted in the report.

Tick data

A file of ticks, one row per price change with a bid and an ask, is read too. The app builds one-minute bars from the bid as it reads, and each minute keeps its real spread, the average of ask less bid over that minute, and its number of ticks as its volume. The import step says when a file is tick data and shows the first minutes built from it. Fills then use each minute's own spread, so a rollover spike in the data is a spike in your fills.

• MetaTrader 5's own tick export (Symbols, Ticks, Export): read as it is. MT5 leaves a price empty when it did not change, and the last one is carried on.
• The TradeOnReplay script: turn on Export real ticks in its inputs and choose how many months. Ticks are many, a million or more a month on a busy pair, so a few months is a good start. The export appears in the list marked ticks.
• Dukascopy tick downloads (Gmt time, Ask, Bid), files with bid and ask columns from other downloaders, and TrueFX files, which have no header.

The file is read as it streams, so a large one does not fill memory; it takes longer than a file of bars, about the time it takes to read the file once. Bars a few seconds apart (second bars) are built into minutes the same way.

Fills from real ticks

The ticks themselves are kept with the dataset, about 16 bytes each, and the Data page shows how many. In a session, the ticks of the few days around where you are are kept in hand, and orders are filled by walking them in order:

• A stop and a target hit in the same minute are settled by which the price really reached first, not by the tie-break setting.
• A stop fills at the first tick past it, and a short's stop is tested against each tick's own ask.

Charts of a few seconds

On a dataset made from ticks, the main chart's timeframe picker also offers S5, S15 and S30: bars of 5, 15 and 30 seconds, built from the ticks. They are offered while the replay is inside the stretch the dataset has ticks for, and the time axis shows seconds. Orders on them fill from the ticks of each bar, never from the minute the bar sits in, which would hold seconds still to come. The session's other instruments keep one-minute bars.

On any dataset, with or without ticks, a pending order now fills at the minute the price reaches it, and the position it opens is only tested for its stop and target from then on. Before, on an hourly chart, a move earlier in the same hour could stop out a position that did not yet exist.

The date format

The import step shows the format it detected and lets you change it. Change it and the file is read again with your choice. This matters for dates like 03/04/2024, which could be 3 April or 4 March: when the data cannot settle it (no day above 12 in the first rows) the importer reads it day first and says so, and the first rows shown beneath tell you at a glance whether that was right.

The clock

Most files carry times with no time zone, so you say which clock they are on. This decides which market session a trade falls in and what hour and day it counts for. MetaTrader exports are usually in the broker's server time (often GMT+2 or +3), not your own: compare the first rows with a chart if unsure.

A file that states its own zone needs no answer. An epoch count is always UTC, and a trailing Z or +03:00 is applied as the row is read, so the clock is set to UTC for you. You can change the clock later without importing again; see Data and the clock.

What is this instrument?

Pick the market from the list (forex, metals, index CFDs, futures, stocks, crypto) and the contract size, smallest trade, lot step, spread and commission fill in. Any of them can still be changed. The one that matters most is the contract size: it is the account-currency value of a 1.00 move in price, per lot, and it multiplies every profit and loss figure. Typical values are 100,000 for forex, 100 for gold, 50 for an E-mini S&P 500 future, and 1 for a share or a coin. Where brokers differ (index CFDs especially) the picker says so; check your broker's contract specification.

For futures a lot is one contract, so only whole numbers make sense. For shares it is one share. Use split- and dividend-adjusted data for stocks, or the history will show jumps that never traded.

Warnings you may see

• Bars are not one minute. Hourly or daily bars import, but orders and stops are checked bar by bar, so fills are less exact than on one-minute data.
• Many decimals. A price carrying more decimals than the app can store at that size is rounded, and the warning says to how many. A value that still cannot be stored is skipped, never clipped.
• Real holes. Gaps beyond a weekend are reported. Replay skips over them like any other missing bar.

Playing, stepping and speed

The controls at the right end of the toolbar move the replay one bar at a time, or play it on its own.

The buttons

• Step forward and back (→ and ←) move one bar. With Shift, ten.
• Play and pause (Space) plays at the chosen speed until you pause or the data ends.
• Jump to date (G) takes you to a moment in your data.

Stepping back moves only what you see. Your trades, orders and balance are not rewound, so a trade you closed stays closed. A challenge that forbids rewinding does not allow it at all.

Speed

The slider sets how fast it plays, in five steps. 1× and 2× are slow enough to follow every candle; from 3× on it is for getting somewhere (a level, an alert, the next session), and 5× is the fast mode.

Click a stop on the slider, drag the handle, or use the arrows either side of it. With the slider focused, the arrow keys change speed instead of stepping. Hover it for the meaning in words.

Playing only some sessions

With a session plan active, the bar also shows a skip button (N) that leaves the current market session now. See Play only some sessions.

Placing orders

The order ticket is the box floating over the chart. Buy and Sell with the lot size in the middle is the short form; the chevron (Z) opens the full ticket.

Market, Pending and OCO

• Market: fills at the current price at once. B buys and S sells with the ticket's values.
• Pending: waits for a price you choose. A buy below the market is a limit and above it a stop; a sell the reverse. Click the chart to pick the price, or type it.
• OCO (one cancels the other): two pending orders, A and B. When one fills the other is cancelled. Use it to catch a breakout in either direction.

Lots, stop, target and break-even

• Lots: the size. The unit depends on the market: lots for forex, contracts for futures, shares for stocks. The smallest size and the step come from the instrument.
• SL and TP: the stop-loss and take-profit prices. They can also be dragged on the chart.
• BE: move the stop to break-even once the trade is this many R in profit. Leave it off to skip.
• Risk and R:R: shown once a stop is set. Risk is what you lose if the stop is hit, after costs; R:R is the target's distance over the stop's.

If a stop and a target are in the same minute

The replay resolves fills on one-minute bars. When both a stop and a target sit inside one bar there is no way to know which came first, so the stop is assumed to fill first. This is the pessimistic choice and the trade's journal entry says when it happened.

The trial, the free version and your licence

The first 14 days include everything. After that you keep a free version, or you unlock the full one with a single payment.

The 14-day trial

It starts the first time the app opens. Every feature is on. A thin banner appears in the last week and says how many days are left. The clock only counts forward: setting the computer's date back does not add days.

The free version

A limit stops you adding past it. It never takes away what you already have: if you finish the trial with ten sessions, all ten stay readable, exportable and deletable, and the one you are playing keeps saving.

Unlocking the full version

Open Licence in the rail on the home screen, paste the key from your purchase email, and press Activate. It is one payment, with no subscription. The licence is checked online once to activate, and again about once a week.

If the computer is offline when a check is due, nothing happens: the licence keeps working for 30 days from the last successful check, with a reminder in the last week. Only after that does it fall back to the free version, and it returns the moment you reconnect.

Moving to another computer

A key can be active on a limited number of computers. On the old one, open Licence and press Deactivate on this computer, then enter the key on the new one. To bring your sessions, journal and data with you, use Back up everything on the Help page and Restore from a backup on the new computer. If you no longer have access to the old computer, write to support and the activation is removed by hand.

The info icons

A small circled i beside a label explains it. Hover it, or move to it with the keyboard, and a short note opens; move away and it closes.

The screens keep their own wording short for this reason: once you know what a field does you do not need to read about it again. The icon is there for the times you do. Clicking away or pressing Esc closes it. Screen readers read the explanation along with the label, so nothing is hidden from them.

Each note is the short form of a page in this guide. Where a note ends with a topic name, that page has the whole story.

What's new

Changes outside the script editor, newest first.

End of October 2026

Weekly and monthly charts

W1 and MN1 are in the timeframe row with the rest, for the main chart and context panes. A week runs from Monday 00:00 and a month from the 1st, on your data's clock. Switching to one shows the last week or month that has closed, never one still forming, so nothing ahead is given away; switching back to a finer timeframe returns you to exactly where you were.

Price alerts

Right-click the chart and choose Add price alert at the price under the mouse. A dashed line with a bell marks it. When a bar touches it, wick or gap, playback stops and a band says so, with Keep it armed or Remove it. Each alert is listed in the right-click menu and in Objects with its own remove button; Remove all is there too. Alerts are saved with the session.

Drag an alert's line up or down to move it; it is armed again where you let go. With one of the session and ICT tools on the chart, right-click on or near one of its levels and the menu also offers an alert right on it, named after it: Add price alert at PDH 1.08500. That covers the previous day's, week's and month's highs and lows, the ADR levels, the high and low of each session's and kill zone's latest range, the edges of open fair value gaps and live order blocks, and equal highs and lows not yet swept. The name shows on the line and in the notice when it is touched. The alert stays at that price: it does not follow the level to the next day.

Something to replay from the first second

A new install opens with DEMO/USD, a practice market the app generates, and a Try it now button. The import wizard gained a guided Dukascopy route that sets the clock from the file, and a file can now be added to an existing dataset. See Bringing in price data.

Late October 2026

Trading sessions on the chart

Right-click the chart and tick Trading sessions to shade Sydney, Tokyo, London and New York behind the candles, each in its own city's hours with daylight saving followed, and the overlaps in a colour of their own. See Trading sessions on the chart.

Black and white candles

The built-in themes draw candles in black and white with outlines, and Reset to defaults brings them back. The bid and ask lines have colours of their own, following the candles until you change them.

Brighter controls

Buy is bright blue and Sell bright red, the toolbar's icons and labels are white, and the colour palette has ten shades per colour on round swatches.

Data, Help and backup

A Data page lists and deletes datasets. A Help page sends feedback with diagnostics, backs up everything to a folder and restores it, and lists the open-source notices. The app now keeps a small error log on this computer.

Share as image, and retakes

A session's results can be saved as a picture to share. A replayed trade shows the original beside your retake. See Sessions and Replaying a trade.

October 2026, newest

Ink is the default theme, and text on bright colours is black

A first run opens in Ink. On any button or badge filled with a bright colour, such as Ink's amber, the text is now black instead of white, and the app picks black or white for each theme from how bright the colour is, so it stays readable in every theme and in your own. Your saved theme is not changed.

Fast playback keeps up

A step now sends the chart only the new candle instead of the whole history, so 5× and 10× reach 5 and 10 candles a second on a normal session. See Playing, stepping and speed.

The product is TradeOnReplay

The app, this guide and the MetaTrader exporter now carry the one name. Files the old exporter wrote are still found and imported.

A 14-day trial, then a free version

Everything is on for 14 days. After that the free version keeps replay, orders, drawings, the journal and your own data, and limits saved sessions, indicators, scripts, prop firm challenges, more instruments in a session, extra chart panes and your own themes. One payment unlocks the rest. See The trial, the free version and your licence.

Playback speed in candles per second

The speeds are 1, 2, 3, 5 and 10 candles per second, on a slider you can click, drag or use from the keyboard. One candle a second is slow enough to follow closely. See Playing, stepping and speed.

More price data, and honest warnings

The importer reads epoch times (Binance, TradingView), Dukascopy's day-first dates, US month-first dates, decimal commas and times stated with a zone. It refuses dates that do not exist, tells you when a date could be read two ways, and warns about bars that are not one minute. You can pick the date format yourself. See Bringing in price data.

Futures, index CFDs, stocks and crypto

The instrument list now includes NASDAQ and US500 CFDs, the main futures, shares and crypto, with sensible contract sizes. A lot is one contract for futures and one share for stocks.

Play only some sessions

Replay only New York, or London and New York, and skip the rest. See Play only some sessions.

Buy and sell colours

A buy is always blue and a sell always orange, whatever theme you use. Before, a theme with an amber accent painted buys the same colour as sells.

Small changes

The name sits beside the logo in the replay window, Exit session is set apart and white, the dashboard's market-session bars fill their space, and toolbar icons with a drop-down line up with the rest and light up only on the icon. Small i icons now explain things in place; see The info icons.

October 2026, latest

Data clock and trades by market session

Each dataset now records which time zone its times are in, chosen when you import it (Kenya by default) and correctable later. Market sessions, hours and weekdays use it, and the Dashboard gained a Trades by market session chart. See Data and the clock.

Panels and menus on the chart

Indicators, Objects, Chart layout and Properties are now full-height edge panels that leave the chart live; small dialogs share one look; the order ticket, right-click menu and indicator settings follow it. See Panels and menus on the chart.

Themes

A Themes page defines every colour: five built-in themes, your own copies, a legibility check, import and export. See Themes.

October 2026, later

Prop firm rules in percent

The profit target, maximum loss and daily loss limit are now typed as a percentage of the account, the way firms state them, with the dollar amount shown beside the field. The Simulation tab's challenge test works the same way. See Starting a challenge.

Edge-to-edge pages

Home, Sessions, Trades, Analytics and Prop firm now run to the window's edges: an icon rail, a header, a bar of controls and two panes that scroll on their own, instead of cards centred on a page. The analytics filters moved from pop-up menus to a pane down the left. See The home screen.

Analytics docks

Analytics now fills the replay window corner to corner, and the triangle in its corner moves it: to the left or right of the chart, below it, or out into a window of its own that can sit on another monitor. See Docking and windows.

October 2026

A home screen

Dashboard, Sessions, Trades, Analytics and Prop firm pages replace the plain session list. Sessions now carry a strategy, a description, time invested and how far the replay has gone. See The home screen.

A real journal

A panel beside the chart with a trade list, a calendar, session notes and a note editor per trade with automatic entry and exit screenshots, tags, an execution grade, a checklist and templates. The old statistics pop-up moved into analytics. See Opening the journal.

Analytics

Filters, five tabs (Performance, Time, Drawdown, Journal, Simulation), CSV export, and a Monte Carlo simulation. See Analytics.

Prop firm mode, extended

A daily loss limit with a configurable basis and reset time, minimum trading days, a time limit, a consistency rule, lot, weekend and news rules, presets, a live HUD with a rules report, no-rewind, and a pass-odds estimate. See Prop firm.

Look and feel

IBM Plex is now bundled with the app (it was named in the theme but never loaded, so the app was using system fonts), with a new icon set, tinted fills and hand-drawn charts that have tooltips and a “show the numbers” table.

Opening the journal

Press the Journal button in the toolbar, next to Indicators, or press J.

The journal opens as a panel on the right and the chart makes room; it does not cover it. A small number on the button counts closed trades you have not marked as reviewed. It has three tabs: Trades, Calendar and Session.

The Trades tab

Closed trades, newest first. Each row has a coloured arrow for buy or sell, the symbol and lots, when it closed, its R, its grade if you gave one, small icons for notes and screenshots, a green tick when reviewed, and the profit or loss.

• Search looks through trades, your notes, tag names and grades.
• All / Wins / Losses / To review filters the list. The count at the right is how many you have reviewed.
• Click a trade to open its entry. [ and ] go to the previous and next trade while one is open and you are not typing.
• The History table in the bottom dock has a Journal link on every row.

Auto screenshots

The camera at the top of the panel turns auto screenshots on or off. While it is on, a picture of the chart is taken when a position opens and another when its trade closes, and both are attached to that trade's entry. Pictures are shrunk to at most 1280 pixels wide and stored as JPEG, so a screenshot is about 100 KB. Trades already open when you resume a session are not captured.

Writing about a trade

Open a trade and you get the facts, your screenshots, a note, and a short review.

The facts

Entry and exit price, how long it was held and in how many bars, the result in R, and two figures you will not find elsewhere: Max against (how far price went against the trade before it closed) and Max for (the best it ever got), both in R. They come from the replay's own price path, so they are exact. If the stop and target were both inside one minute, a note says the stop was assumed to fill first.

Three buttons: Replay this trade starts a new session at its entry with the future hidden, Capture chart takes a screenshot now, and Copy notes puts the entry on the clipboard as Markdown.

The note

Click and type. A new line starts a new block. Type / at the start of a line for a menu:

Typing # , - , [] or > at the start of a line turns it into a heading, bullet, to-do or quote. Enter on an empty bullet or to-do ends the list. Backspace at the start of a block turns it back into text. Pasting text pastes plain text, and pasting an image from the clipboard attaches it as a screenshot. Up and down arrows move between blocks.

Review

• Execution grade, A to F: how well you followed your plan, whatever the result. A winning trade can deserve a D.
• Outcome quality: good win, bad win, good loss or bad loss. A good loss followed the plan and lost; a bad win broke the plan and got lucky. Once you grade a trade the journal suggests one.
• Mark as reviewed clears the trade from your to-review count.

Tags and the checklist

See Tags, templates and checklists. The Delete this entry and its screenshots link at the bottom removes everything written about the trade.

Calendar and session notes

Two more tabs in the journal panel.

Calendar

A month grid starting on Monday. A day with trades shows its net result and trade count, tinted green or red, stronger the bigger the day. Click a day to list its trades, and click one to open its entry. Year shows twelve months with their results; click a month to go to it. Days are the dates of the replayed market, not the dates you practised.

Session

Here you set the session's strategy and description, and write session notes in the same editor, for a daily review or a lesson that belongs to no single trade. It also shows the session's net profit and loss, win rate and expectancy, how long you have spent in it, and a button that opens analytics.

Tags, templates and checklists

Tags only help if you use them the same way every time, so they come in a few fixed groups with a few values each.

Tags

The starting groups are Setup (breakout, pullback, reversal, range fade, trend continuation), Market condition, Emotion and Mistake. Click a tag to apply it. Add beside a group makes a new tag in it, New tag group makes a group, and Delete tags shows a bin beside each tag. Tags are shared by every session, so a tag means the same thing wherever you analyse it.

Checklist

The default Pre-trade checklist has six items (higher-timeframe bias, entering at the planned level, stop placed first, risk within limit, reward-to-risk at least 1.5, no news soon). Tick what you did. Analytics then compares trades where you followed at least 80% of it with the rest.

Templates

Insert Trade plan or Trade review with / in the note editor.

Using them well

Every figure that groups by a tag shows how many trades is behind it, and pale rows have fewer than five. Treat anything with a handful of trades as a hint, not a finding.

Where it is saved

Everything stays on your computer.

• Notes, grades, tags ticked and checklists are saved inside the session, with the same autosave as your trades (a moment after you stop typing).
• Screenshots are separate files in the app's data folder, one folder per session, so they never make the session file heavy.
• Tag groups, checklists and templates are one file shared by all sessions.

Deleting a session deletes its screenshots with it. A session saved by an older version opens as before, with an empty journal.

Opening and filtering

Press Analytics in the toolbar (or A) during a session, or use the Analytics page on the home screen. In a session it fills the window corner to corner and can be docked or popped out.

It reads every saved session and, when you open it mid-session, the live state of the open one, and it follows your trades as they close. Reopening it puts you back on the tab and filters you left.

The tabs are across the top with Filters, Copy summary and Export CSV at the right. The filters are a pane down the left. In a narrow dock or window the pane starts closed and the buttons shrink to icons; Filters opens the pane either way.

Filters

Within one filter the choices are any of; across filters they are all of. Chips at the top of the pane show what is narrowing the figures, each with an ×, and Clear all removes them all. A group with something chosen opens by itself and shows how many.

Breakeven

A trade whose result is within a set number of dollars of zero is breakeven, not a win or a loss. The threshold is on the Performance tab, beside the Breakeven figure, and is $0 until you change it.

Export and share

Export CSV saves the trades behind the current filters, one row each, with R, excursions, grade and tags. Copy summary puts three lines of headline figures on the clipboard.

Every chart has a table

Under each chart, Show the numbers swaps it for a table of the same data. Hover a chart for exact values.

Docking and windows

The small triangle in analytics' top-right corner moves it. Click it and pick a place.

Inside the replay window

The chart always keeps some room, and the place and sizes you choose are remembered. Docked beside the chart, analytics updates as you close trades, so you can watch the figures move while you trade.

In a window of its own

Pop out to a window opens analytics as a second window that you can drag anywhere, including to another monitor. With more than one monitor connected the menu also lists Fill monitor 1, 2… (with each one's size, and which is your main display and which has the replay), which opens it maximised on that display.

• The window follows the replay: it refreshes whenever a session is saved, and it takes the same light or dark theme.
• It stays above the replay window and closes with it, like a floating chart.
• While it is open, A and the toolbar button bring it forward instead of opening a second copy.
• Its own corner triangle puts it back in any of the places above, or moves it to another monitor. Dock back returns it to the place it last had. Closing it with the window's own close button just closes analytics.

Performance

The first tab.

• Profit and loss: the balance after each closed trade. Each trade / Day / 1 Hour / 15 Min thins the curve. Above it: total profit and loss with the return, the balance, win rate, trade count, and the breakeven count.
• Average R, Ideal R, Could have been breakeven: mean and best realised R, the planned R of your stop and target, how far trades ran in your favour, and how many losers had been +1R up before turning.
• Expectancy: the average result of one trade, with a bar of average win against average loss. Profit factor: gross profit over gross loss.
• Winners and Losers: counts, best and worst, average, average duration, and consecutive runs.
• Recent results: a strip of W, L and B for your last 80 trades, and the run you are on.
• Performance by side, Trade frequency, an R-multiple distribution, and net profit by asset and by strategy.

Time

When you win, and when you do not.

• Market session: four small charts (win rate, trades, average R, profit) for Asia (00–07 UTC), London (07–12), New York (12–21) and off-hours. These are fixed real-time windows by entry time, with no daylight-saving shift, so every hour belongs to exactly one session. Your data's clock is converted first, so a trade at 15:30 in Kenyan-clock data is a New York trade (12:30 UTC). A note under the charts states the windows on your own clock: for Kenya, Asia 03:00–10:00, London 10:00–15:00, New York 15:00–00:00. See Data and the clock.
• By hour, with a menu for profit, win rate, number of trades or average R. By day of the week. By month, January to December across all years.
• Day and hour: a heat map of net profit by weekday and entry hour.
• Performance calendar: a month at a time, each day tinted by its result.

Pale bars and cells have fewer than five trades behind them. Hover for the exact count.

Drawdown

The cost of the ride.

• Drawdown on equity, in dollars or percent: how far the balance sat below its previous high. It is measured on the closed-trade balance, which moves when a trade closes, not while one floats. The curve steps rather than slopes for that reason.
• Max, average, time to recover, and now: depth of the deepest drawdown, the mean depth, the average time from the lowest point back to a new high, and whether you are in one.
• Deepest drawdowns: the five worst, with when they started, how long they lasted and whether they recovered.
• Maximum adverse excursion: how far each trade went against you, in R, for all trades, winners or losers. It is exact because the trade happened inside the replay.
• Heat on winning trades: how far winners went against you before they paid.
• What if my stop were tighter? Drag the slider. Any trade that went at least that far against you would have been stopped at that level; the rest are unchanged. Costs are not re-applied.
• Against vs for: a dot per trade, how far against you (across) and for you (up).

Journal insights

Where what you wrote meets what happened.

• Journal coverage: how many trades are reviewed, graded, noted and screenshotted.
• Result by execution grade: the average result of your A trades against your D trades. If A does not out-earn D, either the grade or the plan is the problem.
• Process versus outcome: how many good and bad wins and losses, and what each netted.
• Pre-trade checklist: trades where you followed at least 80% of it against the rest, by win rate, average R and profit.
• Tags: net result for every tag, by group. A mistake tag's total is called out.
• Practice versus real: import a CSV from your broker and compare win rate, profit factor and expectancy. Broker statements have no stop-loss on record, so the real side is in dollars, not R.

Simulation

Your closed trades, drawn at random thousands of times.

Each simulated run takes trades from your own results, either drawing with replacement or reordering the same trades, and builds a balance curve. The chart shows the median and the 25th–75th and 5th–95th percentile bands. Beside it: the chance of finishing in profit, the typical and 5%/95% final balance, the typical worst drawdown, and the chance of losing half.

Tick Test against a challenge to give it a profit target and a maximum loss, each as a percentage of the starting balance with the dollar amount beside it (the loss fixed, or trailing from the equity high). It then reports the chance of passing and of breaching first.

• Re-roll changes the seed. The same seed always gives the same result, so a figure can be reproduced.
• It needs at least two trades and says little under about thirty, and warns you.
• It shows the spread of luck for an edge you already have. It is not a forecast.

How the numbers are worked out

The definitions, so you can check any figure by hand.

Sample sizes are shown beside grouped figures (n=4) and thin groups are drawn paler. The app does not compute Sharpe, Sortino or Kelly: on the small samples a replay produces they are noise dressed as precision.

Starting a challenge

Choose Prop firm challenge in the new session form. Pick a shape, change anything, start.

Presets

Each preset sets its numbers as a share of your starting balance, so it fits any account size. Two-phase, phase 1 (10% target, 5% daily and 10% total loss, 4 days, 30 days), phase 2 (5% target), One-step (10% target, 3% daily, 6% trailing end-of-day loss), Futures-style trailing (6% target, 4% trailing loss that locks at the start balance) and Drawdown only.

The rules

Editing any field by hand switches the preset off (Reset to the preset brings it back). The profit target, maximum loss and daily loss limit are typed as percentages of the starting balance, and the dollar amount they come to is shown beside each, so “10” is never ambiguous. Change the balance and the dollars follow; the percentages stay.

During a challenge

A strip in the title bar shows the room you have left under each limit, on every bar.

• Drawdown room: equity above the floor, with a bar that empties.
• Today: equity above today's daily-loss floor, when there is a daily limit.
• Target: the share of the profit target made.

A bar turns amber when half the room is gone and red when a quarter is left. It is a gauge you can watch approach zero rather than a pop-up after the fact.

What ends an attempt

The drawdown limit and the daily loss limit end it the moment equity touches them, floating profit and loss included, and the strip says BREACHED or DAILY LOSS BREACHED. Once breached an attempt stays breached. A rule judged on your closed trades (time limit, consistency, lot size, weekends, news) turns the strip to RULE BROKEN. Reaching the target with every rule satisfied shows PASSED.

The rules report

Click the strip for a card listing every rule with a tick, cross or flag, a line of detail, and progress bars for the target and trading days. It also shows closed profit, days traded, and what you would keep at your profit split. The consistency rule is shown as information until you reach the target, which is when firms judge it.

The four loss floors

“Maximum drawdown” means four different things at four different firms.

“End of day” is measured on equity (floating included) at the reset time, the more common convention. If your firm uses closed balance instead, treat this as slightly stricter than yours.

The Prop firm page

The fifth page on the home screen.

• Attempts, passed, failed and in progress, with a pass rate.
• Every attempt as a session card. Rules report under it opens the full rule list, the best and worst day, and why an attempt ended.
• Would you pass? replays all your closed trades against a challenge shape. Each trade is scaled to the account size as a share of its own session's starting balance, so a $10,000 practice session and a $100,000 challenge compare fairly. It reports the chance of reaching the target before the loss limit.
• How the rules work, a short guide to the floors and the other rules.

What you can build

The Pine Editor lets you write your own indicators and put them on the chart next to the built-in ones.

Open the Pine Editor tab in the bottom dock, write a script, and press Ctrl Enter. It appears on the chart like any other indicator, with a gear for its settings. Ctrl S saves it to your library.

The language is Pine-like. It is a subset of TradingView's Pine Script v5 that runs offline, inside this app, on the candles the replay has reached. Plenty of Pine indicators paste in and run, and many will not. When something is not supported, the editor tells you which line and what, instead of drawing something different. “Pine Script” is TradingView's trademark, and nothing here is affiliated with it.

What a script can do

• Draw lines, histograms, columns, areas and circles on the chart or in a pane of their own.
• Mark bars with shapes, arrows and characters, stripe the background, and recolour candles.
• Plot candles of its own, such as Heikin Ashi.
• Draw labels, lines, boxes, filled areas between lines, and tables, with hover tooltips on labels and table cells.
• Use another timeframe, such as a daily EMA on an M5 chart.
• Keep state in variables, arrays, maps, matrices, enums, and your own types with methods.
• Share functions, types and enums between scripts by saving them as a library and importing it.
• Expose settings (numbers, switches, colours, timeframes, sessions) that appear in the indicator's gear.

Where to go next

Follow Your first script to run something in two minutes, then read How a script runs to know why a script cannot peek at the future.

Your first script

Run the EMA Cross example, change one setting, and save it. It takes about two minutes.

1. Open the Pine Editor tab in the bottom dock.
2. Press Open ▾, and under Examples choose EMA Cross.
3. Press Add to chart (Ctrl Enter). Two moving averages and buy and sell markers appear. The button now reads Update on chart: edit the script and press it again to refresh the same indicator.
4. Click the gear on the indicator and change Fast length. The chart redraws.
5. Press Save (Ctrl S). The script is now in Open ▾ → Saved and in the Indicators list under My scripts.

The indicators on your chart are kept when you close the app and come back when it starts. See Saving and restoring.

What the script says

//@version=5
indicator("EMA Cross", overlay = true)

fastLen = input.int(9, "Fast length", minval = 1)
slowLen = input.int(21, "Slow length", minval = 2)

fast = ta.ema(close, fastLen)
slow = ta.ema(close, slowLen)

plot(fast, "Fast", color.blue, 2)
plot(slow, "Slow", color.orange, 2)
plotshape(ta.crossover(fast, slow), "Buy", shape.triangleup, location.belowbar, color.green)

• //@version=5 says which language version the script is written for.
• indicator(..., overlay = true) names the indicator and puts it on the price chart. Without overlay it gets a pane of its own.
• input.int(...) makes a setting. It shows up in the gear with the title you give it.
• ta.ema(close, fastLen) is a moving average of the close. The script runs once per bar, so fast is a different number on every bar.
• plot(...) draws a series. plotshape(...) draws a marker on the bars where its condition is true.

Starting from nothing

Press New for an empty script, or paste one from elsewhere. Type a name and press Ctrl Space for the list of functions with their parameters. If a script has unsaved changes, the editor asks before it lets you open another.

How a script runs

A script runs one bar at a time, from the oldest bar to the newest, on the candles the replay has reached.

A bar's value cannot depend on a later bar, because later bars are not there. That is what makes a replay honest: the indicator shows what it would have shown at that moment. On a higher-timeframe pane the newest bar is the partial one, so it grows as you step.

Stepping and re-running

• Stepping forward runs only the new bar.
• Stepping back, jumping, editing the script, or a higher-timeframe bar changing in place re-runs from the start. The output is the same either way.
• barstate.islast, last_bar_index and timenow mean “the bar at the cursor”. A script that reads them is re-run on every step instead of extended. That is correct, only slower.

Calls that are skipped on some bars

A ta.* call inside an if or inside barstate.islast still sees every bar. When its arguments depend on nothing but the bar (series, constants, inputs), the bars it skipped are fed through first. So this works:

if barstate.islast
    hh = ta.highest(high, 30)
    line.new(bar_index - 30, hh, bar_index, hh)

No clock, no randomness

There is no wall clock, and math.random() is refused. A script always gives the same output for the same candles. A loop that never ends is stopped after 500,000 iterations on one bar, with an error on the line.

Language basics

The syntax follows Pine v5. Indentation matters: four spaces or a tab.

x = 1                    // declare
x := x + 1               // change (also += -= *= /= %=)
var total = 0.0          // keeps its value from bar to bar
float f = na             // type words are accepted and ignored
[a, b, c] = ta.macd(close, 12, 26, 9)    // tuples

prev = close[1]          // earlier bars: close[0] is now
ta.sma(close, 5)[1]      // works on any expression

if close > open
    plot(close)
else if close < open
    plot(open)

for i = 0 to 9 by 2      // inclusive; break / continue work
while cond
switch kind              // or a bare `switch` on conditions
    "A" => 1
    => 0

f(a, b = 2) => a * b     // functions; a body can be indented

Series

Every variable is a series: it has a value on every bar. close is today's close, close[1] is the previous bar's, and close[20] is twenty bars back. The first bars of a long lookback have no value yet, which shows as na (a gap on the chart).

var keeps state

A plain total = 0.0 starts again on every bar. var total = 0.0 is set once and keeps whatever you assign to it, so you can count, accumulate, or remember a level.

Operators

+ - * / %, == != < > <= >=, and or not, and ? :. Strings join with +.

• Dividing by zero gives na.
• A comparison with na is false, except !=, which is true (as with NaN). So ta.change(x) != 0 is true on the first bar.

Line wrapping

A statement can continue on the next line if you indent it by something that is not a multiple of four, or end the line with an operator or comma.

Prices are decimals

Candles are stored as integer points, and a script sees close = 1.08432. Float arithmetic can make two moves that are exactly equal in points differ in the last digit.

Inputs and settings

Anything you declare with input.* appears in the indicator's gear, where you can change it without touching the code.

len  = input.int(14, "Length", minval = 1, maxval = 200, group = "Main")
src  = input.source(close, "Source")
mode = input.string("EMA", "Type", options = ["EMA", "SMA"])
tf   = input.timeframe("D", "Timeframe")
sess = input.session("0800-1600", "Session")

Kinds of input

Rules

• An input's default must be a fixed value, not something computed from price.
• Saved values are kept per input name, so renaming an input resets it.
• group and title may be a string kept in a variable (G = "Main"), so a group name can be written once.

Built-in series and functions

Type a name in the editor and press Ctrl Space for the full list with parameters. The list is generated from the same tables the compiler uses, so it never drifts.

Series

• open high low close volume time hl2 hlc3 ohlc4 hlcc4 bar_index
• year month dayofmonth dayofweek weekofyear hour minute second (UTC; dayofweek is 1 = Sunday)
• ta.tr ta.obv ta.accdist ta.pvt ta.nvi ta.pvi ta.wad ta.wvad ta.iii, ta.vwap / vwap (restarts each UTC day)
• time_close, last_bar_time
• syminfo.ticker / mintick / pointvalue / currency / pricescale / basecurrency
• timeframe.period / multiplier / isintraday / isdaily
• barstate.isfirst / islast / isconfirmed ...
• chart.bg_color / fg_color and the chart.is_* flags

ta.*

Moving averages: sma ema rma wma vwma swma hma alma linreg median mode cog.
Oscillators: rsi cci mfi cmo tsi wpr stoch macd.
Bands and ranges: bb bbw kc kcw atr tr dmi sar supertrend.
Statistics: stdev variance dev highest lowest highestbars lowestbars range max min change mom roc percentrank percentile_nearest_rank percentile_linear_interpolation correlation.
Events: crossover crossunder cross rising falling cum valuewhen barssince pivothigh pivotlow.

The older bare names (sma, rsi, ...) still work.

math, str, color, time

• math.* abs ceil floor round sqrt pow log log10 exp sign sin cos tan asin acos atan todegrees toradians max min avg sum round_to_mintick, and pi e phi.
• str.* tostring tonumber length upper lower contains startswith endswith substring replace_all format trim repeat pos split format_time. str.tostring accepts format.mintick, format.percent, format.volume and patterns such as "#.#####".
• color.* new rgb from_gradient r g b t and the named colours.
• time year(time) month(time) ... timestamp(y, m, d, h, mi), all UTC.
• general na nz fixnan int float bool

Sessions and time of day

time(timeframe, session) is the bar's timeframe start ("D", "W" starting Monday, "M", "60"), or na when the bar is outside session. Sessions look like "0800-1600", "2200-0600", or "0800-1600:23456" for chosen days (1 = Sunday), all in UTC. timeframe.change("D") is true on the first bar of each new day, and timeframe.in_seconds("60") converts a timeframe.

Where it differs from TradingView

• ta.ema starts from the first value (like Pine). The built-in EMA indicator starts from an SMA. The two agree after a few hundred bars.
• ta.pivothigh and ta.pivotlow report a pivot only once its right-hand bars exist (rightbars late), so they never see ahead. Plot with offset = -rightbars to put the mark on the pivot bar.
• ta.kc uses an EMA of the true range. The built-in Keltner indicator uses ATR.

Putting output on the chart

A script draws by calling output functions. Each call adds one thing to the chart.

A script with indicator(overlay = false) and no plot has nothing to put in a pane, so its markers and stripes go on the price chart.

Colouring by condition

//@version=5
indicator("Inside Bar", overlay = true)

inside = high < high[1] and low > low[1]

bgcolor(inside ? color.new(color.yellow, 80) : na)
plotshape(inside, "Inside bar", shape.circle, location.abovebar, color.yellow, size = size.tiny)

Pass na to a colour argument to draw nothing on that bar. color.new(color, 80) makes a colour 80% transparent.

Your own candles

//@version=5
indicator("Heikin Ashi")

haClose = (open + high + low + close) / 4
var haOpen = na
haOpen := na(haOpen[1]) ? (open + close) / 2 : (haOpen[1] + haClose[1]) / 2
haHigh = math.max(high, math.max(haOpen, haClose))
haLow = math.min(low, math.min(haOpen, haClose))

plotcandle(haOpen, haHigh, haLow, haClose, "Heikin Ashi", color = haClose >= haOpen ? color.teal : color.red)

Other timeframes

request.security runs an expression on a higher timeframe and hands the result back to each chart bar.

//@version=5
indicator("Daily EMA", overlay = true)

tf = input.timeframe("D", "Timeframe")
daily = request.security(syminfo.tickerid, tf, ta.ema(close, 20))
plot(daily, "Daily EMA", color.orange, 2, plot.style_stepline)

The call is request.security(symbol, timeframe, expression, gaps). It regroups the chart's own bars into the higher timeframe and runs expression on the result.

Only closed bars

A higher-timeframe bar is shown from the chart bar that ends it onwards. Until then you keep seeing the previous closed one. On an M5 chart, "60" shows the previous hour for the first eleven bars of an hour, and the new hour from its last bar.

A script cannot see a bar that has not finished, so replay and a full run give the same picture and nothing repaints. This is why lookahead_on is refused. You do not need the close[1] plus lookahead_on trick: the default already never looks ahead.

Rules

• Timeframes: minutes ("15", "240"), days ("D", "3D"), or "" for the chart's own. It must be a whole multiple of the chart's timeframe and not lower. Weekly and monthly are not offered, because the app's bars stop at one day. Days are UTC days.
• Symbol: the chart's own (syminfo.tickerid, syminfo.ticker, or ""). Other symbols are not available, and neither is request.security_lower_tf. A script is given the chart's own bars, so there is no finer data to ask for.
• gaps = barmerge.gaps_on returns na except on the chart bar where a higher-timeframe bar closed.
• The expression can be a tuple: [a, b] = request.security(..., [ta.rsi(close, 14), high]).
• Call it at the top level of the script, not inside a function and not inside another request.security.
• The first higher-timeframe bar is built from whatever chart bars exist, so on a chart that starts mid-bucket it is a partial one.

Variables inside the expression

Variables used in the expression are recomputed on the higher timeframe from their definition, as Pine does. m = ta.ema(src, len) then request.security(..., m) works, and so do inputs. A variable that is changed with :=, declared with var, or a function that reads script variables cannot be recomputed. The error says so. Put the calculation inside the expression instead.

Arrays

An array holds a list of values. Use one to keep a rolling window, a set of levels, or anything you build up bar by bar.

//@version=5
indicator("Median of the last 9 closes", overlay = true)

var window = array.new_float(0)
window.push(close)
if window.size() > 9
    window.shift()

plot(window.median(), "Median", color.orange)

Making arrays

array.new_float / new_int / new_bool / new_string / new_color(size, initial), array.new<float>(...), and array.from(a, b, ...). Typed declarations (array<float> a = ..., float[] a = ...) are accepted.

Every function can be called either way: array.push(a, x) or a.push(x), including on an expression, as in array.from(x, y).max().

Functions

• Access size get set first last includes indexof lastindexof
• Change push pop shift unshift insert remove clear fill reverse sort(order.descending) concat
• New arrays copy slice(from, to) from
• Statistics (skip na) sum avg min(nth) max(nth) median range variance stdev
• join(separator), and for item in a or for [i, item] in a to loop

Things to know

• A plain a = array.new_float(0) is a new, empty array on every bar. Use var to keep one across bars.
• An index outside the array, or pop, shift, first or last on an empty one, stops the script with an error on that line, as in Pine.
• An array holds at most 100,000 elements.
• a[i] is not element access. It is the history operator, so use a.get(i).

Maps and matrices

A map looks values up by key. A matrix is a grid of rows and columns.

//@version=5
indicator("Up / down days")

var tally = map.new<string, int>()
key = close > open ? "up" : "down"
tally.put(key, nz(tally.get(key)) + 1)

plot(nz(tally.get("up")), "Up", color.green)
plot(nz(tally.get("down")), "Down", color.red)

Maps

map.new<string, float>() with put get contains remove clear size keys values copy put_all.

• put and remove give back the old value, or na. get gives na for a missing key.
• Keys are numbers, strings, bools or colours, never na.
• for [key, value] in m loops over entries in the order they were added.
• At most 100,000 entries.

Matrices

matrix.new<float>(rows, columns, initial) with get set rows columns elements_count row col add_row add_col remove_row remove_col swap_rows swap_columns fill copy transpose reshape sum diff mult det inv trace avg min max.

• Rows and columns count from 0. An index outside the matrix is an error that names the size.
• mult takes a matrix, an array (matrix times vector, gives an array) or a number.
• sum and diff take a matrix of the same size, or a number.
• inv of a singular matrix is an error.
• At most 100,000 elements.

Method form

Method calls work on everything that has a collection or drawing object: m.put(k, v), x.get(r, c), tbl.cell(0, 0, "x"), lbl.set_text("y"). When a variable was created by table.new, map.new, array.new... and so on, the call is checked with that type's argument names. Otherwise the function is chosen from the value when it runs, with positional arguments only.

Types and methods

A type groups related values into one object. A method is a function you call on a value with a dot.

//@version=5
indicator("Swing tracker", overlay = true)

type Swing
    float price
    int bar
    bool isHigh = true

method distance(Swing this, float from) =>
    math.abs(this.price - from)

var last = Swing.new(high, bar_index)
if ta.pivothigh(high, 5, 5) == high[5]
    last := Swing.new(high[5], bar_index - 5)

plot(last.distance(close), "Distance to last swing high")

Types

type Name is followed by an indented list of fields: [type] name [= default]. Name.new(a, b) or Name.new(price = 1.0) makes an object. A field left out takes its default, else na ("" for a string, false for a bool).

p.price reads a field. p.price := 2 and p.count += 1 change it.

Objects are shared, not copied, when assigned: b = a is the same object. a.copy() (or Name.copy(a)) is a new one with the same fields. An object can hold other objects, arrays, maps and so on.

Methods

method name(Type this, ...) => is called as x.name(...). Two methods can share a name for different types, and a method can be defined on float, string and so on, as in close.double(). A built-in method of the same name (a.size() on an array) still works on its own types.

• Types and methods are defined at the top level, before they are used.
• Parameters can have defaults and be passed by name.
• Reading a field of an na object stops the script with an error on that line.
• p[1] is the object the variable held on the previous bar. On the first bar there is none, so guard it: bar_index > 0 ? p[1].x : na.

Enums

An enum is a fixed set of named values. Use one when a script has a few modes, and you want the settings gear to offer them as a dropdown.

//@version=5
indicator("Average type", overlay = true)

enum Kind
    ema = "Exponential"
    sma = "Simple"
    wma

kind = input.enum(Kind.ema, "Average")
len = input.int(20, "Length")
avg = switch kind
    Kind.ema => ta.ema(close, len)
    Kind.sma => ta.sma(close, len)
    => ta.wma(close, len)
plot(avg, "Average")

Defining one

enum Name is followed by an indented list of values. Each is a name, or a name with a title in quotes: sma = "Simple". The title is what people see in the dropdown and what str.tostring gives. Without a title, the name is used. An enum is defined at the top level of the script.

Using the values

• Write a value as Kind.ema.
• Compare with == and !=, or choose with switch, as above.
• A value can be a field of a type, a function argument, or a map key.
• input.enum(default, title, options) makes the dropdown. Pass options = [Kind.ema, Kind.sma] to offer only some values. The default has to be one of them.

The saved setting is the value's name, so renaming a value in the script resets that setting to the default.

Libraries

A library is a script that holds functions, types and enums for other scripts to use. It draws nothing and cannot be added to the chart.

Writing one

Begin the script with library("Name"), then define things. Put export before each one other scripts should be able to use.

//@version=5
library("MyMath")

sq(float x) =>
    x * x

export hyp(float a, float b) =>
    math.sqrt(sq(a) + sq(b))

export type Pair
    float a
    float b = 2

export enum Side
    buy = "Buy"
    sell

Press Save. The editor checks a library as you type, and Add to chart tells you it is a library instead of adding it.

Using one

//@version=5
indicator("Hypotenuse")
import me/MyMath/1 as m

p = m.Pair.new(3, 4)
plot(m.hyp(p.a, p.b))

import author/Name/version as alias finds the saved script whose library() title is Name. Case does not matter, and the author and version are ignored, so import MyMath as m works too. Everything exported is reached through the alias: m.hyp(...), m.Pair.new(...), m.Side.buy.

Rules

• A library can only hold library(), imports, and function, method, type and enum definitions.
• Functions without export are private to the library (sq above).
• A library cannot see the importing script's variables. Pass what it needs as arguments.
• Libraries can import other libraries. A loop between them is an error.
• Only saved scripts can be imported, not the unsaved text in the editor. Save the library first.
• Saving a change to a library re-runs every script on the chart that imports it.
• An error inside a library is reported on the import line, with the library's own line number in the message.

Labels, lines and boxes

These draw objects at a bar and a price, rather than a value on every bar.

//@version=5
indicator("Range box", overlay = true)

var bx = box.new(bar_index, high, bar_index + 20, low, border_color = color.teal, bgcolor = color.new(color.teal, 85))
if barstate.islast
    label.new(bar_index, high, "last", style = label.style_label_down, color = color.red)
    line.new(bar_index - 20, close, bar_index, close, extend = extend.right, style = line.style_dashed)

Signatures

• label.new(x, y, text, xloc, yloc, color, style, textcolor, size, ...)
• line.new(x1, y1, x2, y2, xloc, extend, color, style, width)
• box.new(left, top, right, bottom, border_color, border_width, border_style, extend, xloc, bgcolor, text, ...)
• linefill.new(line1, line2, color) shades the area between two lines. It disappears when either line is deleted. linefill.delete and set_color are available.
• polyline.new(points, curved, closed, xloc, line_color, fill_color, line_style, line_width) draws through an array of points. See below.

Each has set_* and get_* functions (label.set_xy, line.set_xy2, box.set_rightbottom, line.get_price, ...) and delete.

Positions

• x is a bar index by default. With xloc.bar_time it is a time in milliseconds. It may be in the future (bar_index + 10).
• yloc.abovebar and yloc.belowbar put a label just above the bar's high or below its low, ignoring y.
• Label styles: label_up/down/left/right/center, the four corner styles, none, and the shape styles (triangleup, circle, ...).

Polylines

A polyline connects many points with one line, and can fill the shape. Make the points with chart.point.

//@version=5
indicator("Triangle", overlay = true)

if barstate.islast
    pts = array.new<chart.point>()
    pts.push(chart.point.from_index(bar_index - 20, low))
    pts.push(chart.point.from_index(bar_index - 10, high))
    pts.push(chart.point.from_index(bar_index, low))
    polyline.new(pts, closed = true, line_color = color.orange, fill_color = color.new(color.orange, 85))

• chart.point.from_index(index, price), chart.point.from_time(time, price), chart.point.new(time, index, price) and chart.point.now(price). A point has .index, .time and .price.
• curved = true bends the line smoothly through the points. closed = true joins the last point to the first. fill_color shades the inside.
• With xloc = xloc.bar_time the points are placed by their time, not their index.
• The points are fixed when the polyline is made. polyline.delete(id) removes it.
• At most 50 polylines by default. Raise it up to 100 with max_polylines_count.

Keeping the count down

A plain l = line.new(...) makes a new line on every bar. To keep one and move it, declare it with var. To keep only the latest, call line.delete(l) on the old one first.

Past the limit, the oldest is deleted, as in Pine. The limit is 50 of each kind by default. Raise it up to 500 with max_lines_count, max_labels_count or max_boxes_count in indicator(...).

Things to know

• Calling a setter or delete on na does nothing. On anything that is not that kind of object, it is an error.
• Objects are drawn on the chart in pixels and do not affect the price scale, so one far outside the visible prices is simply off screen.
• A label's tooltip shows when you hover the label.

Tables

A table is a panel of cells fixed to a corner of the pane. It is the place for a small summary that should stay put while the chart scrolls.

//@version=5
indicator("Info panel", overlay = true)

var t = table.new(position.top_right, 2, 3, border_color = color.gray, border_width = 1)
table.cell(t, 0, 0, "Panel", text_color = color.white, bgcolor = color.blue)
table.merge_cells(t, 0, 0, 1, 0)
table.cell(t, 0, 1, "Close", text_color = color.white, text_halign = text.align_left)
table.cell(t, 1, 1, str.tostring(close, format.mintick), text_color = color.green, tooltip = "the last close")

Signatures

• table.new(position, columns, rows, bgcolor, frame_color, frame_width, border_color, border_width)
• table.cell(table, column, row, text, width, height, text_color, text_halign, text_valign, text_size, bgcolor, tooltip)
• table.cell_set_*, table.set_*, table.merge_cells, table.clear, table.delete

Behaviour

• Columns and rows count from 0. A cell outside the table is an error that names it.
• A table sits at a corner or edge of the pane (position.top_left ... bottom_right). A new table replaces the one already at its position, so building one on every bar does not pile them up.
• A column is as wide as its widest text. width and height are a percent of the pane instead.
• Calling table.cell again changes only the arguments you pass.
• The default text colour is light grey, readable on the dark chart, not black as on TradingView.
• Hovering a cell that has a tooltip shows it.

Example scripts

Ten examples ship with the editor. Open one from Open ▾ → Examples, or from the Indicators list under My scripts. Each one is run by an automated test, so a change to the language cannot quietly break it.

Recipe: Bollinger Bands

//@version=5
indicator("Bollinger Bands", overlay = true)

len = input.int(20, "Length", minval = 1)
mult = input.float(2.0, "Multiplier", minval = 0.1, step = 0.1)

[basis, upper, lower] = ta.bb(close, len, mult)

plot(basis, "Basis", color.orange)
u = plot(upper, "Upper", color.blue)
l = plot(lower, "Lower", color.blue)
fill(u, l, color.new(color.blue, 90))

Recipe: a line at each day's open

//@version=5
indicator("Daily Open", overlay = true)

newDay = dayofmonth != dayofmonth[1]
var float dailyOpen = na
if newDay
    dailyOpen := open

plot(dailyOpen, "Daily open", color.yellow, 2, plot.style_linebr)

Recipe: an RSI pane with shaded zones

//@version=5
indicator("RSI with Bands")

len = input.int(14, "Length", minval = 1)
upper = input.int(70, "Overbought")
lower = input.int(30, "Oversold")

value = ta.rsi(close, len)

plot(value, "RSI", color.purple, 2)
hline(upper, "Overbought", color.red, hline.style_dashed)
hline(lower, "Oversold", color.green, hline.style_dashed)
bgcolor(value > upper ? color.new(color.red, 85) : value < lower ? color.new(color.green, 85) : na)

What it will not do

Some Pine features are refused on purpose, and some are not built yet. In both cases the editor names the line and the reason.

Limits

• A loop is stopped after 500,000 iterations on one bar.
• An array, map or matrix holds at most 100,000 elements.
• Labels, lines and boxes: 50 of each by default, up to 500 with max_*_count.
• At most 50 tables.
• Polylines: 50 by default, up to 100 with max_polylines_count.

Saving and restoring

The indicators on your chart, and the scripts you save, are kept when you close the app.

Indicators on the chart

Every indicator on the chart, built-in and script, with its settings, is saved a moment after each change and comes back when the app starts. This includes whether it is collapsed, hidden or locked.

• They are restored only at startup, and only onto an empty chart, so they cannot pile up on top of ones you already added.
• If the saved file cannot be read, nothing is restored and nothing is written over it.
• The file is active_indicators.json in the app data folder (on Windows, %APPDATA%\com.onplayfx.barreplay\). It is written to a temporary file first and then renamed, so a crash cannot leave half a file.

Saved scripts

Save (Ctrl S) puts the script in your library: <app data>/scripts/<id>.json. It then shows under Open ▾ → Saved and in the Indicators list under My scripts. The × beside a saved script deletes it.

A library is an ordinary saved script that begins with library("Name"). Scripts that import it find it among your saved scripts, at startup and again whenever you save or delete one.

A script on the chart carries its own source. Chart templates, undocked chart windows and the indicator list all work without looking anything up, and editing the saved copy later does not silently change a script already on the chart.

Replay sessions and templates

Which scripts are on a chart is not saved inside a replay session (nor are the built-in indicators). To keep a particular set, save a chart template.

When something looks wrong

Errors show the line number and what went wrong. If there is no error and the picture is not what you expected, check this list.

What is built

A list of the script editor's features and how each one has been checked, so you know what to trust and what to test.

IN THE APP used in the desktop app and working.
ON SCREEN drawn in a browser test page and looked at, not yet in the app window.
TESTED covered by automated tests (838 pass), not yet looked at on a chart.

Not built

request.security_lower_tf and other symbols. Both need data the script engine is not given (finer bars, or a second symbol aligned to the replay), so they stop with a message that says so. strategy() is refused on purpose. See What it will not do.

Checking it yourself

If a script behaves oddly, copy it and its error line. It becomes a test, and the fix keeps working.

What's new

Changes to the script editor, newest first.

October 2026

Enums, polylines and libraries

Enums with an input.enum dropdown, polylines built from chart.point values, and libraries: save a script that begins with library("Name") and import its exported functions, types and enums from any indicator. p[1] on an object variable is covered by a test.

Indicators survive a restart

The indicators on your chart, built-in and script, come back when the app starts, with their settings. See Saving and restoring.

Tables and hover tooltips

table.* now draws real tables: merged cells, alignment, borders, percent widths and heights. Labels and table cells show their tooltip when you hover them.

Maps, matrices, types and methods

The full set of map functions and matrix maths (mult, det, inv, transpose and more). Generic syntax such as map.new<string, float>() is accepted. Define your own type and method, and call x.method() on collections, drawings, objects and even float and string.

Skipped ta.* calls see every bar

ta.highest(high, 30) inside if barstate.islast used to return na. It now sees every bar, so channel-drawing scripts draw. linefill, the chart.* colours and flags, weekofyear and extra syminfo.* values were added at the same time.

More functions

More ta.* functions, volume-based series, time_close, and many str.* helpers.

Own candles and bar colours

plotcandle, plotbar, plotarrow and barcolor, with Heikin Ashi as an example.

Labels, lines and boxes

label.*, line.* and box.* with styles, extends, bar-time positions and drawing limits.

Arrays

The array library, in function and method form, with for item in a loops.

Higher timeframes

request.security for the chart's own symbol, closed bars only, plus input.timeframe and input.session.

Earlier

The editor with highlighting and autocomplete, indicators-only scripts, the settings gear, the script library, and the examples.