03-27-2021, 03:14 AM
I have noticed that the (no Moves Mover) and (is Repeat Situational) are difficult to use correctly, and the Logic guide gives little guidance about the pit falls.
It seems that the system is designed to protect against recurrent situations within a given turn, and a game seeking alternative methods of avoiding cycling is very tricky to implement. For example, if any of the previos posts are not due to Ludii bugs, then the detailed reasons need to be explained as examples of how not to script, and why not.
I finally succeeded by introducing a separate decision to move again (move Set NextPlayer (player (mover)) and a fall-back pass move, and the game AI are now working, and the game complexity is not hanging, so I guess the script is now finite in a proper way.
Please refer to my next post in the submission thread.
It seems that the system is designed to protect against recurrent situations within a given turn, and a game seeking alternative methods of avoiding cycling is very tricky to implement. For example, if any of the previos posts are not due to Ludii bugs, then the detailed reasons need to be explained as examples of how not to script, and why not.
I finally succeeded by introducing a separate decision to move again (move Set NextPlayer (player (mover)) and a fall-back pass move, and the game AI are now working, and the game complexity is not hanging, so I guess the script is now finite in a proper way.
Please refer to my next post in the submission thread.