A 0.36 version tag is a project in alpha. From around 0.6-0.8 depending on the project, a project becomes beta.
What you are saying here is that the version number acts as a progress bar for how completed the VN is. Never once in any VN, nor any other software ever, have I seen that, and I have legitimately no idea where you could ever find examples to back up stating that as if it is a common fact.
A version number should be plain and simple. It's a
unique identifier of that specific build of the game. It can be
You must be registered to see the links
, a timestamp, hash, build number, chapter, I don't care. As long as it's
unique, it's a usable version number. (It'd be much preferred if a version number always increased from one build to the next, but this isn't necessarily required.)
If the version acts as a progress bar, however, that means it can go forward and backward as the scope of the game/software changes.
Lets say a game is 20% completed, but the dev changes their plans and decides to add a lot more content. In that case, a game that was at v0.20 can then become v0.10 with the next update. The v0.10 update is still a newer version with more content, but since the number is lower, it'll appear that it's an older version of the game. (Worse yet if there was a previous v0.10!)
If, however, the dev used just about any other versioning system, there would be little, if any, confusion at what is the newest version of the game.