Way to screw with modders, Mojang! Seriously, we just started updating stuff with 1.2.4. Don't be jerks. The snapshot doesn't help if you start releasing little mini-updates every couple of weeks. Means pointless busy work.
The point of this 1.2.5 snapshot is so that modders can begin work to update when the actual 1.2.5 release comes out. This way, we won't have to wait so long for 1.2.4 mods to be updated.
The point of this 1.2.5 snapshot is so that modders can begin work to update when the actual 1.2.5 release comes out. This way, we won't have to wait so long for 1.2.4 mods to be updated.
People like you are very reason this should never have been posted. This snapshot wont make updating faster. It will just make more people complain that we update too slow.
People like you are very reason this should never have been posted. This snapshot wont make updating faster. It will just make more people complain that we update too slow.
Glad I'm not the only modder that reacted this way. I definitely had a 'wtf?' moment when I saw this headline.
None, I repeat none, of the perquisites for mods even begin updating until the official update comes out. No one works off snapshots, nor would I want them to. I'd rather be behind than spend all my time updating.
Even once the perquisites are updated its extremely tedious for us modders to setup a new dev environment and then we still have to fix any name or function changes.
Nor am I particularly looking forward to the shakeup the Mod API will cause. Switching to it will probably require me to rewrite half my code, and the other half probably won't work without modding the Mod API. I imagine a lot of modders will stop modding.
This is a bit pessimistic. Let me start with the first part before I go into my speculations on what the ModAPI is going to be like.
One of the things to keep in mind with this "snapshot" is that it is implied that when the 1.2.5 release comes out that the class names and obfuscation is going to be identical to what will appear in this snapshot. In other words, a mod which is built for this snapshot (as opposed to a "normal" weekly test snapshot like happened between versions 1.1 and 1.2) will work on the "official" release version 1.2.5 when it finally comes out.
This is a very good thing and shows a remarkable change in attitude towards the community by doing this. It is also a very positive sign that Mojang is listening to the community and is trying to work with us rather than fight the modding community. It also shows that the move to hire the Bukkit developers is also making a positive impact beyond simply bug fixes but also on community relations.
I hope Mojang keeps this pattern of "pre-releasing" an update before it shows up on the main Minecraft screen asking the bulk of players "Do you want to update?" At the very least it ought to cut down the whining on many of the modding forum threads that complain "why aren't you updated to version x.x.x?" Well, I could hope as I think some of that is going to continue but it doesn't have to be so bad. Waiting a week between the pre-release "preview" and the formal release also pulls some pressures off of the dev team, where they shouldn't necessarily put in features into a release that they decided to throw in at the last minute the night before. Perhaps it shows some more discipline and actual software engineering experience is coming to Mojang as well.
Ultimately if this is a sign of what to expect from Mojang in the future, I expect that formal releases are going to have fewer bugs and in the long run will even be showing much more new content that many in the community would love to see added to the game.
As for what I am expecting in the API, it will be like ModLoader+MP+ Forge and many of the existing APIs. It won't be like MCP (which isn't an API), but there might be some unobfuscated code in terms of "interfaces" to several significant object classes.
No doubt there will continue to be actual modding of the Minecraft software outside of the API, but for a great many of the mods that conform to the API there won't be nearly so much incompatibility from one release to the next. My hope is that there will be a formal way for proposed changes to the API to be made, presented in terms of "tests" (aka actual modding to introduce those proposed API changes), and some way to gain community approval to that API change or having somebody at Mojang "bless" the change and put it formally into the game. If that kind of community involvement happens, there will be no room for complaints from me or any valid complaint by anybody else. Yes, it would be a bit bureaucratic to push through such a change, but there will be some awful proposals as well that need to be weeded out too.
People like you are very reason this should never have been posted. This snapshot wont make updating faster. It will just make more people complain that we update too slow.
Glad I'm not the only modder that reacted this way. I definitely had a 'wtf?' moment when I saw this headline.
It isn't that it will make updating mods faster, but rather that mod developers will have the tools available to update their mods when the vast majority of Minecraft players finally see the "Do you want to update?" screens on their game. A great many players don't even frequent the forums except after an update to grab a mod... presuming they even use mods at all.
I'll admit there are many players who are clueless, or ones like some of my children who simply can't resist to click on the "Agree" button on updating the game even if they know they can't use any of the mods they like if that is done.
Not everybody is like Rigusami who can mod directly with the obfuscated source code. Getting MCP available before the next update is even released formally sounds like a wonderful thing to have happen. On top of that, most modders don't even start their update until after MCP is done... which takes about a week or so to accomplish. The one week delay on formally releasing the new update and giving the modding community a chance to get a "preview" copy sounds like a very good idea. It should be encouraged, not derided.
People like you are very reason this should never have been posted. This snapshot wont make updating faster. It will just make more people complain that we update too slow.
I know it likely won't. I'm merely saying that is the purpose of it. I agree with both you and FlowerChild that people will complain. They will use the preparation thing as an excuse for you guys needing to update your mods faster. I've looked into coding and done some in free time. I've made simple personal mods for myself in minecraft, nothing really big or good enough to post for download on here. No need to jump on me for saying the purpose that Jeb has in mind. I've never looked into the differences between snapshots and the actual version, so I don't know how different or similar they are. Good to see that well-known guys on the forums can be rude sometimes
It isn't that it will make updating mods faster, but rather that mod developers will have the tools available to update their mods when the vast majority of Minecraft players finally see the "Do you want to update?" screens on their game.
To my knowledge, Jeb has said NOTHING about this pre-release having anything to do with "Modders Can Prepare Now".
THAT is what I'm objecting to and why I have no idea where the headline for this news item came from. That headline seems to be pure fiction created by whomever wrote it.
I'm not complaining about what Jeb is doing with the pre-release. I'm complaining about a baseless headline that has the potential for promoting update-trolling by misrepresenting the actual situation.
To my knowledge, Jeb has said NOTHING about this pre-release having anything to do with "Modders Can Prepare Now".
THAT is what I'm objecting to and why I have no idea where the headline for this news item came from. That headline seems to be pure fiction created by whomever wrote it.
I'm not complaining about what Jeb is doing with the pre-release. I'm complaining about a baseless headline that has the potential for promoting update-trolling by misrepresenting the actual situation.
The plan for 1.2.5 is to prepare the build today but release it as a snapshot, to give MCP and bukkit a few days to prepare
That is a tweet from Jeb about 14 hours ago. I assume this is where the headline came from. But now I realize that he said MCP and bukkit time to prepare, not the modders in the community. Sacheverell seems to have manipulated it in a way to sound better.
I understand why someone like you would be complaining about this. With big mods and a popular following of them, it must get annoying with constant "UPDATE WOLVES NOW!!!11!!" I don't know how difficult it is to update something of that size, as my coding knowledge is very limited, but I know it takes some time to get everything right. Personally I'd prefer if the snapshots weren't every week, and were more towards bi-weekly or once a month.
To my knowledge, Jeb has said NOTHING about this pre-release having anything to do with "Modders Can Prepare Now".
THAT is what I'm objecting to and why I have no idea where the headline for this news item came from. That headline seems to be pure fiction created by whomever wrote it.
Jeb did explicitly say that the purpose of this snapshot was for the MCP guys to be able to prepare their tools for the 1.2.5 update. Perhaps it is reading between the lines, but if new classes and methods are going to be introduced into the formal release that isn't in this snapshot, what would be the point of even mentioning MCP and Bukkit? THAT is where the "headline" came from.
Perhaps it is a presumption on the part of some, but I think it is a very reasonable guess that there will be no significant changes between this snapshot and the formal release. I agree it would be nice for Jeb to formally state that (he may even say that tomorrow if you push him on the topic), but I can't imagine new content being introduced after this snapshot without the modding community screaming at the top of its lungs if new classes are introduced *after* MCP has updated its tool chain.
I use lots of mods so I've come to dislike updates that don't add much.
This update is fixing a very critical bug that in theory could crash just about every computer playing Minecraft at some point or another if you play with the current version of the game. If you don't mind your save file getting corrupted or worse, I suppose this update isn't needed. It isn't much additional content, but very important bug fixes that you should consider yourself lucky if you haven't had any problems.
The main issues seem to be with the terrain generation routines. If you use a bunch of mods, it may not be so big of a deal because you may not even be using those terrain generation routines. But it is a big deal for most players.
Jeb did explicitly say that the purpose of this snapshot was for the MCP guys to be able to prepare their tools for the 1.2.5 update. Perhaps it is reading between the lines, but if new classes and methods are going to be introduced into the formal release that isn't in this snapshot, what would be the point of even mentioning MCP and Bukkit? THAT is where the "headline" came from.
You're really stretching it man. I think the headline is very clear, and Jeb's statement (which I had also seen) was very clear.
The two statements give completely different impressions. The headline says that this somehow allows all modders to prepare now for the 1.2.5 update. Jeb's post says that it will help MCP and Bukkit prepare. They are not the same thing by any stretch.
Lol, I almost have my mods updated for 1.2.4... Poof the 1.2.5 came out.... (I dont know when Jeb_ release it) but, They dont give a break for the modders? Can't keep a mod for a month. Like the previously beta ones... The update routine was good but this one is like too fast.
Also bukkit released their recommended build for 1.2.4... poof 1.2.5 Need to wait for the 1.2.5 RB. >.<
(sorry about what I said, I dont have the mood to be happy :/)
Rollback Post to RevisionRollBack
MagicLauncher is the best launcher I ever used! Hoping the developer would update for 1.13.x and 1.14.x
Lol, I almost have my mods updated for 1.2.4... Poof the 1.2.5 came out.... (I dont know when Jeb_ release it) but, They dont give a break for the modders? Can't keep a mod for a month. Like the previously beta ones... The update routine was good but this one is like too fast.
I completely agree with this statement.... other than the bug is so serious that it really needs to be fixed in a formal update and made available to ordinary Minecraft users (there is a patch right now for 1.2.4 if you don't mind modding including a source code diff from Mojang). It is also the kind of bug that is a bit harder to find, hence why it has been allowed to live for even the past two weeks at all. I consider that bug more than sufficient for a new update even if it breaks mods (and there have been a couple other bug fixes since then too).
Get version 1.2 stable in some fashion, then it can sit for awhile with new content and weekly snapshots of the development kind and the mods can settle down. I say this as a mod developer knowing full well I need to update my software for this new update and for me personally I would rather not have the update, but I think it is better for the game for it to happen.
On the whole though, these kind of rapid updates do need to end. When version 1.3 comes out, I sure hope that some sort of quality assurance testing happens where these kind of nasty bugs can be discovered *before* they work their way into a formal release version of the game. This isn't nearly as bad as the 1.6 beta bugs and rapid succession of mods that happened (quickly getting to version 1.6.6 in a matter of a week) and some other similar kinds of "testing by release" that was done in the past. For a game that is supposedly in a formal "gold edition" release out of beta, these kind of bugs should be found not by the user community but by some sort of testing process.
That testing process can involve volunteers agreeing to help hunt for bugs that are fans of the game and just want to pound on the latest content, so I'm not against "weekly updates" or anything else that offers pre-release versions of the game for those that know the software may be buggy. I'm just saying that when the software is declared "ready for prime time" that it really should be too. The modding community is working off of that formal release version and not the weekly snapshots, and that is how I think it ought to be too.
just finished updating my server + plugin source in like, a week ago ? and *poof.... 1.2.5
Mojang, you should care about us more, server admins, plugin developer, texture artists, and modders.
I can bet all of my money that Notch, Jeb_, or any other Mojang guys NEVER know how hard it is to maintain a minecraft server.
They NEVER know how to stay sane while updating your server, mods, texture pack, when tons of 12 - 15 years olds screaming "Pweazz update to 1.2.4" or "halppp, it says outdated server what do i do ?
This is why i think its really hard to maintain a minecraft mod, text pack, servers, and server plugins.
1. In other games like doTa, RF, ragnarok, in 1 GB RAM you can hold like 200 players +, in minecraft, 1 GB can only hold 15, or 25 (without any mod), its a HUGE hardware requirement.
2. Lots of players are retarded enough not to ask "update or not" when they logged in to minecraft and see "update now ?" button
3. Plugin developers spent their time coding for FREE, or coding for a very cheap price. My developer accept $20 for a HUGE plugin that needs a lot of time to code. It is because they LOVE the game and wants to contribute something to the community.
4. Server admins, theyre using their creativity to attract members to their server, adding new features to give players best experience and to make it different, not just another singleplayer.
5. I used some mods like minimap, optifine, and zombe. Those are really good tools for building, and admining a server. And there are lots of mods that adds completely new playing experience like tale of kingdoms. Minecraft mods is VITAL in my opinion.
And the last thing. We are doing this for Free and for Fun. Because we LOVE minecraft, we LOVE the game, and we LOVE the community. Mojang should really look down below to us.
We can't sit down 24/7 trying to update our mods, server, or texture packs, this is our hobby not our job !
1.7.3, the first time i played minecraft, was the golden era of minecraft IMO. The game is very simple, yet very complex. Every updates introduce new big things to the game (like when updating to 1.8), and 1.8 to 1.0.0
And every updates came in a sane amount of time, not every 4 - 5 weeks !
Mojang, please stop this nonsense and think about people that contribute a lot to the community.
just finished updating my server + plugin source in like, a week ago ? and *poof.... 1.2.5
Mojang, you should care about us more, server admins, plugin developer, texture artists, and modders.
I can bet all of my money that Notch, Jeb_, or any other Mojang guys NEVER know how hard it is to maintain a minecraft server.
They NEVER know how to stay sane while updating your server, mods, texture pack, when tons of 12 - 15 years olds screaming "Pweazz update to 1.2.4" or "halppp, it says outdated server what do i do ?
This is why i think its really hard to maintain a minecraft mod, text pack, servers, and server plugins.
1. In other games like doTa, RF, ragnarok, in 1 GB RAM you can hold like 200 players +, in minecraft, 1 GB can only hold 15, or 25 (without any mod), its a HUGE hardware requirement.
2. Lots of players are retarded enough not to ask "update or not" when they logged in to minecraft and see "update now ?" button
3. Plugin developers spent their time coding for FREE, or coding for a very cheap price. My developer accept $20 for a HUGE plugin that needs a lot of time to code. It is because they LOVE the game and wants to contribute something to the community.
4. Server admins, theyre using their creativity to attract members to their server, adding new features to give players best experience and to make it different, not just another singleplayer.
5. I used some mods like minimap, optifine, and zombe. Those are really good tools for building, and admining a server. And there are lots of mods that adds completely new playing experience like tale of kingdoms. Minecraft mods is VITAL in my opinion.
And the last thing. We are doing this for Free and for Fun. Because we LOVE minecraft, we LOVE the game, and we LOVE the community. Mojang should really look down below to us.
We can't sit down 24/7 trying to update our mods, server, or texture packs, this is our hobby not our job !
1.7.3, the first time i played minecraft, was the golden era of minecraft IMO. The game is very simple, yet very complex. Every updates introduce new big things to the game (like when updating to 1.8), and 1.8 to 1.0.0
And every updates came in a sane amount of time, not every 4 - 5 weeks !
Mojang, please stop this nonsense and think about people that contribute a lot to the community.
my favorite world is unplayable because of a bug in the generation sub-routen
and all you moders you want them to slow down??
don't you see that once we get to 1.3 you will not have to update every single release
my favorite world is unplayable because of a bug in the generation sub-routen
and all you moders you want them to slow down??
Yes, because slowing down tends to imply *testing* code before releasing it to the general public and not releasing it with world-destroying bugs. The releases we're still getting now are mainly bug-fixes for a release that occurred about a month ago.
Too bad you weren't using BTW btw. I fixed that vanilla world-conversion bug in the first release of the mod for 1.2.3.
just finished updating my server + plugin source in like, a week ago ? and *poof.... 1.2.5
Mojang, you should care about us more, server admins, plugin developer, texture artists, and modders.
I can bet all of my money that Notch, Jeb_, or any other Mojang guys NEVER know how hard it is to maintain a minecraft server.
You, sir, don't know what you are talking about. I know you might be out of the loop and not aware of what has happened in terms of why this update is happening, but I assure you that they are very much aware of how hard it is to maintain a Minecraft server. Heck, Mojang just hired a bunch of server focused developers who are working on improving the client-server interactions and making it easier to maintain servers.
Your anger over having a rapid series of updates is justified, and if you think venting your spleen here on these forums is cathartic for you, I hope it worked for you. Mojang does need to be aware that these kind of updates to cause pain to ordinary users, and that the rapid series of nearly weekly or semi-weekly updates causes considerable chaos.
That said, I think they are fully aware of what is happening. I have never seen a group of game developers that is more a part of the game playing community than Mojang. These are not just guys collecting a paycheck and making games but people who are making the game they would love to play themselves.
Also, expect that this madness is going to end. This series of rapid updates is just a temporary problem.
Yes, because slowing down tends to imply *testing* code before releasing it to the general public and not releasing it with world-destroying bugs. The releases we're still getting now are mainly bug-fixes for a release that occurred about a month ago.
Too bad you weren't using BTW btw. I fixed that vanilla world-conversion bug in the first release of the mod for 1.2.3.
i actually am using your mod it is one of my favorites but there is a MAJOR crash bug in both vanilla and your mod within 1.2.4 tera gen something about terrain already being decorated
i actually am using your mod it is one of my favorites but there is a MAJOR crash bug in both vanilla and your mod within 1.2.4 tera gen something about terrain already being decorated
Ah, sorry, wrong one. Thought you were talking about the blocks at height-limit world-conversion bug that wound up getting fixed in 1.2.4.
This is a new one I don't have any information on. Must be rather infrequent as this is actually the first time I've heard about it.
The point of this 1.2.5 snapshot is so that modders can begin work to update when the actual 1.2.5 release comes out. This way, we won't have to wait so long for 1.2.4 mods to be updated.
People like you are very reason this should never have been posted. This snapshot wont make updating faster. It will just make more people complain that we update too slow.
Glad I'm not the only modder that reacted this way. I definitely had a 'wtf?' moment when I saw this headline.
This is a bit pessimistic. Let me start with the first part before I go into my speculations on what the ModAPI is going to be like.
One of the things to keep in mind with this "snapshot" is that it is implied that when the 1.2.5 release comes out that the class names and obfuscation is going to be identical to what will appear in this snapshot. In other words, a mod which is built for this snapshot (as opposed to a "normal" weekly test snapshot like happened between versions 1.1 and 1.2) will work on the "official" release version 1.2.5 when it finally comes out.
This is a very good thing and shows a remarkable change in attitude towards the community by doing this. It is also a very positive sign that Mojang is listening to the community and is trying to work with us rather than fight the modding community. It also shows that the move to hire the Bukkit developers is also making a positive impact beyond simply bug fixes but also on community relations.
I hope Mojang keeps this pattern of "pre-releasing" an update before it shows up on the main Minecraft screen asking the bulk of players "Do you want to update?" At the very least it ought to cut down the whining on many of the modding forum threads that complain "why aren't you updated to version x.x.x?" Well, I could hope as I think some of that is going to continue but it doesn't have to be so bad. Waiting a week between the pre-release "preview" and the formal release also pulls some pressures off of the dev team, where they shouldn't necessarily put in features into a release that they decided to throw in at the last minute the night before. Perhaps it shows some more discipline and actual software engineering experience is coming to Mojang as well.
Ultimately if this is a sign of what to expect from Mojang in the future, I expect that formal releases are going to have fewer bugs and in the long run will even be showing much more new content that many in the community would love to see added to the game.
As for what I am expecting in the API, it will be like ModLoader+MP+ Forge and many of the existing APIs. It won't be like MCP (which isn't an API), but there might be some unobfuscated code in terms of "interfaces" to several significant object classes.
No doubt there will continue to be actual modding of the Minecraft software outside of the API, but for a great many of the mods that conform to the API there won't be nearly so much incompatibility from one release to the next. My hope is that there will be a formal way for proposed changes to the API to be made, presented in terms of "tests" (aka actual modding to introduce those proposed API changes), and some way to gain community approval to that API change or having somebody at Mojang "bless" the change and put it formally into the game. If that kind of community involvement happens, there will be no room for complaints from me or any valid complaint by anybody else. Yes, it would be a bit bureaucratic to push through such a change, but there will be some awful proposals as well that need to be weeded out too.
It isn't that it will make updating mods faster, but rather that mod developers will have the tools available to update their mods when the vast majority of Minecraft players finally see the "Do you want to update?" screens on their game. A great many players don't even frequent the forums except after an update to grab a mod... presuming they even use mods at all.
I'll admit there are many players who are clueless, or ones like some of my children who simply can't resist to click on the "Agree" button on updating the game even if they know they can't use any of the mods they like if that is done.
Not everybody is like Rigusami who can mod directly with the obfuscated source code. Getting MCP available before the next update is even released formally sounds like a wonderful thing to have happen. On top of that, most modders don't even start their update until after MCP is done... which takes about a week or so to accomplish. The one week delay on formally releasing the new update and giving the modding community a chance to get a "preview" copy sounds like a very good idea. It should be encouraged, not derided.
Version 2.1 now updated for MC 1.6.2
I know it likely won't. I'm merely saying that is the purpose of it. I agree with both you and FlowerChild that people will complain. They will use the preparation thing as an excuse for you guys needing to update your mods faster. I've looked into coding and done some in free time. I've made simple personal mods for myself in minecraft, nothing really big or good enough to post for download on here. No need to jump on me for saying the purpose that Jeb has in mind. I've never looked into the differences between snapshots and the actual version, so I don't know how different or similar they are. Good to see that well-known guys on the forums can be rude sometimes
To my knowledge, Jeb has said NOTHING about this pre-release having anything to do with "Modders Can Prepare Now".
THAT is what I'm objecting to and why I have no idea where the headline for this news item came from. That headline seems to be pure fiction created by whomever wrote it.
I'm not complaining about what Jeb is doing with the pre-release. I'm complaining about a baseless headline that has the potential for promoting update-trolling by misrepresenting the actual situation.
The plan for 1.2.5 is to prepare the build today but release it as a snapshot, to give MCP and bukkit a few days to prepare
That is a tweet from Jeb about 14 hours ago. I assume this is where the headline came from. But now I realize that he said MCP and bukkit time to prepare, not the modders in the community. Sacheverell seems to have manipulated it in a way to sound better.
I understand why someone like you would be complaining about this. With big mods and a popular following of them, it must get annoying with constant "UPDATE WOLVES NOW!!!11!!" I don't know how difficult it is to update something of that size, as my coding knowledge is very limited, but I know it takes some time to get everything right. Personally I'd prefer if the snapshots weren't every week, and were more towards bi-weekly or once a month.
Jeb did explicitly say that the purpose of this snapshot was for the MCP guys to be able to prepare their tools for the 1.2.5 update. Perhaps it is reading between the lines, but if new classes and methods are going to be introduced into the formal release that isn't in this snapshot, what would be the point of even mentioning MCP and Bukkit? THAT is where the "headline" came from.
Perhaps it is a presumption on the part of some, but I think it is a very reasonable guess that there will be no significant changes between this snapshot and the formal release. I agree it would be nice for Jeb to formally state that (he may even say that tomorrow if you push him on the topic), but I can't imagine new content being introduced after this snapshot without the modding community screaming at the top of its lungs if new classes are introduced *after* MCP has updated its tool chain.
This update is fixing a very critical bug that in theory could crash just about every computer playing Minecraft at some point or another if you play with the current version of the game. If you don't mind your save file getting corrupted or worse, I suppose this update isn't needed. It isn't much additional content, but very important bug fixes that you should consider yourself lucky if you haven't had any problems.
The main issues seem to be with the terrain generation routines. If you use a bunch of mods, it may not be so big of a deal because you may not even be using those terrain generation routines. But it is a big deal for most players.
Version 2.1 now updated for MC 1.6.2
You're really stretching it man. I think the headline is very clear, and Jeb's statement (which I had also seen) was very clear.
The two statements give completely different impressions. The headline says that this somehow allows all modders to prepare now for the 1.2.5 update. Jeb's post says that it will help MCP and Bukkit prepare. They are not the same thing by any stretch.
Also bukkit released their recommended build for 1.2.4... poof 1.2.5 Need to wait for the 1.2.5 RB. >.<
(sorry about what I said, I dont have the mood to be happy :/)
I completely agree with this statement.... other than the bug is so serious that it really needs to be fixed in a formal update and made available to ordinary Minecraft users (there is a patch right now for 1.2.4 if you don't mind modding including a source code diff from Mojang). It is also the kind of bug that is a bit harder to find, hence why it has been allowed to live for even the past two weeks at all. I consider that bug more than sufficient for a new update even if it breaks mods (and there have been a couple other bug fixes since then too).
Get version 1.2 stable in some fashion, then it can sit for awhile with new content and weekly snapshots of the development kind and the mods can settle down. I say this as a mod developer knowing full well I need to update my software for this new update and for me personally I would rather not have the update, but I think it is better for the game for it to happen.
On the whole though, these kind of rapid updates do need to end. When version 1.3 comes out, I sure hope that some sort of quality assurance testing happens where these kind of nasty bugs can be discovered *before* they work their way into a formal release version of the game. This isn't nearly as bad as the 1.6 beta bugs and rapid succession of mods that happened (quickly getting to version 1.6.6 in a matter of a week) and some other similar kinds of "testing by release" that was done in the past. For a game that is supposedly in a formal "gold edition" release out of beta, these kind of bugs should be found not by the user community but by some sort of testing process.
That testing process can involve volunteers agreeing to help hunt for bugs that are fans of the game and just want to pound on the latest content, so I'm not against "weekly updates" or anything else that offers pre-release versions of the game for those that know the software may be buggy. I'm just saying that when the software is declared "ready for prime time" that it really should be too. The modding community is working off of that formal release version and not the weekly snapshots, and that is how I think it ought to be too.
Version 2.1 now updated for MC 1.6.2
just finished updating my server + plugin source in like, a week ago ? and *poof.... 1.2.5
Mojang, you should care about us more, server admins, plugin developer, texture artists, and modders.
I can bet all of my money that Notch, Jeb_, or any other Mojang guys NEVER know how hard it is to maintain a minecraft server.
They NEVER know how to stay sane while updating your server, mods, texture pack, when tons of 12 - 15 years olds screaming "Pweazz update to 1.2.4" or "halppp, it says outdated server what do i do ?
This is why i think its really hard to maintain a minecraft mod, text pack, servers, and server plugins.
1. In other games like doTa, RF, ragnarok, in 1 GB RAM you can hold like 200 players +, in minecraft, 1 GB can only hold 15, or 25 (without any mod), its a HUGE hardware requirement.
2. Lots of players are retarded enough not to ask "update or not" when they logged in to minecraft and see "update now ?" button
3. Plugin developers spent their time coding for FREE, or coding for a very cheap price. My developer accept $20 for a HUGE plugin that needs a lot of time to code. It is because they LOVE the game and wants to contribute something to the community.
4. Server admins, theyre using their creativity to attract members to their server, adding new features to give players best experience and to make it different, not just another singleplayer.
5. I used some mods like minimap, optifine, and zombe. Those are really good tools for building, and admining a server. And there are lots of mods that adds completely new playing experience like tale of kingdoms. Minecraft mods is VITAL in my opinion.
And the last thing. We are doing this for Free and for Fun. Because we LOVE minecraft, we LOVE the game, and we LOVE the community. Mojang should really look down below to us.
We can't sit down 24/7 trying to update our mods, server, or texture packs, this is our hobby not our job !
1.7.3, the first time i played minecraft, was the golden era of minecraft IMO. The game is very simple, yet very complex. Every updates introduce new big things to the game (like when updating to 1.8), and 1.8 to 1.0.0
And every updates came in a sane amount of time, not every 4 - 5 weeks !
Mojang, please stop this nonsense and think about people that contribute a lot to the community.
my favorite world is unplayable because of a bug in the generation sub-routen
and all you moders you want them to slow down??
don't you see that once we get to 1.3 you will not have to update every single release
Yes, because slowing down tends to imply *testing* code before releasing it to the general public and not releasing it with world-destroying bugs. The releases we're still getting now are mainly bug-fixes for a release that occurred about a month ago.
Too bad you weren't using BTW btw. I fixed that vanilla world-conversion bug in the first release of the mod for 1.2.3.
You, sir, don't know what you are talking about. I know you might be out of the loop and not aware of what has happened in terms of why this update is happening, but I assure you that they are very much aware of how hard it is to maintain a Minecraft server. Heck, Mojang just hired a bunch of server focused developers who are working on improving the client-server interactions and making it easier to maintain servers.
Your anger over having a rapid series of updates is justified, and if you think venting your spleen here on these forums is cathartic for you, I hope it worked for you. Mojang does need to be aware that these kind of updates to cause pain to ordinary users, and that the rapid series of nearly weekly or semi-weekly updates causes considerable chaos.
That said, I think they are fully aware of what is happening. I have never seen a group of game developers that is more a part of the game playing community than Mojang. These are not just guys collecting a paycheck and making games but people who are making the game they would love to play themselves.
Also, expect that this madness is going to end. This series of rapid updates is just a temporary problem.
Version 2.1 now updated for MC 1.6.2
i actually am using your mod it is one of my favorites but there is a MAJOR crash bug in both vanilla and your mod within 1.2.4 tera gen something about terrain already being decorated
Ah, sorry, wrong one. Thought you were talking about the blocks at height-limit world-conversion bug that wound up getting fixed in 1.2.4.
This is a new one I don't have any information on. Must be rather infrequent as this is actually the first time I've heard about it.