All reports
stirfryeighteen_displayed reports
#8006: "Number of cards in the game appear less than 18"
notabug: This is not a bug
1
What is this report about?
What happened ? Please select from below
Rules: a rule of the game has not been respected
Detailed description
• Which part of the rules was not respected by the BGA adaptation
There should always be exactly 18 cards in the game (duh)• Is the rules violation visible on game replay? If yes, at which move number?
Move #9. There are no cards on the table, 11 in the deck, 3 in my hand and 3 in the other player's hand. Total of 17...?• What is your browser?
Mozilla v5
Report history
30. Jul 2017 22:39 • umnikos • Bug has not been reproduced by delopers yet:
F5 did NOT solve the problem, so it must be something to do with the game itself.
The problem appeared more than once and the result is always that there are always less than 18 cards. I didn't notice a pattern in the appearance since I don't count the cards every time but it's a really common bug (and it's weird)
Image of the bug: imgur.com/a/LoSHR
The problem appeared more than once and the result is always that there are always less than 18 cards. I didn't notice a pattern in the appearance since I don't count the cards every time but it's a really common bug (and it's weird)
Image of the bug: imgur.com/a/LoSHR
31. Jul 2017 7:51 • DrKarotte • This is not a bug:
The missing card is the one you have discarded just before.
31. Jul 2017 20:33 • umnikos • This is not a bug:
@DrKarotte Then why is the deck not updated with my new hand?
1. Aug 2017 7:51 • DrKarotte • This is not a bug:
Which turn number should that happen?
I cannot see anything wrong.
This is probably some misunderstanding. All discarded and cooked cards are put back to the deck after cooking (this is not done "visible").
I cannot see anything wrong.
This is probably some misunderstanding. All discarded and cooked cards are put back to the deck after cooking (this is not done "visible").
Add something to this report
Please add here anything that seems relevant to reproduce this bug or understand your suggestion:
- 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.
