A tiny update fixing only ONE bug breaks every single mod and Bukkit plugin out there? Whatever happened to those updates NOT breaking the entire game? Then I have to wait like a week for all of the mods I use to be updated because Mojang overlooked one bug and decide to fix it more than two months after they release 1.6. It's seriously one of the most irritating things about this game. I'm usually a patient guy, but not for stupid things like this.
The Meaning of Life, the Universe, and Everything.
Join Date:
3/10/2013
Posts:
196
Xbox:
f*** Microsoft
Member Details
Yeah… I'm not even going to bother updating my plugin for 1.6.4. Consider it a punishment if you need my plugin but decided to be a jerk by updating your server to 1.6.4. And my server is staying at 1.6.2 until 1.7 comes out.
If Mojang cared about every single mod/plugins, the game would still be in alpha.
By the way nothing forces you to update your server. It's not a major update with tons of new features.
Not everyone runs a server. I wanted to play on The Walls servers, and they were all 1.6.4.
If Mojang cared about every single mod/plugins, the game would still be in alpha.
By the way nothing forces you to update your server. It's not a major update with tons of new features.
When they made tiny updates like that that fixed bugs back in the day, it didn't break all the mods. Now they keep doing that. What are they doing different?
Also, I'm not peeved because I'm running a server; it's the servers I connect to.
Ooohh one guy doesn't want to create a new profile that can join his servers. Let's stop all development and bug fixes.
Speak again when you've updated Zombe, Rei Minimap, BetterSprinting, ChatLog, RadarBro, and ModLoader plus all the common Bukkit plugins for us. Maybe then you won't think it was worth it to break all of these for some tiny bug fix on witches' huts.
Regardless, that tiny update should not have broken anything. It just shows that the game is programmed badly when you can't change one thing without affecting other things.
Ooohh one guy doesn't want to create a new profile that can join his servers. Let's stop all development and bug fixes.
Like I've said, it's stupid that this used to not happen but now it is. What are they doing different? And why update after two months rather than just throw it into 1.7? Also, I prefer to use mods while I'm on servers, so I can't play without them (especially ones like Optifine and BetterSprinting).
If Mojang cared about mods/plugins, we'd already have the API.
If Mojang didn't give a crap about mods/plugins then Mojang making an API wouldn't even be considered.
Also, it's the server's call on whether to update or not. Many servers are updating because there are plugins for 1.6.4 that fix critical bugs like horses despawning and such. So you really can't blame Mojang. Blame the server for updating to 1.6.4, if the server gains less from updating than from not updating then they probably won't update yet.
Speak again when you've updated Zombe, Rei Minimap, BetterSprinting, ChatLog, RadarBro, and ModLoader plus all the common Bukkit plugins for us. Maybe then you won't think it was worth it to break all of these for some tiny bug fix on witches' huts.
Regardless, that tiny update should not have broken anything. It just shows that the game is programmed badly when you can't change one thing without affecting other things.
Rule of coding number 1: If you have a lot of code, small changes make big bugs. It doesn't mean the game is programmed badly, it means it's REALLY large and many features rely on other features that rely on other features that rely on other features that rely on a changed feature.
Rollback Post to RevisionRollBack
Quote from Fermat »
I have discovered a truly remarkable proof of this, which this margin is too small to contain.
[;/quote]
Rule of coding number 1: If you have a lot of code, small changes make big bugs. It doesn't mean the game is programmed badly, it means it's REALLY large and many features rely on other features that rely on other features that rely on other features that rely on a changed feature.
That's why you write your code in layers. You have your base code, then code that builds on top of that. Content should be the very last layer. Thus changing something that effects content shouldn't effect anything else.
Like I've said, it's stupid that this used to not happen but now it is. What are they doing different? And why update after two months rather than just throw it into 1.7? Also, I prefer to use mods while I'm on servers, so I can't play without them (especially ones like Optifine and BetterSprinting).
It's like asking why Mojang bothers to fix bugs. If they don't release bug fixes, then you will constantly be playing with a buggy game until they get fixed in the next update where there will be tons of more bugs. Wait like the rest of the population.
It's like asking why Mojang bothers to fix bugs. If they don't release bug fixes, then you will constantly be playing with a buggy game until they get fixed in the next update where there will be tons of more bugs. Wait like the rest of the population.
But why after two months? Why not the week after? Why not even two weeks after? I don't know about you, but I find it dumb.
It's like asking why Mojang bothers to fix bugs. If they don't release bug fixes, then you will constantly be playing with a buggy game until they get fixed in the next update where there will be tons of more bugs. Wait like the rest of the population.
But they're releasing a bug fix so close to 1.7. Why can't it just wait until 1.7? What's so important about that bug fix? Most of all, fixing that bug should NOT affect nearly everything in the game.
Rule of coding number 1: If you have a lot of code, small changes make big bugs. It doesn't mean the game is programmed badly, it means it's REALLY large and many features rely on other features that rely on other features that rely on other features that rely on a changed feature.
The witch huts shouldn't be a low-level feature. It should be riding on top of a lot of abstraction layers. Even structure spawning as a whole should not affect most of the game. In fact, a client on a multiplayer server controls absolutely none of that.
I'm writing a chat server for a school project right now. If I want to make it so admins can delete a text chat room, I don't have to go change how audio chats work.
If Mojang didn't give a crap about mods/plugins then Mojang making an API wouldn't even be considered.
Also, it's the server's call on whether to update or not. Many servers are updating because there are plugins for 1.6.4 that fix critical bugs like horses despawning and such. So you really can't blame Mojang. Blame the server for updating to 1.6.4, if the server gains less from updating than from not updating then they probably won't update yet.
I agree with you; however, The Walls servers, which don't even have witch huts, horses, etc. decided to update to 1.6.4, and it's mainly what I play besides my cousin's server. I'm assuming they did it because they wanted to be up-to-date and not lose players who are too technologically declined to not update or downgrade, which is an update that should've been fixed a long time ago or thrown into 1.7.
But they're releasing a bug fix so close to 1.7. Why can't it just wait until 1.7? What's so important about that bug fix? Most of all, fixing that bug should NOT affect nearly everything in the game.
What do you mean by affecting nearly everything in the game? I think you meant that being able to use mods is affected by it. Also who knows when 1.7 will be released? It could take a long time. So once again I say this
1. If you're playing single player then whether or not to update for something like a small bug fix update is YOUR choice.
2. If it's on a server then it's the server owner's call on whether to update or not. Weight the benefits over the negatives.
Blame the server for updating to 1.6.4, if the server gains less from updating than from not updating then they probably won't update yet.
If they don't update, they get a million players asking how to downgrade or complaining that the server isn't updated when others are. You'd think that the new launcher would fix that problem, but it's still an annoyance.
Rollback Post to RevisionRollBack
My Bukkit plugin for IP-banning offline players, logging addresses, and more:
What do you mean by affecting nearly everything in the game? I think you meant that being able to use mods is affected by it.
If it breaks a mod that changes the game's graphics, then it must have changed the graphics somehow. If it breaks a mod that changes the sprint controls, then it must have changed how sprinting works. There's something called MVC (model, view, controller) that they clearly don't understand.
I get that it's the server owner's decision to update. As if that helps at all. I kept my server at 1.6.2, but if I want to play on the other servers that all updated, I have to lose most of my mods.
1.7 should be coming out soon, judging by their release cycle. No need to put everyone through this inconvenience for a minor bug fix. Updating Bukkit plugins is the most stressful part for a server owner because new versions might not be stable.
If they don't update, they get a million players asking how to downgrade or complaining that the server isn't updated when others are. You'd think that the new launcher would fix that problem, but it's still an annoyance.
Do you seriously doubt the intelligence and knowledge of people? The new launcher has made switching versions A CRAP TON easier. If you're ignorant about changing versions then you would probably ask (like this forum) or search on how to do it if you wanted to. So what do you expect? That Mojang invent some mind reading crap to automatically switch versions for you?
Don't forget this is a small bug update we're talking about. If people rather play on the server than get a few bugs fixed then they won't update or will revert back.
If it breaks a mod that changes the game's graphics, then it must have changed the graphics somehow. If it breaks a mod that changes the sprint controls, then it must have changed how sprinting works. There's something called MVC (model, view, controller) that they clearly don't understand.
Hmm well I don't know anything about coding but I'm sure the experts and what not will reason with you *shrugs*. What I do know is that you can't just make an update adapt to every single version of mods/plugins (though they are working on modding api)..... + in this situation it's simply moot since it's not worth updating and it's the server's choice.
Not everyone runs a server. I wanted to play on The Walls servers, and they were all 1.6.4.
If Mojang cared about mods/plugins, we'd already have the API.
When they made tiny updates like that that fixed bugs back in the day, it didn't break all the mods. Now they keep doing that. What are they doing different?
Also, I'm not peeved because I'm running a server; it's the servers I connect to.
Speak again when you've updated Zombe, Rei Minimap, BetterSprinting, ChatLog, RadarBro, and ModLoader plus all the common Bukkit plugins for us. Maybe then you won't think it was worth it to break all of these for some tiny bug fix on witches' huts.
Regardless, that tiny update should not have broken anything. It just shows that the game is programmed badly when you can't change one thing without affecting other things.
Like I've said, it's stupid that this used to not happen but now it is. What are they doing different? And why update after two months rather than just throw it into 1.7? Also, I prefer to use mods while I'm on servers, so I can't play without them (especially ones like Optifine and BetterSprinting).
If Mojang didn't give a crap about mods/plugins then Mojang making an API wouldn't even be considered.
Also, it's the server's call on whether to update or not. Many servers are updating because there are plugins for 1.6.4 that fix critical bugs like horses despawning and such. So you really can't blame Mojang. Blame the server for updating to 1.6.4, if the server gains less from updating than from not updating then they probably won't update yet.
Rule of coding number 1: If you have a lot of code, small changes make big bugs. It doesn't mean the game is programmed badly, it means it's REALLY large and many features rely on other features that rely on other features that rely on other features that rely on a changed feature.
That's why you write your code in layers. You have your base code, then code that builds on top of that. Content should be the very last layer. Thus changing something that effects content shouldn't effect anything else.
But why after two months? Why not the week after? Why not even two weeks after? I don't know about you, but I find it dumb.
But they're releasing a bug fix so close to 1.7. Why can't it just wait until 1.7? What's so important about that bug fix? Most of all, fixing that bug should NOT affect nearly everything in the game.
The witch huts shouldn't be a low-level feature. It should be riding on top of a lot of abstraction layers. Even structure spawning as a whole should not affect most of the game. In fact, a client on a multiplayer server controls absolutely none of that.
I'm writing a chat server for a school project right now. If I want to make it so admins can delete a text chat room, I don't have to go change how audio chats work.
I agree with you; however, The Walls servers, which don't even have witch huts, horses, etc. decided to update to 1.6.4, and it's mainly what I play besides my cousin's server. I'm assuming they did it because they wanted to be up-to-date and not lose players who are too technologically declined to not update or downgrade, which is an update that should've been fixed a long time ago or thrown into 1.7.
Still, it's the server's final call on whether to update or not.
What do you mean by affecting nearly everything in the game? I think you meant that being able to use mods is affected by it. Also who knows when 1.7 will be released? It could take a long time. So once again I say this
1. If you're playing single player then whether or not to update for something like a small bug fix update is YOUR choice.
2. If it's on a server then it's the server owner's call on whether to update or not. Weight the benefits over the negatives.
If they don't update, they get a million players asking how to downgrade or complaining that the server isn't updated when others are. You'd think that the new launcher would fix that problem, but it's still an annoyance.
If it breaks a mod that changes the game's graphics, then it must have changed the graphics somehow. If it breaks a mod that changes the sprint controls, then it must have changed how sprinting works. There's something called MVC (model, view, controller) that they clearly don't understand.
I get that it's the server owner's decision to update. As if that helps at all. I kept my server at 1.6.2, but if I want to play on the other servers that all updated, I have to lose most of my mods.
1.7 should be coming out soon, judging by their release cycle. No need to put everyone through this inconvenience for a minor bug fix. Updating Bukkit plugins is the most stressful part for a server owner because new versions might not be stable.
Do you seriously doubt the intelligence and knowledge of people? The new launcher has made switching versions A CRAP TON easier. If you're ignorant about changing versions then you would probably ask (like this forum) or search on how to do it if you wanted to. So what do you expect? That Mojang invent some mind reading crap to automatically switch versions for you?
Don't forget this is a small bug update we're talking about. If people rather play on the server than get a few bugs fixed then they won't update or will revert back.
Hmm well I don't know anything about coding but I'm sure the experts and what not will reason with you *shrugs*. What I do know is that you can't just make an update adapt to every single version of mods/plugins (though they are working on modding api)..... + in this situation it's simply moot since it's not worth updating and it's the server's choice.
Yes. Every time there's some update that my server isn't on immediately, a bunch of people ask me how to downgrade.