View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000947 | FSSCP | gameplay | public | 2006-06-15 00:01 | 2007-10-22 03:45 |
| Reporter | Goober5000 | Assigned To | WMCoolmon | ||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Summary | 0000947: Mission log gets screwed up when a ship departs | ||||
| Description | In lieu of 1000 words, check the attached screenshot. This is at the end of "A Flaming Sword". The mission log seems to behave normally until it receives a departure event, but then the departure events take over. (The old events are still there, just lost in the flood.) Also, the "departed" ships still appear on the escort list. | ||||
| Additional Information | I'm betting this has something to do with WMC's new limbo code. NB: It only happens on the main branch, not the 3.6.9 branch. | ||||
| Tags | No tags attached. | ||||
|
2006-06-15 00:03
|
|
|
|
I think I just fixed this, looks like I mistook a piece of code for being unused. Odd that it didn't have any major effect other than the mission log, though. |
|
|
The escort list doesn't count? It also affected, at least, the ai goals (goals weren't cleared) and the debriefing, so I'm guessing it was major. :p |
|
|
Looks to be fixed. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-06-15 00:01 | Goober5000 | New Issue | |
| 2006-06-15 00:03 | Goober5000 | File Added: log.jpg | |
| 2006-06-15 00:04 | Goober5000 | Description Updated | |
| 2006-06-15 00:30 | Goober5000 | Additional Information Updated | |
| 2006-06-15 03:42 | WMCoolmon | Note Added: 0005845 | |
| 2006-06-15 05:04 | Goober5000 | Note Added: 0005846 | |
| 2006-06-16 20:56 | Goober5000 | Note Added: 0005851 | |
| 2006-06-16 20:56 | Goober5000 | Status | assigned => resolved |
| 2007-10-22 03:45 | taylor | Resolution | open => fixed |