2020-09-28 18:30 EDT

View Issue Details Jump to Notes ] Related Changesets ]
IDProjectCategoryView StatusLast Update
0002319FSSCPFREDpublic2012-12-14 23:04
Assigned ToGoober5000 
Product Version3.6.13 
Target VersionFixed in Version 
Summary0002319: Alt names and callsign mission save issues.
DescriptionI notice this when looking at a test file for 2300. I added a null "" and blank " " callsign in the ship editor to see what would happen and test changing it. Well the ship editor just reset to <none> and I assumed that it wasn't legal. I did test changing to "" and " " for 2300 and that worked as designed. While looking at the file to make sure I noticed the following:

$Callsign: a3_orig
$Callsign: a4_orig
$Callsign: b1_orig
$Callsign: b2_orig
$Callsign: b3_orig

Doing some more testing I confirmed that even though the ship editor shows <none> if you change it to "" or " " it is actually still written to file. Same with alt names.

Further testing also showed that unused entries removed from all ships still write to the file as well. Only way to remove them is notepad.
TagsNo tags attached.
Attached Files




Goober5000 (administrator)

Fix committed to trunk@9433.

+Related Changesets

-Issue History
Date Modified Username Field Change
2010-10-04 18:43 FUBAR-BDHR New Issue
2012-11-27 01:48 Goober5000 Assigned To => Goober5000
2012-11-27 01:48 Goober5000 Status new => assigned
2012-12-14 23:04 Goober5000 Changeset attached => fs2open trunk r9433
2012-12-14 23:04 Goober5000 Note Added: 0014465
2012-12-14 23:04 Goober5000 Status assigned => resolved
2012-12-14 23:04 Goober5000 Resolution open => fixed
+Issue History