Even if this DOES go into a full update (Which I highly doubt), it would be ridiculous if random people could just join your SP world. SP worlds will probably just have an option you can toggle if you want it to be open to the community.
The idea is alright, it has pros and cons, I would prefer if when you make a world you could choose when creating the world if you want it to be complete single player or the cross over of ssp and smp. This would stop those people from complaining and make everybody else happy.
I can't even run Minecraft on high or medium settings. Let alone add the processing of a server into the mix. What is worrying me is that merging them together might cause some unnecessary lag since now, players' computers will have to burden running the client AND the server. This in turn will affect slow computers (such as mine).
This is what I am talking about when I say that they wanted critisizem, not a yes or no answer.
Why do you not like the update? What information do you have about this and could you provide a credible source to backup your claims? What can Mojang do to make this update happen better rather than throw alll the code down the metaphorical trash bin and start on something else? Why would you assume I own a segway, I am much too poor to own one currently, but it is on a list of things I am planning to buy that I keep in my fanny pack at all times. Please stop going through my fanny pack if indeed you have been going through my fanny pack.
You know what I find annoying?
People who make assumptions.
Like you assuming that supporters of this snapshot only do it to support Mojang. And the people who assume they know what features will and will not be included in this experamintal update. And the people who assume that they will have decreased preformance because their computer will be running the server software in the background even though the current SSP system takes just as much memory as the SMP does.
Why would this not go into the next update? Obviously it won't go in as it is now; the current code is experimental and requires a lot more work, but the basic features it includes will almost certainly be in 1.3.
Perhaps you misunderstood me I meant, like you said, that it won't go in the game as it is now. With the toggle button however, I'd have no problem with the implementation of this mode, as it would have no impact should you choose to keep your world closed from MP.
some delicious tears in this thread. This is what they should have been doing from the beginning. A lot of new players might not know or remember, but in SMP a lot of things did not work for a very long time, and when they did it was different from single player. SSP running on a local server is how it should have been from the beginning to avoid all of those issues.
Multiplayer is the future, how can anyone be against this? What ever minor cons you may have are trivial compared to the huge pros. I just hope it's easy on the people used to running servers, hope that model doesn't change too much.
I don't know it sounds like a good idea in theory but this might, as so many people *cough* *cough* have said before, there might be increased lag and some of the glitches in multiplexer, however this means that people like Etho and others who do stuff like him will be able to make things that work in both single and multi-player (because they will be the same thing).
Also I think that (if Mojang goes through with this) that they are doing this to save time as Meduax said: "Now that they're unifying SSP and SMP they can finally have one and only one codebase which leads to far better chances of squishing bugs because there aren't two possible sources anymore." this means that updates and cool new features will come more often since they only have to code it one time give the guys at Mojang a break if there was a way to do less work you all would take it and here you hypocrites are getting angry at Mojang because they are trying to do the same thing but not doing a half-assed job as well as trying to make it easier for modders
and if you don't like the update use NonMcStalgia (i hope i got that right) to revert back to an older version of minecraft
Make it so that single player stays single player. Also, make it so that the local network thing is in multiplayer. I never could figure out how to set up a server so I couldn't. Make it so that your local network can just hold 2 players.
Rollback Post to RevisionRollBack
Was I helpful? Press the "+" button at the bottom right! Thanks!
To all those people complaining about how the mods will break, MOD API! Remember?
The server will start automagically.
You won't be forced to allow multiplayer.
The server is just a way to unify the game engine for modding.
The server will also make it easier to chase bugs.
This change will make modding easier by making SSP & SMP plugins the same. Modders will no longer need to make separate SSP/SMP mods because of this!
Rollback Post to RevisionRollBack
Please please please let official plugins API be Java-aware. Maybe not Java-centric, tho. (looking at you, Oracle vs The World)
Personally, all I care about is the easy mod installation. This whole single player/multiplayer merging scenario (or whatever) won't bother me as long as I can play Tropicraft. (I've tried installing it the old fashioned way, you know, %appdata% in search box, open bin, delete META-INF, installing modloader and forge, didn't work. Can't wait for official mod support.)
I'd prefer it if it was a toggable feature. I like the idea, but being forced to connect to your local connection everytime you want to play single player, may get annoying, because of the longer duration to get on, and the obvious mob/redstone lag. If it was a toggable in "World Options" to have a single player world connect to localhost or not, that would be perfect for I'm sure a lot of people. Want to have this feature? Toggle it on. Don't want the feature? Toggle it off.
The sheer amount of misinformation flying around here is mind boggling. It's almost as bad as the sheer unwillingness to read what has been given.
People are jumping to some incredibly uneducated assumptions.
I can see how many people are worried about this, and to be honest if I didn't know what I know about how these sorts of architectures work I'd probably be scared to. But what you people who are scared need to do though is stop being reactionary, take a breath and read some of the very detailed and well thought out posts people have been putting out to help explain what is going on.
I'm probably going to be beating a dead horse here but maybe I can help people click in on what's going on and why this is the best way this can be done, why you're seeing bugs now, and how this can improve the way we all play the game in the future.
I suppose the best place to start would be to address worries about performance, bugs, and the like.
The reason why you are seeing so many more bugs and problems in this particular snapshot then you would be seeing even in a current SMP world is because it is partially implimented work. The whole point of this snapshot is to begin seperating LOGIC from RENDERING.
What this means is that all of the actual number crunching, determining where mobs are, the world being generated, storing the time and advancing ticks on redstone machines, this is all going to get moved to the server. It's going to do all of the heavy lifting of actually making your world work. What is the client going to do? It's going to handle showing you things. It will take all of the information that the server is working out and sending you, and turning it into the pretty blocks you know and love.
Traditionally in SSP this was all done in the same place; right in your minecraft.jar. When the process is completed your computer won't be doing any more work than it already does. If anything you will see a performance increase. How? Even the cheapest of computers these days is multi-core. As it stands now, Minecraft can't really take advantage of that whole extra chunk of power your machines have. With this update it will.
Consolidating the two development branches (SSP and SMP) will mean more time for bug fixes as work isn't duplicated. So those funky things that happen on servers? They'll be fixed far faster now.
Worried about the possibilities of a griefer or noob coming onto your world and screwing things up? That isn't possible in the planned system unless you purposefully bring them in. If you want to just play by yourself it will play that way by default.
Concerned about difficulties in performing port-forwarding if you do want people to play? If they code their system right it won't even need to be done. It'll just work.
So how can this update make things better? Well beyond the cool factor of being able to invite someone to your world to show off what you've been doing, this will make the game smoother for everyone. Whether you play on a server or by yourself the game will run better, likely run faster, and ultimately will have fewer bugs. Mods will be able to run on both servers and local games without having to code twice. One code for everything. The possibility of automatically providing needed mods/plugins when connecting to a modded SMP world becomes possible.
Let's face it: Multiplayer in Minecraft was an after-thought. It's been a tacked on bonus feature for a long time. This update begins a process of aligning the game with a vision of making multiplayer something key to the game and not a second-rate citizen.
If multiplayer had been included from the get-go we would have been using this system right from the very beginning. This is the way it's going to be done, and it's the way it should be done.
That said, there are valid concerns and those are the bug complaints that have been brought up on the Reddit page. Like pausing when playing by yourself; there should be some logic for it to detect this and is definitely a valid complaint to be brought up.
But at the end of the day, this is the right path for Minecraft's future. So instead of doomsaying, why don't we all help Jeb and Mojang in making this the smoothest, best restructering possible?
While I'm not gonna freak out and yell about how much I hate it, I don't think a forced crossover is a good idea. I won't be using it or updating Minecraft anymore, if all SSP worlds are going to be a forced crossover. SSP and SMP should stay two seperate things. I have the SMP server I play with my friends, and my own SSP worlds. I certainly dont want to take a lag/error/lack of mods whatever hit on SSP just for some feature that I have no interest in. It should be a toggle option on world creation, if it is absolutely going to be implemented.