What would they do after 1.9? Would they go to 2.0? (But that might be weird because people will think its a 2nd minecraft), or will they go back to 1.0 and add something to the version (like how before it was beta and alpha).
(Those of you with minecraft 16.5 are probably laughing at me right now >_<)
What would they do after 1.9? Would they go to 2.0? (But that might be weird because people will think its a 2nd minecraft), or will they go back to 1.0 and add something to the version (like how before it was beta and alpha).
Yeah but they called it official realese so whats next?
Rollback Post to RevisionRollBack
Error 129583651: Central brain overheat while trying to think of funny signature for the Minecraft forums.
I'm guessing it will be 2.0 because in the April Fools thing they said "2.0 fianally coming" or something like that. Of corse that was all a joke though, so I can't be sure.
If the sales keep up, it'll be 1.10.0 (or 10.0). If the sales fall, however, They may stop updating and keep working on Scrolls or 0x10c; even if they're at 7.0 or whatever the wjhdf.
If they stopped updating they would shoot themselves in the foot. A game like Minecraft relies on updates, as Tekkit has proven. If it gets stuck on one version for too long, the player base stagnates and people move away.
Example: Technic stopped updating their packs for a long while, people drifted away to FTB.
That's what the Plugin API would be for. People would still be able to easily make mods with a supported system if Mojang stops releasing official updates.
1.91 - 1.99
Then when it is time for 2.0 again they will go to 1.991
And will soon grow to 1.9999999999999999999999999999999999999991.
There will never be a 2.0.
(But for real)
I think that Kholdstare is right, It will most likely go to 1.10 unless MoJang decides to rewrite the code which will most likely not happen.
What would they do after 1.9? Would they go to 2.0? (But that might be weird because people will think its a 2nd minecraft), or will they go back to 1.0 and add something to the version (like how before it was beta and alpha).
(Those of you with minecraft 16.5 are probably laughing at me right now >_<)
they'll probaly make some other gay crap like scrolls or such
In my opinion, it would be best to move to 2.0.0 along with the implementation of the complete mod API, because, as modifications aren't technically supported, implementing it technically adds a huge new facet to the game, technically.
In my opinion, it would be best to move to 2.0.0 along with the implementation of the complete mod API, because, as modifications aren't technically supported, implementing it technically adds a huge new facet to the game, technically.
There is an argument to be made that implementing the Workbench Plugin API and moving all vanilla content to resource pack plugins would be significant enough to call a 2.0.0 version. But then again all it took to move to Beta was server-side inventory, so...
(Those of you with minecraft 16.5 are probably laughing at me right now >_<)
Yeah but they called it official realese so whats next?
Program versions don't follow the rules of decimals, y'know.
Ever get tired of squids? Support dolphins in Minecraft!
That's what the Plugin API would be for. People would still be able to easily make mods with a supported system if Mojang stops releasing official updates.
Going along a Hexadecimal system would be pretty cool, but also confuse a lot of people... Unfortunately, in all likelihood it will be 1.10.0.
Then when it is time for 2.0 again they will go to 1.991
And will soon grow to 1.9999999999999999999999999999999999999991.
There will never be a 2.0.
(But for real)
I think that Kholdstare is right, It will most likely go to 1.10 unless MoJang decides to rewrite the code which will most likely not happen.
In my opinion, it would be best to move to 2.0.0 along with the implementation of the complete mod API, because, as modifications aren't technically supported, implementing it technically adds a huge new facet to the game, technically.
There is an argument to be made that implementing the Workbench Plugin API and moving all vanilla content to resource pack plugins would be significant enough to call a 2.0.0 version. But then again all it took to move to Beta was server-side inventory, so...