03-04-2024, 03:01 AM
(06-02-2023, 02:19 PM)AlexanderBrady Wrote: The space where the player drops their piece on to is marked with a state to allow them to drop there, and that state is removed when the piece is dropped. However, this rule works in most cases. I will list the cases which do and don't work in plain English to see if you can understand where things go wrong.
1) Freely place a piece on a space with a certain state, which causes the state in the target space to change to 0 (no-placement) and the state in adjacent spaces to change to states (1-6) depending on what placements end up being allowed. This works when the state in all adjacent spaces is also 0.
2) Drop a piece from hand to a space with a certain state, changing the state of that space to 0. Then change the states in adjacent spaces to one of the non-zero states (1-6). This works when the state in all adjacent spaces is 0.
3) Freely place a piece on a space with a certain state, which causes the state in the target space to change to 0 (no-placement) and the state in adjacent spaces to change to states (1-6) depending on what placements end up being allowed. This still works when the state of any of the adjacent spaces was non-zero to begin with.
4) Freely place a piece on a space with a certain state, which causes the state in the target space to change to 0 (no-placement) and the state in adjacent spaces to change to states (1-6) depending on what placements end up being allowed. This DOESN'T work when the state of any of the adjacent spaces was non-zero to begin with AND the drop move causes the state in an adjacent space to change.
I'm not sure if Ludii realizes this, but the state changes never take away moves, only add to them. But because it is a different state, maybe Ludii regards it as a different move even if the end effect is the same.
I was having the same problem and found the code that was causing the error. Thank you for your reply with a lot of useful information for me.