[Sesquipedalian]

Probably this has been assumed by the people who will be organising/running the source code project, but spelling things our never hurt anyone, so here is my little thought

When the management team gets up and running, it might be an idea to release the "official" enhanced versions of the FS2 engine as patches with version numbers, so that whereas right now the standard version of FS2 is v1.20, new patched versions could be things like version 2.0 and 2.4 and so on.  Presumably later versions of "official" FS2 engine codes will be reverse-compatible with earlier ones.  Thus, it would be nice if one could release a campaign that made use of a modified FS2 engine and simply include a note saying "This campaign requires FreeSpace 2 version 2.1 or later," in something similar to the way games say that they require DirectX version whatever or later.

Who knows, perhaps we could get to host "official" patches on the server where the current patch (v1.20) is held.

[EdrickV]

If you mean patches as in auto-update stuff, I don't think that will happen. For our FS2 exes, there is no auto-update. And no launcher save the regular one. Different people are using different version numbers, but I personally think for the "official" group's version strings we should start with 1.30 and add a U on there to note it's an unofficial version. So the string would be 1.30 U and anyone who looks could tell the difference between it and a release, in case they ever do make a 1.30 release. Incidently, I'm intending to make a simplified launcher/setup program for use with a FS2 exe I have that uses a seperate registry key so I can have my settings for both of them be different. (May give that launcher program some options for dealing with multiple FS2 exes too.)

[Inquisitor]

Obviously, I also think the fully modified source should be available with every release as well.

Numbering scheme sounds sensible.

[DTP]

well i call mine DTP Version v 0.1 and 0.2 and so on.

That way ppl will know who build the dam thing + ppl can easely keep track of what # of release this version is until it hits version 1 that is supposed to be bug free.

Remember, it is unofficial fan made modifications, so by adding a name/nick to the version description this will clearly seperate it from anything else.

[EdrickV]

One thing to remember, there is not a lot of space for the actual version string. (The version string for the GCC one runs off the edge of the main hall screen.)

[penguin]

Originally posted by EdrickV
One thing to remember, there is not a lot of space for the actual version string. (The version string for the GCC one runs off the edge of the main hall screen.)

heh, so move it over... we can do that, we have the source

[EdrickV]

Move it over too far and it'll run into the tech room text, unless we completely change the version string's location. (Like moving it to the top of the screen.)

[DTP]

in the mainhall?. why not simply have it in the Pilot select screen?, like i have done it. The very first thing you run into if you dont use options like use last pilot.

I dont need ppl to know "I" build this, the beta hud text is only there because i dont want ppl to use it for campaigns yet.

But for testing theire respective mods so that they will have it ready when i release DTP version 1.0.

and so far I have had no bug reports.

[EdrickV]

There is a version string that displays in the lower right corner of the main hall. That was built into the exe and as that is now an established location for the version info, that's the logical place to note unofficial upgrades. (Notices elsewhere can be done, like you did with yours DTP, though they might not look well with some TCs.)

Edit: That version string, would be used for things like auto-udate, PXO, and maybe other forms of multi-player games.

[DTP]

IF TC`s have a problem with that Location they can simply mail me, and i will remove, relocate it or whatever.

Those words is put there because i fear that some day somebody would get theire hands on the thing and write a mail to Interplay OR volition about that theire game can't connect to parrallax online .