Latest
Write your own indicators, in Pine
- New on Elite, in beta: write an indicator in Pine and it turns up in the indicator picker on every chart in the app — the trade chart, the replay, and the Backtest Lab.
- Paste the script and press Test code. It tells you what it will draw before you save it — "3 plots · 2 inputs · on the candles" — or which line it couldn't read and why. It runs the script rather than just reading it, so a length that's too long for the history you have comes back as "nothing has a value on any bar" instead of a green tick and an empty chart.
- You can't save a script that hasn't passed. An indicator that quietly draws nothing looks exactly like one whose data hasn't loaded, and you'd go looking in the wrong place.
- Every input you declare becomes a real input on the chart. Change a length or a multiple from the chart itself, on the fly, without going back to edit the script.
- Six worked examples to start from rather than an empty box: moving average, Bollinger Bands, RSI, MACD, ATR as a percentage of price, and a 200-EMA trend filter.
- It runs a subset of Pine, which is why it's marked beta — a script TradingView accepts may not compile here yet. Anything outside the subset is named when you test it, so you get "request.security is not supported" rather than a shrug. The subset is growing, and anything that tests green today keeps working as it does.
- Joining the Discord is now one button: Connect Discord & join. You authorise TradeGlitch, your account is added to the server, and the app knows which Discord account is yours.
- That replaces the invite link, which is gone. A link is forwardable — it sits in a group chat long after it was issued — so a members-only server was filling up with people who weren't members. There's no longer a link to forward.
- Every password box now has an eye to show what you've typed: login, signup, reset, and all three boxes when you change your password. Typing a password you can't see, twice, against a checklist telling you it isn't good enough yet, is the worst input in any product.
- A tag used at two stages now keeps a separate timeframe at each. A gap you spotted on the 15m and entered on the 5m records both numbers, each labelled with the stage it belongs to — where before the two shared one list and afterwards you couldn't tell which was which.
- Analytics still treats those as one tag. How your 5m FVG trades do is the same question whether you noted the 5m at setup or at entry.