SP: little to no bugs or lag.
MP: plenty of bugs and lag.
If you had to get rid of one, which would you keep.
Oh. and the LAN thing doesn't do anything for me as I'm the only one who plays minecraft in my house. How many people actualy have more than 2 people who both play multiplayer and live in the same house. (ie: in the same LAN network)
Me, wife and 2 kids. Or kids and their friends. I run a server of my desktop, and our laptops run as clients, down to a 512MB Toshiba w/ Intel Graphics back from the Middle Dynasty or something. It actually works, and while the low-end pc's are jumpy, moving the server to another pc takes a lot of load from them.
I always play running a separate server process (w23b) on this rig, a Core2Dou with 4 GB ram and ATI 6970 graphics. DaxNitros shader mod made it jump a bit in 1.2.5, but other than that I am getting very smooth running using a 256px texpack, using MCpatcher over optifine.
Mojang is only a small company with little many coders everyone will complain if Mojang sold out and sold Minecraft to a multi-millionaire company where we may not have ANY say whatsoever of the game, the community is SO PICKY it's unbelievable, Mojang are trying to fix the majority of the severe bugs in SP before they have main focus on SMP, not saying they haven't done a dime on SMP because they have, if you read Notchs blog you would of read all of this, just because you CANT SEE IT doesn't mean that it hasn't been fixed, it's the members of community that say that Mojang are lazy, when they have done alot more then you expected, don't like it, don't play it.
Yeeeaaahhhh, see, that's called: "Not a valid excuse".
I've watched SMALLER devs with LESS MONEY (alot less money, actually, nowhere even close to Mojang's) and LESS MANPOWER fix LARGER BUGS more OFTEN. I follow quite alot of indie devs, and this sort of thing works for many of them.
The problem isnt laziness. The PROBLEM is them adding more new features..... ***BEFORE*** they fixed the broken old ones. It's really not a very bright move, particularly considering the nature of some of these new features, which can cause old bugs to get EVEN BUGGIER. They should never have started this stupid merge untill AFTER they had fixed the extremely numerous (and in many cases, extremely old) bugs that SMP was full of. WHY they went and did so anyway, without doing that, is beyond me (and frankly, I'd rather not know).
I mean, they started in on this..... and then suddenly, with it half done and pieces still broken and sparking left and right, Jeb suddenly throws in a couple of extra content features. It's like.... wait, what? Why are you doing that NOW, instead of finishing what you started first?
Well. It hasnt actually happened yet. Its just in snapshots which are designed to T E S T this stuff before official release.
so you know, think about that before you go on a winge binge.
Now if 1.3 was out and it was cr^p and buggy as hell. Then you can go on...
Yes, I know this. I've done beta testing of much buggier games, but again, those games would get bugs fixed BEFORE new and potentially buggier content was added.
Also, it seems like this is one of the last snapshots before 1.3 (or so I keep hearing), and if so, that's a...... problem, so to speak.
Also..... considering that this IS testing, there's been, well...... very little proper response to all of the bugs. Quite alot of people are testing these snapshots. The presence of each bug has become EXTREMELY obvious by this point. Yet still, a new snapshot, and.... "Hey, can place redstone on upside down stairs or something now! :D", instead of progress in removing the bugs that everyone has been now screaming about for weeks. That's NOT a good thing.
If mojang had fixed most of th bugs before the merge, then the merge would not have happened for years and years. Doing the merge earlier is better than doing it later. The earlier they do the merge, the faster they can squash bugs.
If mojang had fixed most of th bugs before the merge, then the merge would not have happened for years and years. Doing the merge earlier is better than doing it later. The earlier they do the merge, the faster they can squash bugs.
I doubt that, it's all about priority. It would take less time if they focused on bugs instead of wandering around almost aimlessly putting their work into whatever random things they feel like.
The problem isnt laziness. The PROBLEM is them adding more new features..... ***BEFORE*** they fixed the broken old ones. It's really not a very bright move, particularly considering the nature of some of these new features, which can cause old bugs to get EVEN BUGGIER. They should never have started this stupid merge untill AFTER they had fixed the extremely numerous (and in many cases, extremely old) bugs that SMP was full of. WHY they went and did so anyway, without doing that, is beyond me (and frankly, I'd rather not know).
I'm terribly sorry, but where are these bugs that are apparently so egregious in official releases? It feels like I'm playing a different game because I've encountered extremely few harmful bugs. Besides, Mojang is constantly fixing bugs with each snapshot and release.
I mean, they started in on this..... and then suddenly, with it half done and pieces still broken and sparking left and right, Jeb suddenly throws in a couple of extra content features. It's like.... wait, what? Why are you doing that NOW, instead of finishing what you started first?
These finer content additions are negligible. I imagine Jeb might want a break from working on the merge, so of course it makes sense to work on other things momentarily. Whether he works on it now or later is still the same amount of time used, and 1.3 would feel rather lackluster for many Minecrafters received no new content with it.
Also..... considering that this IS testing, there's been, well...... very little proper response to all of the bugs. Quite alot of people are testing these snapshots. The presence of each bug has become EXTREMELY obvious by this point. Yet still, a new snapshot, and.... "Hey, can place redstone on upside down stairs or something now! ", instead of progress in removing the bugs that everyone has been now screaming about for weeks. That's NOT a good thing.
You are aware that different members of Molang handle different pieces of the game, right? Whilst Jeb was continuing to work on the merge Dinnerbone added in the redstone and upper half-slab/upside down staircase thing. What efficiency Mojang does display is far from bad, I assure you.
I doubt that, it's all about priority. It would take less time if they focused on bugs instead of wandering around almost aimlessly putting their work into whatever random things they feel like.
Well, he's mostly right actually. By implementing the merge now, fixing a bug later wipes it off the board for both SP and MP. It is more intelligent to commit the merge first.
So strange. Every snapshot I play has NO LAG whatsoever.
I honestly can't see the issue, and many people reporting lag have better computers than I do.
I have the same kind of experience; it's hard to discuss the quality of Minecraft when something like this pops up.
Rollback Post to RevisionRollBack
"Victory is like a watermelon. It's hard to spell and it tastes good."
Well, he's mostly right actually. By implementing the merge now, fixing a bug later wipes it off the board for both SP and MP. It is more intelligent to do commit the merge first.
Oh yeah, duh. xD
I guess I meant more of getting rid of bugs before adding new content, merge is a given.
SP: little to no bugs or lag.
MP: plenty of bugs and lag.
If you had to get rid of one, which would you keep.
Well, considering SP got lonely and boring within the first month of playing while I still have fun with MP 1 1/2 years later despite bugs and such...screw SP.
Rollback Post to RevisionRollBack
My Spigot/CraftBukkit plugins: TallNether - Generate a 256-block high nether
I guess I meant more of getting rid of bugs before adding new content, merge is a given.
New features tend to introduce more bugs as well, so its a real balancing act when it comes to planning. Since the merge changes the framework, and will probably generate all kind of issues, bug fixing everything from 1.2.5 THEN doing the merge would had been a waste of time.
Testing the most recent week 26 snapshot, I can report that there has been a great improvement in mob lag and terrain generation lag over any of the previous 1.3 pre-releases. It's still there slightly there for the mobs causing slight delays in knockback, which is noticable compared to 1.2.5 single player which had no lag of any kind for me - running far view distance, fancy graphics and an HD texture pack.
The more irksome thing I am finding is that there are all sorts of visual/lighting glitches that have previously only been confined to multiplayer. When generating new chunks you often get a terrible mish-mash of pitch black overhangs that don't update until you move into them and large patches of see through ground/chunk errors.
Hopefully, these issues will be fixed before the official release. Then both single and multiplayer will be more equal in terms of performance.
I have the same kind of experience; it's hard to discuss the quality of Minecraft when something like this pops up.
Indeed, good sir. I mean, my PC is pretty good (I designed and built it myself!), but I certain don't consider it a high-end rig.
Despite this, people with significantly better rigs than mine are having huge lag issues. I think it comes down to the Windows/Java environments. I used to have a hard time with HD texture packs until I reinstalled Windows and Java. Not a hiccup since. :3
Rollback Post to RevisionRollBack
The Internet is a big place, friend. I've been places you've n͍̺e̩v̦e̦̰͍͓̩ͅr̜̭̝̬̬͉̤̬ ͙ịm̖͇a͍͇̤͙̥g̤̘i͔͖̤̼̪̬n͖͔̳̬̯e̩̘ḓ͈͔̠̙͇̼̯.͎
The more irksome thing I am finding is that there are all sorts of visual/lighting glitches that have previously only been confined to multiplayer. When generating new chunks you often get a terrible mish-mash of pitch black overhangs that don't update until you move into them and large patches of see through ground/chunk errors.
Hopefully, these issues will be fixed before the official release. Then both single and multiplayer will be more equal in terms of performance.
Dang! those are some of the worst examples of that that I've seen. I'm having the same issue though, the game runs great for me me, no lag or low fps; but those lighting glitches are killing me. I see a lot of people saying they were in SMP before now, but I've never seen them before the 1.3 snapshots.
I find it weird how every update the glitches only get stranger, just like that snapshot they added jungles and the head in your inventory would point south or w/e so half the time your head would be backwards or the flying squid which we still have.
..or that /kill doesn't kill me in creative, which might be intentional but kind of funny:
Edit: okay, it doesn't work in survival either, wtf mojang..
guys relax remember this is a snapshot not the officiail (bad spelling is bad) update and if it was the 1.3 update...... ok just imagine this if every snapshot was an update that shown on the minecraft launcher then you would not have that much time to play the snapshots (and what mean when i said that if every snapshot was an update i meant officail update) oh and that see through unloaded chunks bug you just could just use that to find diamods and bassically even though jeb "broke minecraft" i still like it minecraft is minecraft no matter what oh and just one more thing if you have alot of HUGE worlds in minecraft than thats proboly whats causing that problem with your minecraft running slowly ok so heres some diamonds
The lighting issues are really starting to **** me off, Jeb and Nathan have thus far neglected the bug, and have shown no signs of even acknowledging it exists.
But whoop de do, ("guess what? It's a hardware problem, not a update problem, your computer just sucks!") or ("It will be fixed in the next snapshot anyway!") This is how the minecraft community responds to everything wrong with their precious game, I have seen these two arguments time and time again on the forums, in relation to the lighting bug.
I don't like to brag about my PC specs, but lets just say I can more than handle any game at max settings. Secondly, every thread that acknowledges a bug gets shot down, with the OP getting belittled. The snapshots are here for testing and reporting bugs, not pretending they don't exist.
Further more, almost every week for the last 5 or 6 weeks (who is keeping track?) I've seen someone say "they will fix X bug in the next snapshot, stop crying". Clearly Mojang isn't going to fix these bugs if everyone keeps quiet about it.
Indeed, good sir. I mean, my PC is pretty good (I designed and built it myself!), but I certain don't consider it a high-end rig.
Despite this, people with significantly better rigs than mine are having huge lag issues. I think it comes down to the Windows/Java environments. I used to have a hard time with HD texture packs until I reinstalled Windows and Java. Not a hiccup since. :3
I think this is the real problem as well. My computer is not that great, yet I've seen literally no change at all from the merge. My SP plays just like it always did. If you have a decent computer and you're still having problems, you might want to check for software issues.
When so many people get so many different results, it's probably not Minecraft that's the issue, folks.
MP: plenty of bugs and lag.
If you had to get rid of one, which would you keep.
Oh. and the LAN thing doesn't do anything for me as I'm the only one who plays minecraft in my house. How many people actualy have more than 2 people who both play multiplayer and live in the same house. (ie: in the same LAN network)
I always play running a separate server process (w23b) on this rig, a Core2Dou with 4 GB ram and ATI 6970 graphics. DaxNitros shader mod made it jump a bit in 1.2.5, but other than that I am getting very smooth running using a 256px texpack, using MCpatcher over optifine.
Yeeeaaahhhh, see, that's called: "Not a valid excuse".
I've watched SMALLER devs with LESS MONEY (alot less money, actually, nowhere even close to Mojang's) and LESS MANPOWER fix LARGER BUGS more OFTEN. I follow quite alot of indie devs, and this sort of thing works for many of them.
The problem isnt laziness. The PROBLEM is them adding more new features..... ***BEFORE*** they fixed the broken old ones. It's really not a very bright move, particularly considering the nature of some of these new features, which can cause old bugs to get EVEN BUGGIER. They should never have started this stupid merge untill AFTER they had fixed the extremely numerous (and in many cases, extremely old) bugs that SMP was full of. WHY they went and did so anyway, without doing that, is beyond me (and frankly, I'd rather not know).
I mean, they started in on this..... and then suddenly, with it half done and pieces still broken and sparking left and right, Jeb suddenly throws in a couple of extra content features. It's like.... wait, what? Why are you doing that NOW, instead of finishing what you started first?
Yes, I know this. I've done beta testing of much buggier games, but again, those games would get bugs fixed BEFORE new and potentially buggier content was added.
Also, it seems like this is one of the last snapshots before 1.3 (or so I keep hearing), and if so, that's a...... problem, so to speak.
Also..... considering that this IS testing, there's been, well...... very little proper response to all of the bugs. Quite alot of people are testing these snapshots. The presence of each bug has become EXTREMELY obvious by this point. Yet still, a new snapshot, and.... "Hey, can place redstone on upside down stairs or something now! :D", instead of progress in removing the bugs that everyone has been now screaming about for weeks. That's NOT a good thing.
I'm terribly sorry, but where are these bugs that are apparently so egregious in official releases? It feels like I'm playing a different game because I've encountered extremely few harmful bugs. Besides, Mojang is constantly fixing bugs with each snapshot and release.
These finer content additions are negligible. I imagine Jeb might want a break from working on the merge, so of course it makes sense to work on other things momentarily. Whether he works on it now or later is still the same amount of time used, and 1.3 would feel rather lackluster for many Minecrafters received no new content with it.
You are aware that different members of Molang handle different pieces of the game, right? Whilst Jeb was continuing to work on the merge Dinnerbone added in the redstone and upper half-slab/upside down staircase thing. What efficiency Mojang does display is far from bad, I assure you.
Well, he's mostly right actually. By implementing the merge now, fixing a bug later wipes it off the board for both SP and MP. It is more intelligent to commit the merge first.
I have the same kind of experience; it's hard to discuss the quality of Minecraft when something like this pops up.
I guess I meant more of getting rid of bugs before adding new content, merge is a given.
Well, considering SP got lonely and boring within the first month of playing while I still have fun with MP 1 1/2 years later despite bugs and such...screw SP.
My Spigot/CraftBukkit plugins:
TallNether - Generate a 256-block high nether
FarLandsAgain - Restores the Far Lands
User: *BOOM* You're dead.
Cleverbot: I divide by zero and come back as an angel ninja.
New features tend to introduce more bugs as well, so its a real balancing act when it comes to planning. Since the merge changes the framework, and will probably generate all kind of issues, bug fixing everything from 1.2.5 THEN doing the merge would had been a waste of time.
The more irksome thing I am finding is that there are all sorts of visual/lighting glitches that have previously only been confined to multiplayer. When generating new chunks you often get a terrible mish-mash of pitch black overhangs that don't update until you move into them and large patches of see through ground/chunk errors.
Hopefully, these issues will be fixed before the official release. Then both single and multiplayer will be more equal in terms of performance.
They took 40 blocks. That’s as many as four tens. And that’s horrible.
Indeed, good sir. I mean, my PC is pretty good (I designed and built it myself!), but I certain don't consider it a high-end rig.
Despite this, people with significantly better rigs than mine are having huge lag issues. I think it comes down to the Windows/Java environments. I used to have a hard time with HD texture packs until I reinstalled Windows and Java. Not a hiccup since. :3
Dang! those are some of the worst examples of that that I've seen. I'm having the same issue though, the game runs great for me me, no lag or low fps; but those lighting glitches are killing me. I see a lot of people saying they were in SMP before now, but I've never seen them before the 1.3 snapshots.
..or that /kill doesn't kill me in creative, which might be intentional but kind of funny:
Edit: okay, it doesn't work in survival either, wtf mojang..
(Kyoshinda whats your texture pack?)
@darthmauler: I had those graphical glitches in sp too, before the merge.
But whoop de do, ("guess what? It's a hardware problem, not a update problem, your computer just sucks!") or ("It will be fixed in the next snapshot anyway!") This is how the minecraft community responds to everything wrong with their precious game, I have seen these two arguments time and time again on the forums, in relation to the lighting bug.
I don't like to brag about my PC specs, but lets just say I can more than handle any game at max settings. Secondly, every thread that acknowledges a bug gets shot down, with the OP getting belittled. The snapshots are here for testing and reporting bugs, not pretending they don't exist.
Further more, almost every week for the last 5 or 6 weeks (who is keeping track?) I've seen someone say "they will fix X bug in the next snapshot, stop crying". Clearly Mojang isn't going to fix these bugs if everyone keeps quiet about it.
When so many people get so many different results, it's probably not Minecraft that's the issue, folks.
Don't be an idiot.