I'm not liking this at all. Mojang, when will you realize we just want actual mod support? Look at Magic Launcher, please. If players can do it, why can't you? Please just add a function to the launcher to add mods just like Magic Launcher does. Hell, ask the creator of Magic Launcher to help you with that new launcher of yours. Just, please, give us something to automatically let us add mods and remove mods.
Mojang is working on it. They know all you haters want the stupid mod API but you have to be patient. It won't just come flying out of Jebs butt like you thing it will.
No, however it will be potentially (depends on a lot of factors for jars that old and we don't have a testable version of this system yet) possible to switch between your modified 1.2.5 jar and vanilla 1.6 or any other modified jar you have without having to manually change the installs. You will be able to select it from the launcher's main menu.
Mod compatibility across versions will happen at a later point, but I doubt you would be able to backdate mods to jar's older than that point. So let us say hypothetically that the API comes out at version X.XX, mods updated to that point will be compatible with versions newer than X.XX but probably not mods older than X.XX. However this is a bit of a ways off still and has not much to do with the new client.
Okay, so just to be clear then: The new launcher does a similar thing with versions that MultiMC does with instances, allowing players to switch between versions of Minecraft that each have their own mods installed.
When the mod API comes out, it will grant mod compatibility across versions for the version it comes out for and updates that come out after that. So if it came out in 1.9, I would be able to use mods from 1.2.5 with 1.9 and later but probably wouldn't be able to use 1.9 mods with 1.2.5 or any other versions that came out before 1.9. Right? I still don't fully understand what exactly the modding API is or what it will do. Some people make it sound like it won't change anything, while others make it sound like the end of mod incompatibilities forever.
Okay, so just to be clear then: The new launcher does a similar thing with versions that MultiMC does with instances, allowing players to switch between versions of Minecraft that each have their own mods installed.
When the mod API comes out, it will grant mod compatibility across versions for the version it comes out for and updates that come out after that. So if it came out in 1.9, I would be able to use mods from 1.2.5 with 1.9 and later but probably wouldn't be able to use 1.9 mods with 1.2.5 or any other versions that came out before 1.9. Right? I still don't fully understand what exactly the modding API is or what it will do. Some people make it sound like it won't change anything, while others make it sound like the end of mod incompatibilities forever.
You more or less have it right except for being able to use 1.2.5 mods in newer jars. If the API were to come out in 1.9, any mod that used the API would be compatible with versions after that point. So a mod using the API that came out with 2.0 would be usable with 1.9 in that case, or at least in theory (it depends on things like the mod using vanilla content after 1.9). However a 1.9 mod using the API would be compatible with 1.9, 2.0, 2.1, etc. The API just opens up the possibilityforbackwards compatibility, however that isn't the main point of the API and is more on the mod developers to make that work then it is Mojang. There is also major issues with 1.2.5 in particular since the 1.3 patch had major code refactoring, if the 1.2.5 mod wasn't updated for that refactoring, it wont work. Also all mods would have to be updated at least once to convert to the API.
What you will be able to do with the new client is decide if you want to play vanilla 1.6, or play a modified 1.2.5 jar. So basically it allows multiple instances of minecraft to be installed and selected through the launcher. This is similar I believe to what MultiMC and MagicLauncher does.
Part of what the API would allow is forward compatibility, where each time the game updates, mods should not break. So a mod made after the API should potentially always work with each new version of the game from that point.
As for what the API is and does, it is a set of tools that allows modders to more easily mod Minecraft by providing a way to interact with the game code. Right now modifying minecraft requires a lot of brute force and methods that Mojang would rather people not do, you also rely on things like MCP in order to get any kind of modding done.
People moan for the API a lot really not for the modding tools it will provide, but for the forward compatibility it will offer, which is a shame.
I'm unsure if I was able to make that more clear for you.
People moan for the API a lot really not for the modding tools it will provide, but for the forward compatibility it will offer, which is a shame.
I'd rather have the modding tools, if they're properly documented. It would make doing anything a heck of a lot simpler. Forge's setup is downright nonsensical, and this is coming from a guy who has known Java for quite some time...
Thanks for the help, EnzerDeLeo, I think I have a much better understanding of it all now.
As excited as I am for the mods not breaking with the mod API, I have to say I think it's even more exciting to think that it will make creating mods so much easier. Given what modders have already done without the API, I can only begin to imagine what we'll see once it's released.
A somewhat unrelated thought: I think it would help mod authors a lot if there was an officially added way to choose between different items to craft from one recipe. That way mods that happen to use the same recipe for different items wouldn't become incompatible. Not being familiar with the inner workings of Minecraft, I have no idea how possible this is, but I think it's something worth considering.
I hope they will have a nifty folder to hold our beta jars in like the mods or better yet, have the jars included for those who did'nt back em up in the past. Would be nice to be able to get a unmodded 1.3 beta server up and running that anyone can join.
Rollback Post to RevisionRollBack
“By three methods we may learn wisdom: First, by reflection, which is noblest; Second, by imitation, which is easiest; and third by experience, which is the bitterest.” - Confucius
Thanks for answering these much wondered questions. Hopefully we will get the chance to see the mod api in 1.7.
Do you think they will come out with it on THAT update? They said it would be out so long ago. So I doubt it. Kinda sucks too that they were going to come out with it and never did.
Rollback Post to RevisionRollBack
Time to get back to the Classic times. A cake, with a saw inside of it.
Big Bam Bam, Bigaram Dip.
Not at all.
They didn't mention anything about a function for adding mods like Magic Launcher. I don't know what the heck this ''mod API'' is, and if it is what I'm talking about then seriously, why all the bullcrap about it not being added in earlier versions? The creators of magic launcher could easily just help them add a button to their new launcher that says ''Add Mods'' or ''Setup'', which would open up a new screen like in Magic Launcher that would let people choose if they want to run a different jar (say you have minecraft.jar and minecraftmodified.jar, you could pick one of them and do things with them, which I will explain now) and they could have a function to add a mod, boop, it would appear in the list, and you could remove it if you wanted to.. you know, just go download magic launcher, you'll see what I mean..
Mojang, please, ask help of the creators of magic launcher before releasing this new launcher.. please. We all want a really simple mod adding feature..
EDIT: Nevermind, apparently this mod api thingamajig is some backwards compatibility mod-feature and mod maker..? SCREW THAT! Why is NOBODY even BOTHERING to ask for a mod-adding feature instead? The mod api thing can go screw itself. I want my mod-adding feature. I don't give a single grain of sand about this because, like, I don't make mods, maybe? SERIOUSLY -,-
If you want a simple way of adding mods, just use Magic Launcher or MultiMC. The mod API will stop mods made with it (or updated with it, or however you want to put it) from breaking when Minecraft is updated, which is amazingly useful, and it will also make modding much easier which means more mods and better mods. Honestly, you sound like a spoiled child. Just because you don't care about something or don't understand what it is doesn't mean that everyone should drop what they're doing to do what you want instead. You're no more important than anyone else, and the mod adding feature that you're demanding is already present in Magic Launcher and MultiMC.
i know its kind of being selfish with the game but remember others are'nt as fortunate with money or relatives. think about it if a kid/teen was happy for the update and lost his only friends just to be alone again.
Do you think they will come out with it on THAT update? They said it would be out so long ago. So I doubt it. Kinda sucks too that they were going to come out with it and never did.
Well, the launcher means we are now just one step closer.
Rollback Post to RevisionRollBack
Enjoy raiding and pvp in highly customizable and well organized groups, but hate the setup of Factions? Then check out my upcoming server containing multiple custom plugins and opearting on Minecraft version 1.8!
After 2 year's I think everyone know that, never seen someone constipated for 2 years.
A new launcher is always to be remembered, because it's while working on a new launcher that we got the nice "One thing that kind of fell between chairs is the mod support." while for the 6 past month we were thinking ( because told so ) we would 'soon' get the source code, for free.
1) The mod api has not been in the works for 2 years. Notch came forth and gave a full open apology that it was never started. The engine work that had to be done before the API could be started has been an ongoing process for less than a year, starting with patch 1.3 in August 2012. The whole over two years bit is user hearsay that has been accepted as truth.
2) The launcher and features of the launcher are necessary for the API to work.
3) You were never told you would be getting the source code for free. It was something that Notch was thinking about, under a paid license, but it would be 1) A legal nightmare and 2) would be a bad option because it would not give you any of the benefit of an API, it would just take out MCP (which isn't a roadblock for modding as MCP updates after patches incredibly fast) from the modding equation. Mods would still break on updates, mods would still be inherently incompatible.
Not at all.
They didn't mention anything about a function for adding mods like Magic Launcher. I don't know what the heck this ''mod API'' is, and if it is what I'm talking about then seriously, why all the bullcrap about it not being added in earlier versions? The creators of magic launcher could easily just help them add a button to their new launcher that says ''Add Mods'' or ''Setup'', which would open up a new screen like in Magic Launcher that would let people choose if they want to run a different jar (say you have minecraft.jar and minecraftmodified.jar, you could pick one of them and do things with them, which I will explain now) and they could have a function to add a mod, boop, it would appear in the list, and you could remove it if you wanted to.. you know, just go download magic launcher, you'll see what I mean..
Mojang, please, ask help of the creators of magic launcher before releasing this new launcher.. please. We all want a really simple mod adding feature..
EDIT: Nevermind, apparently this mod api thingamajig is some backwards compatibility mod-feature and mod maker..? SCREW THAT! Why is NOBODY even BOTHERING to ask for a mod-adding feature instead? The mod api thing can go screw itself. I want my mod-adding feature. I don't give a single grain of sand about this because, like, I don't make mods, maybe? SERIOUSLY -,-
Are you dense? The launcher is adding a way to install mods via folders, they discuss this in the OP. At Minecon 2012 they discussed a mod repository where mods can be stored, browsed through by players through the game and installed on the fly, I would assume this works similar to the current version of GMod. The OP also goes into talks about allowing features so that mod developers can push updates to their mods to a repository and the game will detect if you are using an outdated mod and will ask if you would like to automatically update. The features you are complaining about have been discussed at length by the developers since the end of 2012, they are just now coming to the point where it will begin to be possible add those features as it requires a TON of behind the scenes changes. Mojang doesn't officially support third party modifications, do not get mad at them that installing third party modifications is not easy right now (again, they never intended people to modify the game, that is why everything keeps breaking, that is why people have to rely on legally gray things like MCP to mod), they are out of their own good will trying to make it easier to install third party modifications, but it takes time, calm down.
Secondly, the API is a tool that makes modding the game a hell of a lot easier than it currently is. As a side effect, the API will potentially make mods no longer break with each update as they will be using an officially supported feature to interact with the game, this is what mod developers want the most and the API is for mod developers. Again, calm down.
Good job reading into rumor mills, they've haven't given a time frame for when the API will be out in a long time now and have openly stated that they are working on fixes and rewrites to the game engine that are needed to be done before the API is out and you can see those changes yourself in each patch.
But no, go ahead and be angry.
disinformation
you are the type that be spreadin rumors, they stated it would be out soon and we all seen it, therefore mauled
you are the type that be spreadin rumors, they stated it would be out soon and we all seen it, therefore mauled
Except my information comes from Jeb and Dinnerbone's tweeter feed. And "out soon" is a vague term, it does not mean out now or within any defined amount of time. In fact, I believe that they have been saying that they are working towards the API, not "The API will be out soon". After their last "aiming to release in x patch" notice, they made an official apology, explained the situation in depth at Minecon and have stated that it will be done when it is done. You are merely looking for a reason to whine about something they don't have to implement.
Mojang is working on it. They know all you haters want the stupid mod API but you have to be patient. It won't just come flying out of Jebs butt like you thing it will.
Okay, so just to be clear then: The new launcher does a similar thing with versions that MultiMC does with instances, allowing players to switch between versions of Minecraft that each have their own mods installed.
When the mod API comes out, it will grant mod compatibility across versions for the version it comes out for and updates that come out after that. So if it came out in 1.9, I would be able to use mods from 1.2.5 with 1.9 and later but probably wouldn't be able to use 1.9 mods with 1.2.5 or any other versions that came out before 1.9. Right? I still don't fully understand what exactly the modding API is or what it will do. Some people make it sound like it won't change anything, while others make it sound like the end of mod incompatibilities forever.
You more or less have it right except for being able to use 1.2.5 mods in newer jars. If the API were to come out in 1.9, any mod that used the API would be compatible with versions after that point. So a mod using the API that came out with 2.0 would be usable with 1.9 in that case, or at least in theory (it depends on things like the mod using vanilla content after 1.9). However a 1.9 mod using the API would be compatible with 1.9, 2.0, 2.1, etc. The API just opens up the possibility for backwards compatibility, however that isn't the main point of the API and is more on the mod developers to make that work then it is Mojang. There is also major issues with 1.2.5 in particular since the 1.3 patch had major code refactoring, if the 1.2.5 mod wasn't updated for that refactoring, it wont work. Also all mods would have to be updated at least once to convert to the API.
What you will be able to do with the new client is decide if you want to play vanilla 1.6, or play a modified 1.2.5 jar. So basically it allows multiple instances of minecraft to be installed and selected through the launcher. This is similar I believe to what MultiMC and MagicLauncher does.
Part of what the API would allow is forward compatibility, where each time the game updates, mods should not break. So a mod made after the API should potentially always work with each new version of the game from that point.
As for what the API is and does, it is a set of tools that allows modders to more easily mod Minecraft by providing a way to interact with the game code. Right now modifying minecraft requires a lot of brute force and methods that Mojang would rather people not do, you also rely on things like MCP in order to get any kind of modding done.
People moan for the API a lot really not for the modding tools it will provide, but for the forward compatibility it will offer, which is a shame.
I'm unsure if I was able to make that more clear for you.
I'd rather have the modding tools, if they're properly documented. It would make doing anything a heck of a lot simpler. Forge's setup is downright nonsensical, and this is coming from a guy who has known Java for quite some time...
As excited as I am for the mods not breaking with the mod API, I have to say I think it's even more exciting to think that it will make creating mods so much easier. Given what modders have already done without the API, I can only begin to imagine what we'll see once it's released.
A somewhat unrelated thought: I think it would help mod authors a lot if there was an officially added way to choose between different items to craft from one recipe. That way mods that happen to use the same recipe for different items wouldn't become incompatible. Not being familiar with the inner workings of Minecraft, I have no idea how possible this is, but I think it's something worth considering.
And by the way, I only read the TL;DR section
Big Bam Bam, Bigaram Dip.
If you want a simple way of adding mods, just use Magic Launcher or MultiMC. The mod API will stop mods made with it (or updated with it, or however you want to put it) from breaking when Minecraft is updated, which is amazingly useful, and it will also make modding much easier which means more mods and better mods. Honestly, you sound like a spoiled child. Just because you don't care about something or don't understand what it is doesn't mean that everyone should drop what they're doing to do what you want instead. You're no more important than anyone else, and the mod adding feature that you're demanding is already present in Magic Launcher and MultiMC.
Well, the launcher means we are now just one step closer.
Enjoy raiding and pvp in highly customizable and well organized groups, but hate the setup of Factions? Then check out my upcoming server containing multiple custom plugins and opearting on Minecraft version 1.8!
Public alpha starting soon! Sign up today!
1) The mod api has not been in the works for 2 years. Notch came forth and gave a full open apology that it was never started. The engine work that had to be done before the API could be started has been an ongoing process for less than a year, starting with patch 1.3 in August 2012. The whole over two years bit is user hearsay that has been accepted as truth.
2) The launcher and features of the launcher are necessary for the API to work.
3) You were never told you would be getting the source code for free. It was something that Notch was thinking about, under a paid license, but it would be 1) A legal nightmare and 2) would be a bad option because it would not give you any of the benefit of an API, it would just take out MCP (which isn't a roadblock for modding as MCP updates after patches incredibly fast) from the modding equation. Mods would still break on updates, mods would still be inherently incompatible.
Are you dense? The launcher is adding a way to install mods via folders, they discuss this in the OP. At Minecon 2012 they discussed a mod repository where mods can be stored, browsed through by players through the game and installed on the fly, I would assume this works similar to the current version of GMod. The OP also goes into talks about allowing features so that mod developers can push updates to their mods to a repository and the game will detect if you are using an outdated mod and will ask if you would like to automatically update. The features you are complaining about have been discussed at length by the developers since the end of 2012, they are just now coming to the point where it will begin to be possible add those features as it requires a TON of behind the scenes changes. Mojang doesn't officially support third party modifications, do not get mad at them that installing third party modifications is not easy right now (again, they never intended people to modify the game, that is why everything keeps breaking, that is why people have to rely on legally gray things like MCP to mod), they are out of their own good will trying to make it easier to install third party modifications, but it takes time, calm down.
Secondly, the API is a tool that makes modding the game a hell of a lot easier than it currently is. As a side effect, the API will potentially make mods no longer break with each update as they will be using an officially supported feature to interact with the game, this is what mod developers want the most and the API is for mod developers. Again, calm down.
.......you have no idea what an API is for do you?
you are the type that be spreadin rumors, they stated it would be out soon and we all seen it, therefore mauled
Except my information comes from Jeb and Dinnerbone's tweeter feed. And "out soon" is a vague term, it does not mean out now or within any defined amount of time. In fact, I believe that they have been saying that they are working towards the API, not "The API will be out soon". After their last "aiming to release in x patch" notice, they made an official apology, explained the situation in depth at Minecon and have stated that it will be done when it is done. You are merely looking for a reason to whine about something they don't have to implement.
It means I'll just keep using Magic Launcher until everything else is implemented in the new 'official' launcher.
Clearly he does not.