All reports
notalone_displayed reports
#30244: "Flashback triggered on the wrong card the turn after playing 2 hunt cards."
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
Flashback is suppose to be used on the last hunt card that was discarded. The turn prior I was able to play 2 cards because of tracking. The 1st card I played was anticipation, 2nd was mirage. Anticipation was targeted by flashback.• Is the rules violation visible on game replay? If yes, at which move number?
Yes. Anticipation played at move 75, Mirage at 78, Flashback at 89.• What is your browser?
Google Chrome v87
Report history
17. Dec 2020 21:25 •
pabula • Bug has not been reproduced by delopers yet:
25. Aug 2021 10:27 • the same situation at my table:
boardgamearena.com/9/notalone?table=194534783
I do want to play Flashback on my last played card which was Stasis (2nd card played) but I can't as the card on the top is Forbidden Zone which I played before Stasis.
boardgamearena.com/9/notalone?table=194534783
I do want to play Flashback on my last played card which was Stasis (2nd card played) but I can't as the card on the top is Forbidden Zone which I played before Stasis.
KenFin1 • Bug has not been reproduced by delopers yet:
5. Mar 2023 21:21 •
16. Feb 2024 12:48 • I had the same problem in my game today.
Tracking played - Forbidden zone (phase 2) then detour (phase 3)
I tried to play flashback at phase 3 but I couldn't select detour again. It kept saying i couldn't use the card (flashback) this phase.
boardgamearena.com/table?table=353530998 (see move 115-117)
Tracking played - Forbidden zone (phase 2) then detour (phase 3)
I tried to play flashback at phase 3 but I couldn't select detour again. It kept saying i couldn't use the card (flashback) this phase.
boardgamearena.com/table?table=353530998 (see move 115-117)
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.