Staredit Network > Forums > SC1 UMS Mapmaking Assistance > Topic: When does it make sense to increment a map's major version?
When does it make sense to increment a map's major version?
Mar 24 2019, 2:03 pm
By: sethmachine  

Mar 24 2019, 2:03 pm sethmachine Post #1


I am going by the Semantic versioning as outlined here:

In short, versions are 3 numbers: MAJOR.MINOR.PATCH

E.g. "LostKingdoms-v1.13.15.scx" would be major version 1, minor version 13, patch version 15.

Starcraft map files are only consumed by players and do not have dependencies, e.g. a custom map never depends on other custom maps, unlike actual programming APIs, etc.

So when would you increment the major version of a Starcraft map?

Patch makes a lot of sense--you fixed a bug but otherwise added no new functionality to the map.
Minor is just adding new functionality without breaking existing functionality.

So maybe Major version is used when you fundamentally change triggers or how players used to do stuff.

For example, if I changed the cost of buying a unit by X amount, would this be a major version? Or really just a "balance" version (so maybe it should be MAJOR.MINOR.PATCH.BALANCE or something?). Technically changing costs is a breaking change, because it forces players to revise their strategies...

But, if I removed a spell from the game, or removed access to buildings/units/tech tree, maybe that's a MAJOR version?

But if I add a new spell/inventory system, but all other systems stay the same, wouldn't that be a MINOR version?

Let me know your thoughts.


Mar 25 2019, 1:35 am Dem0n Post #2

ᕕ( ᐛ )ᕗ

It's really all just preference. Most of the versions of maps out there don't make any sense. Personally, I'd do a minor increment for every update I do to the map, unless I completely change how the map plays, in which case I might do a major increment.

Mar 25 2019, 6:36 am NudeRaider Post #3

We can't explain the universe, just describe it; and we don't know whether our theories are true, we just know they're not wrong. >Harald Lesch

For small projects where I don't expect more than around a dozen versions, I just go with a single number.

For larger ones, the first is a major feature update where there is a learning curve because so much has changed.
2nd is a minor feature update that at most add a couple of things here and there.
Third is a bugfix release.

The latter seems pretty similar to the semantic versioning.

Removing just a spell/building/unit would be a minor version imo.

  Back to forum
Please log in to reply to this topic or to report it.
Members in this topic: None.
[11:29 am]
Christien Chapman -- I wish I could help
[11:29 am]
Christien Chapman -- Ok
[11:28 am]
Christien Chapman -- O
[08:03 pm]
No-Name-Needed-II -- If anyone who moderates this site is listening, I've been trying to recover my No-Name-Needed account but I've lost track of my email and pass word for it when my old computer crashed.
[04:25 pm]
Apos -- green
[03:03 pm]
lil-Inferno -- ya
[2020-7-07. : 1:15 am]
RdeRenato -- xd
[2020-7-07. : 12:35 am]
KrayZee -- Indigo
[2020-7-06. : 10:14 pm]
Christien Chapman -- Ok
[2020-7-06. : 10:14 pm]
Christien Chapman -- Pink
Please log in to shout.

Members Online: Roy, jun3hong, GGmano, miyuki292160, MTiger156