View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0022237 | AI War 2 | Bug - Other | Nov 18, 2019 3:35 pm | Nov 18, 2019 4:55 pm | |
| Reporter | alocritani | Assigned To | BadgerBadger | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 1.009 Hotfix | ||||
| Fixed in Version | 1.010 Extracting Those Archives | ||||
| Summary | 0022237: Hacking history: aborted hacking is listed as 0 | ||||
| Description | If you start an hack and become crippled, no hack cost is deducted but hacked building is destroyed. If you start an hack and then abort, full hack cost is deducted but hacked building is available again. by the way, is this difference intended? any way, in both cases hack history says that hack costed 0 point, but in case 0000002 (hack aborted) this is not true. In attached savegame, you can start an hack, stand still and be crippled or start and stop hacking. | ||||
| Tags | No tags attached. | ||||
|
|
Well, without knowing which building you are talking about it's hard to say. The logic for hacking different structures is totally different. Assuming you mean an ARS then the reasoning for the difference between cripple vs cancel is as follows. Suppose the player started a hack with one fleet, then realized they picked the wrong fleet and cancelled the hack, we don't want to penalize the player for that. It's an easy mistake/misclick to make. If however the AI has crippled your flagship then you are penalized because the AI got the advantage against you. If the AI does stuff to you then you have to take the consequences. There was a bug where we weren't correctly filling in the Hacking Event Log fields after cancelling an ARS hack and I've fixed that. |
|
|
Sorry, I was not aware of different logic for different structure; IIRC what I wrote is related to fleet extender (double capacity of fleet line) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Nov 18, 2019 3:35 pm | alocritani | New Issue | |
| Nov 18, 2019 4:11 pm | BadgerBadger | Assigned To | => BadgerBadger |
| Nov 18, 2019 4:11 pm | BadgerBadger | Status | new => resolved |
| Nov 18, 2019 4:11 pm | BadgerBadger | Resolution | open => fixed |
| Nov 18, 2019 4:11 pm | BadgerBadger | Fixed in Version | => 1.010 Extracting Those Archives |
| Nov 18, 2019 4:11 pm | BadgerBadger | Note Added: 0054626 | |
| Nov 18, 2019 4:55 pm | alocritani | Note Added: 0054627 |
