I would suggest playing around with the barstate commands when assigning the variable. You could try something like if barstate.isnew and high > high[1] buyprice = high + 2% Although, the problem with this is that it is subject to repainting. TradingView suggests using barstate.isconfirmed as a way ...

It's a little hard to tell what you are trying to say from the image. The number will show when you hover over the indicator when the value is added to the plot() function. I can see that you have something plotted from the second image. Could it be that you added a display.none command when you plo...

I went through and changed some things so it would compile. I added comments to the script and highlight them with *** so you will be able to see what I changed. This way you can you go through it in a pinescript editor. // @version=5 // Define strategy input parameters //*************I added a stra...

The only thing that I can think of would be to use a variable for the default value that can be changed. I tried this and I get an error saying 10:47:11 AM — Compilation error. Line 10: Syntax error: Arguments of input function must be of constant type, or 'source' builtin variables So it looks like...

You can create a strategy script pretty easily by using strategy.entry under the same condition as your alert messages. You might need to switch from using alertcondition() to alert() functions, but this is pretty easy. The main strategy function calls to set up a strategy script are strategy.entry(...

I was interested in seeing how this worked too, but I had the same problem when I tried to copy/paste the code into the pine editor. I don't know if some of the formatting changed with it was pasted on the forum. Maybe try to use the code button under the full editor?

I'm pretty sure you would have to set up the bot for each chart because the strategy has to be applied to the chart in order to scan for a set up, and the only way to do this is to have the strategy attached to each chart individually.

I think you would have to set up a work around for this since you can't create an options list for a logical operator that won't translate this input as a string and a string won't be able to perform a comparison. I would suggest creating another level to this with a boolean input so that false tran...

Interesting idea. This is how I would go about setting up a drop down for your input string with or as the default value since it has the highest priority.

logicalOperatorInput = input.string("or", title = "Logical Operator Options", options = ["or", "and", "not"])

Yeah I think your indicator is awesome, but it has gone over my head a little bit. I wish I could help because I would love to have something like this myself as well. I hope you are able to get it worked out in time.