All reports
capereurope_displayed reports
#160740: "Burning a green card when opponent has the conductor did not result in a caper being lost"
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
Their advantage of causing opponent to lose a caper when their card was burned was not gained.
It works for purple/yellow cards if the thief has that ability but not for green/conductor.• Is the rules violation visible on game replay? If yes, at which move number?
Yes. Most recent move.• What is your browser?
Google Chrome v133
Report history
8. Mar 2025 20:18 • Martin65 • Bug has not been reproduced by delopers yet:
Problem appeared each time I have played to my knowledge .
8. Mar 2025 21:07 • Kayvon • More information is requested by developers to reproduce this bug:
I’d like to help figure this out. On which move number did it occur?
In order to diagnose what’s happening, we need to know where to look in your game. You can find the current move number by looking in the upper-left corner where the progression is indicated (in landscape for mobile users). You can also find the move number by clicking on the log and looking at the link that’s provided when it offers you the option to replay from that point. Or you can click the 'View game replay' button after the game ends and either find it in the log or walk through the replay.
Please be aware that we're not BGA employees, just gaming enthusiasts like you, so the BGA framework prevents us from analyzing games that are still in progress. If you haven’t concluded your game yet just wait until it’s over before following up. If we don’t hear back from you in the next few days, we may close out this report, but we can also reopen it when you follow up.
In order to diagnose what’s happening, we need to know where to look in your game. You can find the current move number by looking in the upper-left corner where the progression is indicated (in landscape for mobile users). You can also find the move number by clicking on the log and looking at the link that’s provided when it offers you the option to replay from that point. Or you can click the 'View game replay' button after the game ends and either find it in the log or walk through the replay.
Please be aware that we're not BGA employees, just gaming enthusiasts like you, so the BGA framework prevents us from analyzing games that are still in progress. If you haven’t concluded your game yet just wait until it’s over before following up. If we don’t hear back from you in the next few days, we may close out this report, but we can also reopen it when you follow up.
9. Mar 2025 9:27 • Martin65 • More information is requested by developers to reproduce this bug:
Hi,
It is move 39.
Thank you.
It is move 39.
Thank you.
9. Mar 2025 9:46 • Martin65 • More information is requested by developers to reproduce this bug:
Actually the move hasn't finished yet as the opponent still needs to complete an action so maybe that is why. I will update.
9. Mar 2025 22:11 • Martin65 • More information is requested by developers to reproduce this bug:
Move 39 completed.
9. Mar 2025 23:21 • Kayvon • More information is requested by developers to reproduce this bug:
BGA framework prevents us from analyzing games that are still in progress. If you haven’t concluded your game yet just wait until it’s over before following up.
12. Mar 2025 15:40 • Kayvon • This is not a bug:
After looking through the rules and the implementation, I've confirmed this is the intended behavior. Only immediate "always" effects are reverted, not effects based on playing cards of a certain color.
This has been a point of confusion with many players, myself included, which is why we confirmed the correct behavior with the publisher while the adaptation was in beta.
This has been a point of confusion with many players, myself included, which is why we confirmed the correct behavior with the publisher while the adaptation was in beta.
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.
