Ok I have spent a bit of time investigating the new luancher a bit more in hopes of finding out how much of a blow this will be to modders (which I probably should have done before originally posting).
I was able to get a modded 1.5.1 minecraft with forge as well as a mod working using the new launcher. So short answer not a whole lot. Getting a modded version of the game however required renaming/editing of a few files, but I assume majong will automate this better. Interestingly forge still dumps the "/mods" folder inside the ".minecraft" folder meaning that Forge at least isn't compartmentalising it as Mojong seems to would like. This really seems like the only thing Forge might need to change for the new luancher (which is actually quite trivial).
Right now there is really none of this separate jars for the engine and version that is talked about in the OP. Weather that is a bit of misinformation or something that is not implemented yet is anyone's guess. If it is not misinformation I can see many mods being crippled by it. If it says how it is however changes will be easy to adapt to.
I doubt they'll store it in the registry, but I'm not sure where exactly.
It is all stored in a .json file within the versions folders in .minecraft. Registry makes zero sense because minecraft is cross platform and the registry is not.
The only thing better would be to put my server automatically.
Rollback Post to RevisionRollBack
Jingo's Minecraft Server [Towny]
IP - join.jingomcs.com
Welcome. We use Towny for protection. The people and staff are what makes our community great. Be a part of it. Join!
Ok I have spent a bit of time investigating the new luancher a bit more in hopes of finding out how much of a blow this will be to modders (which I probably should have done before originally posting).
I was able to get a modded 1.5.1 minecraft with forge as well as a mod working using the new launcher. So short answer not a whole lot. Getting a modded version of the game however required renaming/editing of a few files, but I assume majong will automate this better. Interestingly forge still dumps the "/mods" folder inside the ".minecraft" folder meaning that Forge at least isn't compartmentalising it as Mojong seems to would like. This really seems like the only thing Forge might need to change for the new luancher (which is actually quite trivial).
Right now there is really none of this separate jars for the engine and version that is talked about in the OP. Weather that is a bit of misinformation or something that is not implemented yet is anyone's guess. If it is not misinformation I can see many mods being crippled by it. If it says how it is however changes will be easy to adapt to.
1. Learn to spell.
2. The engine and game being separate is part of the API they're working on, why the hell are you talking about it here like it's part of the launcher?
1. Learn to spell.
2. The engine and game being separate is part of the API they're working on, why the hell are you talking about it here like it's part of the launcher?
Ohh wow, I miss-spelled launcher, whoopy doo.
It specifically mentions that new versions will be compartmentalised (i.e. engine away from the versions)
Humm. All the new/proposed features seem to be a step in the right direction in terms of customization. Things like choosing install directory without batch file workarounds/third party clients should have been a thing from the start. At least, in my opinion.
Ok I have spent a bit of time investigating the new luancher a bit more in hopes of finding out how much of a blow this will be to modders (which I probably should have done before originally posting).
I was able to get a modded 1.5.1 minecraft with forge as well as a mod working using the new launcher. So short answer not a whole lot. Getting a modded version of the game however required renaming/editing of a few files, but I assume majong will automate this better. Interestingly forge still dumps the "/mods" folder inside the ".minecraft" folder meaning that Forge at least isn't compartmentalising it as Mojong seems to would like. This really seems like the only thing Forge might need to change for the new luancher (which is actually quite trivial).
Right now there is really none of this separate jars for the engine and version that is talked about in the OP. Weather that is a bit of misinformation or something that is not implemented yet is anyone's guess. If it is not misinformation I can see many mods being crippled by it. If it says how it is however changes will be easy to adapt to.
I understand your concerns, but I feel that modders/third party APIs will adapt to whatever changes are made somewhat easily. Particularly, all the eyes and ears on alert for these changes, on top of all the people who contribute, something would probably be whipped up rather quickly in terms of Forge. I do like that you're looking into things though.
Edit: Goodness. look at all the unparsed BBCode. o.O
Ok I have spent a bit of time investigating the new luancher a bit more in hopes of finding out how much of a blow this will be to modders (which I probably should have done before originally posting).
I was able to get a modded 1.5.1 minecraft with forge as well as a mod working using the new launcher. So short answer not a whole lot. Getting a modded version of the game however required renaming/editing of a few files, but I assume majong will automate this better. Interestingly forge still dumps the "/mods" folder inside the ".minecraft" folder meaning that Forge at least isn't compartmentalising it as Mojong seems to would like. This really seems like the only thing Forge might need to change for the new luancher (which is actually quite trivial).
Right now there is really none of this separate jars for the engine and version that is talked about in the OP. Weather that is a bit of misinformation or something that is not implemented yet is anyone's guess. If it is not misinformation I can see many mods being crippled by it. If it says how it is however changes will be easy to adapt to.
Yeah, seeing that the feature to select separate jars was added only last week, I am not too surprised that things are a little bumpy for getting a modified jar to work. Today is Thursday meaning we should be getting another snapshot, so who knows what new features will be pushed. The whole compartmentalizing to separate the engine and version sounds like something that is more in the works than something we will see immediately. While I wouldn't be surprised if that was a change made for 1.6, I also wouldn't doubt that there was a bit of misunderstand and that the whole version system was setting up ground work for such a change. From what we were told during Minecon 2012, the eventual goal is to have the game completely separated from the engine to the point where MC itself is a plugin.
http://www.pcmag.com/encyclopedia/term/37856/api
For anyone still confused about what an API is. Just substitute Minecraft for where they mention operating system, and mods for where they mention application. A perfect example of APIs are both DirectX and OpenGL, which let programmers easily interface the game engine with the gaming hardware.
As for me, I'm neither surprised nor upset about anything to do with the current state of Minecraft. Why? Because I'm not really playing it too much until it reaches the API state or even further along. I personally feel that it's still in beta, and Notch simply said it was a release version so he could move on.
Look at it this way, Notch is like Will Wright or Peter Molyneux. Yes he can code, but he's really more of the creative type who has grand visions and then tries to bring them to life. With everything considered he did a pretty good job bringing Minecraft to life. But that's where his major talent and vision lies. So he finally reached a point where coding Minecraft was both no longer fun, and beyond his ability, because in truth he quite likely codes in the manner of the first definition of "hacker" by the seat of his pants. Which is fine for small coding jobs, but can create a code monster when you do a big one. So that's where first Jeb stepped in and then he brought others on board to help move things along. But they still have to work with the code that Notch wrote, and I bet there's a lot in the way Notch did the original code that makes doing things like APIs hard if not impossible. But from what I can see they do have a goal of giving us what we were told we were going to get. Thing is it's going to take time getting the code monster under control before they can even start moving it forwards to the goal line.
In truth the only reason we're involved with the development of Minecraft is due to how it was first funded. And that's not a bad thing. We could instead of waited 3-5 years while all the development was done without us even knowing and then have the finished game handed to us for 50 bucks. Or we simple relax in the knowledge that it will get done... eventually. You can either play with it, or set it down and wait till it's more polished (like I'm doing), and you can either fool around modding it, or take a break. Choice is yours because it's going to be a bit, and there's nothing either you or I can do about it.
Yeah, seeing that the feature to select separate jars was added only last week, I am not too surprised that things are a little bumpy for getting a modified jar to work. Today is Thursday meaning we should be getting another snapshot, so who knows what new features will be pushed. The whole compartmentalizing to separate the engine and version sounds like something that is more in the works than something we will see immediately. While I wouldn't be surprised if that was a change made for 1.6, I also wouldn't doubt that there was a bit of misunderstand and that the whole version system was setting up ground work for such a change. From what we were told during Minecon 2012, the eventual goal is to have the game completely separated from the engine to the point where MC itself is a plugin.
I really don't mind the fiddling at the moment, I only did it to see if it would work. To tell you the truth I was actually quite surprised that it did. Although I guess in a way it does go to prove that having this functionality may not actually require so much work.
What keeps bugging me about the "engine split" is (coming from a modder's perspective now) what happens when something needs to be edited in the engine itself? Will that not destroy all the other "versions"? Sorry for bringing it back to the API, but we were told that the future modding API would allow us to edit "everything" (source) yet this engine/game spit seems to me that it would either make it more difficult, more prone to crashes and/or just more messy.
All in all, at the moment, I don't have any problems with the launcher (hell it makes playing minecraft on ubuntu less of a hassle) it will just be interesting to see exactly how this engine split thing will pan out.
I really don't mind the fiddling at the moment, I only did it to see if it would work. To tell you the truth I was actually quite surprised that it did. Although I guess in a way it does go to prove that having this functionality may not actually require so much work.
What keeps bugging me about the "engine split" is (coming from a modder's perspective now) what happens when something needs to be edited in the engine itself? Will that not destroy all the other "versions"? Sorry for bringing it back to the API, but we were told that the future modding API would allow us to edit "everything" (source) yet this engine/game spit seems to me that it would either make it more difficult, more prone to crashes and/or just more messy.
All in all, at the moment, I don't have any problems with the launcher (hell it makes playing minecraft on ubuntu less of a hassle) it will just be interesting to see exactly how this engine split thing will pan out.
I can see where your coming from with the mods argument on this but I feel that once everything is set and done and FTB and Technic get their stuff straightened out their launchers will resemble that of the new minecraft launcher with better mod and mod pack support, currently on FTB and Technic launchers you can add custom mods and modpacks with little to no fuss to the launcher or the client, and who knows Mojang does have a history of using other mods developers mods in full game maybe they are using the frame work of FTB and/or Technic's launcher for their own launcher. It's just a thought.
how does the new launcher cope with MCPatcher and randommobs?
Seeing that it is too early in development, who knows. The developers of those modifications will have to take a look at the launcher when ti gets closer to release and the launcher isn't in what is essentially an alpha state. That said, 1.6 does add a vanilla version of RandomMobs, the new horses take advantage of a similar system (though not as fleshed out as what you would see with MCpatcher's controls). Jeb stated that for now the system would be only taken advantage of by horses, but it is there.
Very excited for the option to choose what version you want to play! No more MCNostalgia so it will be much easier. Can't wait to play beta 1.7.3 or 1.6.5
If the new launcher allows for the changing of Minecraft versions easily, then can the alpha and beta jars of Minecraft be included? It would be nice to easily switch between old Minecraft version so that we can enjoy the older style of Minecraft. When I say alpha and beta Minecraft, I mean the original releases of them.
Okay, now THAT is interesting! There will be a special Minecraft Core to make it so the game's critical data that runs the game itself and a new folder called "Version" that will allow me to download mods according to what I really want to use at any time and when a Mod has updated, it'll automatically port the new version into the newest version of Minecraft! I'm willing to bet that the creators of Minecraft Forge are going to be thrilled when this gets released!
Plus, with this being the beginnings of what will become the brand new Mod API, I'm willing to bet that its production is beginning to show signs that it's about to become available within a few months or so! I'm SERIOUSLY looking forward to when it is finally available, but heck, I will NOT hesitate to update my Minecraft as soon as 1.6 becomes available, because then I'll be going absolutely CRAZY with it!
Rollback Post to RevisionRollBack
Come visit my Scroll on Dragon Cave here: My DC Scroll
Too Long; Didn't Read .. the full 8 pages. (Yes I do care about reading it all over a two or three day span of being at this page, gave me enough time to hear all the whiny, self-centered brats young ones. )
Now if only we could teach our young generations how to be respectful (see the ever annoying Call of Duty kids and such on YouTube... or just via the game itself. I heard that the XBox 360 is where most of them hang out) then we could have less bad apples ( ) everywhere.
EDIT: I'm for the step forward in Minecraft's coding design and content. It shall help me take my first leap into Java easier once I do so.
I doubt they'll store it in the registry, but I'm not sure where exactly.
I was able to get a modded 1.5.1 minecraft with forge as well as a mod working using the new launcher. So short answer not a whole lot. Getting a modded version of the game however required renaming/editing of a few files, but I assume majong will automate this better. Interestingly forge still dumps the "/mods" folder inside the ".minecraft" folder meaning that Forge at least isn't compartmentalising it as Mojong seems to would like. This really seems like the only thing Forge might need to change for the new luancher (which is actually quite trivial).
Right now there is really none of this separate jars for the engine and version that is talked about in the OP. Weather that is a bit of misinformation or something that is not implemented yet is anyone's guess. If it is not misinformation I can see many mods being crippled by it. If it says how it is however changes will be easy to adapt to.
It is all stored in a .json file within the versions folders in .minecraft. Registry makes zero sense because minecraft is cross platform and the registry is not.
IP - join.jingomcs.com
Welcome. We use Towny for protection. The people and staff are what makes our community great. Be a part of it. Join!
1. Learn to spell.
2. The engine and game being separate is part of the API they're working on, why the hell are you talking about it here like it's part of the launcher?
Please don't get on other members' case about their spelling/grammar. It's actually against our rules. See here, and scroll down to "Grammar Harrass".
I understand your concerns, but I feel that modders/third party APIs will adapt to whatever changes are made somewhat easily. Particularly, all the eyes and ears on alert for these changes, on top of all the people who contribute, something would probably be whipped up rather quickly in terms of Forge. I do like that you're looking into things though.
Edit: Goodness. look at all the unparsed BBCode. o.O
Yeah, seeing that the feature to select separate jars was added only last week, I am not too surprised that things are a little bumpy for getting a modified jar to work. Today is Thursday meaning we should be getting another snapshot, so who knows what new features will be pushed. The whole compartmentalizing to separate the engine and version sounds like something that is more in the works than something we will see immediately. While I wouldn't be surprised if that was a change made for 1.6, I also wouldn't doubt that there was a bit of misunderstand and that the whole version system was setting up ground work for such a change. From what we were told during Minecon 2012, the eventual goal is to have the game completely separated from the engine to the point where MC itself is a plugin.
For anyone still confused about what an API is. Just substitute Minecraft for where they mention operating system, and mods for where they mention application. A perfect example of APIs are both DirectX and OpenGL, which let programmers easily interface the game engine with the gaming hardware.
As for me, I'm neither surprised nor upset about anything to do with the current state of Minecraft. Why? Because I'm not really playing it too much until it reaches the API state or even further along. I personally feel that it's still in beta, and Notch simply said it was a release version so he could move on.
Look at it this way, Notch is like Will Wright or Peter Molyneux. Yes he can code, but he's really more of the creative type who has grand visions and then tries to bring them to life. With everything considered he did a pretty good job bringing Minecraft to life. But that's where his major talent and vision lies. So he finally reached a point where coding Minecraft was both no longer fun, and beyond his ability, because in truth he quite likely codes in the manner of the first definition of "hacker" by the seat of his pants. Which is fine for small coding jobs, but can create a code monster when you do a big one. So that's where first Jeb stepped in and then he brought others on board to help move things along. But they still have to work with the code that Notch wrote, and I bet there's a lot in the way Notch did the original code that makes doing things like APIs hard if not impossible. But from what I can see they do have a goal of giving us what we were told we were going to get. Thing is it's going to take time getting the code monster under control before they can even start moving it forwards to the goal line.
In truth the only reason we're involved with the development of Minecraft is due to how it was first funded. And that's not a bad thing. We could instead of waited 3-5 years while all the development was done without us even knowing and then have the finished game handed to us for 50 bucks. Or we simple relax in the knowledge that it will get done... eventually. You can either play with it, or set it down and wait till it's more polished (like I'm doing), and you can either fool around modding it, or take a break. Choice is yours because it's going to be a bit, and there's nothing either you or I can do about it.
I really don't mind the fiddling at the moment, I only did it to see if it would work. To tell you the truth I was actually quite surprised that it did. Although I guess in a way it does go to prove that having this functionality may not actually require so much work.
What keeps bugging me about the "engine split" is (coming from a modder's perspective now) what happens when something needs to be edited in the engine itself? Will that not destroy all the other "versions"? Sorry for bringing it back to the API, but we were told that the future modding API would allow us to edit "everything" (source) yet this engine/game spit seems to me that it would either make it more difficult, more prone to crashes and/or just more messy.
All in all, at the moment, I don't have any problems with the launcher (hell it makes playing minecraft on ubuntu less of a hassle) it will just be interesting to see exactly how this engine split thing will pan out.
I can see where your coming from with the mods argument on this but I feel that once everything is set and done and FTB and Technic get their stuff straightened out their launchers will resemble that of the new minecraft launcher with better mod and mod pack support, currently on FTB and Technic launchers you can add custom mods and modpacks with little to no fuss to the launcher or the client, and who knows Mojang does have a history of using other mods developers mods in full game maybe they are using the frame work of FTB and/or Technic's launcher for their own launcher. It's just a thought.
Seeing that it is too early in development, who knows. The developers of those modifications will have to take a look at the launcher when ti gets closer to release and the launcher isn't in what is essentially an alpha state. That said, 1.6 does add a vanilla version of RandomMobs, the new horses take advantage of a similar system (though not as fleshed out as what you would see with MCpatcher's controls). Jeb stated that for now the system would be only taken advantage of by horses, but it is there.
I've been here for a loooooooooong time.
P.S Just because you're le mad doesn't mean my message should be deleted)
Plus, with this being the beginnings of what will become the brand new Mod API, I'm willing to bet that its production is beginning to show signs that it's about to become available within a few months or so! I'm SERIOUSLY looking forward to when it is finally available, but heck, I will NOT hesitate to update my Minecraft as soon as 1.6 becomes available, because then I'll be going absolutely CRAZY with it!
n'tRead .. the full 8 pages. (Yes I do care about reading it all over a two or three day span of being at this page, gave me enough time to hear all the whiny, self-centeredbratsyoung ones. )Now if only we could teach our young generations how to be respectful (see the ever annoying Call of Duty kids and such on YouTube... or just via the game itself. I heard that the XBox 360 is where most of them hang out) then we could have less bad apples ( ) everywhere.
EDIT: I'm for the step forward in Minecraft's coding design and content. It shall help me take my first leap into Java easier once I do so.