Welcome to the Forum Archive!

Years of conversation fill a ton of digital pages, and we've kept all of it accessible to browse or copy over. Whether you're looking for reveal articles for older champions, or the first time that Rammus rolled into an "OK" thread, or anything in between, you can find it here. When you're finished, check out the boards to join in the latest League of Legends discussions.

GO TO BOARDS


Why did the version number change to 3.5?

12
Comment below rating threshold, click here to show it.

Riot Natural20

Senior Release Manager

03-21-2013

Hey all! You will see this with the PBE deploy scheduled for later today.

UPDATE:
After some more discussion, we have decided to go with 3.5 instead. It achieves the same goal of removing the leading zero, while preserving our numbering system which will tell you that we are on the 5th release of Season 3.

That's it though. We're done!


What happened?
3.05 has been renumbered to 3.5. Subsequent releases will also be renumbered (3.6, 3.7, etc).

Why?
We changed the version number at the start of season 3 to have the leading zero in the second position (3.01). Turns out that we are now running into lots of different systems in our code that have to deal with the leading 0, and they do not handle this well. This was starting to cause some major issues for upcoming tech and rather than fix all the different systems and potentially run into this issue over and over again, we'll just increment the version.

How does this affect me?
It does not!
But we wanted to let you know why it was changing, and it is a visible change so we thought players would be curious.

-Riot Natural20


Comment below rating threshold, click here to show it.

NotoriousBLT

Senior Member

03-21-2013

That's just how Natural20 rolls.


Comment below rating threshold, click here to show it.

Zerglinator

Senior Member

03-21-2013

It was a Mega Zero.


Comment below rating threshold, click here to show it.

Sir Azural

Senior Member

03-21-2013

Thanks for the heads up! There would have been a lot of people asking about the major change in the version number.


Comment below rating threshold, click here to show it.

Fulgulet

Senior Member

03-21-2013

Good to know that.


Comment below rating threshold, click here to show it.

Fulgulet

Senior Member

03-21-2013

Quote:
Lord Azural:
Thanks for the heads up! There would have been a lot of people asking about the major change in the version number.


I like the irony in this

Good to know the news anyway.


Comment below rating threshold, click here to show it.

Goth Skunk

Senior Member

03-21-2013

Quote:
Riot Natural20:
Hey all! You will see this with the PBE deploy scheduled for later today.

What happened?
3.05 has been renumbered to 3.15. Subsequent releases will also be renumbered (3.16, 3.17, etc).

Why?
We changed the version number at the start of season 3 to have the leading zero in the second position (3.01). Turns out that we are now running into lots of different systems in our code that have to deal with the leading 0, and they do not handle this well. This was starting to cause some major issues for upcoming tech and rather than fix all the different systems and potentially run into this issue over and over again, we'll just increment the version.

How does this affect me?
It does not!
But we wanted to let you know why it was changing, and it is a visible change so we thought players would be curious.

-Riot Natural20


But but but...

Now we can't have version Pi... D:


Comment below rating threshold, click here to show it.

RichardMcNixon

Senior Member

03-21-2013

Welcome to the Future

All 327 champions will be unlocked for players.

Introducing Poro-Racing Queues

Karma's Re-Re-Launch is ready for testing

RP costs now displayed in Pesos to reflect current economic standards


Comment below rating threshold, click here to show it.

Nexus Crawler

Senior Member

03-21-2013

Quote:
Grimmgore:
That's just how Natural20 rolls.


Shen'ed.

Thanks for letting us know.


Comment below rating threshold, click here to show it.

Otrova

Junior Member

03-21-2013

Wish you luck in coming up with a more robust solution to this issue. This sounds like a bit of a hack fix.


12