I have seen some maps with version numbers such as v1.72, however when I update my map that is above version 1.0 it only goes up in 0.1 increments. How do people get the version to go up in 100ths after 1.0?
Also, I have uploaded the map to both NA and SEA for testing, but on SEA I accidentally selected major revision the first time, so now my version numbers are WAY out of sync and the patch notes are out of sync with the SEA version. Is there anyway to reset my version number or is it forever screwed? I guess I could publish the NA one multiple times to catch up but I don't want it to have a rediculously high version number.
Minor and major revision numbers are independent of each other (0.1, 0.2, 0.3 ... 0.9, 0.10, 0.11, ... 0.99, 0.100, 0.101 ...)
And yes, there is no way to revert map back. I remember blizz dev saying that version numbers are more than a visual aesthetic and are used for various other things, so allowing to change them at will wouldn't be so simple.
How it went for me was it went from v1.0, to 1.1 -1.9, then it went to v1.10, v1.11, I suspect v1.100 will come next if I end up publishing that many new versions.
@DuckyTheDuck: Go@Deadzergling: Go
Oh that's cool, that means I wont have to go up to 2.0... but it'll still be annoying to sync the version numbers :)
I think how I'd handle it might be, to not give a rats ass about the version number syncing up until you are to the point of a release. Then you can simply major update both of them, have both start at 2.0, versions synced :)
Just write a map version into map details and map and screen and wherever and ignore the publishing version :)
Or just only update with major releases like to create "OVER v9000.0".
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I have seen some maps with version numbers such as v1.72, however when I update my map that is above version 1.0 it only goes up in 0.1 increments. How do people get the version to go up in 100ths after 1.0?
Also, I have uploaded the map to both NA and SEA for testing, but on SEA I accidentally selected major revision the first time, so now my version numbers are WAY out of sync and the patch notes are out of sync with the SEA version. Is there anyway to reset my version number or is it forever screwed? I guess I could publish the NA one multiple times to catch up but I don't want it to have a rediculously high version number.
Did you rename your map? check if the ratings are still there
Minor and major revision numbers are independent of each other (0.1, 0.2, 0.3 ... 0.9, 0.10, 0.11, ... 0.99, 0.100, 0.101 ...)
And yes, there is no way to revert map back. I remember blizz dev saying that version numbers are more than a visual aesthetic and are used for various other things, so allowing to change them at will wouldn't be so simple.
@DeltaV: Go
How it went for me was it went from v1.0, to 1.1 -1.9, then it went to v1.10, v1.11, I suspect v1.100 will come next if I end up publishing that many new versions.
@xxxDisturbedxxx: Go I don't want to rename it :D
@DuckyTheDuck: Go@Deadzergling: Go Oh that's cool, that means I wont have to go up to 2.0... but it'll still be annoying to sync the version numbers :)
@DeltaV: Go
I think how I'd handle it might be, to not give a rats ass about the version number syncing up until you are to the point of a release. Then you can simply major update both of them, have both start at 2.0, versions synced :)
Just write a map version into map details and map and screen and wherever and ignore the publishing version :)
Or just only update with major releases like to create "OVER v9000.0".