Extension versions

[george moromisato]

The mod itself will be marked as 1.0 in the xml which might be confusing, so perhaps we should change how we've been marking our mods?

I agreed with everything except this last bit. The mod should be marked as "1.1" in the XML so that players with version 1.0 don't try to load it.

Think of 1.05 as "beta 1.1" so the "1.1" version in the XML will be accepted in 1.05.

Sorry for the confusion. This just makes it easier for me to support mods.

[Prophet]

Yes, that was my point but re-reading it now it seems it was worded poorly.

Until now, we've been marking our xmls with the previous stable version and from now on we should be using the next stable version.

[george moromisato]

Yes, that was my point but re-reading it now it seems it was worded poorly.

Until now, we've been marking our xmls with the previous stable version and from now on we should be using the next stable version.

Yes--that's a better way of saying it.

[PKodon]

Thanks George and Prophet for clarifying this.

And, I agree with Prophet, as far as Xelerus goes, we need to keep distinguishing which beta a mod is targeted for.

Perhaps, too, if we have older versions of our mods that work with 1.01, they should remain on Xelerus, at least until 1.1 is released (such as DSF and VUI), and, if we release new version that uses functions from one of the betas, release that as a beta, as well, until 1.1 comes out (meaning there may be 2 versions of a mod on Xelerus, at the same time).

Otherwise we end up defeating the purpose of having a stable version: that new players can have fun in a relatively bug-free game, using whatever mods they wish to use.

So, everyone, don't go rushing out to delete the 1.0 version of your mods because you've got an updated version that only works with a beta.

PK

[alterecco]

I have just switched to a model where i keep my beta versions off of xelerus, and only upload the stable versions there. I find that gives me nice control over what is being exposed where.

Regarding the version number used on xelerus. It should be pretty straightforward. It represents the latest version of T that the mod works with. In many cases it has not been updated by the owner though, and there is not much we can do about that.

[PKodon]

Alterecco:

I don't know, to me, the version shown on Xelerus should be the EARLIEST version it will work with, if it uses features not available in earlier betas (that is, if it's written to use something introduced in 1.03, then that should be it's version, as anything before that would break it). Also, have there been functions which have become deprecated in later versions of Transcendence, and eventually no longer supported?

I know, some people wish old mods would go away, but, even if no longer usable in their current form, if one can get permission, it would be nice if some of those old mods were brought up to date by someone, even if it's not the original author.

PK