> the move is applied automatically the moment the done does stone_width/2 in a free direction
Shouldn't a move be complete when the stone bumps into a wall and stops moving? I guess you already have the code to detect that event. You can hook the move counter there.
Keyboard navigation is definitely due on a computer. Select a stone with mouse and move with arrows or awsd. We can play two handed. It's much better on a phone now because we can throw stones to walls with a finger.
But I see how it can be confusing when the path to travel is 1*stone_width. I don't have a good idea how to preserve the behavior on a bigger board and making it less confusing on a smaller one.
> the move is applied automatically the moment the done does stone_width/2 in a free direction
Shouldn't a move be complete when the stone bumps into a wall and stops moving? I guess you already have the code to detect that event. You can hook the move counter there.
Keyboard navigation is definitely due on a computer. Select a stone with mouse and move with arrows or awsd. We can play two handed. It's much better on a phone now because we can throw stones to walls with a finger.