The last 3 updates 1.5, 1.6, and now 1.7 have had some really serious bugs in them making things rather difficult for users. The current trend warns me to stay away from the updates until they settle down.
Some of these bugs especially this last update where a certain kind of crash will not allow you to use your world is pretty serious.
Serious enough of a bug to have been tested for before release of the update.
It seems to me if Notch does not have the equipment or time needed for proper testing then maybe he should put together a testing team to minimize bugs before each release.
This added testing would only cost an extra week and add a tremendous amount of class to his operation.
Plus I am quite sure volunteers for pre-release testing would not be hard to find.
Rollback Post to RevisionRollBack
A Fan-Boy never admits anything bad about his favorite game.
If a game in production were the Titanic ocean liner, a Fan-Boy would not admit the ship was sinking even when his feet were getting wet.
The last 3 updates 1.5, 1.6, and now 1.7 have had some really serious bugs in them making things rather difficult for users. The current trend warns me to stay away from the updates until they settle down.
Some of these bugs especially this last update where a certain kind of crash will not allow you to use your world is pretty serious.
Serious enough of a bug to have been tested for before release of the update.
It seems to me if Notch does not have the equipment or time needed for proper testing then maybe he should put together a testing team to minimize bugs before each release.
This added testing would only cost an extra week and add a tremendous amount of class to his operation.
Plus I am quite sure volunteers for pre-release testing would not be hard to find.
The people how play minecraft now are the testers to some degree. You have to remember minecraft is not a complete game yet, so just players are the testers.
The people how play minecraft now are the testers to some degree. You have to remember minecraft is not a complete game yet, so just players are the testers.
BIG bugs which ruin worlds or other really dumb stuff should be chased down before release to the general public. This is just good programming practice.
You don't just throw something out there and hope it works ok, General public "testing" or not.
Rollback Post to RevisionRollBack
A Fan-Boy never admits anything bad about his favorite game.
If a game in production were the Titanic ocean liner, a Fan-Boy would not admit the ship was sinking even when his feet were getting wet.
You may notice from the Minecraft version history that every update comes with bugs. This happens with every game, you just don't see it because most developers aren't nice enough to let you play the beta.
You may also notice that every update is followed almost immediately by bug fixes. No one can be 100% sure where the bugs will show up, and the best way to test the game is to release it to everyone that plays the game, in the form of the updates you get to enjoy. No matter how many testers you get, they will never find the bugs as fast as when everyone is testing at the same time.
So your choices are as follows:
A.) Require the updates to take far longer and risk having the update occur with the more hidden bugs still intact, or..
B.) Play the game as the Beta that it is and get on with your life. The current system is the most efficient.
Rollback Post to RevisionRollBack
Quote from Berginator94 »
I'm almost 100% positive that this have been suggested before but i'll suggest it again anyways
Yeah right, 1,000,000 people getting their worlds ruined or other crap. The first ten can find the big stuff. Let everyone else find the little stuff.
Why is it the stupid know-it-all YES FANS have to turn everything I say into something wrong?
I have a right to my opinion and every single statement is never as wrong as that.
Stupid know-it-all YES FANS never help a BETA.
They do nothing but tell people how wasteful it was to comment and nothing more.
Rollback Post to RevisionRollBack
A Fan-Boy never admits anything bad about his favorite game.
If a game in production were the Titanic ocean liner, a Fan-Boy would not admit the ship was sinking even when his feet were getting wet.
Yeah right, 1,000,000 people getting their worlds ruined or other crap. The first ten can find the big stuff. Let everyone else find the little stuff.
Why is it the stupid know-it-all YES FANS have to turn everything I say into something wrong?
I have a right to my opinion and every single statement is never as wrong as that.
Stupid know-it-all YES FANS never help a BETA.
They do nothing but tell people how wasteful it was to comment and nothing more.
1.7_0: Bug causes worlds to crash.
1.7_1: Crashed worlds are loadable again.
1.7_2: Crashed worlds now work again.
And that took.. a day? Two? You ARE a Beta tester. That's what you payed for. That's why you're not paying full-price.
Rollback Post to RevisionRollBack
Quote from Berginator94 »
I'm almost 100% positive that this have been suggested before but i'll suggest it again anyways
To post a comment, please login or register a new account.
Some of these bugs especially this last update where a certain kind of crash will not allow you to use your world is pretty serious.
Serious enough of a bug to have been tested for before release of the update.
It seems to me if Notch does not have the equipment or time needed for proper testing then maybe he should put together a testing team to minimize bugs before each release.
This added testing would only cost an extra week and add a tremendous amount of class to his operation.
Plus I am quite sure volunteers for pre-release testing would not be hard to find.
If a game in production were the Titanic ocean liner, a Fan-Boy would not admit the ship was sinking even when his feet were getting wet.
The people how play minecraft now are the testers to some degree. You have to remember minecraft is not a complete game yet, so just players are the testers.
BIG bugs which ruin worlds or other really dumb stuff should be chased down before release to the general public. This is just good programming practice.
You don't just throw something out there and hope it works ok, General public "testing" or not.
If a game in production were the Titanic ocean liner, a Fan-Boy would not admit the ship was sinking even when his feet were getting wet.
You may also notice that every update is followed almost immediately by bug fixes. No one can be 100% sure where the bugs will show up, and the best way to test the game is to release it to everyone that plays the game, in the form of the updates you get to enjoy. No matter how many testers you get, they will never find the bugs as fast as when everyone is testing at the same time.
So your choices are as follows:
A.) Require the updates to take far longer and risk having the update occur with the more hidden bugs still intact, or..
B.) Play the game as the Beta that it is and get on with your life. The current system is the most efficient.
Try 1,000,000 people will find that 10 won't
lol
THis man SPEAKS THE TRUTH!
Yeah right, 1,000,000 people getting their worlds ruined or other crap. The first ten can find the big stuff. Let everyone else find the little stuff.
Why is it the stupid know-it-all YES FANS have to turn everything I say into something wrong?
I have a right to my opinion and every single statement is never as wrong as that.
Stupid know-it-all YES FANS never help a BETA.
They do nothing but tell people how wasteful it was to comment and nothing more.
If a game in production were the Titanic ocean liner, a Fan-Boy would not admit the ship was sinking even when his feet were getting wet.
1.7_0: Bug causes worlds to crash.
1.7_1: Crashed worlds are loadable again.
1.7_2: Crashed worlds now work again.
And that took.. a day? Two? You ARE a Beta tester. That's what you payed for. That's why you're not paying full-price.