I still hit the loop recursion limit with this loop, even if I break the loop at the end (break value=1), once it ran through all data inside the array. (by comparing the loop index with array length befor, see screenshot) If I increase the break value to 2, I get another error right away. So a value of 1 inside the "Break" instruction should be sufficient.
I also tried:
- using synchronous movement, removing the distance check
- locking the behaviour (5 ticks per second)
- increasing wait time
I can't see a way how this loop is causing a recursion. At that point inside the behaviour, it's also the only loop thats ever running! I therefor consider this a bug. Either with the loop recursion detection, or with the loop instruction itself.
I'm going to bypass loop instructions, and implement them "manually", in hope this just skips the loop recursion check...
