Hi @Paul, or anyone with better coding skills than me, can anyone figure out if this HeuristicsCycle code looks right for an ML3 version?

I cannot get an ML3 version (using algo 3 for £/tick N) to work properly when coded. It’s like the ML2’s v4 without the trailing stop, but with one more part added, i.e., number 3 algo and using the line: elsif heuristicsalgo3 = 1 then… When I use it it does not take any trades?

The only way I can get the Value Z Money Mgt algo = “N” to work (pls see screens and GraphZ blue line) is to use the “HeuristicsCycleLimit = 2” version and then // out the “elsif heuristicsalgo3 = 1 then” line of code. I have had that blue line work to the end to other tests.
I have tried ValueZ replacing the N’s in the buy code but get an error from PRT asking me to report. Maybe N cannot be ValueZ? I really think though if N can be replaced with ValueZ and we can get the money management ML3 algo coded right the performance will increase. I’ve seen it do £25k in two months using N in the buy code before a tbt warning came on. I’ve attached the “work in progress” Renko ML3 V4 below.