The new launcher also means that loading language packs is easier. Assets/lang, and drop a pack there. Ta-da. If only there were a "Show Language Pack Folder" option in languages...
So, something that I could have sworn I heard about in the past, and haven't heard a single word about since was the move from item/block ID numbers to a naming system, effectively removing ID limits and conflicts... Any news on that at all?
I'm very happy to hear about the new changes coming with the launcher! It will add a whole new depth of ease to running, modding and just overall fun. Even something like knowing what folders to place where can be daunting for new players, who want to step a little beyond total vanilla MC.
That is because there is still a lot of engine stuff to get done before they can even think about pushing out the API.
The past few full patches have had a lot of behind the scenes engine work being done, even the rewrite for redstone was a big step forward towards the API. This patch is another large step, with updated OpenGL, Java libraries and the version selector being major engine updates that needed to be done. The Java libraries in particular are important because those need to be pushed out first before Mojang is able to push the Rendering update they have been talking about since Minecon2012 (and is the last remaining thing in their way from pushing it out, if I remember correctly).
So why is all this engine stuff important to do before they start on the API? Well, lets say they stop what they are doing right now, held off 1.6, and worked their asses to push the API out as a stand alone update, and then went back to working on 1.6. Since there is still a lot of engine work that is being done and 1.6 includes a lot of engine work, if they pushed the 1.6 after the API, the API would break, and all mods and what have you that use the API would break, making the API kine of useless in regards to keeping mods and such from breaking with each update.
See, the engine needs to be in as perfect shape as possible and they need to open up core parts of the game as much as possible so that the API can hook into those components.
That is why the API is taking so long, they are getting the game, and more importantly, the engine, ready for an API to take advantage of it. There is no point pushing out an API that 1) Cannot access the game to its full potential and 2) Is built upon an engine that still needs a lot of major updates that would then break the API.
So, for myself, I am happy when they don't talk about the API, but push out engine related updates. Sure it is not as shiny as a new feature, but I know that it is an important step in getting the API out and that is what matters the most.
I'm aware of reasons behind its delay, but I believe it is very possible for them to complete the engine updates during snapshots and release the API after the engine is complete - all in 1.6.
I do too, but I have to wonder, isn’t this almost exactly like MultiMC (with the exception of the Forge button) thereby making it practically obsolete?
Does anyone know if it eliminates cracked minecraft servers?
Just pay for the goddamn game, . Think of it like this: If nobody payed for it, it wouldn't exist. By not paying for it, you are being selfish and ignorant by forcing others to support it for you instead of being responsible.
Just pay for the goddamn game, . Think of it like this: If nobody payed for it, it wouldn't exist. By not paying for it, you are being selfish and ignorant by forcing others to support it for you instead of being responsible.
Yea! It's not like there can be actual reason behind such acts.[sarcasm]
So basically modders yet again get the short end of the sword with yet another major mod breaking update. All this "new" and "ground breaking" luncher brings to me is yet another major rewrite to my mods. Every update requires small re-write, but the last few have required extensive rewrites. This seems like it will be even worse. Furthermore downloading the development luncher, it is currently impossible to edit the minecraft jar (all edits are overwritten)
We get promiced an API literally nearly 2 years ago and all we get is empty promises of an APi that will likely be inadequate for the majority of complex mods. Why do we continue to do this while majong treat us like second class citizens.
finally we have a ram setting, had to many mods once and had to run it with a batch file just so it woundnt crash from lack of memory, also, for the more advanced players will there be some kind of "folder" option, say save launcher1 in minecraft1 folder and launcher2 in minecraft2 folder, it would help for seperate world saving and the overall usefull ness if a modder wasrewrite the gui of the launcher or something like that (think aether mod launcher (yes it is updating))
Rollback Post to RevisionRollBack
If the cake is a lie........ does that mean if i build a house out of cake my house isn't real?
Your sense of style is pathetic , I always look to java programers for style , because where ever they are , they always have .class.
Pepridge farms does...
Good job Guys, the community has faith in ya!
MoK ^-^
That is because there is still a lot of engine stuff to get done before they can even think about pushing out the API.
The past few full patches have had a lot of behind the scenes engine work being done, even the rewrite for redstone was a big step forward towards the API. This patch is another large step, with updated OpenGL, Java libraries and the version selector being major engine updates that needed to be done. The Java libraries in particular are important because those need to be pushed out first before Mojang is able to push the Rendering update they have been talking about since Minecon2012 (and is the last remaining thing in their way from pushing it out, if I remember correctly).
So why is all this engine stuff important to do before they start on the API? Well, lets say they stop what they are doing right now, held off 1.6, and worked their asses to push the API out as a stand alone update, and then went back to working on 1.6. Since there is still a lot of engine work that is being done and 1.6 includes a lot of engine work, if they pushed the 1.6 after the API, the API would break, and all mods and what have you that use the API would break, making the API kine of useless in regards to keeping mods and such from breaking with each update.
See, the engine needs to be in as perfect shape as possible and they need to open up core parts of the game as much as possible so that the API can hook into those components.
That is why the API is taking so long, they are getting the game, and more importantly, the engine, ready for an API to take advantage of it. There is no point pushing out an API that 1) Cannot access the game to its full potential and 2) Is built upon an engine that still needs a lot of major updates that would then break the API.
So, for myself, I am happy when they don't talk about the API, but push out engine related updates. Sure it is not as shiny as a new feature, but I know that it is an important step in getting the API out and that is what matters the most.
I'm aware of reasons behind its delay, but I believe it is very possible for them to complete the engine updates during snapshots and release the API after the engine is complete - all in 1.6.
I hope so
I do too, but I have to wonder, isn’t this almost exactly like MultiMC (with the exception of the Forge button) thereby making it practically obsolete?
Just pay for the goddamn game, . Think of it like this: If nobody payed for it, it wouldn't exist. By not paying for it, you are being selfish and ignorant by forcing others to support it for you instead of being responsible.
Yea! It's not like there can be actual reason behind such acts.[sarcasm]
We get promiced an API literally nearly 2 years ago and all we get is empty promises of an APi that will likely be inadequate for the majority of complex mods. Why do we continue to do this while majong treat us like second class citizens.
Your sense of style is pathetic , I always look to java programers for style , because where ever they are , they always have .class.