All reports
unconditionalsurrender_displayed reports
#49268: "Possible to do bombing runs that can never be intercepted"
fixed: Bug has been fixed
2
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
Not hugely important but it is possible to hack the game when doing bombing runs; you select the factory but then click on "undo", rather than "confirm", then click on "bombing run" a second time; when you select another factory it will trace back to the first factory you select, not back to home location of the bomber. (Presumably you can also just click again on the same factory, though I didn't check that).
Then "confirm" and the bomber will just teleport to factory1 and trace a path between factory1 and factory 2 before returning, thus avoiding any possibility of interception.• Is the rules violation visible on game replay? If yes, at which move number?
You can read the latest history on the above game; my UK bomber trace is a trace from Prague to Posen, not a trace from London to Posen.
• What is your browser?
Google Chrome v93
Report history
26. Sep 2021 17:18 •
Sourisdudesert • This report has been closed automatically because there was no vote/comment on it for a long time:
13. Feb 2023 12:16 •
16. Feb 2023 18:01 • Report closed automatically because it has not been upvoted or commented for a while.
Your bug has probably been fixed already, or was linked to a temporary failure of BGA service.
In any case, when filling a bug report, make sure to have an explicit title linked to the incident (ex: with error message), so other players can recognize it and vote for it.
Your bug has probably been fixed already, or was linked to a temporary failure of BGA service.
In any case, when filling a bug report, make sure to have an explicit title linked to the incident (ex: with error message), so other players can recognize it and vote for it.
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.