- Sep 12, 2019
- 171
- 354
I swear your willingness to answer the same inane questions time and again impresses me more than your game.When a zero is added to the right of a one, it turns into a 10.
I swear your willingness to answer the same inane questions time and again impresses me more than your game.When a zero is added to the right of a one, it turns into a 10.
This quote is never not going to be relevant.We literally have the "versioning number" discussion a hundred times in every topic for every game.
At this point, some one needs to just list their game version as Ham Sandwich.Bacon.Cola just to really fuck with people.
Just ignore the decimal and just put a v.A bit confused about the numbering since the game version jumped from 0.9 to 0.1 (0.10 = 0.1)
Because they want to make 1.0 the "final" release. And 1.1 the bugfix on the final release.Just ignore the decimal and just put a v.
In other words, v9 -> v10.
No idea why so many devs seem to love the decimal if updates are not to be taken as a percentage of an already planned whole.
"planned"No idea why so many devs seem to love the decimal if updates are not to be taken as a percentage of an already planned whole.
In my line of work, I spend a lot of time planning what and how I'm going to do a project only to throw at least 90% of it out the window when I get there. The 10% I don't throw out is the part of the plan where I'll just have to make it up as I go."planned"
In my entire career as a dev, I don't think I've ever seen a planning hold up for more than a month.
Because it's an incredibly standard software versioning system. I mean, Warcraft III is up to v1.32.5. And using the version number as a percentage in decimal format requires a lot more planning than you probably think. In order for the version number to accurately match, you would need to plan out every single scene before your first release, then never change anything. Any form of revision or especially feature creep is going to throw it off, not to mention what happens if something unexpected happens during development and you can't do something you planned.No idea why so many devs seem to love the decimal if updates are not to be taken as a percentage of an already planned whole.
I think an easy way to think of it is that the actual "Version" of this game is v0. This means that v0.9 and v0.10 are updates to that version. When you add another decimal point (e.g., v0.9.2), that will usually indicate a patch/bugfix to that version/update.Because it's an incredibly standard software versioning system. I mean, Warcraft III is up to v1.32.5. And using the version number as a percentage in decimal format requires a lot more planning than you probably think. In order for the version number to accurately match, you would need to plan out every single scene before your first release, then never change anything. Any form of revision or especially feature creep is going to throw it off, not to mention what happens if something unexpected happens during development and you can't do something you planned.
Yeah, it is just that some of us expect version numbers to be 'real' numbers ...but they are not.I think an easy way to think of it is that the actual "Version" of this game is v0. This means that v0.9 and v0.10 are updates to that version. When you add another decimal point (e.g., v0.9.2), that will usually indicate a patch/bugfix to that version/update.
One way of looking at v0.9.2 (for example) would be:
Version: 0
Update: 9
Patch: 2
This also means that you can expect there will be a v0.10.1 at some point after v0.10 comes out.
I guess that I've been playing video games for so long (since Pong) that I've just gotten used to being able to interpret various version formats.Yeah, it is just that some of us expect version numbers to be 'real' numbers ...but they are not.
Autism and/or OCD can make our minds scream out when we see things that go against what we think they should be. Math/Numbers have rules, and version numbers ignore most of them.
The problem is you're applying the wrong rules.Yeah, it is just that some of us expect version numbers to be 'real' numbers ...but they are not.
Autism and/or OCD can make our minds scream out when we see things that go against what we think they should be. Math/Numbers have rules, and version numbers ignore most of them.
Version 0 means the product is incomplete.Just ignore the decimal and just put a v.
In other words, v9 -> v10.
No idea why so many devs seem to love the decimal if updates are not to be taken as a percentage of an already planned whole.
So you're saying I'm a dumbass? Them's fighting wordsIt's happening
TLDR: No, this is an alpha. What you see is 1 week's worth of development time.
Here's the definition of Alpha for you:
The "alpha phase" of software development follows the early programming and design stages, but precedes the "beta phase" in which the software closely resembles the final version.
Beta 1 adds at least 30 minutes of content for Lin alone.
The date system is great for something that doesn't have a defined end point but is out of beta, like operating systems. Linux just updates forever. Very much agree on the Android naming scheme being mostly useless. They're alphabetical, but the actual version number gives more information.Version 0 means the product is incomplete.
Version 1 means the product is complete.
Version 2 would mean the product was overhauled or revamped.
Devs tend to put thought into their numbering systems, believe it or not. Warcraft, League of Legends, Minecraft, just about every dev uses a style like this because it's incredibly easily readable.
How are you going to know if v8 of Harem Hotel isn't finished? All v8 points out to the average user is "8 updates." Nothing about how far along the game is, or how close it is to being finished, or when the update was released.
v0.8 clearly tells you this is not complete, but there have been 8 updates still.
v5.6.2020 tells you when the update was released, but not about if it's stable, or complete, or if this is the first test build someone has released.
vCupcake is stupid
Don't download v0.10. It's an incomplete alpha. It will most likely break your save and barely has any content anyway. There's a discussion about this all through the last few pages. Either grab v0.9.2 or wait until v0.10 is out of beta and has a public release.is there a compressed version for 0.10? 4.6gb on mega is too much to download...
Wait, wait. Are you claiming that there are public builds of .01 to .99 of Warcraft III somewhere out there? Surely you know that the earliest launch build is the 1.0 build, right? Obviously if the initial version represents the whole that means that the developer considered it a full game. That's what "1.0" means. It's whole. Anything below 1.0 is not whole and is the fractional percentage that the game state is at. e.g. .08 = 8/100 = 8% complete relative to the whole.Because it's an incredibly standard software versioning system. I mean, Warcraft III is up to v1.32.5. And using the version number as a percentage in decimal format requires a lot more planning than you probably think. In order for the version number to accurately match, you would need to plan out every single scene before your first release, then never change anything. Any form of revision or especially feature creep is going to throw it off, not to mention what happens if something unexpected happens during development and you can't do something you planned.
No, 0.08 does NOT mean 8% complete.Wait, wait. Are you claiming that there are public builds of .01 to .99 of Warcraft III somewhere out there? Surely you know that the earliest launch build is the 1.0 build, right? Obviously if the initial version represents the whole that means that the developer considered it a full game. That's what "1.0" means. It's whole. Anything below 1.0 is not whole and is the fractional percentage that the game state is at. e.g. .08 = 8/100 = 8% complete relative to the whole.