A begrudgingly assembled heap of technical indicators, duct-taped together for a scripting language so limited, it makes Excel macros look like advanced AI — because apparently, suffering builds character. And also RSI curves.
So you've decided to get rich using the arcane arts of Pine Script, huh? Good for you. This repository contains a patchwork quilt of lovingly hand-stitched technical indicators, each written with mathematical precision, half-sincere perfectionism, and a deep resentment for Pine Script’s idea of "versioning".
Don't worry if you're new to this – odds are high you are. And yes, some of this will look like algebra had a baby with Excel. But stick around. You might just learn something useful. Like how to separate actual trading logic from the fever dreams of a YouTube crypto-bro who shills "secret indicators" between affiliate links and protein shake ads. Or at least learn how to avoid blowing up your account after copying a strategy named “MoonSniper V8.3 Ultimate” posted by a dude named Kevin420 in the TradingView forums.
- Finite Impulse Response Trends
- Infinite Impulse Response Trends
- Oscillators
- Momentum Indicators
- Volatility Indicators
- Volume Indicators
- Trend Dynamics
- Cycles Indicators
- Price Channels and Bands
- Stop and Reverse Indicators
- Signal Filters
- Numerics
- Statistics
- Error Metrics
You can also explore The Complete Master List of All Indicators (Warning: Side effects may include widened eyes, sudden trading epiphanies, and the irrational confidence of someone who just discovered MACD for the first time. No refunds.)
- Mathematically Accurate: These aren't your average copy-pasta indicators ripped from some rando’s trading post written during a Red Bull crash. No weird hacks, no mystical constants, and absolutely zero Reddit-sourced Fibonacci “enhancements” that only work during Mercury retrograde on a leap year. If you needed magic, go back to tuning MACD with moon phases. You're welcome.
- Optimized Code: Every calc cycle counts when your backtest says you're the next Buffet but your live trades scream “please clap.” Wherever possible, indicators are written in O(1) instead of O(n) — which, for the uninitiated, means they run in constant time instead of chugging through each bar like a hungover intern on earnings day. If you're not sure what that means, just know that O(1) is the kind of code that slaps, not drags.
- Proper Initialization: No na-filled fakeouts. No warm-up rituals involving ten candles, a goat, and three lines of if bar_index > 100. Just proper initialization from bar one, like your indicators actually graduated basic training and didn’t just wander in from Pine Script kindergarten.
- Error Compensation: FIR, IIR, LOL – if it can be made more accurate, I made it so. If not, I added enough math to make it look accurate until it isn’t. Because numbers matter. Especially when they're wrong.
- Reasonable Documentation: Some parts are documented. Some aren’t. Consider it a spiritual journey. If you're confused, it's either in the docs, the code, or the stars. Besides, real traders don’t read documentation – they just tweet angrily until someone answers.
- MIT Licensed: Use it, abuse it, fork it, launch a tokenized DAO around it. Just don’t DM me asking for “just a quick tweak” or to review your “super secret trading strategy” in broken Pine v2. This isn’t Fiverr, and I’m not your unpaid TA sensei.
- Navigate to the
indicatorsfolder. Find your poison – sorry, your indicator. - If you have no idea what you're doing, copy the whole script. If you think you do, steal the function block and use it in your masterwork.
- Paste it into TradingView's editor. If you don't know where that is, you may not be ready. Go back. Train more. Or join a Discord server and pretend you're backtesting a strategy by using random numbers. Same thing.
- Apply it to your chart. Watch it do math better than your last three indicators combined. That includes many built-in indicators in Pine Script library
- Shower the dev with Github stars and fame. Not because I care, but because validation keeps me from writing Python again.
I crafted this library during late-night sessions where Pine Script and I developed a love-hate relationship. (It's mostly hate. Pine Script started it.) My therapist says it’s “growth.” I say it’s syntax errors.
If you're brave enough to contribute, please ensure your PR is mathematically sound enough to make your calculus professor weep with joy. If implementations sucks, don't worry. I'll settle for "doesn't crash TradingView" and "actually does what it claims to do." Extra karma if your indicator doesn't give false signals during sideways markets—that's the holy grail we're all pretending exists.
Please don't ask me to make an "indicator that never fails to predict the future." I already made one: it's called "not trading." Patent pending. Also backtested on my dreams.
MIT. Do what you want. Seriously. Start a shady token. Build your own cult. Just don't blame me when the backtest lies to you.