Alle rapporten
Caper: Europe rapporten
#160740: "Burning a green card when opponent has the conductor did not result in a caper being lost"
notabug: Dit is geen bug
1
Waarover gaat dit rapport?
Wat is er gebeurd? Selecteer uit het onderstaande
Regels: een spelregel werd niet gerespecteerd
Gedetailleerde beschrijving
• Met welk onderdeel van de regels is geen rekening gehouden bij de BGA-versie?
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 de inbreuk op de spelregels zichtbaar in de spelherhaling? Indien ja, bij welk zetnummer?
Yes. Most recent move.• Welke browser gebruik je?
Google Chrome v133
Rapportgeschiedenis
8 mrt 2025 20:18 • Martin65 • Bug is nog niet gereproduceerd door de ontwikkelaars:
Problem appeared each time I have played to my knowledge .
8 mrt 2025 21:07 • Kayvon • De ontwikkelaars vragen meer informatie om deze bug te reproduceren:
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 mrt 2025 9:27 • Martin65 • De ontwikkelaars vragen meer informatie om deze bug te reproduceren:
Hi,
It is move 39.
Thank you.
It is move 39.
Thank you.
9 mrt 2025 9:46 • Martin65 • De ontwikkelaars vragen meer informatie om deze bug te reproduceren:
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 mrt 2025 22:11 • Martin65 • De ontwikkelaars vragen meer informatie om deze bug te reproduceren:
Move 39 completed.
9 mrt 2025 23:21 • Kayvon • De ontwikkelaars vragen meer informatie om deze bug te reproduceren:
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 mrt 2025 15:40 • Kayvon • Dit is geen 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.
Dit rapport aanvullen
Gelieve hier alle informatie toe te voegen die relevant is om deze bug te reproduceren of jouw suggestie te begrijpen:
- Andere tafel ID / zet ID
- Loste F5 het probleem op?
- Kwam het probleem meerdere keren voor? Altijd? Willekeurig?
- Als je een schermafbeelding van deze bug hebt (goede gewoonte), kun je Imgur.com gebruiken om deze te uploaden, de link kopiëren en hier plakken.
