I have found the issue. It was the function that contained the loop being called multiple times.
1 Like
That’s great to hear! In the future, if you test certain parts of your code on their own to see how they behave on their own, it’ll be easier to identify if the problem is actually with that part of the code or elsewhere. In this case, you would have come to a solution quicker if the function you speak of was shared.
Always good to figure things out for yourself though, and satisfying too!
The issue wouldn’t have arisen in the finished product. The initialize function is going to be executed by a chat command, but I temporarily made it activate when a start brick was touched because the chatted event isn’t reliable in studio. I didn’t do a debounce for when the start brick was touched.
2 Likes