View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0015359 | AI War 1 / Classic | Bug - Gameplay | Jun 2, 2014 4:33 pm | Jun 6, 2014 1:55 pm | |
| Reporter | malkiel | Assigned To | keith.lamothe | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 7.033 | ||||
| Fixed in Version | 7.034 | ||||
| Summary | 0015359: sabotage hacking targeting issues | ||||
| Description | normally, it works as intended, but upon loading an autosave about 15 times trying to survive my second worst bad decision ever, I had 10 sec left on a hack of an interplanetary munitions booster. when it completed that hack, there was a better than not chance of it ignoring the ion cannon nearby to it and targeting the raid engine literally across the system. while this was gravy for me, it is not working correctly. after it killed the raid engine, it found no further targets... the ion cannon was still sitting right there. I will test in other situations at a later time. if you cannot duplicate, I'll see if I can get you a file where it happens. seems approx. 70% chance. the ion cannon is mark 3, if that matters. The bad decision was my second planet captured (not counting HW) bordering 3 raid engines, and then I started hacking an ARS on one of those worlds, for those wondering. | ||||
| Tags | No tags attached. | ||||
| Internal Weight | New | ||||
| parent of | 0015374 | new | hacking progress tooltip is inaccurate when negative | |
| Not all the children of this issue are yet resolved or closed. | ||||
|
|
I will need a save for this, as it's likely very situation-specific. |
|
|
will attempt to duplicate. first save is when it was targeted on the force field nearby. second save is right after it hit said force field, and had re targeted on to the raid engine. error exists in that there is an ion cannon closer to the sabotage hacker in save number two, but I cannot promise it will not retarget correctly when you load it heh. guess it's a good thing I keep early versions of save files. edit to note providing of saves, second edit because number two linked to a very old issue unexpectedly. |
|
|
|
|
|
|
|
|
For 7.034: * Fixed a bug where MkI Ion Cannons were not eligible targets for the sabotage hacker (despite the other Ions being eligible). Thanks :) So actually the really strange thing would have been if it _did_ target the mkI ion, as it lacked the CanBeSabotaged flag entirely. |
|
|
you might want to check the mk3 sir, my original post was from about 30 minutes before those saves I sent, where a mk3 was not targetable by the sabotage. will attempt to duplicate that as well. so.. in my third save uploaded, it had run out of timer on a mk2 ion cannon and failed to kill it. verified issue on mk2 ion cannon. attaching save. (still 7.33) also, letting it finish the timer simply fails to destroy the ion cannon and also fails to expend hacking, so it's not as bad as it _could_ be. mk4 was properly destroyed by a sabotage hack prior to mark 2 on this testing file. whenever I load that mark 2 save, it instantly kills said ion cannon. I also attempted to duplicate my problems with a mark 3, but it was working fine this time around (could not generate error). something is still amiss though, and I submit the third save as evidence of that, insofar as _if_ the hack had _just_ finished, wouldn't there be a notification for a post hacking response? As there is not, it can only be surmised that the hack did _not_ just finish in the save, else there would be a vigorous response. Yet if you pause immediately upon loading, you can look at that shiny, doomed Ion Cannon. my poor mk1 fighters, I weep for them. XD |
|
|
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Jun 2, 2014 4:33 pm | malkiel | New Issue | |
| Jun 6, 2014 11:46 am | keith.lamothe | Note Added: 0038454 | |
| Jun 6, 2014 11:46 am | keith.lamothe | Assigned To | => keith.lamothe |
| Jun 6, 2014 11:46 am | keith.lamothe | Status | new => feedback |
| Jun 6, 2014 12:09 pm | malkiel | Note Added: 0038456 | |
| Jun 6, 2014 12:09 pm | malkiel | Status | feedback => assigned |
| Jun 6, 2014 12:43 pm | malkiel | File Added: replicating sabotage hack failure.sav | |
| Jun 6, 2014 12:43 pm | malkiel | File Added: replicating sabotage hack failure 2.sav | |
| Jun 6, 2014 12:46 pm | malkiel | Note Edited: 0038456 | |
| Jun 6, 2014 12:47 pm | malkiel | Note Edited: 0038456 | |
| Jun 6, 2014 1:05 pm | malkiel | Relationship added | parent of 0015374 |
| Jun 6, 2014 1:23 pm | keith.lamothe | Internal Weight | => New |
| Jun 6, 2014 1:23 pm | keith.lamothe | Note Added: 0038463 | |
| Jun 6, 2014 1:23 pm | keith.lamothe | Status | assigned => resolved |
| Jun 6, 2014 1:23 pm | keith.lamothe | Fixed in Version | => 7.034 |
| Jun 6, 2014 1:23 pm | keith.lamothe | Resolution | open => fixed |
| Jun 6, 2014 1:35 pm | malkiel | Note Added: 0038465 | |
| Jun 6, 2014 1:54 pm | malkiel | Note Edited: 0038465 | |
| Jun 6, 2014 1:55 pm | malkiel | File Added: mk 2 same error.sav | |
| Jun 6, 2014 1:55 pm | malkiel | Note Edited: 0038465 | |
| Jun 6, 2014 2:08 pm | malkiel | Note Edited: 0038465 |
