View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001458 | FSSCP | FRED | public | 2007-08-09 19:38 | 2007-08-17 23:33 |
| Reporter | Tolwyn | Assigned To | karajorma | ||
| Priority | normal | Severity | tweak | Reproducibility | N/A |
| Status | resolved | Resolution | no change required | ||
| Summary | 0001458: is-destroyed-delay & waves | ||||
| Description | I am not entirely sure whenever or not it is a bug. Anyways: If one or more waves do not arrive (because their origin, a carrier, is destroyed), should the is-destroyed-delay goal be satisfied? Because it is not now. I believe, that in earlier builds ships, that were going to launch, must be destroyed with their mothership. | ||||
| Tags | No tags attached. | ||||
| related to | 0001318 | resolved | Goober5000 | Wing destruction log entries should be more accurate |
|
|
It is only satisfied when all the waves that could arrive have been destroyed and that's the way it's been since retail. I understand why that seems counter-intuitive if the vessel they launch from is destroyed but what if that vessel departs instead? |
|
|
I believe, although I have not tested it, that using or is-destroyed-delay is-departed-delay should work. |
|
|
Should this be closed? It seems solved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2007-08-09 19:38 | Tolwyn | New Issue | |
| 2007-08-11 19:02 | karajorma | Note Added: 0008365 | |
| 2007-08-12 18:40 | Tolwyn | Note Added: 0008368 | |
| 2007-08-15 19:33 | Turey | Note Added: 0008382 | |
| 2007-08-17 23:33 | karajorma | Status | new => resolved |
| 2007-08-17 23:33 | karajorma | Resolution | open => no change required |
| 2007-08-17 23:33 | karajorma | Assigned To | => karajorma |
| 2007-08-31 08:46 | Goober5000 | Relationship added | related to 0001318 |
