06-17-2021, 07:58 AM
I understand it can be confusing, but there can be more than one problem in a script.
1) Main outstanding point:
What I cannot work around is the the problem with the "I" pieces placed on the edges showing in the wrong positions and/or causing index out of range and preventing the move. This could be the same bug as N-Meshed that you said you have fixed - but is not yet released. Please fix or confirm it already is fixed... (you can see the problem in the " ... 1.2.1b.lud" file (or not see it, if it is already fixed) Just try placing two pieces of the same color diagonally adjacent and see where/if the connection line is placed.
Minor additional requests
2) The rest I have worked around, however scripting like this is like walking through a minefield, so I have posted so you can clear them. I think you would want to remove bugs that are clearly identified and appreciate me taking time to identify the problem. So FWIW:
Definitely, in "(= 2 (count Pieces #1 "Ball" in:(intersection (sites Around Cell (from)) (sites Around Cell (to)))))" the Ludii is ignoring the "Ball" constraint.
3) There must be a cleaner way to handle the Halfway edge scripting instead of converting to array, but I had compiler errors with many tries and that is what finally worked. I doubt it is worth your time to dig into it or explain it to me unless it is something obvious. But if there is a kind of "why didn't he simply do it this way" solution, which doesn't take you time to think about, I would be thankful for the guidance.
1) Main outstanding point:
What I cannot work around is the the problem with the "I" pieces placed on the edges showing in the wrong positions and/or causing index out of range and preventing the move. This could be the same bug as N-Meshed that you said you have fixed - but is not yet released. Please fix or confirm it already is fixed... (you can see the problem in the " ... 1.2.1b.lud" file (or not see it, if it is already fixed) Just try placing two pieces of the same color diagonally adjacent and see where/if the connection line is placed.
Minor additional requests
2) The rest I have worked around, however scripting like this is like walking through a minefield, so I have posted so you can clear them. I think you would want to remove bugs that are clearly identified and appreciate me taking time to identify the problem. So FWIW:
Definitely, in "(= 2 (count Pieces #1 "Ball" in:(intersection (sites Around Cell (from)) (sites Around Cell (to)))))" the Ludii is ignoring the "Ball" constraint.
3) There must be a cleaner way to handle the Halfway edge scripting instead of converting to array, but I had compiler errors with many tries and that is what finally worked. I doubt it is worth your time to dig into it or explain it to me unless it is something obvious. But if there is a kind of "why didn't he simply do it this way" solution, which doesn't take you time to think about, I would be thankful for the guidance.