My Human bot in Brawlwood has a tendency to raise the infinite loop error once in a while. It would be nice if I could view a partially completed version of the match (up to the infinite loop) to try and get an idea of what the problem is.
Tracking the infinite loop match recovery issue over here: https://github.com/codecombat/codecombat/issues/772
The problem is that we don’t currently have a way to know which method is infinitely looping and null it out–all we can do is abort the whole simulation. I think once we implement statement limitations, we’ll be in a better place to selectively limit runtimes, but we haven’t gotten to that part yet.