Author Topic: Version control  (Read 1133 times)

0 Members and 1 Guest are viewing this topic.

Offline WMCoolmon

  • Purveyor of space crack
  • 213
Something that's been in the back of my mind for awhile - the FSSCP should add version identifiers to the files used for different versions of fs2_open.
For example, the whole fiasco with the ship trails; the problem is, to maintain backwards compatibility the value cannot simply be on or off. They have to be on, off, or undefined in order to support backwards compatibility-whenever nebulas are enabled in FS2, so are ship trails.
Adding a version identifier would fix this; if the identifier were present and noted that the file was designed for that version of fs2_open, fs2_open would run the file with all the changes/additions in that version of fs2_open.
If the version field was less than the version of fs2_open, fs2_open could display a warning and/or attempt to emulate that version.
If the version field wasn't present, fs2_open would assume it was a file for the original FS2 and run it as such.
-C