i really think mojang should not declare a stable version for mc for a while, they should release it as a tester only and hold back calling anything a stable update. so modders can get caught up again and not have to worry about everyone demanding a new mod update to go along with a mc update.
I am somewhat sympathetic to Mojang in terms of their still being a small company and until recently only two developers (and for most of the development of Minecraft, just Notch). It is very hard to discipline yourself when you are working by yourself to follow any kind of testing routine for the software you are producing, much less commit to a "release" vs. "development" branch of the software. By doing that, you need to basically update two different versions of your software at the same time, where you might even introduce new bugs in the process simply by trying to fix old bugs.
A larger software development team though is going to bring some discipline into the system by necessity, as developers need to communicate with each other more and be working with common interfaces. In other words, the API is going to be needed just for projects completely internal to Mojang, much less something in the modding community. Testing is going to also be a much larger issue as one developer starts to encounter "bugs" caused by somebody else's module/class. It does create some "friction" between the developers, but if the team can work things out on the whole I think the overall quality of the software is going to improve if for no other reason than to keep all of the developers on the same page and working together.
Give Mojang a chance to come together. They just held a "mini-conference" (their term) for the new developers and planned out a roadmap for Minecraft, which I think is going to be a very good thing. There is a vision for the future of the game, and be prepared to see that vision be implemented in the next few months.
Can Somebody explain to me what the Mod API will do? I know it will help mods in some various way, but i'm not sure what.
For "simple mods", you won't need to be pushing the mod developer to update the mod to the current version of Minecraft. It simply will work as intended even after new updates from Mojang.
Well, that is the hope anyway. Expect that the API is going to be unstable for at least a little bit until the "bugs can be worked out".
We really won't know for sure what the API even is until Mojang releases the information in a formal sense to developers and gives the API protocol along with recommended development tools. I can speculate somewhat based upon other kinds of API tools and libraries, assuming that is what Mojang thinks it ought to be like but it is really an "educated guess" and not anything definite. It will be something somewhat like ModLoader (aka you will just drop the "mod" into a "mod folder" and it should work) but there are more things to it as well.
I could offer more details, but at best that is speculating and not anything certain.
For "simple mods", you won't need to be pushing the mod developer to update the mod to the current version of Minecraft. It simply will work as intended even after new updates from Mojang.
Well, that is the hope anyway. Expect that the API is going to be unstable for at least a little bit until the "bugs can be worked out".
We really won't know for sure what the API even is until Mojang releases the information in a formal sense to developers and gives the API protocol along with recommended development tools. I can speculate somewhat based upon other kinds of API tools and libraries, assuming that is what Mojang thinks it ought to be like but it is really an "educated guess" and not anything definite. It will be something somewhat like ModLoader (aka you will just drop the "mod" into a "mod folder" and it should work) but there are more things to it as well.
I could offer more details, but at best that is speculating and not anything certain.
What I would like to know, If mod developers are playing an important role in minecraft do you really think it's wise to release 1 update after the other, if you are lucky, which in most cases you are not these updates more often just breaks most of the code and we have to re-write a whole deal of the code, not to mention all the bugs that has to be dealt with the bugs on mods for 1.2.4 has not even been fixed yet in a lot of the mods heck we have lost more decent developers these past couple of months due to excatcly this same thing updates been released like sweeties. For that matter most of the popular mods like BuildCraft and IC2 has not even been updated to 1.2.4 yet so it's not just a matter of running your code through MCp and all is well it's bone breaking work each time with fixes.
I do appreciate all the attention minecraft gets in regards to updating it with new content, but there comes a time in just about every mod developers life where enough is enough and they stop updating and simply leave so I'm I the only one thinking that it's a bit unprofesional to release one update after the other escpecially when your game is also heavily dependant on mod developers.
I think there is a balance that should be kept in updates, each updates players have to wait for servers to update, mods to update, mods are dependant on each other so one has to wait for the other and in that same time players are still force to play on previous versions we stil have most players playing on 1.2.3 that hasn't updated yet because they waiting for the mods to be converted to 1.2.4, which is most likely not going to happen because they all going to sit back and wait for 1.2.5 or maybe 1.2.6 or 1.2.7
So in short I really think there should be a balance that needs to be maintained in regards to updates maybe I'm the only that feels like that, and maybe not I do not as a mod developer myself this really de motivates me a lot.
I play without a single mod on many of my machines. So tell me, how does this make Minecraft, a Mod Developer dependent game?
I'll tell you since that was a rhetorical question, it does not, in fact You made Yourself Mod Developer dependent.
Yeah. I wish they would make it so there will be no need for mod updates each minecraft update. That would be just awesome
Can't wait to see what's new in 1.2.5, I hope they fixed the seed issue.
Seed issue?
Rollback Post to RevisionRollBack
If I helped you or you like my post, PLEASE click the green + button it only takes 2 seconds and it helps out a lot, thanks. Please click him, or he will die.
Yeah. I wish they would make it so there will be no need for mod updates each minecraft update. That would be just awesome
Can't wait to see what's new in 1.2.5, I hope they fixed the seed issue.
In terms of server mods, until the plugin API is built into vanilla, there is no way around updating Bukkit servers after every update since the craftbukkit.jar file actually replaces the entire minecraft_server.jar.
I think it's good that Jeb_ and the rest of Mojang are trying to communicate more with the Minecraft Community, but I think this rapid release of versions is more harmful than good. I understand that there is a huge bug that needs to be fixed and apparently is going to be fixed in 1.2.5, but I've seriously been deterred from playing Minecraft over the last week or two simply because of the sheer speed in which these updates are coming out. I'm getting tired of it.
I made the mistake of updating from 1.1 to 1.2 without backing up my .jar file, and I'm just not going to be bothered trying to find a 1.1 .jar file and going through a whole "downgrading" process just so I can play on my favorite SMP server... so I've gone over a month without multiplayer really, and I'm kinda tired of playing by myself for the most part because 99% of the servers out there are a load of garbage. "Sign up on our forums [that you're never going to visit again] and apply for building rights [because let's face it, you signed on to our server today so you could spend 2 days waiting for build rights, what fun]!"
I can't tell you how many times I've ran into this while searching for a good multiplayer server to play on. I've spent hours trying to find a half-way decent server and to my dismay, I've only found 1. And they're not past 1.1 yet because of the sheer amount of updates dropping on us all the time, and trying to configure the server to work properly with all the mods on it to 1.2.4. Now 1.2.5 is around the corner, and... what? Another month delay on the update process for the server? Bullcrap. This is starting to end up like the 1.6 fiasco all over again.
Call this harsh, or whatever you wish to call it, but this is just how I feel about these updates happening as quick as they are. I'm not upset at the modding community because I understand that it's something that they do in their spare time as a hobby, not their full time job, but the least Mojang could do is give the modding community whatever they need from the finished copy of the version they're going to release in two weeks time so that they have ample time with which to update their mods to be ready for the new release when it drops, instead of saying what they are now with giving a pre-release version that may or may not have changes from the final version they're dropping in just one week, or just dropping a surprise update like they've done in the past and have the whole modding community scrambling to get their stuff updated, only to drop a new version mere weeks after they've spent their free time updating their mods to be compatible with the last version.
And don't get me wrong, I do enjoy new game content, but I'd rather the new game content came without breaking the current mod content so often.
I am somewhat sympathetic to Mojang in terms of their still being a small company and until recently only two developers (and for most of the development of Minecraft, just Notch). It is very hard to discipline yourself when you are working by yourself to follow any kind of testing routine for the software you are producing, much less commit to a "release" vs. "development" branch of the software. By doing that, you need to basically update two different versions of your software at the same time, where you might even introduce new bugs in the process simply by trying to fix old bugs.
A larger software development team though is going to bring some discipline into the system by necessity, as developers need to communicate with each other more and be working with common interfaces. In other words, the API is going to be needed just for projects completely internal to Mojang, much less something in the modding community. Testing is going to also be a much larger issue as one developer starts to encounter "bugs" caused by somebody else's module/class. It does create some "friction" between the developers, but if the team can work things out on the whole I think the overall quality of the software is going to improve if for no other reason than to keep all of the developers on the same page and working together.
Give Mojang a chance to come together. They just held a "mini-conference" (their term) for the new developers and planned out a roadmap for Minecraft, which I think is going to be a very good thing. There is a vision for the future of the game, and be prepared to see that vision be implemented in the next few months.
Version 2.1 now updated for MC 1.6.2
most mods from 1.2.4 work in 1.2.5
For "simple mods", you won't need to be pushing the mod developer to update the mod to the current version of Minecraft. It simply will work as intended even after new updates from Mojang.
Well, that is the hope anyway. Expect that the API is going to be unstable for at least a little bit until the "bugs can be worked out".
We really won't know for sure what the API even is until Mojang releases the information in a formal sense to developers and gives the API protocol along with recommended development tools. I can speculate somewhat based upon other kinds of API tools and libraries, assuming that is what Mojang thinks it ought to be like but it is really an "educated guess" and not anything definite. It will be something somewhat like ModLoader (aka you will just drop the "mod" into a "mod folder" and it should work) but there are more things to it as well.
I could offer more details, but at best that is speculating and not anything certain.
Version 2.1 now updated for MC 1.6.2
I just took the Minecraft Noob test! Check out what I scored. Think you can beat me?!
To take the test, check out
https://minecraftnoobtest.com/test.php
Don't click this link, HE is haunting it...
my level of paitence dropped a bit, finally mod api.
, i found the smilies. and this calls for smilies, i have been waiting for in game mod support since i installed my first mod.
I play without a single mod on many of my machines. So tell me, how does this make Minecraft, a Mod Developer dependent game?
I'll tell you since that was a rhetorical question, it does not, in fact You made Yourself Mod Developer dependent.
Seed issue?
Please click him, or he will die.
In terms of server mods, until the plugin API is built into vanilla, there is no way around updating Bukkit servers after every update since the craftbukkit.jar file actually replaces the entire minecraft_server.jar.
I made the mistake of updating from 1.1 to 1.2 without backing up my .jar file, and I'm just not going to be bothered trying to find a 1.1 .jar file and going through a whole "downgrading" process just so I can play on my favorite SMP server... so I've gone over a month without multiplayer really, and I'm kinda tired of playing by myself for the most part because 99% of the servers out there are a load of garbage. "Sign up on our forums [that you're never going to visit again] and apply for building rights [because let's face it, you signed on to our server today so you could spend 2 days waiting for build rights, what fun]!"
I can't tell you how many times I've ran into this while searching for a good multiplayer server to play on. I've spent hours trying to find a half-way decent server and to my dismay, I've only found 1. And they're not past 1.1 yet because of the sheer amount of updates dropping on us all the time, and trying to configure the server to work properly with all the mods on it to 1.2.4. Now 1.2.5 is around the corner, and... what? Another month delay on the update process for the server? Bullcrap. This is starting to end up like the 1.6 fiasco all over again.
Call this harsh, or whatever you wish to call it, but this is just how I feel about these updates happening as quick as they are. I'm not upset at the modding community because I understand that it's something that they do in their spare time as a hobby, not their full time job, but the least Mojang could do is give the modding community whatever they need from the finished copy of the version they're going to release in two weeks time so that they have ample time with which to update their mods to be ready for the new release when it drops, instead of saying what they are now with giving a pre-release version that may or may not have changes from the final version they're dropping in just one week, or just dropping a surprise update like they've done in the past and have the whole modding community scrambling to get their stuff updated, only to drop a new version mere weeks after they've spent their free time updating their mods to be compatible with the last version.
And don't get me wrong, I do enjoy new game content, but I'd rather the new game content came without breaking the current mod content so often.
SNES ROMs