ID:190776
 
Would version 1.50 be 150, and 1.1 be 2? cause I don't understand that version system.
Every program really has it's own versioning system. Usually, very very major milestone versions raise the first number. Smaller updates, like bugfixes, raise the second number (or third, fourth, .... if you want to split it into many different sizes of updates).

-AbyssDragon
In response to AbyssDragon
A easy system to use is add:
-0.05 for a bug fix.
-0.1 for a new small feature.
-0.4 for a new system (Big).
-0.1 for a new map.
-0.1 for a new race/class/character.
-0.2 for a new quest.


Although you'll usually have to change some of that around depending on the importance of things like quests and races/class/character's.
-DogMan
In response to Dog Man
Well, you really should only increase any number by one. Any updates to a number cause all lower numbers to reset to zero. If you're doing a two tiered system, it would go like this:

First release: 0.1
Do some bug fixes: 0.2
Couple of new features: 0.3
Major upgrade: 1.0
Bug fixes: 1.1
More fixes: 1.2
New features: 1.3
Bug fixes: 1.4

etc..

It only serves to confuse people if the versioning system doesn't make sense. It's okay to have some versions that are never released, but don't jump from 1.2 to 1.5 in one step. This is especially important if you have multiple people working on development.

-AbyssDragon
In response to AbyssDragon
The main point is:

It can work out anyway you want it to work out.