Yeah, sorry about that 
My initial tests seemed to indicate that I had to use an external variable if I was to use a loop counter that would not reset each time the tick went through the macro. Either Epic changed something in 4.8 so that this was no longer needed or (more likely) I overlooked something. Anyway I’m glad I took a second look. It’s a lot easier to implement like this.
Let me know if you find a good way to have loops per tick be adjusted automatically depending on the requirements of the specific loop. I’ve implemented these loops in my toolkit the last few days in preparation for my mobile update. Turns out it might not really be needed, as even my pretty old smartphone is able to run the pathfinding pretty smoothly without having to split up the loops. I guess one should always make sure whether you really need to optimize before you begin doing so Ah well, I’m sure I’ll find some use for them in any case.