-
Notifications
You must be signed in to change notification settings - Fork 1
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
Player choice pull request #3
Conversation
…erative playing pawn assignment. Bug fix with basic player pending.
…awn in best_player_move
…(now 70% win rate against firsty first)
…each player in test
Hi @Tomansion, Thanks for fixing the tests, documentation and formatting. I'll try to not forget those in the future. :) I wonder whether you have some kind of platform in place to test and rank new AIs (besides the project's testers)? Cheers, |
Perfect, then I'll merge those changes
Good idea! I make and deploy web applications, we could do some kind of leaderboard and a place to drag and drop players. I'm not planning on doing this anytime soon, but I will look into how other people did it safely. |
Sounds good! I have some basic experience with Flask and React so I would be happy to contribute. There is also an interesting platform for ai development for board and video games called "codinGame". They don't have Santorini yet so it would be possible to deploy it there, although one needs to reach a certain level (by creating successful AIs) to be allowed that possibility. |
Player pawn selection on move
Now implementing the real rules of Santorini, the Player class must now tell which pawn to move.
Thank you @daniPclos for starting the implementation in #2 and doing most of the work.
I've copied your changes and applied the following changes: