-
Notifications
You must be signed in to change notification settings - Fork 10
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
Game can't end unless a human wins [GH-2] #11
Comments
…r message to deal with computer win.
I've now created a game save which can be used to reproduce this issue. See issue 11 reproduction.zip. It looks like the exact issue behavior has changed since this issue was first raised:
This is no longer accurate. What happens now is that the next turn message for the last surviving human stays on the screen and the game freezes. The backend then runs though the rest of the game (computers only) in the background. When the game is over and there is one surviving computer player, the UI updates again and the game over message is displayed. |
I'm going to look to fix this by implementing option one where the game will end with a different game over message. |
This should now be fixed and this issue should no longer block work on GH-2. |
Describe the bug
If all human players die, the game does not end and the last surviving player must keep clicking through the next turn message as the computer players continue.
If a computer player wins, the game will not end but will continue. This is because the check for player death is done in the conquer handling in the view which the computer player doesn't invoke.
To Reproduce
All human players must be conquered, and a computer player must then conquer all other players.
Expected behaviour
When a computer player wins, the game should end and there should be the appropriate message.
When all human players die but computer players remain, this could be handled in multiple ways.
System Information (please complete the following information):
n/a (This is a code bug/issue)
Additional context
n/a
The text was updated successfully, but these errors were encountered: