CASOON Open Source
Experiments in technical analysis, written in Pine Script.
A loose collection of TradingView indicators and strategies in Pine Script v6 for market structure, trend, momentum and confluence. Most of it is unfinished. One habit runs through all of it: checking whether a script's inputs carry a signal on the instrument it runs on, not only whether its maths is correct.
Experimental, not advice
These scripts are for learning and chart analysis. They do not recommend any trade, no page here claims a signal is profitable, and a backtest says nothing about future results. Many indicators are drafts that have not been checked on real charts, and quality varies widely. Trading involves substantial risk of loss; decisions and their consequences are your own.
- indicator directories, each with its own page
- 95
- scripts with a declared Data Contract so far
- 42
- catalogued indicators not, or barely, checked on real charts
- 64 of 96
- scripts published on TradingView
- 6
What it does
Data before maths
Whether volume is trade volume comes from syminfo.volumetype, not from the existence of a volume series. Without it, volume parts switch off visibly and the remaining weights are renormalised.
A Data Contract in the header
Scripts state which data they need — price, volume, open interest, a reference market — and a verdict: CFD-degraded, Reference-required or Exchange-only.
One role per indicator
An indicator measures one thing: structure, trend strength, exhaustion. Composite indicators combine roles explicitly and show which part drives the reading.
Alerts that keep working
Named conditions with stable titles and codes, one message format, and a bar-close gate so an alert does not fire on a forming bar and vanish.
7 strategy wrappers
Standalone strategies for the Strategy Tester, with confirmed-bar entries and a guard that warns on Heikin Ashi, Renko and other synthetic chart types.
Quickstart
From choosing an indicator to a first alert. The walkthrough in the documentation covers each step.
- Pick an indicator by the question you want answered, from the index or the sidebar.
- Check its data requirements: the Data Contract in the header, or the README.
- Paste the
.pinefile into the Pine Editor, or add the published version on TradingView. - Create an alert from its named conditions; messages carry a stable code per indicator.
<code> · <event> · {{ticker}} {{interval}}
CPM4 · WATCH LONG · {{ticker}} {{interval}}
CPM4 · LONG · {{ticker}} {{interval}}Frequently asked questions
What is this repository exactly?
A running collection of experimental TradingView indicators and strategies in Pine Script v6, not a finished product catalog. Quality is treated as an ongoing process, including whether an indicator’s inputs carry a real signal on the instrument it runs on.
How do I use one of the indicators?
Open the .pine file for the indicator you want, copy its contents, then in TradingView use Pine Script Editor → Paste → Add to Chart.
What does the "Data Contract" in a script header mean?
It states which data the indicator needs — price, volume, open interest or a reference market — and gives a verdict: CFD-degraded, Reference-required or Exchange-only, so you know whether it fits your instrument before adding it.
Are the strategies ready to trade?
No single status applies to all of them. Each strategy under strategies/ is standalone and hand-maintained, and its status — for example "Promising" or "Not ready — not yet backtested" — is listed in the README and its own assessment file.
Is anything here financial advice?
No. The scripts are for learning and chart analysis, no page claims a signal is profitable, and a backtest says nothing about future results. Trading involves substantial risk of loss.