This document highlights the major improvements and design changes between kScript v1 and kScript v2. The goal of v2 is to make scripting more intuitive, powerful, and performant for indicator developers.
1. Execution Model
Legacy approach - not recommended
- Execution was line-by-line and evaluated expressions directly
- Developers had to manually assemble time-aligned series using:
buildTimeseries(...)mergeTimeseries(...)matchTimestamp(...)timeseries(...) constructor
- This was unintuitive and often led to performance bottlenecks
- Introduces per-bar execution model, similar to Pine Script
- Script phases:
- Initialization → definitions, inputs, data subscriptions
- Calculation → runs once per bar
- Plotting → render output
- No need for manual alignment; the engine handles timeseries iteration automatically
2. Keyword Arguments (kwargs)
Functions accepted only positional arguments, making scripts harder to read and maintain.plotLine(rsiTs, 3, ["red", "green"])
All functions now support keyword arguments (kwargs). More readable and order-independent.plotLine(value=rsiTs, width=3, colors=["red", "green"])
3. Compiler Improvements
- Most errors surfaced only at runtime
- Developers had to debug by trial and error
- Strong compile-time analysis
- Detects syntax errors, scope violations, and type mismatches before execution
- Safer and faster iteration for script developers
4. Data Subscriptions
All data sources handled via the generic source(...) function.timeseries ohlcvTs = source("ohlcv", "BTCUSDT", "BINANCE")
Dedicated functions for specific data types:
ohlcv(symbol, exchange)trades(symbol, exchange)orderbook(symbol, exchange)
Improves readability and ensures correct schema handling.timeseries ohlcvTs = ohlcv(symbol="BTCUSDT", exchange="BINANCE")
5. Technical Indicator Functions
- Functions like
rsi, ema returned a full timeseries
- Developers often misunderstood how to work with them, leading to redundant or incorrect code
- Each technical function returns a scalar value per bar
- Much simpler to use directly in expressions and plots
var r = rsi(source=ohlcvTs.close, period=14)
plotLine(value=r, width=2, colors=["#3fa9f5"], label=["RSI"], desc=["Relative Strength Index"])
6. Field Accessors
Accessing fields from data was clunky and inconsistent.
Clean accessors for multi-field series like OHLCV:
ohlcvTs.closeohlcvTs.openohlcvTs.highohlcvTs.lowohlcvTs.volume
var diff = ohlcvTs.close - ohlcvTs.open
7. Reverse Index Access
- Forward-style indexing only (oldest first)
- Hard to get the latest values directly
Reverse indexing: ts[0] → latest bar, ts[1] → one bar before last, etc.var lastClose = ohlcvTs[0].close
var prevClose = ohlcvTs[1].close
8. Function Definitions
No support for custom functions.
User-defined functions via func. Enables modular, reusable code.func safeDiv(a, b) {
return b == 0 ? 0 : a / b
}
9. Loops
No support for looping constructs.
Full support for for and while loops (restricted to var variables).for (var i = 0; i < 5; i = i + 1) {
print(text=i)
}
10. Plot Functions
Limited plotting functions (plotLine, plotBar).
Extended plotting options:
plotLine(...)plotBar(...)plotCandle(...)plotShape(...)
All support kwargs and flexible styling. 11. Standard Library
Minimal helper set.
Extended standard library with math, indicators, and utility helpers:
- Indicators:
rsi, ema, sma, stoch, ma, …
- Helpers:
abs, round, max, min, …
- Debugging:
print, printTimeSeries
Summary
kScript v2 delivers major improvements over v1:
Per-bar execution eliminates manual time alignment
Keyword arguments make functions clear and self-documenting
Compile-time checking prevents most runtime surprises
Dedicated subscription functions improve clarity
Technical indicators return scalars per bar instead of entire timeseries
Field accessors make OHLCV data ergonomic
Reverse indexing gives direct access to the latest data
Functions and loops enable modular and expressive code
Extended plot functions and library unlock richer visualization and analysis
