Map Versioning

posted on May 2nd, 2010, 11:14 am

Hmm .... I guess I see your point there.  I just assume it's because I've seen the errors in the first version and correct them for future versions.


  Maps seem generally to be a little different than patches, persay, as a simple error in pathing, nebula placement, or some other such thing is not usually the kind of thing people generally know about unless they pay very close attention to the forums .

 
    I dunno.  Seems not to be a HUGE issue, but also there seems to not be quite such an easy answer .

posted on May 2nd, 2010, 5:24 pm

You can already do this

Ex: Countermeasures_002

posted on May 2nd, 2010, 6:09 pm

I guess it really coming down to two types of updating. Most of my updates tend to be tweaks or bug fixes so it makes no sense to, lets say, use Sigma Draconis 1.0 when 1.2 is essentially the same by design but minus any identified bugs. However, if I should release a significantly different Sigma Draconis 2.0 then I could keep 1.2 active just in case folks like that one more 

So in terms of map naming, I'll revise my proposed convention and say;

1. Any significant new release should be versioned appropriately (e.g. "1.0" or "I" etc...).
a. The txt, bmp and bzn files for any given map should be constant between versions, if the update contains bug fixes and minor adjustments, so that any new versions will simply over write it.
b. If the newer version contains significant design changes, which affect the way the map is played, then it should be rebranded/versioned appropriately (e.g. "2.0" or "II" etc...). The bzn/txt/bmp files should be renamed according to create an entirely new map entry.



Lol, before you know it, we'll have a book called The Rules of Aqu.... ahem "Guidelines for Map Making" (wait... we already do !)

posted on May 2nd, 2010, 6:15 pm

You can already do this

Ex: Countermeasures_002

  Read the whole thread you tit. 

posted on May 2nd, 2010, 10:21 pm

The one problem with versioning with numbers etc is that sometimes it isn't actually a separate version. Maybe use parentheses to indicate versions, i.e. Malta II (v2)

posted on May 2nd, 2010, 10:47 pm

Aye that could work too, for those that have gone with alternative version methods and could come under rule 1 as another sub-rule.

1. Any significant new release should be versioned appropriately (e.g. "1.0" or "I" etc...).
a. The txt/bmp/bzn files for any given map should be constant between versions, if the update contains bug fixes and minor adjustments, so that any new versions will simply over write it.
b. If the newer version contains significant design changes, which affect the way the map is played, then it should be rebranded/versioned appropriately (e.g. "2.0" or "II" etc...). The bzn/txt/bmp files should be renamed according to create an entirely new map entry.
c. Any bug fixes to a particular version should be shown as a sub-version of an overall release (i.e. 1.0 -> 1.1 - 1.2 etc... or I (v1), I (v2), I (v3) etc)

posted on May 12th, 2010, 5:55 pm

I see no proper way of avoiding that some idiot creates a fake map version 10.0 that overwrites the legit maps. another problem may be that armada doesn't have a way to compare map checksums between clients. i fear that map versioning will be impossible. i'll keep that in mind however when working on the bzn format the next time and see if anything can be done.

posted on May 12th, 2010, 5:59 pm

One thing I wonder is what if someone forgot to update the map version?

[Canny]

posted on May 12th, 2010, 6:49 pm

Last edited by Canny on May 13th, 2010, 7:40 pm, edited 1 time in total.

Need a way to version maps and download appropriately.

I.e. I host using
Player 1 joins has  
Player 2 joins has


I and Player two need to download Map v.3.

i was thinking of adding a version map list to the map pack, but replaced it with players in brackets in the text file. i am now gonna add the version number.

currently the version based on the modification level.
Cells V1.0
Briar Patch V1.0
Point Blank Range v1.2
The Triad of Evil v2.1
Where Eagles Dare V1.7 (Updated)

planning another few maps 'Dizzy', 'A Drift' and 'Lazy Turbine'. this version thing will be added. i can think of a few ways to make sure the files are versioned, but i would need to check to make sure.