#HOW TO CHECK A GAMES VERSION CODE#

1.0 will typically be the gold master, and patches will start from there: 1.1, 1.2. That said, the scheme you mentioned is quite common for released games. The most important thing is not the actual convention, but the fact that everyone sticks to it. Practice will vary depending on companies, teams and projects: there is no such thing as a best practice. If you make lists of the features that will need to be implemented before each increment, you'll also have a plan to follow, but in the end it's your decision as to what fits into each category.ДЄs far as I know, there is no standard for that. For example, if you're incrementing the minor build number, the revision and package both reset to 0.Д®ven though the categories are defined, there's still ambiguity for what kind of features actually cross over between a revision and a minor build number.

#HOW TO CHECK A GAMES VERSION CODE#

Package: Your code stays the same, external library changes or asset file update.Д¬ombined changes roll over to the most significant change. Revision: Minor alterations on existing features, small bug fixes, etc. Minor build number: Used for feature updates, large bug fixes etc. Major build number: This indicates a major milestone in the game, increment this when going from beta to release, from release to major updates. I worked for a company that essentially broke it down like this: There is no standard, but you should do it in a way that makes sense to you and contains all the information you may need to track that build.

How to check a games version