View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0023666 | AI War 2 | Balance Issue | Sep 7, 2020 7:51 pm | Sep 7, 2020 11:39 pm | |
| Reporter | ParadoxSong | Assigned To | |||
| Status | new | Resolution | open | ||
| Product Version | Beta 2.133 Hotfixes | ||||
| Summary | 0023666: Manually cancelling a hack: The worst of both worlds? | ||||
| Description | I asked around before posting this, but this is posted under the assumption if the hacking flagship is crippled, you do not lose your hacking points. I originally had quite the essay to write here, but I'd just like to point out that the dilemma of letting your ship get crippled to save some of your limited resource (hacking points) vs cancelling the hack to save some response forces from spawning is, uh, not really much of one. The punishment for cancelling is just too great. If you agree, changing manual cancellations to do any of: A) Not prevent re-attempting the hack (but still eating your hacking points) B) Continuing to release the regularly ordained response forces, but reimburse your points (and prevent re-attempts) C) Reimbursing your hacking points, but, still counting said points as "spent" for purposes of increasing AI Response D) Default behaviour, but returning a portion of your spent hacking points, what portion, I can't speak to. Or, something else! I just don't feel like manually cancelling a hack is a legitimate call unless your homeworld is for sure gonna die if you don't cancel, flagships aren't exactly expensive to rebuild, but hacking points are forever. | ||||
| Tags | No tags attached. | ||||
|
|
FWIW you lose the hacking points even if the hacking flagship gets crippled. The basic idea is hacking is a risk and failing it has consequences. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Sep 7, 2020 7:51 pm | ParadoxSong | New Issue | |
| Sep 7, 2020 11:39 pm | Strategic Sage | Note Added: 0058400 |
