Skip to content
TradequixDocsOpen the terminal
OverviewStart here, search, progress
  • Introduction
  • Quickstart
  • How a script runs
  • Types and qualifiers
  • Operators, conditionals and loops
  • Functions and methods
  • Objects and enums
  • Arrays, matrices and maps
  • Strings and colours
  • Time and sessions
  • Bar states
  • Plotting
  • Inputs
  • Technical analysis
  • Drawings and tables
  • Multiple timeframes
  • Strategies
  • Alerts in scripts
  • Repainting
  • The Pine editor
  • Indicator settings
  • Coming from TradingView
  • The data
  • Publish and sell
  • Catalogue and community
  • Your dashboard and earnings
  • Errors and debugging
  • Limits
  • Coverage
  • Built-in catalogue
  • Cookbook
  • Write Pine with AI
  • FAQ
  • Glossary
  • Cheat sheet
  • Function reference
  • Will it run here?
  • Error index

Reference

Coverage

Which parts of Pine Script v6 work on Tradequix, which are verified by our own tests, and which are not available.

View as MarkdownOpen in ClaudeOpen in ChatGPT

Tradequix runs Pine through PineTS 0.11.1. This page combines PineTS's own coverage notes with what Tradequix has tested itself. It is honest rather than complete: "works" here means tested on this platform, not that every argument of every function has been compared with TradingView.

Status key#

MarkMeans
VerifiedCovered by Tradequix's own tests and rendered on a real chart
SupportedImplemented by PineTS; used by scripts here, not exhaustively tested
PartialWorks with known limits, listed alongside
Not availableFails or returns na, with an explicit message

Language#

FeatureStatusNotes
Bar-by-bar execution, series, [] historyVerified
var, varip, na, nzVerified
if, switch, for, for … in, whileSupportedInfinite loops are stopped with an error
User functions f(x) => …VerifiedIncluding multi-line bodies
Tuples [a, b] = f()Verified
Arrays, matrices, mapsVerifiedRepresentative operations tested
User-defined types, enumsSupported
Methods, objectsPartialUpstream marks these as in progress
import of librariesNot availableNeeds a library resolver this platform does not have

Namespaces#

NamespaceStatusNotes
ta.*VerifiedSeventy-plus functions; all 62 built-ins use them
math.*, str.*, color.*Verified
input.*VerifiedEvery type becomes a settings field
plot*, hline, fill, bgcolor, barcolorVerifiedAll styles drawn natively
plotshape, plotchar, plotarrowVerifiedDraw where the series is true or non-zero
plotcandle, plotbarVerified
label, line, box, table, polyline, linefillVerifiedSome shapes and table layouts are approximate
strategy.*VerifiedNot every order variant tested
request.security, request.security_lower_tfVerifiedSee Multiple timeframes
request.financial, earnings, dividends, economic, footprintNot availableReturn na with a warning
alert, alertconditionPartialShown in the editor console; no background delivery
chart.left_visible_bar_time and other viewport valuesPartialNot verified
syminfo.*, timeframe.*, barstate.*SupportedSymbol, timeframe and precision come from the chart

Known differences from TradingView#

  • Data. Volume is a tick count, and the feed has no fundamentals or order flow. See The data.
  • Rendering. Values are exact; some marker and label shapes, proportional arrow sizes, curved lines and table layouts are close but not pixel-identical.
  • Realtime. The last bar recalculates as it forms; exact rollback behaviour of varip on every tick is not verified.
  • Modified tickers. Heikin Ashi, Renko and similar fail explicitly instead of serving plain candles.

For the status of each individual function, see the function reference, which lists every name the engine implements. For PineTS's own coverage tables, see the PineTS language coverage and API coverage pages.

PreviousLimitsNext Built-in catalogue

On this page

  • Status key
  • Language
  • Namespaces
  • Known differences from TradingView

Use with AI

View as MarkdownOpen in ClaudeOpen in ChatGPT