Tell us your ideas and suggestions to help us improve Kiyotaka

Got something you’d like to tell us? Suggest it here and vote for other users’ ideas.

Triggering Alerts from kscript

I wanted to share a feature request that I believe would significantly improve the flexibility of Kiyotaka. Right now, alert conditions are extremely simple and limited because they can only be defined through the UI when creating the alert. In many cases, the logic inside a script is far more dynamic and complex than what the alert panel can express. Feature request: Enable alerts to be programmatically triggered directly from Pine Script using something like alert(), not just sending a message for an already-created alert, but actually allowing the script to define the condition itself at runtime. Concretely: Users should be able to call alert("LONG") inside their logic. In the alert creation panel, the user simply selects “Allow script-triggered alerts” (similar to “Any alert() function call”). Kiyotaka should fire an alert whenever the script executes the alert() call. This would completely unlock scripts that rely on multi-step logic that simply cannot be pre-defined as a static alert condition in the UI. It would be much more powerful if: A script could register multiple named alerts in code (e.g., alert("long_signal"), alert("short_signal")), and The alert panel would even allow users to pick which one(s) to activate. This would bring Kcript much closer to full automation, without requiring users to choose between oversimplified alert conditions. I hope this is something the team might consider — it would be an enormous improvement for quantitative and algorithmic traders. Thanks! Gianluigi

An Anonymous User 3 months ago

2
💡

Feature Request

Aggregated Liquidations Heatmap

Seconding Sahand’s suggestion on Discord, I propose and would love to use an aggregated heatmap for futures liquidations. As seen on Coinglass, it provides a useful complement to the orderbook. While the coordinates of liquidations evolve as time passes, and therefore their heatmap cannot offer ironclad predictions, it does rely on positions held actually and currently, unlike the orderbook which only displays a public intent to buy or sell in the future. Looking back at large liquidation events through such a heatmap also improves analysis of major capitulations and identification of reversal pivots that become future levels of interest.

An Anonymous User 2 months ago

1
💡

Feature Request

Kscreener -filters and alerts

It would be great to have filters in K-Screener combined with alerts — allowing users to set alerts based on active filters. For example, when no symbols match the filters and a new one appears, an alert is triggered, with optional confirmation time and cooldown to avoid noise from symbols frequently appearing and disappearing.

An Anonymous User 2 months ago

💡

Feature Request

kScript Access to Price-Level Order Flow

Access to bid volume, ask volume, and delta at each price level per bar - enabling footprint-based indicator development in kScript. since the kScript v2 buy_sell_volume() function only gives aggregate buy/sell volume per bar - it doesn't break down volume by price level within the bar, so it would be nice to have a data source function to gather bid,ask, delta per any given tick.

An Anonymous User 3 months ago

💡

Feature Request

Add Precise Price Input + Missing Toolbar Tools

When using toolbar tools like horizontal lines, there needs to be an option to manually input the exact price in the settings. Trying to place it perfectly by hand is inefficient. The toolbar is also missing some basics like a standard horizontal ray tool, and a magnet mode so objects snap cleanly to candle wicks.

An Anonymous User 2 months ago

2
💡

Feature Request