#18889: "Double card when steeling opponents barn not occurring"
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 claiming an opponents barn you should be awarded 2 cards.
-
• Please explain what you wanted to do, what you did and what happened
Move 169
• Which browser are you using?
Google Chrome v83
-
• 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 claiming an opponents barn you should be awarded 2 cards.
-
• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
Move 169
• Which browser are you using?
Google Chrome v83
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
When claiming an opponents barn you should be awarded 2 cards.
• Which browser are you using?
Google Chrome v83
-
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
When claiming an opponents barn you should be awarded 2 cards.
• Which browser are you using?
Google Chrome v83
-
• Which part of the rules was not followed by the BGA adaptation?
When claiming an opponents barn you should be awarded 2 cards.
-
• Is the rules violation visible on game replay? If yes, at which move number?
Move 169
• Which browser are you using?
Google Chrome v83
-
• What was the game action you wanted to do?
When claiming an opponents barn you should be awarded 2 cards.
-
• What did you try to do to trigger this game action?
Move 169
-
• What happened when you tried to do this (error message, game status bar message, ...)?
• Which browser are you using?
Google Chrome v83
-
• At which step of the game did the problem occur? What was the current game instruction?
When claiming an opponents barn you should be awarded 2 cards.
-
• What happened when you tried to do this game action (error message, game status bar message, ...)?
Move 169
• Which browser are you using?
Google Chrome v83
-
• 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 claiming an opponents barn you should be awarded 2 cards.
• Which browser are you using?
Google Chrome v83
-
• 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 claiming an opponents barn you should be awarded 2 cards.
-
• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
Move 169
• Which browser are you using?
Google Chrome v83
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
When claiming an opponents barn you should be awarded 2 cards.
• Which browser are you using?
Google Chrome v83
Report history
The first claiming of an opponents barn works correctly and 2 cards are awarded however subsequent reclaims of that barn are only awarded 1 card.
This would still be a bug
At move 135, there is a 4 parcels takeover containing the central barn. There is correctly 1 card drawn. But the barn is still displayed with the small grass touches, which means it's still considered free...
That's strange, but it explains why, at move 164, the take over gave only 1 card.
It was a problem happening when taking free barns *and* taking over opponents parcels. The computation of the resulting state was wrongly using initial barns and not recomputed barns... so the fact that the barns was now occupied was lost
So I could with a few lines of code rebuild state just before the move causing problems, then playing it and see why the code didn't return the expected result.
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.
