#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 taken care of in PRIORITY!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detailed description
-
• Please copy/paste the error message you see on your screen, if any.
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 explains what you wanted to do, what you do and what happened
• What is your browser?
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?
• What is your browser?
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.
• What is your browser?
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.
• What is your browser?
Firefox
-
• Which part of the rules was not respected 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?
• What is your browser?
Firefox
-
• Which 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 do you try to do to trigger this game action?
-
• What happened when you try to do this (error message, game status bar message, ...)?
• What is your browser?
Firefox
-
• At which step of the game did the problem occurs (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 try to do a game action (error message, game status bar message, ...)?
• What is your browser?
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.
• What is your browser?
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?
• What is your browser?
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.
• What is your browser?
Firefox
Report history
Maybe this issue would be better addressed to BGA management.
Add something to this report
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? 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.
