By using this site, you agree to our Privacy Policy and our Terms of Use. Close
EpicRandy on 18 August 2023
Edit Thread
trasharmdsister12 said:
Ryuu96 said:

I don't really know if this means anything.

Does 1.1 usually indicate a launch version and anything after is bug fixing?

It depends on each team's nomenclature for how they update build #'s but typically 1.0 is what they'd assign to a "Gold" or release version. The first number behind the decimal would usually indicate a larger bug fix patch, while subsequent numbers behind decimals would track smaller and smaller fixes. Numbers behind decimals are also usually reset to 0 when a higher increment is added to a higher decimal placement (# further along the left). 

So looking at your examples, Fallout had 1 major bug fixes update for launch while Starfield has had 6 plus an additional 35 smaller fixes. 

Increasing the left-most number usually indicates a much larger feature addition and compilation of bug fixes and is often associated to big content releases or done in association with DLCs that come with major new features/QoL updates (ex. No Man's Sky is at version 4.13 and the version numbers are associated with certain bigger updates they've released). 

Pretty much this. Also, my guess for the rightmost number is that it may be reserved for hotfixes on a prod (not realistic in a video game because it will cause an insane level of downloads for client users) or a prod-ready (more realistic) version. Since up to this point no released version existed this number may simply have not been used at all. Now there's a release version (reviewers version) it's possible will see this number change from time to time but should be reset every time a new major/minor is released.

While a game is in full dev with no release version QA simply identifies from the dev build and logs any bugs they see and devs will simply create new minors for the fixes. But when there is a release version, as well as reviewing dev builds QA must also review in depth any version that has been identified for release (in this case) 1.6.35.0. Any bugs logged by QA while reviewing this version will be fixed through a hotfix (a branch of development that is created with the tagged-for-release version as source) which will increase the hotfix number (rightmost).

Another use of this number may simply be a build number or unique identifier for the build agent that performed the build, but I doubt those here since 0 would not be possible.

Edit: found this simplified image to illustrate what I'm talking about :

Last edited by EpicRandy - on 18 August 2023