All reports
tashkalar_displayed reports
#55838: "Can't claim isolation task"
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
Move #240 (last move), I isolate his common piece at the top, but the system says I can't claim the task.• Is the rules violation visible on game replay? If yes, at which move number?
The position is visible. it's clear that it's isolated properly. See screenshot.• What is your browser?
Google Chrome v96
Report history
26. Dec 2021 18:36 •
Quinarbre • This is not a bug:
26. Dec 2021 18:57 •
24. May 2023 21:53 • The top piece is not isolated. Move it east, southeast, and then southwest, and it becomes adjacent to a friendly piece.
Saxmaam • This is not a bug:
24. May 2023 21:54 • This report has been marked not a bug. Does that mean someone needs to file another bug report?
Quinarbre • This is not a bug:
24. May 2023 22:06 • No, it means there is no bug.
You're incorrectly claiming that task : the piece that's surrounded by yours is still adjacent to a Nethervoid piece (by southeast corner).
If you think another piece is eligible tell me which and I'll point you to your mistake.
You're incorrectly claiming that task : the piece that's surrounded by yours is still adjacent to a Nethervoid piece (by southeast corner).
If you think another piece is eligible tell me which and I'll point you to your mistake.
Saxmaam • This is not a bug:
25. May 2023 0:49 • Thank you for your reply. It finally clicked with me what this is saying. I think the text on the card could be improved, but I get it now. (The problem is the phrase “within two squares”, but I agree that there is only one way to meet all of the criteria on the card. I think it should say “two squares away”).
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.