I will fix bugs or migrate your old tradingview pine script to v6
Pine Script v6 Developer for TradingView Indicators and Backtested Strategies
About this Gig
Your Pine script broke on v6, is repainting silently, or just stopped firing alerts? Send me the code and I'll return a clean v6 version in 24-48 hours with a short before/after note explaining every change I made. If I genuinely can't fix it in scope, you get a full refund - no retainer, no partial-fix bill.
What I handle quickly:
- Deprecated-function fixes (study to indicator, security to request.security)
- - v3, v4 or v5 to v6 migrations
- - "Cannot modify a variable that is a reference" errors
- - Repaint issues (barstate, lookahead, request.security quirks)
- - Alerts that stopped firing after a TradingView update
- - Slow scripts hitting the compute budget - I rewrite the hot paths
Please send me the .pine file (not a screenshot) before you order.
If a script turns out to be properly unfixable - say it leans on a workaround that v6 removed - I will tell you up front and refund rather than rebuild for the sake of it. A clean rewrite is sometimes cheaper, and I have a separate gig for that.
Please don't send:
- Pirated or cracked paid indicators
- - Scripts you want reverse-engineered from another seller
Been writing Pine for 10 years, 31 live markets. Most broken scripts, I have seen the
Platform:
TradingView
Development technology:
PineScript
FAQ
How do I send you my broken script?
Paste the full Pine source into the order's message area (TradingView's Share -> Export source works), or attach a .pine text file. Include the error message TradingView shows you and a short note on what you expected the script to do.
My script worked fine on v4 - why does v6 reject it?
Pine v4 to v6 introduced breaking changes: study() became indicator(), security() became request.security(), type declarations got stricter, label.new + line.new style arguments changed. Most v4 scripts need 15-40 syntax edits plus a repaint-safety review.
Will you also improve my script, or only fix what is broken?
Default is a clean fix with a before/after note. If I spot an obvious correctness bug (a repaint, a wrong valuewhen index, a missing barstate.isconfirmed), I'll flag it and ask if you want it fixed as part of the job. Scope upgrades are a separate order.
What does unfixable - refund rather than overcharge mean?
If after inspecting your script I conclude it would take more hours than your tier's price can cover - because the underlying logic needs a rewrite, not a fix - I'll refund rather than quote you half-fixed work. You lose zero.
Does this include protecting or obfuscating my script?
No. This gig is about fixing broken Pine, not code protection. If you need a closed-source invite-only publication, buy a separate development gig; obfuscation of someone else's open-source Pine is not a service I'll offer.
