-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PuzzlePlayer revamp #31
Comments
(Duplicate issue): Dan's request: Change UNSOLVABLE and SOLVABLE to LOSE and WIN respectively, and label moves as WINS, LOSES, and TIES along |
Dan's request: Legend based moves instead of indexed based moves (i.e. typing '01' instead of writing '0' for move '0->(0,1)') |
Visual of remoteness table. For every step, see the history of the remoteness as "text line graph". |
Dan's request: If you press Enter with nothing inputted and there is only one move available to input, you should be able to execute that one move |
I think if you press enter without specifying any move, it should just select the best move. therefore, if there is only one move, it will always just choose that |
Dan's request: Support undoes. Possibility is by maintaining the history of the Puzzle states. |
Similar to the Gamesman analysis portion of their Text UI, integrate some form of analysis we can make on the Solver and design it as a function. A good starting point would be counting the number of positions with the same remoteness.
The text was updated successfully, but these errors were encountered: