01-16-2021, 06:51 AM
Currently walks can define pieces and requirements for movement.
In Canoe, a win condition is a certain shape Plus the absence of one's own pieces in the neighborhood
In other games certain leaps are not allowed over other pieces.
Might an extension to the Walk syntax help:
Capital letters function as before, but lowercase letters require that the cell reached by that particular letter's movement meet special conditions.
The default condition would not containing a mover's piece. An optional condition would be must be Empty, or must be Enemy
Alternatively,
F: Forward over anything
Fe: Forward over emply
Fm: Forward over mover occupied
Fn: Forward over next occupied
Fx: forward except over mover
L: Left
Le: Left over empty ...
R: Right ...
etc
The move or goal condition would then fail if there were a mis-match.
This would allow a great deal of flexibility, and fit with your existing system
In Canoe, a win condition is a certain shape Plus the absence of one's own pieces in the neighborhood
In other games certain leaps are not allowed over other pieces.
Might an extension to the Walk syntax help:
Capital letters function as before, but lowercase letters require that the cell reached by that particular letter's movement meet special conditions.
The default condition would not containing a mover's piece. An optional condition would be must be Empty, or must be Enemy
Alternatively,
F: Forward over anything
Fe: Forward over emply
Fm: Forward over mover occupied
Fn: Forward over next occupied
Fx: forward except over mover
L: Left
Le: Left over empty ...
R: Right ...
etc
The move or goal condition would then fail if there were a mis-match.
This would allow a great deal of flexibility, and fit with your existing system