KSP version number in craft file

[Justin Kerbice]

Hi,

I've seen KSP add its own version number to craft file as follow:

ship = a_ship

version = 0.23.0

description

What the point of having a "binary style" version checking (craft_version=game_version => ok, else ko) ?

I've tried some crafts made with 0.23.5 on 0.23 and it's work, despite KSP don't want it.

A better version control + versioning itself could be use.

To keep thing as simple as possible, parts can include their first version appearance, example:

in 0.23.5: FL-T400 fuel tank can have version=0.7.3 (or 0.18, the last compatible version, ie 0.16)

and

Kerbodyne S3-3600 : version=0.23.5

So in 0.23.5, if I use just FL-T400 tank + some old parts, my craft can have

version=0.22 (assuming there is a part introduced the first time in KSP 0.22)

loading it in prior version of the game might work except for all < 0.22 (0.21 and older), which is fair.

With such system, which is very simple and reliable (as long as it's human mistake free, which can always happen), there is no need to edit craft files by hand "at our own risks" .

[sal_vager]

The number shows what version that craft was made in, KSP does a basic check as if it loads an old craft there can be issues with parts, if a craft can load though then all is good

A suggestion like this is something so minor though that I can honestly say you should not expect to see it implemented, there's just not enough to be gained and the change could render ALL previous craft files unusable.

That'd be bad.