It's 1.20 not 1.2

[Khazar]

Well isn't this a stupid thing to argue about.

im with you.

[Tsukino]

Its obvious that they are proper decimals which is why it has been 1.15, 1.16, 1.17, 1.18, 1.9, 1.20, 1.21 etc etc, some people do refer to them and 1.5, 1.6, 1.7, 1.8 and 1.9, but if they followed that logic, we would be on v2 now.

1.20=1.2, 1.12 (although it didnt exsist) =/= 1.2 its not rocket science.

Wrong. I'll try and elaborate on my previous post.

There are two basic systems, one where there are decimals and one where there are two (or more) numbers separated with a dot.

Decimal: 1.00, 1.01, 1.02, 1.03, 1.04, 1.05, 1.06, 1.07, 1.08, 1.09, 1.10, 1.11, 1.12, 1.13, 1.14, 1.15, 1.16, 1.17, 1.18, 1.19, 1.20, 1.21, ...

Non-decimal: 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 1.10, 1.11, 1.12, 1.13, 1.14, 1.15, 1.16, 1.17, 1.18, 1.19, 1.20, 1.21, ...

Notice how from 1.10 onward they look the same, but the patterns are not. Since we started with 1.15 (1.15a to be exact) there's no way to tell what system they're using until we start getting version updates after 2.0 (in which case we'll see the pattern prior to 2.10) or someone from the team tells us what system they use.

Also theoretically once you hit 1.99 with decimals you must roll over to 2.0, while with non-decimals you can just continue to 1.100, though 100 revisions to a version without updating the first number would be very rare. Of course there are other variant systems too, with multiple dot separators, whole numbers only, or just dates, rather than these types of version numbers, they just obviously don't apply to FFXIV.

Their usage of both 1.20 and 2.0 do suggest that they use the non-decimal system, because normally you would use 1.2 or 2.00, depending on how you truncate them (either you'd omit all trailing zeroes or always show them up to the place to which you plan revisions to be). It does not preclude them from using decimals though.

In before 100 more posts claiming "but 1.2 = 1.20!" and "no, software is always two separate numbers!" because no one reads anyone else's posts or clicks on Wikipedia links explaining everything.

[Nahaara]

If you want I can create another thread about "OMG THIS IS NOT THE TIME TO CHARGE" or "I HAVE THIS GREAT IDEA". Your choice ;D

Touche

/10char

[Baxter]

Yoshi can you release jobs early? This is what happens when your playerbase has nothing else to do.

[Claire_Pendragon]

Seeing how 1.2 in a way never really happen due to them later switching over calling it "Patch" and not version update and calling it 1.15 and so on lol. But i think people just think it faster saying 1.9 is faster then saying 1.19 like how we say lol but w/e it all the same thing to me

1.9 does not equal 1.19.
1.9 = 1.90

since they use 1.19a i would assume it is not 19th patch, but 19.5% into 2.0. (A, b, c etc...)
but as mentioned, until 1.20 or 1.2, we won't know for sure.

but also to mention, you do NOT have to go from 1.99 to 2.0.
you can still go to 1.991 1.992 1.993 etc...

[Alhanelem]

1.02 happened. If you knew decimals, you'd know that


Unless, of course, I'm a total idiot and somehow it's not decimals and for some reason 1.10 came after 1.9, and not 1.09...

The thing is, it's not a decimal number. The dot is a period, not a decimal point, and is intended to separate primary version from sub-version.

Many developers even use a four tiered system, e.g. 1.0.1.2 . This is not one number. it's four numbers. But even in a two tier system, the #.# is not a decimal number, it's two numbers separated by a dot/period.

Everyone has their own methodology when it comes to versioning, but usually the first number represents the major version. an increase of this number is usually a major software overhaul or otherwise includes many entirely new software components. Each number following the first one represents a rmore minor update than the one before it. In the four tier system, the second number, in the context of games, might mean a notable content update and/or a large compilation of fixes. the third/fourth numbers if present usually represent major (visible to users) and minor bugfixes (behind the scenes stuff usually), respectively.

Note that this is just one common interpretation and every developer adapts a versioning system to their own personal tastes.

Some developers simply use the build number, e.g. build 1264- This literally means that the current version is the 1264th time the software was built/compiled.

[Keith_Dragoon]

Isn't this a silly thing to argue about? >.>

Since this topic is silly, you must tell me who made your sig! >_>;

[Kailea_Nagisa]

Yoshi can you release jobs early? This is what happens when your playerbase has nothing else to do.

did I miss the memo? are all other games on the planet destroyed? Last I checked other games existed....*looks over at his NES collection* yeah I see some right here, oh and there are my PSX games too, yeah other games DO exist ;p

[Answa]

The thing is, it's not a decimal number. The dot is a period, not a decimal point, and is intended to separate primary version from sub-version.

Many developers even use a four tiered system, e.g. 1.0.1.2 . This is not one number. it's four numbers. But even in a two tier system, the #.# is not a decimal number, it's two numbers separated by a dot/period.

Everyone has their own methodology when it comes to versioning, but usually the first number represents the major version. an increase of this number is usually a major software overhaul or otherwise includes many entirely new software components. Each number following the first one represents a rmore minor update than the one before it. In the four tier system, the second number, in the context of games, might mean a notable content update and/or a large compilation of fixes. the third/fourth numbers if present usually represent major (visible to users) and minor bugfixes (behind the scenes stuff usually), respectively.

Note that this is just one common interpretation and every developer adapts a versioning system to their own personal tastes.

Some developers simply use the build number, e.g. build 1264- This literally means that the current version is the 1264th time the software was built/compiled.

Which is precisely the subject I left open in the end. I don't that SE handles these as 1.2, 1.3, 1.4, 1.5, ... 1.9, 1.10, 1.11. Regardless, that's how I think about these version numbers, because it's how my brain works.

[normalforce]

1.9 does not equal 1.19.
1.9 = 1.90

since they use 1.19a i would assume it is not 19th patch, but 19.5% into 2.0. (A, b, c etc...)
but as mentioned, until 1.20 or 1.2, we won't know for sure.

but also to mention, you do NOT have to go from 1.99 to 2.0.
you can still go to 1.991 1.992 1.993 etc...

Actually, it would go 1.99, 1.100, 1.101, etc.