ID:259924
 
When you add your game to your hub you can only use a whole number. I usually update with decimals. My game is in 0.2 but it wont let me put that in so i had to make it 2, that would be a good idea.
Why do people even use decimals in the version number to begin with?
In response to EGUY
Some people think if it's just a minor fix, like typos or a tiny bug, they don't want to change the version number a whole number. It makes it look like a much bigger update. Lots of people do, including me.
In response to EGUY
A lot of people go with the major.minor[.revision[.build]] format for version numbering.
In response to Repiv
Repiv is right.

world
status="Version: [major].[minor].[revision]"


var/major=1
var/minor=2
var/revision=5


Thats the exact format I use.

~>Jiskuha
In response to Airjoe
I personally agree.

[major].[minor][build]

Major is updated if there is something BIG done.

Minor is updated if I reach a milestone with my builds, something recognizable enough as a new system, or an addition to the world that is more than just "new sword added!"

I only use build for bugs that shouldn't have made it into the game. For this, I tend to use letters.
This isn't likely to change any time soon, because it would require changing the hub protocol to handle version numbers other than integers. This would break all older versions of Dream Seeker in one fell swoop. Which is not a good thing. =)

What I would like to see is a custom "version" field, in which you can enter arbitrary text strings, that is displayed as the version number on the hub entry.

In the meantime, I've seen some people use the version numbering like this: [major][minor][revision]. There's no reason to restrict yourself to increasing version numbers sequentially. =)
In response to Crispy
Actually, you could have it like this format

[integar].[integar]

So that its 2 integar numbers with a . in the middle, allowing you to have like 1.8
In response to Strawgate
...also known as a double integer, which wouldn't be supported by older versions of BYOND. What you can do is, instead of versioning like 1.2b==>1.3, you can version like 010202==> 010300, simply ridding yourself of the double integer problem.
How is this even a problem? List whatever version number you want in the body of the hub entry and if necessary track your own specialized version number yourself in the game itself or what have you.
In response to tenkuu
It was added, YAY!

~>Jiskuha
In response to Jiskuha
Hey, cool. Thanks, whoever did that! =)