#41790: "Never skip any player, even if they have abandoned the game"
What is this report about?
What happened? Please select from below
What happened? Please select from below
Please check if there is already a report on the same subject
If yes, please VOTE for this report. Reports with the most votes are given PRIORITY!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detailed description
-
• Please copy/paste the error message you see on your screen, if applicable.
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
-
• Please explain what you wanted to do, what you did and what happened
• Which browser are you using?
Firefox
-
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
-
• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
• Which browser are you using?
Firefox
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
• Which browser are you using?
Firefox
-
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
• Which browser are you using?
Firefox
-
• Which part of the rules was not followed by the BGA adaptation?
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
-
• Is the rules violation visible on game replay? If yes, at which move number?
• Which browser are you using?
Firefox
-
• What was the game action you wanted to do?
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
-
• What did you try to do to trigger this game action?
-
• What happened when you tried to do this (error message, game status bar message, ...)?
• Which browser are you using?
Firefox
-
• At which step of the game did the problem occur? What was the current game instruction?
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
-
• What happened when you tried to do this game action (error message, game status bar message, ...)?
• Which browser are you using?
Firefox
-
• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
• Which browser are you using?
Firefox
-
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
-
• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
• Which browser are you using?
Firefox
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
When a player quits the game, it seems the current implementation would skip that player and let the remaining player play twice. This does not seem to be a good choice, because Gopher is sensitive to parity. Perhaps the system can play some random move (if available) for the player who quits.
• Which browser are you using?
Firefox
Report history
Maybe this issue would be better addressed to BGA management.
Add to this report
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appear several times? Every time? Randomly?
- If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
