Library "FrizBug" Debug Tools | Pinescript Debugging Tool Kit All in one Debugger - the benefit of wrapper functions to simply wrap variables or outputs and have the code still execute the same. Perfect for Debugging on Pine str(inp) Overloaded tostring like Function for all type+including Object Variables will also do arrays and matricies of all...
After studying several other scripts, I believe I have found the Holy Grail! (Or perhaps I've just found a bug with Tradingview's Pinescript v4 language) Anyhow, I'm publishing this script in the hope that someone smarter than myself could shed some light on the fact that adding a trailing stop to any strategy seems to make it miraculously...no that's an...
This is just published for visibility as a public service until the Pine devs are able to fix or document this behavior. The barssince() function returns different values when inside a conditional context. As long as it can be documented (and relied upon), this could be a pretty cool feature, but right now this is now how I read the help documentation to...
This is a code to showcase a function call bug in PineScript. Problem description: When a function is called from inside of if-then scope, this function may return an invalid result. Code description: Two identical code pieces are used to perform simple calculation. The only difference is that one piece has a part of its code wrapped into a...
I found a bug with built-in percentrank function. Sometimes it gives unexpected and incorrect results. You can see a one of them on the chart. ALL scripts which use percentrank function are affected. No matter which version they use, no matter who is their author - ALL scripts which use this built-in function can work incorrectly. If you want to avoid...
Hello Tradingview Community, I've been playing around with some various volume-based indicators, and recently have been experiencing a delay in the entries for my strategy for 2 minutes in this scenario. If the time is adjusted, it also is delayed 2 bars. In this example, the "Short" position should enter when the blue line Crosses under the upper green line,...
Functions with parameters do not work correctly: the returned value is sometimes different from the expected one. The example script works correctly only when idx = 1 (instead of the current line 6).
the way to work around the bug for this specific strategy, altho its not as efficient as it would if both orders activation was possible.