View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0022517 | AI War 2 | Bug - Gameplay | Jan 4, 2020 6:25 pm | Jan 10, 2020 6:25 am | |
| Reporter | WolfWhiteFire | Assigned To | BadgerBadger | ||
| Status | closed | Resolution | won't fix | ||
| Product Version | 1.025 Hotfix | ||||
| Summary | 0022517: Sabotage Defense Hack failed to destroy the target after completion | ||||
| Description | During a campaign, I was attacking a planet with an ion eye, not active, using sabotage defenses to destroy it so that the rest of my armada could come to assist. About 5 seconds before hack completion, I paused and sent all my ships in, expecting it to activate for a few seconds before being destroyed by the hack. (there were no other possible targets on planet and the hack listed the ion eye as the target) It activated about 3 seconds before hack completion, as expected, however after hack completion it was not destroyed, it just kept firing. I waited a fair bit to see if it was just delayed for some reason, however it remained intact and there was no longer an option to sabotage defenses on the planet. TLDR: Ion eye was activated a few seconds before hack completion and was completely unaffected by the hack. | ||||
| Tags | No tags attached. | ||||
|
|
Active eyes are immune to the sabotage hack. You need to finish the hack before sending in your ships. |
|
|
Why do active eyes need to be immune to sabotage? If you make them vulnerable in the interest of clarity and not having people step in this particular newbie trap, will it enable some explotative tactic? I don't think "carry out a hacking defense while dealing with an active eye" is very appealing. If active eyes DO need to be immune to sabotage, then the hack should not complete and fail silently. It should either abort immediately (refunding hacking progress) with a warning to the player that the eye has become active and can no longer be sabotaged, or pause with the same warning. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Jan 4, 2020 6:25 pm | WolfWhiteFire | New Issue | |
| Jan 4, 2020 6:40 pm | BadgerBadger | Note Added: 0055331 | |
| Jan 10, 2020 2:45 am | BadgerBadger | Assigned To | => BadgerBadger |
| Jan 10, 2020 2:45 am | BadgerBadger | Status | new => closed |
| Jan 10, 2020 2:45 am | BadgerBadger | Resolution | open => won't fix |
| Jan 10, 2020 6:25 am | Fluffiest | Note Added: 0055483 |
