Well in the very unlikely occurance which defently never happens, then you do a thing that is called roll back (by the power of github to reload the old version) or "Look, a three headed monkey!" and quickly do a patch for the patch strategy.
The standard is as follows: pre-Alpha → Alpha → Beta → Release Candidate → Release So all before (release) is 0.xxx.xxx. That means you are almost done with your game and you can name it 0.5 or 0.9. It all depends on you how low you want to go with number. It is a convention, but you can make your own up.
today I was interested in this question and here is the video! Fantastic!)
Oh, nice!
"So let's say you mess something up, which never happens to a software developer" *coughs whole lungs out*
Well in the very unlikely occurance which defently never happens, then you do a thing that is called roll back (by the power of github to reload the old version) or "Look, a three headed monkey!" and quickly do a patch for the patch strategy.
thanks now i understand what the numbers are for fully
Thanks i was wondering this!!!
Thanks for watching it!
Woah.. now it all makes sense but what if u only see tw[ numbers like 2.0?
Then it is the second final version after release. The first number is the most important one, rest numbers after the dot are internal for developer.
@@1upIndie oh okay, thank you!
What if it's like a beta game What version would it be?
The standard is as follows: pre-Alpha → Alpha → Beta → Release Candidate → Release
So all before (release) is 0.xxx.xxx. That means you are almost done with your game and you can name it 0.5 or 0.9. It all depends on you how low you want to go with number. It is a convention, but you can make your own up.
I don't like this
This is an industry standard and a guide how you can setup versions. You can use whatever you see fit and completly ignore it.
you could honestly just go “version “i.hate.life”
though most sites force you to use numerical characters