All reports
parks_displayed reports
#165078: "Visit 2 parks on same turn, in accordance with rulebook"
notabug: This is not a 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
I was allowed to visit 2 parks in the same turn
-
• Is the rules violation visible on game replay? If yes, at which move number?
Move 133
• What is your browser?
Google Chrome v135
Report history
14. Apr 2025 2:36 • Kayvon • Bug has not been reproduced by delopers yet:
Report short description
"Visit 2 parks without having an extra action that let me visit the second park"
changed to
"Visit 2 parks on same turn, in accordance with rulebook"
"Visit 2 parks without having an extra action that let me visit the second park"
changed to
"Visit 2 parks on same turn, in accordance with rulebook"
14. Apr 2025 2:37 • Kayvon • This is not a bug:
> I was allowed to visit 2 parks in the same turn
That's true! When you have a moment, take a look at the updated rulebook. You'll find that's perfectly fine.
That's true! When you have a moment, take a look at the updated rulebook. You'll find that's perfectly fine.
29. Apr 2025 13:15 • Chaotic Midnight • This is not a bug:
Table #663479504
Move #83
The game gave me an option to visit 2-3 parks in one single turn as long as I have the resources to do it I think (I didn't do it because of the rules hahaha)
Move #83
The game gave me an option to visit 2-3 parks in one single turn as long as I have the resources to do it I think (I didn't do it because of the rules hahaha)
29. Apr 2025 14:10 • Kayvon • This is not a bug:
> I didn't do it because of the rules hahaha
You might take a closer look at the rules, or even at the earlier comments you just replied to. It's completely allowed.
You might take a closer look at the rules, or even at the earlier comments you just replied to. It's completely allowed.
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.
