This is the worst patch I've seen Mojang put out in a year.
On may 26th, they patched the game 4 times and fixed a ton of bugs. Why is it that this time they fix two bugs and then leave us with no information. :/
I just don't get it. Why the sudden change in policy and quality, Mojang?
The bigger the game, the bigger the codes.
The bigger the codes, the longer they have to search.
Can you make it better then them? then make it and stop crying.
There's a thing called a debugger. It comes with 99% of compilation software. Makes it real easy to find buggy code.
So fixing two gamebreakers that crashed the game being fixed is a garbage patch? Go f*** yourself and make a better patch for everyone then. We're waiting.
1> Remember this is a forum with a young audience, so I suggest you watch your language.
2> My point is he fixed those two things and then fixed nothing else, VS back in may he launched 1.6 and then updated it 4 times that day fixing just as many game breaking crash bugs.
If the system was tidy and the functions and vairables were worderd well enough then the system being bigger shouldn't be a problem. People are going to complain no matter what, but customer feedback is very important and the community getting together and sharing their concerns and ideas actually helps the developers. If we "stopped crying" then nothing will get fixed because the developers would not know about it.
I know that there is a mannorism to this, and this thread is probably the wrong way to go about it. 1.8.1 has come out and it's better than 1.8 because it has less bugs, it didn't cost you anything to update so why complain? I think the purpose of this thread is to say, stop rushing updates take your time and fix the bugs properly. Which is constructive criticism. Then people would only complain that bug fixes don't come out fast enough.
No one can win this battle.
This is exactly what I'm saying. I'd also like to play the game I paid for, which is not possible on one of my computers (my home computer) so I can only play when I'm in my studio, which is quite unfair to me (and my work ethic.) :wink.gif:
So why is it he only fixed two things and not fixed the lag problems, the un-optimized laggy code, or even better yet, why didn't they just delay the release of 1.8 till it was ready? at least with the pre-releases I could revert back to 1.7.3 if I wanted to.
I was also going to money to the equation, but then I realised that this is just beta software and he didn't have to let us play (I bet Notch is damn happy he did though because hes a millionare now). I also do find it annoying that I can't play on my Mac with a 9500M because of the massive performance degrade, I log in with 70+fps after 10 minutes of playing it drops to 21 and the lag spikes are crazy. This is a big problem which to me seems to have slipped under the rug just because it's not 100% of the community experiencing these problems. No matter what fog distance I play on I always avarage 20 FPS which is strange since changing the fog distance is meant to make FPS go up.
Playing beta software I would accept bugs. I wouldn't expect to be forced to buy a new computer to run the next update because of memory leaks and other nasty things. I can play Amnesia the dark descent on everything to the highest with no lag. Though it isn't a good comparison because Amnesia doesn't run on Java but it gives a good idea of what my graphic card is capable of doing.
He could have not let us play, but then minecraft may not have been heard of and then probably not even finished. Who knows, maybe he would have finished it sooner. It's irrelevant though anyways. What's happened has happened, right? Consequences are consequences. Only time will tell the future.
The only problem I have with this update is that I still can't load a world without crashing. ;D
And I'd rather not revert back to my last backup, which is 1.5_01.
So pretty much you people who can actually DO something should be darn grateful you can actually load a world.
There are a lot of great things about the update. But unfortunately it's almost entirely incomplete and half assed. Villages with no one in them. Strongholds with nothing in them. Experience points that do nothing. Mushroom biomes that don't generate. Etc. Plus, dougs griefing our worlds, and no more F toggle? Some bad decisions here.
Feedback is important, but calling bugfixes a "garbage patch" isn't feedback. It's complaining that Mojang isn't the perfect God-like game devs that everyone praises them as. They can only do so much.
There's a thing called a debugger. It comes with 99% of compilation software. Makes it real easy to find buggy code.
No it doesn't. It's a tool. It makes it easier, not easy. Does a shovel make it "easy" to dig holes? No. it is still backbreaking work. But it's easier than using your bare hands to dig a hole.
Code is organized and has comment tags for a reason.
Yes. And that reason is to make maintenance easier. Comments help while debugging, but they don't do the job for you.
As well as #s for code lines. It's all very simple and there's a method to it.
OK. well then rip open GDB and get cracking fixing these other game-breakers! But really, while there is a method, it's not a silver bullet you can apply to everything. issues that seem to be occuring in one part of the code could be a result of a logic error in a completely different part of the program that causes a violation of an assumed precondition or places data structures in a state for which the other code is not expecting. Breakpoints on the first obvious place do nothing to help, since by that time the buggy code has already executed and the code being examined is perfectly fine. So you end up having to trace back. Warranted, it's all perfectly logical, but it's not always a simple series of steps as you imply. And sometimes the occurence of a bug or issue is so intermittent just finding a condition that will break in the suspect code at the right time can be a massive pain; you can't break into it every single time, otherwise the debugger could easily taint the conditions that cause the intermittent bug to occur; and even if that wasn't the case, who knows how many times the debugger will need to be told to continue execution. And even then, all you've succeeded in doing is confirming that the bug is indeed something in the program (which was already rather obvious) and then begins the painstaking process of tracing what data structures were made inconsistent and how. The simplicity in that last sentence is inversely proportional to how difficult that process can be.
2> My point is he fixed those two things and then fixed nothing else, VS back in may he launched 1.6 and then updated it 4 times that day fixing just as many game breaking crash bugs.
Or maybe they actually released it with relatively fewer game-breaking bugs? the two that were fixed were the only ones I knew about.
That raining through blocks issue seems to only occur in certain circumstances. I haven't been able to find a way to 100% reproduce it, myself.
Why am I the only one who has absolutely no problems at all?
Rollback Post to RevisionRollBack
"It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts."
::Quote from The Adventures of Sherlock Holmes
Why am I the only one who has absolutely no problems at all?
You aren't. I encountered the raining through the roof issue but both time a disconnect/reconnect fixed it. Much like the Missing chunk errors in 1.7.3 and earlier, which I've seen absolutely none of so far. I'm very pleased with this update. And it's running a LOT faster than either of the prereleases, and runs faster on my laptop than 173. (although with only a touchpad I didn't play for very long). Personally this is my favourite update yet. The cave generation has definitely been changed, caves are bigger, there are ravines, the occasional (now, thank goodness) abandoned mineshaft, etc. I've yet to find a stronghold. There are of course a few tiny issues, but the thing is- they already know about it. They're still finishing off some of the stuff for which they've laid a groundwork. Each update doesn't have to be completely cohesive on it's own, it's the final product they are working towards that needs to be cohesive, not the incremental changes working towards that goal.
Because Notch has two new babies now, Cobalt and Scrolls. I think he has lost intrest in Minecraft and left Jeb to do all the work. Notch will occasionally give Jeb an order.
I prefer Jeb's way of doing things and listening to the community and seeing what they want, like the better shader mod and pistons. Notch prefers for everything being his code and his idea. I agree with him with the F key being removed, it's a graphical setting and no graphical changes should be made with a simple keystroke because in theory you only set these once. But that doesn't happen because of the shoggy unoptimised coding peoples perfomance degrades over time which forces them to change the fog level very often which makes the F key a very good idea.
But the F key isn't a fix to peoples problems. Jeb is probably going through alot at the moment because hes got the entire community as well as Notch on his sholders, but atleast hes trying to get this game delieved for MineCon. Though I have my doubts.
Notch is not working on scrolls or cobalt. He's working on minecraft. Mojang is working on scrolls and cobalt, but mojang =/= notch. Notch did take a week to work on a prototype for another project, but that is done, and he is back to minecraft.
There are a lot of great things about the update. But unfortunately it's almost entirely incomplete and half assed. Villages with no one in them. Strongholds with nothing in them. Experience points that do nothing. Mushroom biomes that don't generate. Etc. Plus, dougs griefing our worlds, and no more F toggle? Some bad decisions here.
That is what "half of the adventure update" means. Half of it is not done yet, but they released it early to give people something to play with.
The only complaint I have about the update, is that's it's not in the starting-screen.
So until I know exactly WHAT it is, I'll play on 1.8 Core (at least until the various Mods start to get updated, which looks like it may take a while with a few exceptions)
it fixes crashing with the shift click into full chests and dispensers.
Rollback Post to RevisionRollBack
OG Member of BrenyBeast's private BeastCraft Server
I don't think it's that easy. If it were, programming would probably be a lot easier. There comes a point in software complication when the errors are too complicated for a debugger to give much useful information, and they may be shrouded in things the debugger does not like but are in fact working, but weird, code.
And if you'll recall, the first couple of patches after 1.7 introduced more bugs than they were supposed to fix, and a couple of times did not fix the ones they were claimed to. 1.8.1 is a small, but effective patch and there is nothing to complain about but the things it did not address. If I wanted to whine about the patch job, I'd be asking for a couple more like this, not yelling about how bad it was.
This thread is so poorly thought-out that I fear I may be feeding a troll.
I feel bad for Majong and all who work there. They can't win no matter what they do. Is anything good enough for the children who are on this forum? I think Majong should stop working on it entirely and tell everyone to go **** themselves. Here they are putting out a game AND free updates with more content but still its not good enough. Like I said Majong should call it quits. I'd love to see the kiddies cry and complain on here than. The more they ***** the more I laugh.
This is the worst patch I've seen Mojang put out in a year.
On may 26th, they patched the game 4 times and fixed a ton of bugs. Why is it that this time they fix two bugs and then leave us with no information. :/
I just don't get it. Why the sudden change in policy and quality, Mojang?
Why am I the only one who has absolutely no problems at all?
No problems at all here either and I'm on a laptop with integrated video, dual core CPU, and only 4G ram. Also, 1.8.1 patch fixed my only problem with 1.8; the amazingly poor FPS (12-15 constantly). 1.8.1 brought me back up to 30-40 FPS. So I'm happy. Plus my friend's server is still up and running with no problems, no crashes, and no lag.
I also kinda think this topic should be locked just because it's a trolling topic anyway. It's neither helpful nor useful to have threads that are just full of complaints.
No it doesn't. It's a tool. It makes it easier, not easy. Does a shovel make it "easy" to dig holes? No. it is still backbreaking work. But it's easier than using your bare hands to dig a hole.
Yes. And that reason is to make maintenance easier. Comments help while debugging, but they don't do the job for you.
OK. well then rip open GDB and get cracking fixing these other game-breakers! But really, while there is a method, it's not a silver bullet you can apply to everything. issues that seem to be occuring in one part of the code could be a result of a logic error in a completely different part of the program that causes a violation of an assumed precondition or places data structures in a state for which the other code is not expecting. Breakpoints on the first obvious place do nothing to help, since by that time the buggy code has already executed and the code being examined is perfectly fine. So you end up having to trace back. Warranted, it's all perfectly logical, but it's not always a simple series of steps as you imply. And sometimes the occurence of a bug or issue is so intermittent just finding a condition that will break in the suspect code at the right time can be a massive pain; you can't break into it every single time, otherwise the debugger could easily taint the conditions that cause the intermittent bug to occur; and even if that wasn't the case, who knows how many times the debugger will need to be told to continue execution. And even then, all you've succeeded in doing is confirming that the bug is indeed something in the program (which was already rather obvious) and then begins the painstaking process of tracing what data structures were made inconsistent and how. The simplicity in that last sentence is inversely proportional to how difficult that process can be.
Or maybe they actually released it with relatively fewer game-breaking bugs? the two that were fixed were the only ones I knew about.
That raining through blocks issue seems to only occur in certain circumstances. I haven't been able to find a way to 100% reproduce it, myself.
They have the tools, they even have the money to hire more people, and they have even PROVEN that they can address bugs faster than they are at the moment. Look at the facts, dude. These are not amateurs we're talking about. Notch has a history of programming professionally, and I believe Jeb does too. They have had plenty of bug reports, and plenty of time to fix these bugs. Face it, this update was a failure. It makes them look bad in the eyes of their peers. Not their fan-base, but their peers. Competitors and future prospective employees.
Do you srsly care about them.
It is the parents fault for letting them on this UGH community.
Everytime notch brings a update... WHINE WHINE WHINE WHINE!!!!
No wonder he doesnt feel like working on it, people are gonna whine anyway.
Bah.
Notch is not working on scrolls or cobalt. He's working on minecraft. Mojang is working on scrolls and cobalt, but mojang =/= notch. Notch did take a week to work on a prototype for another project, but that is done, and he is back to minecraft.
That is what "half of the adventure update" means. Half of it is not done yet, but they released it early to give people something to play with.
Notch is working on Scrolls and Cobalt and Minecraft. Too much at one time for such a small dev team.
So if I told you I was gonna give you a chocolate chip cookie in two weeks, and then I said "well, the cookie isn't done yet, I'm only gonna give you half of the cookie" and then two weeks comes and I tell you, "Well, the half of your cookie isn't done yet. Can you wait?" and then when I finally give you that half it's only got one or two chocolate chips on it, how would you feel?
I don't think it's that easy. If it were, programming would probably be a lot easier. There comes a point in software complication when the errors are too complicated for a debugger to give much useful information, and they may be shrouded in things the debugger does not like but are in fact working, but weird, code.
And if you'll recall, the first couple of patches after 1.7 introduced more bugs than they were supposed to fix, and a couple of times did not fix the ones they were claimed to. 1.8.1 is a small, but effective patch and there is nothing to complain about but the things it did not address. If I wanted to whine about the patch job, I'd be asking for a couple more like this, not yelling about how bad it was.
This thread is so poorly thought-out that I fear I may be feeding a troll.
Look at the speed at which Mojang fixed bugs in their previous patches (I supplied the source for you in the OP) and tell me they're still living up to the standard of quality they have set for themselves. Then tell me my CONCERN is unwarranted.
No problems at all here either and I'm on a laptop with integrated video, dual core CPU, and only 4G ram. Also, 1.8.1 patch fixed my only problem with 1.8; the amazingly poor FPS (12-15 constantly). 1.8.1 brought me back up to 30-40 FPS. So I'm happy. Plus my friend's server is still up and running with no problems, no crashes, and no lag.
I also kinda think this topic should be locked just because it's a trolling topic anyway. It's neither helpful nor useful to have threads that are just full of complaints.
So it fixed YOUR problems, so my concerns and problems are now irrelevant to Mojang? Freedom of speech, broski. I has it, so I doubt the thread will be locked. It would look dumb of them to lock a thread in which I stated my opinion and have set and example in not responding to people in a rude manner. Although people, like you, are being quite rude to me.
On may 26th, they patched the game 4 times and fixed a ton of bugs. Why is it that this time they fix two bugs and then leave us with no information. :/
I just don't get it. Why the sudden change in policy and quality, Mojang?
Source:
http://www.minecraftwiki.net/wiki/Version_history
There's a thing called a debugger. It comes with 99% of compilation software. Makes it real easy to find buggy code.
1> Remember this is a forum with a young audience, so I suggest you watch your language.
2> My point is he fixed those two things and then fixed nothing else, VS back in may he launched 1.6 and then updated it 4 times that day fixing just as many game breaking crash bugs.
This is exactly what I'm saying. I'd also like to play the game I paid for, which is not possible on one of my computers (my home computer) so I can only play when I'm in my studio, which is quite unfair to me (and my work ethic.) :wink.gif:
So why is it he only fixed two things and not fixed the lag problems, the un-optimized laggy code, or even better yet, why didn't they just delay the release of 1.8 till it was ready? at least with the pre-releases I could revert back to 1.7.3 if I wanted to.
Code is organized and has comment tags for a reason.
As well as #s for code lines. It's all very simple and there's a method to it. Just like anything else. Just sounds like laziness to me.
He could have not let us play, but then minecraft may not have been heard of and then probably not even finished. Who knows, maybe he would have finished it sooner. It's irrelevant though anyways. What's happened has happened, right? Consequences are consequences. Only time will tell the future.
And I'd rather not revert back to my last backup, which is 1.5_01.
So pretty much you people who can actually DO something should be darn grateful you can actually load a world.
Sounds like Sarah Palin's kids.
Bristol and Trig and Geometry.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNo it doesn't. It's a tool. It makes it easier, not easy. Does a shovel make it "easy" to dig holes? No. it is still backbreaking work. But it's easier than using your bare hands to dig a hole.
Yes. And that reason is to make maintenance easier. Comments help while debugging, but they don't do the job for you.
OK. well then rip open GDB and get cracking fixing these other game-breakers! But really, while there is a method, it's not a silver bullet you can apply to everything. issues that seem to be occuring in one part of the code could be a result of a logic error in a completely different part of the program that causes a violation of an assumed precondition or places data structures in a state for which the other code is not expecting. Breakpoints on the first obvious place do nothing to help, since by that time the buggy code has already executed and the code being examined is perfectly fine. So you end up having to trace back. Warranted, it's all perfectly logical, but it's not always a simple series of steps as you imply. And sometimes the occurence of a bug or issue is so intermittent just finding a condition that will break in the suspect code at the right time can be a massive pain; you can't break into it every single time, otherwise the debugger could easily taint the conditions that cause the intermittent bug to occur; and even if that wasn't the case, who knows how many times the debugger will need to be told to continue execution. And even then, all you've succeeded in doing is confirming that the bug is indeed something in the program (which was already rather obvious) and then begins the painstaking process of tracing what data structures were made inconsistent and how. The simplicity in that last sentence is inversely proportional to how difficult that process can be.
Or maybe they actually released it with relatively fewer game-breaking bugs? the two that were fixed were the only ones I knew about.
That raining through blocks issue seems to only occur in certain circumstances. I haven't been able to find a way to 100% reproduce it, myself.
::Quote from The Adventures of Sherlock Holmes
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYou aren't. I encountered the raining through the roof issue but both time a disconnect/reconnect fixed it. Much like the Missing chunk errors in 1.7.3 and earlier, which I've seen absolutely none of so far. I'm very pleased with this update. And it's running a LOT faster than either of the prereleases, and runs faster on my laptop than 173. (although with only a touchpad I didn't play for very long). Personally this is my favourite update yet. The cave generation has definitely been changed, caves are bigger, there are ravines, the occasional (now, thank goodness) abandoned mineshaft, etc. I've yet to find a stronghold. There are of course a few tiny issues, but the thing is- they already know about it. They're still finishing off some of the stuff for which they've laid a groundwork. Each update doesn't have to be completely cohesive on it's own, it's the final product they are working towards that needs to be cohesive, not the incremental changes working towards that goal.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNotch is not working on scrolls or cobalt. He's working on minecraft. Mojang is working on scrolls and cobalt, but mojang =/= notch. Notch did take a week to work on a prototype for another project, but that is done, and he is back to minecraft.
That is what "half of the adventure update" means. Half of it is not done yet, but they released it early to give people something to play with.
it fixes crashing with the shift click into full chests and dispensers.
And if you'll recall, the first couple of patches after 1.7 introduced more bugs than they were supposed to fix, and a couple of times did not fix the ones they were claimed to. 1.8.1 is a small, but effective patch and there is nothing to complain about but the things it did not address. If I wanted to whine about the patch job, I'd be asking for a couple more like this, not yelling about how bad it was.
This thread is so poorly thought-out that I fear I may be feeding a troll.
How to not die in a cave
It's worse than that I fear. They didn't even write this patch. idshift did.
Which helps me not in the least. My favorite server is still down pending fixes for two more serious crash bugs that kill servers.
No problems at all here either and I'm on a laptop with integrated video, dual core CPU, and only 4G ram. Also, 1.8.1 patch fixed my only problem with 1.8; the amazingly poor FPS (12-15 constantly). 1.8.1 brought me back up to 30-40 FPS. So I'm happy. Plus my friend's server is still up and running with no problems, no crashes, and no lag.
I also kinda think this topic should be locked just because it's a trolling topic anyway. It's neither helpful nor useful to have threads that are just full of complaints.
I would assume you are playing SSP.
SSP works reasonably well currently.
SMP does not.
They have the tools, they even have the money to hire more people, and they have even PROVEN that they can address bugs faster than they are at the moment. Look at the facts, dude. These are not amateurs we're talking about. Notch has a history of programming professionally, and I believe Jeb does too. They have had plenty of bug reports, and plenty of time to fix these bugs. Face it, this update was a failure. It makes them look bad in the eyes of their peers. Not their fan-base, but their peers. Competitors and future prospective employees.
Sounds like you, brah.
Notch is working on Scrolls and Cobalt and Minecraft. Too much at one time for such a small dev team.
So if I told you I was gonna give you a chocolate chip cookie in two weeks, and then I said "well, the cookie isn't done yet, I'm only gonna give you half of the cookie" and then two weeks comes and I tell you, "Well, the half of your cookie isn't done yet. Can you wait?" and then when I finally give you that half it's only got one or two chocolate chips on it, how would you feel?
Look at the speed at which Mojang fixed bugs in their previous patches (I supplied the source for you in the OP) and tell me they're still living up to the standard of quality they have set for themselves. Then tell me my CONCERN is unwarranted.
So it fixed YOUR problems, so my concerns and problems are now irrelevant to Mojang? Freedom of speech, broski. I has it, so I doubt the thread will be locked. It would look dumb of them to lock a thread in which I stated my opinion and have set and example in not responding to people in a rude manner. Although people, like you, are being quite rude to me.