Todos os informes
Informes de capereurope_displayed
#160740: "Burning a green card when opponent has the conductor did not result in a caper being lost"
notabug: Isto non é un erro
1
Sobre qué é este informe?
Qué aconteceu? Por favor selecciona debaixo
Regras: unha regra do xogo non foi respectada
Descrición detallada
• Qué parte das regras non se cumpriron na adaptación da BGA?
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.• é visible a violación das regras na repetición? Se o é, en que número de movemento?
Yes. Most recent move.• Cal é o teu navegador?
Google Chrome v133
Historial de informes
8. Mar 2025 20:18 • Martin65 • O erro aínda non foi reproducido polos desenvolvedores:
Problem appeared each time I have played to my knowledge .
8. Mar 2025 21:07 • Kayvon • Os desenvolvedores requiren máis información para reproducir este erro:
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 • Os desenvolvedores requiren máis información para reproducir este erro:
Hi,
It is move 39.
Thank you.
It is move 39.
Thank you.
9. Mar 2025 9:46 • Martin65 • Os desenvolvedores requiren máis información para reproducir este erro:
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 • Os desenvolvedores requiren máis información para reproducir este erro:
Move 39 completed.
9. Mar 2025 23:21 • Kayvon • Os desenvolvedores requiren máis información para reproducir este erro:
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 • Isto non é un erro:
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.
Engade a este informe
Por favor engade aquí calquera cousa que sexa relevante para reproducir este erro ou entender a túa suxestión:
- Outro DI de mesa / ID de movemento
- Premer F5 resolveu o problema?
- Apareceu o problema varias veces? Tódalas veces? Aleatoriamente?
- Se tes un pantallazo deste erro (boa práctica), podes usar Imgur.com para subilo e copiar/pegar a ligazón aquí.
