View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001732 | FSSCP | FRED | public | 2008-07-22 06:41 | 2008-07-24 20:22 |
| Reporter | FUBAR-BDHR | Assigned To | karajorma | ||
| Priority | normal | Severity | trivial | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.6.9 | ||||
| Fixed in Version | 3.6.10 | ||||
| Summary | 0001732: Using guardian on a ship that is destroyed before a mission = crash | ||||
| Description | This is one of those that's so trivial I want to smack myself for reporting it but since someone did it (not me) figured it might be a good idea. If you use the ship-guardian sexp on a ship that is destroyed before the mission the game may crash at mission start and definitely will in debug mode. Looks like the ship-guardian sexp checks to see if the ship is destroyed, departed, or hasn't arrived yet but has no way of knowing a ship is destroyed before the mission. | ||||
| Additional Information | Original crash in TBP 3.6.9 but I made a test mission and confirmed in a recent 3.6.10 build. | ||||
| Tags | No tags attached. | ||||
|
2008-07-22 06:41
|
|
|
|
Fixed. It was a simply Int3() which shouldn't have been there since as we can see it is perfectly valid for the ship not be in-mission nor be on the parse arrival list. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2008-07-22 06:41 | FUBAR-BDHR | New Issue | |
| 2008-07-22 06:41 | FUBAR-BDHR | File Added: DBM_Guardian.fs2 | |
| 2008-07-24 18:31 | karajorma | Status | new => assigned |
| 2008-07-24 18:31 | karajorma | Assigned To | => karajorma |
| 2008-07-24 20:22 | karajorma | Status | assigned => resolved |
| 2008-07-24 20:22 | karajorma | Fixed in Version | => 3.6.10 |
| 2008-07-24 20:22 | karajorma | Resolution | open => fixed |
| 2008-07-24 20:22 | karajorma | Note Added: 0009494 |
