05-27-2023, 03:58 PM
I have found this kind of behavior can happen if a consequence of a condition affects a boolean that creates the condition. You are not allowed to do that in ludii, but the compiler doesn't enforce it. This is my off-hand experience - I didn't look at your code, but I was wrestling with the same issue today, and it took a while to hunt down the bit of code that was causing it. Could also be going into an infinite loop or not able to find any valid move,say dueto an ifAfterwards clause or a (to) that moves to the (from) i.e. a zero distance move is among the moves it is considering to make.