Alle rapporter
capereurope_displayed rapporter
#160740: "Burning a green card when opponent has the conductor did not result in a caper being lost"
notabug: Dette er ikke en feil
1
Hva handler denne rapporten om?
Hva har skjedd, eller hva gjelder det? Vennligst velg
Regler: en regel i spillet har ikke blitt respektert
Detaljert beskrivelse
• Hvilken del av reglene ble ikke respektert av BGA-tilpasningen
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.• Er regelbruddet tydelig i spilloggen? Hvis ja, Hvilket trekknummer?
Yes. Most recent move.• Hvilken nettleser bruker du?
Google Chrome v133
Rapporthistorikk
mars 8 th 2025 20:18 • Martin65 • Feilen har ikke blitt reprodusert av utviklerne enda:
Problem appeared each time I have played to my knowledge .
mars 8 th 2025 21:07 • Kayvon • Utviklerne ønsker mer informasjon for å kunne reprodusere denne programfeilen:
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.
mars 9 th 2025 9:27 • Martin65 • Utviklerne ønsker mer informasjon for å kunne reprodusere denne programfeilen:
Hi,
It is move 39.
Thank you.
It is move 39.
Thank you.
mars 9 th 2025 9:46 • Martin65 • Utviklerne ønsker mer informasjon for å kunne reprodusere denne programfeilen:
Actually the move hasn't finished yet as the opponent still needs to complete an action so maybe that is why. I will update.
mars 9 th 2025 22:11 • Martin65 • Utviklerne ønsker mer informasjon for å kunne reprodusere denne programfeilen:
Move 39 completed.
mars 9 th 2025 23:21 • Kayvon • Utviklerne ønsker mer informasjon for å kunne reprodusere denne programfeilen:
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.
mars 12 th 2025 15:40 • Kayvon • Dette er ikke en feil:
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.
Legg til noe i denne rapporten
Legg til her noe som synes relevant for å reprodusere denne feilen eller forstå forslaget ditt:
- En annen bord ID / flytt ID
- Løste F5 problemet?
- Oppstod problemet gjentatte ganger? Hver gang? Tilfeldig?
- Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet her.
