All reports
harvest_displayed reports
#150457: "Mick può fare più di una azione campo bonus a turno."
worksforme: Developers did not manage to reproduce this 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
Mick dovrebbe poter fare solamente una azione campo bonus a turno, durante il 4° turno ho potuto utilizzare questo bonus due volte scegliendo due tessere sul mercato.• Is the rules violation visible on game replay? If yes, at which move number?
Il numero della mossa non riesco a vederlo, ma si può vedere bene dalle mie azioni:
1° azione: ho pagato 2 pigne per scegliere la tessera centrale del mercato, che garantisce 1 azione campo ed il riempimento del secchio, ed ho fatto due azioni campo (tendere + raccogliere) poi ho riempito il secchio;
2° azione: ho pagato 1 pigna per scegliere la tessera a sinistra del mercato, che garantisce il potenziamento di 1 seme e due azioni campo ed ho fatto 3 azioni campo (piantare, tendere e raccogliere).
Quindi al posto di 1+2+1(bonus)=4 azioni campo ne ho fatte 1+1(bonus)+2+1(bonus)=5• What is your browser?
Google Chrome v131
Report history
21. Dec 2024 21:00 •
Kayvon • More information is requested by developers to reproduce this bug:
21. Dec 2024 22:04 • 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.
Kayvon • Developers did not manage to reproduce this bug:
28. Dec 2024 1:51 • Unfortunately, we haven't received a response with the required information, so I'm going to close the request. If the information is provided later on, we can always reopen this and investigate.
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.