Alla rapporter
Caper: Europe rapporter
#160740: "Burning a green card when opponent has the conductor did not result in a caper being lost"
notabug: Detta är ingen bugg
1
Vad handlar denna rapport om?
Vad hände? Välj från alternativen nedan
Regler: en av spelets regler har inte respekterats
Detaljerad beskrivning
• Vilken del av reglerna respekterades inte av BGA-adaptionen?
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.• Är regelbrottet synligt i återuppspelning? Om ja, vilket nummer är det på draget?
Yes. Most recent move.• Vad har du för webbläsare?
Google Chrome v133
Rapporthistorik
8 mar 2025 20:18 • Martin65 • Buggen har inte kunnat återupprepas av utvecklarna än:
Problem appeared each time I have played to my knowledge .
8 mar 2025 21:07 • Kayvon • Mer information efterfrågas av utvecklarna för att kunna återskapa detta fel:
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 • Mer information efterfrågas av utvecklarna för att kunna återskapa detta fel:
Hi,
It is move 39.
Thank you.
It is move 39.
Thank you.
9 mar 2025 9:46 • Martin65 • Mer information efterfrågas av utvecklarna för att kunna återskapa detta fel:
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 • Mer information efterfrågas av utvecklarna för att kunna återskapa detta fel:
Move 39 completed.
9 mar 2025 23:21 • Kayvon • Mer information efterfrågas av utvecklarna för att kunna återskapa detta fel:
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 • Detta är ingen bugg:
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.
Lägg till något till denna rapport
Lägg till här allt som verkar relevant för att reproducera det här felet eller förstå ditt förslag:
- Ett annat spelbords-ID / drag-ID
- Löste F5 problemet?
- Uppträdde problemet flera gånger? Varje gång? Slumpmässigt?
- Om du har en skärmdump av denna buggen (vilket är bra), så kan du använda Imgur.com för att ladda upp den och kopiera/klistra in länken här.
