Is anyone having problems with this snapshot?
For be it just freezes to the loading screen... :/
This could be if you put the snapshot Minecraft.zip into the .minecraft/bin directory renamed as minecraft.jar . If so, unzip it and use the file in the zip instead.
My advice to Mojang is to bring up the failure reason from the .minecraft/server/server.log when a single player connection attempt does not work. Otherwise you will have people wanting a simple gaming experience having to wander through log files and command prompts.
The connection stuff is kinda annoying and all, but who else wishes they would fix the large biome generation soon? I want to play this snapshot, but the biomes end up clashing with each other and you get those weird cutoffs of biomes (just like when you wanted to play your 1.7.3 world in 1.8). This is the biggest problem I have with this snapshot. Please let the next snapshot have at least this fixed.
snapshot works fine for me, except for one bug: once in hardcore mode, when I logged in I respawned at spawn with no inventory, and everything I had on previously was gone forever. My guess is that the server created me as a second player, but the single player mode could only support one player.
Guys calm down, this is just a snapshot. If you're unhappy with how Minecraft is for you right now, just go back to 1.2.5! Simple as that!
I would except for the fact that they stuck a client/server setup for single player game play.
On another note, I noticed another bug or two at lunch today. Mobs and villagers are walking through blocks half way and poping out suddenly. Also when I break stuff up with a pick it disappears as it falls to the ground but I can still pick it up if I run over it. This will make things that drop longer distances or in to uncontrolled water currents almost impossible to retrieve.
So many bugs I never had in single player before. Ah well if I find more I'll post it here.
I have no idea why some of you are crying about lag on smp with this .jar, because I have a 400MB server and it has NO LAG at all...
Although one thing I noticed is when you go into the nether or the end it does a weird spazzy thing.
I have no idea why some of you are crying about lag on smp with this .jar, because I have a 400MB server and it has NO LAG at all...
Although one thing I noticed is when you go into the nether or the end it does a weird spazzy thing.
I have no problems with SMP.. it's the SSP I have issues with. Epecially since I'm getting SMP game play experience in SSP. There is no reason for a client/server setup for a single player game mode.
Ughh these idiots are still going on about how they hate minecraft because theyre making it better but encounter a few major issues that will probably be fixed tomorrow... =/
Ughh these idiots are still going on about how they hate minecraft because theyre making it better but encounter a few major issues that will probably be fixed tomorrow... =/
Nobody said they hated minecraft. If anything they love Minecraft SSP as it currently is without the need of a local server. Why? because the code for servers is buggy which causes performance and gameplay issues. Even local servers have latency issues and performance problems. This isn't even getting into the muiltiplayer bugs that have been here years.
So they are going to fix 2 years worth of server and muiltiplayer bugs in just 1 week? You sure?
I'm sorry but insulting other posters because they don't want too see Minecraft SSP become laggy and filled with bugs is hardly constructive considering it is a valid complaint. No one asked for SSP to be scrapped and replaced with SMP local server mode. Why scrap a version of SSP that works in favour for one thats filled with bugs/lag?
There is no excuse for high latency in the "Single player mode" of any game. Nor should there be latency issues on local servers. Many games update their single player and muiltiplayer modes without conflicts or forcing single players onto local servers. Why exactly should minecraft be treaty any differently?
If its not broken don't fix it. Local servers should be optional and SSP should be single player without servers like every other game out there that has a single player mode.
Im sorry but I get very angry when I see people complaining about something that has hardly been touched on yet...
If everyone will experience SMP bugs jeb deff will try and get most of them fixed. Both him and you know the bugs and if you were in jebs feet and wanted to have only one thing to update instead of 2 (SMP and SSP) then Im sure ud try to fix them too, not just leave it there and have the entire community complain.
Im sorry but I get very angry when I see people complaining about something that has hardly been touched on yet...
If everyone will experience SMP bugs jeb deff will try and get most of them fixed. Both him and you know the bugs and if you were in jebs feet and wanted to have only one thing to update instead of 2 (SMP and SSP) then Im sure ud try to fix them too, not just leave it there and have the entire community complain.
People also get upset when something that just works gets tossed out in favor of something that doesn't work. As for hardly being touched on, yanking out the entire single player code base to replace it with a client/server setup is no small feet. On stable the terrain renders near instanly to visual range and on this test snapshot the terrain takes a minute or two to render because of client/server interactions.
Also on ever update since I started playing in alpha (including snapshots) there have never been chunk errors in my game in single player. This update has introduced those to my game play. I have to log out and log back in to a single player game in order to render things correctly.
The complaints are there for a reason, people are concerned this will make it in to live. Without feedback Jeb and the others will never know how things really work on other peoples machines when they make changes like this.
The complaints are there for a reason, people are concerned this will make it in to live. Without feedback Jeb and the others will never know how things really work on other peoples machines when they make changes like this.
I can appreciate legitimate complaints that point out specific bugs and a way to reproduce those bugs, along with a reasoned dispute over a design philosophy based upon years of experience and knowledge about the topic in question. I don't think Mojang is some sort of Valhalla full of gods that can do no wrong. They are most certainly human and can make some mistakes, where I've certainly seen some real nasty bugs pop up over the time I've been involved with Minecraft.
What I can't stand is sheer ignorance or resistance to change simply because it is a change, and an apparent unwillingness to even consider why something is being done, such as what I am seeing with those voicing opposition to the SSP/SMP merger as well as other changes in the game.
I'll also point out that the old way of doing "single player" really didn't work very well. It was buggy and kludged together... or perhaps you could say that the server stuff was kludged together as an afterthought. Either way, trying to make Minecraft simultaneously a single player console-like game and a multi-player interactive game was not working out very well and really didn't work. Quite often fixing bugs for either "single player" or "multi-player" introduced new bugs into one or the other and sometimes both. I suppose that Mojang could have simply said that multi-player content was a bad idea and thrown out all of the client/server code entirely, but I don't see that as a reasonable solution.
On the positive side, all of these changes are forcing the Minecraft development team (now that there is more than just Notch doing the development) to re-evaluate all of the subroutines which cover the client-server interactions and solidifying all of the details of that interaction into a solid code base. Stuff is going to break when this happens, but what these developers at Mojang are doing is a much cleaner design and something that is much less likely to create bugs in the future. Bugs which show up only for SSP or only for SMP will be a thing of the past.
You may say that this "works", but I argue that it "just barely works". The Minecraft development team can spend the rest of this year trying to fight each other doing bug fixes slowly by keeping separate single and multi player interactions in the software, or they can start to implement new features like allowing worlds up to 65k blocks high or putting in completely new content. I would rather than Minecraft get out of the bug squishing stage, which is precisely where it will be stuck for the next year or two if this effort for unifying the code didn't happen. Keeping this stuff separate is an accident waiting to happen and is in fact one of the sources for a great many bugs in the game.
That the transition process of making single player interactions happen through TCP/IP packets on a local host server is going to be rough, I will appreciate that. I'm just glad that the issues being raised are happening with the ordinary snapshots rather than something only being discovered on the formal release versions. That is a good thing and one of the reasons why the snapshots are being done at all. Pound on the snapshot and find out what doesn't work... but complaining that this is something different so it must be bad is just being ignorant.
Also on ever update since I started playing in alpha (including snapshots) there have never been chunk errors in my game in single player. This update has introduced those to my game play. I have to log out and log back in to a single player game in order to render things correctly.
Woah you had a,CHUNK ERROR? Woah! Thats so hoirrible! It mustve been so much trouble logging off then back on again! Im suprised that you made it! Omg i just cant believe it, a CHUNK ERROR!!!? You mustve been the first man in history to discover a chunk error! Someone should write a book about you: The Man Who Had To Log Off Then Back On To Get Rid Of A Chunk Error.
This could be if you put the snapshot Minecraft.zip into the .minecraft/bin directory renamed as minecraft.jar . If so, unzip it and use the file in the zip instead.
You may need to diagnose a problem with the single player server using its log file in .minecraft/server/server.log .
I have some issues and fixes on this thread: http://www.minecraftforum.net/topic/1221077-12w19a-launcher-issues-and-solutions
My advice to Mojang is to bring up the failure reason from the .minecraft/server/server.log when a single player connection attempt does not work. Otherwise you will have people wanting a simple gaming experience having to wander through log files and command prompts.
You can get one too!
>> ** <<
How Will The Mods Work!?!?!?!?!? >.<
CLICK>>>
I would except for the fact that they stuck a client/server setup for single player game play.
On another note, I noticed another bug or two at lunch today. Mobs and villagers are walking through blocks half way and poping out suddenly. Also when I break stuff up with a pick it disappears as it falls to the ground but I can still pick it up if I run over it. This will make things that drop longer distances or in to uncontrolled water currents almost impossible to retrieve.
So many bugs I never had in single player before. Ah well if I find more I'll post it here.
Although one thing I noticed is when you go into the nether or the end it does a weird spazzy thing.
I have no problems with SMP.. it's the SSP I have issues with. Epecially since I'm getting SMP game play experience in SSP. There is no reason for a client/server setup for a single player game mode.
I got this from signature craft!
Nobody said they hated minecraft. If anything they love Minecraft SSP as it currently is without the need of a local server. Why? because the code for servers is buggy which causes performance and gameplay issues. Even local servers have latency issues and performance problems. This isn't even getting into the muiltiplayer bugs that have been here years.
So they are going to fix 2 years worth of server and muiltiplayer bugs in just 1 week? You sure?
I'm sorry but insulting other posters because they don't want too see Minecraft SSP become laggy and filled with bugs is hardly constructive considering it is a valid complaint. No one asked for SSP to be scrapped and replaced with SMP local server mode. Why scrap a version of SSP that works in favour for one thats filled with bugs/lag?
There is no excuse for high latency in the "Single player mode" of any game. Nor should there be latency issues on local servers. Many games update their single player and muiltiplayer modes without conflicts or forcing single players onto local servers. Why exactly should minecraft be treaty any differently?
If its not broken don't fix it. Local servers should be optional and SSP should be single player without servers like every other game out there that has a single player mode.
If everyone will experience SMP bugs jeb deff will try and get most of them fixed. Both him and you know the bugs and if you were in jebs feet and wanted to have only one thing to update instead of 2 (SMP and SSP) then Im sure ud try to fix them too, not just leave it there and have the entire community complain.
People also get upset when something that just works gets tossed out in favor of something that doesn't work. As for hardly being touched on, yanking out the entire single player code base to replace it with a client/server setup is no small feet. On stable the terrain renders near instanly to visual range and on this test snapshot the terrain takes a minute or two to render because of client/server interactions.
Also on ever update since I started playing in alpha (including snapshots) there have never been chunk errors in my game in single player. This update has introduced those to my game play. I have to log out and log back in to a single player game in order to render things correctly.
The complaints are there for a reason, people are concerned this will make it in to live. Without feedback Jeb and the others will never know how things really work on other peoples machines when they make changes like this.
I can appreciate legitimate complaints that point out specific bugs and a way to reproduce those bugs, along with a reasoned dispute over a design philosophy based upon years of experience and knowledge about the topic in question. I don't think Mojang is some sort of Valhalla full of gods that can do no wrong. They are most certainly human and can make some mistakes, where I've certainly seen some real nasty bugs pop up over the time I've been involved with Minecraft.
What I can't stand is sheer ignorance or resistance to change simply because it is a change, and an apparent unwillingness to even consider why something is being done, such as what I am seeing with those voicing opposition to the SSP/SMP merger as well as other changes in the game.
I'll also point out that the old way of doing "single player" really didn't work very well. It was buggy and kludged together... or perhaps you could say that the server stuff was kludged together as an afterthought. Either way, trying to make Minecraft simultaneously a single player console-like game and a multi-player interactive game was not working out very well and really didn't work. Quite often fixing bugs for either "single player" or "multi-player" introduced new bugs into one or the other and sometimes both. I suppose that Mojang could have simply said that multi-player content was a bad idea and thrown out all of the client/server code entirely, but I don't see that as a reasonable solution.
On the positive side, all of these changes are forcing the Minecraft development team (now that there is more than just Notch doing the development) to re-evaluate all of the subroutines which cover the client-server interactions and solidifying all of the details of that interaction into a solid code base. Stuff is going to break when this happens, but what these developers at Mojang are doing is a much cleaner design and something that is much less likely to create bugs in the future. Bugs which show up only for SSP or only for SMP will be a thing of the past.
You may say that this "works", but I argue that it "just barely works". The Minecraft development team can spend the rest of this year trying to fight each other doing bug fixes slowly by keeping separate single and multi player interactions in the software, or they can start to implement new features like allowing worlds up to 65k blocks high or putting in completely new content. I would rather than Minecraft get out of the bug squishing stage, which is precisely where it will be stuck for the next year or two if this effort for unifying the code didn't happen. Keeping this stuff separate is an accident waiting to happen and is in fact one of the sources for a great many bugs in the game.
That the transition process of making single player interactions happen through TCP/IP packets on a local host server is going to be rough, I will appreciate that. I'm just glad that the issues being raised are happening with the ordinary snapshots rather than something only being discovered on the formal release versions. That is a good thing and one of the reasons why the snapshots are being done at all. Pound on the snapshot and find out what doesn't work... but complaining that this is something different so it must be bad is just being ignorant.
Version 2.1 now updated for MC 1.6.2
Woah you had a,CHUNK ERROR? Woah! Thats so hoirrible! It mustve been so much trouble logging off then back on again! Im suprised that you made it! Omg i just cant believe it, a CHUNK ERROR!!!? You mustve been the first man in history to discover a chunk error! Someone should write a book about you: The Man Who Had To Log Off Then Back On To Get Rid Of A Chunk Error.
XD no offence