I can guarantee someone has missed a point here. I see a lot of people complaining they want to be able to 'opt-in' for this server thing...
I think you guys are holding your breathe over nothing. IF Mojang implements this correctly, you wont notice that much of a change to your single-player experience. I am pretty sure they have thought of people who do not want to go online, so I am sure the game will check for an available connection to begin with. There WILL be a whitelist system to keep people out, or you can just not invite anyone to play in your world. It's simple.
I am all for this change. A transparent, easy to use system of creating a world and inviting people you choose is a good idea. I have, in the past, had to copy my world files into another folder and start a server app to get it accessible as a multi-player map, then setup connection, then tell my friends how to setup. It's going to be awesome to just create a world, decide I'm done building or playing on my own and call a friend. Tell them to fire up Minecraft and start playing in my world.
As for those who are complaining about EXTRA time for mod releases...how can that be? With the mod APi being implemented, we don't have to worry about mods needing to be reworked to work with later releases AND you no longer have to worry about the mod working on multiplayer vs singleplayer.
For someone who doesn't have an internet connection, I am sure Mojang will do the right thing and make sure people can still play without that internet connection. Sadly, this MAY not be true, there are plenty of games I have purchased that refuse to work since I cannot "validate" I am the owner of the game without being online, which now happens rarely. It's still annoying, yes. I will agree. But I have a feeling Mojang will do the right thing.
I have also been playing Minecraft since Alpha. Yes, there have been moments I did not agree with additions or removals, but as a whole, the game is still a great game. For instance, people were upset (so was I) that the adventure update did not turn out like we all wanted. I'm still here and still playing. The same people who are complaining about these points and stating they'll stay on 1.2.5, were also the ones who have stated they were going to stay on 1.6... ... ...
As for the mod support everyone is saying they have been waiting for...not an easy thing to implement, and Jeb has stated that there will not be a version labeled 1.3 UNTIL the Mod API and SMP/SSP merger is done and good. Expect snapshots for a bit longer.
My only gripe right now is I can't test the server ability the way they envision it yet. I cannot give proper feedback.
I find it quite funny how these kids go running their mouth about an update that was barely implemented and barely tested. The crossover will save tons of time making mods, it will make updating the game 2x as fast(more updates) etc. It will also fix multiplayer.
MCX360 has no currently known multiplayer bugs, why? Because it and pocket edition are built on the running from localhost method. Many games run single player games from a localhost just for the simplicity of programming it.
Of course this immensely benefits multiplayer and allows for inviting friends to SSP, but it also affects solo SSP as you will get more updates and more support. If mojang is only working on one game as opposed to the current 2, then they can pay more attention to the bugs/improvements that need to be fixed/made in the game.
I'm glad they have finally done what they should have done from the start.
The Meaning of Life, the Universe, and Everything.
Join Date:
2/16/2011
Posts:
63
Member Details
My god. After reading this thread, my head hurts due to the sheer stupidity displayed by at least half the posters. There are no legitimate downsides to this change which aren't pre-existing bugs.
SMP is buggy, but those bugs can be fixed. This is in general, a positive change. Stop being so selfish, multiplayer needs to be fixed just as much as single player.
If you want SSP to be less buggy, you can help by reporting bugs.
TIP: If you aren't a programmer, don't complain about mojang's choice. You have no idea what you're talking about.
I really hope this goes through, if not for anything else than just to stick it to these simple-minded, self-centered jackasses *cough AdelWolf cough*. I do think that previous features should be expanded upon before adding other frivolous additions, but the merge is anything but frivolous; it is a decision that was made for purely technical reasons, which doesn't impact the single-player experience in ANY way and even enhances it in several important aspects.
Phew. These asinine responses are not good for my blood pressure, let me tells yeh. I really appreciate Flameheart's efforts to placate and reason with all these hooligans, though.
Do you like video games with an engaging story, beautifully hand-drawn graphics, incredible musical scores, and a difficulty that requires carefully thought-out strategy? Then follow this link and greenlight one of the most deserving games this side of Stardew Valley! http://steamcommunit...s/?id=133229519
TIP: If you aren't a programmer, don't complain about mojang's choice. You have no idea what you're talking about.
TIP: If you don't know the people talking, then shut your mouth, as you don't have the first damn clue if they know what they are talking about or not. Assumptions , get you nowhere.
TIP: If you don't know the people talking, then shut your mouth, as you don't have the first damn clue if they know what they are talking about or not. Assumptions , get you nowhere.
I think the fact that these people he's referring to are making this out to be a bad decision provides enough information to assume they know NOTHEENG.
But really now, if implemented correctly, this could be the best thing that happened to Minecraft. I'll wait for the full 1.3 release to come around before I go flapping my face-hole about any bugs or annoyances.
Exactly, why did they leave it this way for 1.3? Oh wait, we don't know. This is one of the things most likely to be changed for the actual release. Remember: This is only a snapshot.
I think the fact that these people he's referring to are making this out to be a bad decision provides enough information to assume they know NOTHEENG.
But really now, if implemented correctly, this could be the best thing that happened to Minecraft. I'll wait for the full 1.3 release to come around before I go flapping my face-hole about any bugs or annoyances.
And that is why some things never get fixed because people don't say a thing about the bugs to begin with...idiots.
With all due respect bro, if there were a downside to this update about which people could legitimately get upset or worried, then many more people on this forum would be upset or worried over it.
However there is literally no down side to this update. At worst, it will mean a few minor inconveniences for us players while they sort out the teething problems - that is the only possible thing to be upset about, and these issues are so minor that to use them as an excuse to complain would really be simply childish.
This update means:
*) Faster bugfixes for issues within the game.
*) Faster official updates.
*) Better mod support, a simplified modding system, and easier mod intergration with few conflicts.
*) Better playabillity for multiplayer gamers, with no loss of playabillity for single player fans.
And no real cons at all - nothing that will cause long term or serious problems. How can people not be excited by all this potential?
The issues that people keep bringing up are often misguided, baised upon a lack of understanding of the full facts. Surely those that do have a little more information are not 'idiots' for trying to explain said facts to them and give them a fuller understanding of the matter, in order to allay some of those unfounded fears?
No real cons at all? are you stupid? Read back to my other posts to see the cons. And.. lol.. misunderstanding.. I understand it all perfectly, and I still do.. not.. want.. server intergration to my single player worlds. I don't get why fanboys can't grasp the concept not everyone wants this. I do not want anything of the sort going on. If I wanted a possibility of having people in my worlds, guess what? I'd get a server for that. But, single player is just that,. SINGLE. Having an ability to pause the game, ect. Just read back.
Keep the multi far far seperate from singleplayer. It is that simple. Speed of updates, is no issue to me. Better mod support is of no issue to me. I use two mods and that's it. TMI and Zombe. Whenever MC Updates, I just wait for them to update before I do, it's not that hard. Half of the bug fixes they do, causes more bugs, or breaks things that are actualy useful. Either way.. I've said this over and over already. You want my reasons why, go through my post history.
As mentioned previously, this low-level change should streamline the MC updates and, after the initial pain of changes required, make the modding community only have to support one build type. All the paranoia and misinformation is unfounded.
Those flailing about with ad hominem attacks are the ones lacking in relevant education/experience/maturity and, although I know they don't care, should probably stop embarrassing themselves. If they can't see why these changes are surely to be a positive for MC but refuse to turn off their right brain long enough to read and understand the explanations provided, I've no time for the lot of them.
And that is why some things never get fixed because people don't say a thing about the bugs to begin with...idiots.
Perhaps "flapping my face-hole about bugs and annoyances" was a poor choice of words. People should definitely be pointing these things out (that's what the snapshots are for, of course), but there's a difference between just alluding to them and spelling THE END OF MINECRAFT AS WE KNOW IT.
Welp, let's discuss the backlash over Diablo III's single player being hosted on a remote server. I was already dead set against this before I came across this article. http://www.cracked.c...nnoying-future/ I'm sure Mojang won't be even half as annoying about this as Blizzard.
SCENARIOS for singleplay.
1)It's like 10 or 20 years in the future....
You: "I'm feeling nostalgic. I want to play Minecraft, like old times."
Server: "Sorry, Minecraft servers went down years ago. Nothing is forever."
You: "You lie, can still run PC games from the early 90s on emulators."
Server: "Guess you'll need to figure out some kinds of hack then."
2) You: "I want to finish those last 3 skyscrapers."
Server: Sorry, servers are down, system maintenance."
You: "It's been an hour, maintenance should be over by now."
Server: Sorry, we're having different server problems now."
3)You: "I'm going to build a giant mushroom village today."
Server: "No you're not. Either your modem died or you forgot to pay your internet bill."
You: But I'm broke until next Friday."
Server: "Too bad, no Minecraft for a week."
You: "Grr! This isn't an MMORPG! It's singleplayer!"
Basically, those of us who don't like multiplayer don't want multiplayer problems. We want to play offline when our internet & cable are dead, we don't want to wait 5 minutes let alone 1 hour to be able to access our solo campaign. We don't want to be constantly booted out of our world because the servers are having a fit.
Make texture packs? Tired of people telling you to upload better screencaps? Send me a message with a link to your pack & I can help. (Check my Planet Minecraft blogs for photography examples). http://www.planetminecraft.com/member/likalaruku/
My god. After reading this thread, my head hurts due to the sheer stupidity displayed by at least half the posters. There are no legitimate downsides to this change which aren't pre-existing bugs.
SMP is buggy, but those bugs can be fixed. This is in general, a positive change. Stop being so selfish, multiplayer needs to be fixed just as much as single player.
If you want SSP to be less buggy, you can help by reporting bugs.
TIP: If you aren't a programmer, don't complain about mojang's choice. You have no idea what you're talking about.
The Irony....
Your telling SSP players to not be selfish when they could be forced too play a version of SSP that has latency issues due too poor server code, many muiltiplayer bugs and severe performance issues. When previously they didn't have ANY of them problems. All to improve the game for SMP players.
The update is the scrapping of true SSP too focus on SMP and all we get in this thread is SMP players insulting SSP players for posting about all the issues they are suddenly going to have too deal with. You guys need to put yourselves in their shoes and show consideration for a significant amount of the player base. Minecraft started as a SINGLE PLAYER GAME. There are a significant amount of players who only play minecraft in single player. Yet your view is that muiltiplayer should come first? At the cost of the quality of the single player experience?
To all you saying all the bugs, latency issues and performance issues will be fixed in the next update. Have you been here 2 years? Thats how long all of them issues have been here. If they were that easy too fix they would of done it before even considering a merge. The client too server code is in serious need of a rework consisdering even local servers have latency issues and performance problems. You can't say its going to be fixed, you can't say when its going too be fixed, its all complete speculation without any basis in reality. Your just happy SMP will get all the attention from now on and not looking at the facts.
They should of assigned a dev too directly rewriting the code for servers as this alone could fix most of the SMP problems you currently see. Hosting a server is a resource hog in comparison too running Minecraft SSP. Servers create their own latency and performance problems even on local host because the communication with clients is not working correctly and the server code is far from optimised. This is what needed looking at to get the SMP fixed.
The whole point of this merger is to make these fixes and improvements possible, whereas currently they are not.
So yes, this may cause a few problems in the short term, for both SSP and SMP players. But in the longrun it will be beneficial, not just for multiplayer advocates, but single players as well. It will allow the team to make progress where currently they are at an impass. And in real terms, once the few teething problems are resolved, the gameplay experience for single player users will appear exactly the same as it does currently - visually and in gameplay terms, practically nothing will have changed.
The fixes and improvements are possible before the merge as the current SSP seems to play no part in it. It's SMP running on a local host server as evidenced by having exactly the same bugs, lag and performance issues as the current SMP client without any of the strengths of the current SSP. Therefore them issues could be fixed without having to force SMP local host mode on current SSP players.
The one usefull thing this snapshot has shown us is that many of the bugs are caused by the way the servers are coded and how they communicate with clients. When you see lag and stuttering on a local host server with just you playing on the same computer you know its the server code causing it or how the communication is handled between client/server.
When you see more resources being used when hosting a SMP local host server rather then running the originally SSP then you know the server code lacks optimization. That is something they NEED too fix before even thinking of going live with this update or a section of players will find that ssp is barely playable.
I am not sure where you get the idea that these bugs, performance and latency issues can't be fixed without forcing a local host for ssp. All of these issues excisted long before the snapshot. We should be given a option of running a server or not until the server code is completely fixed, optimization and the bugs gone.
I understand that writing in a local host server code into ssp has big advantages but currently i don't think its anywhere near ready. If thats what their intention is in the future update they need to make sure they don't force anything until its ready. SSP in its current form has no major bugs or performance issues like SMP. The devs need to take this into account. Your not going to make any SSP happy if we are stuck with a worse game for a few weeks/months.
So let me get this straight...you're asking Mojang to completely ignore SSP entirely and spend all their time fixing SMP, meaning that there will be no new updates/fixes to SSP for the duration of that project.
Then you want them to bring SSP and SMP together in their office, which in itself is a big task, and again ignore any fixes/updates to the SSP that we play.
Then you want them to sit down and fix all the issues that are caused by the merger of the two modes, further ignoring their fanbase and letting the game stagnate, until finally the thing is ready for release?
Aside from being a severe letdown for the community whom I doubt would put up with such a long delay without any updates or news, such a plan would also be hugely time consuming and not in any way cost effective. We as gamers would be waiting for months or more with nothing new to play, and Mojang would be throwing huge amounts of time and energy into repeating similar actions over and over again. Who would pay for all that time lost and money spent?
With this way of implementation, they only need to fix the bugs once, not multiple times over seperate versions of the game. It involves much less work for them, costs less, and will result in quicker and more visible results for us, the consumers. The only price is a little disruption which can be completely avoided if one simply sticks with version 1.2.5 until the update is completed - nobody is forcing anyone to move to the snapshots, so we can play perfectly bug-free with that version until 1.3 is complete.
Really bro, no offence intended, but all things considered I don't think your arguments make much sense...
On the other hand, SSP players could just avoid the snapshots and stick to 1.2.5 until 1.3 is ready. That's exatly what I, as a huge SSP fan, have done. Not that hard, surely?
And besides, how many SSP players would be happy if we were stuck with 1.2.5 for a year or so, with no updates whatsoever, while Mojang were busy with the server code?
There is no true merge. It's SMP on a local host server rebranded as SSP or thats exactly how it plays currently. If you fix the current issues with servers and SMP there won't be anymore bugs too fix. Why? because all SSP is in the snapshot is SMP. They are one in the same with the only difference being the server type. It's the same game! unless you can prove otherwise?
If you think its going to take a year for them too fix all the issues with servers and SMP then forcing players to play SMP on a local host server (the new SSP mode) is already going too ruin minecraft for a lot of players. Many of the SMP bugs break some of the features of minecraft. Some of the bugs completely ruin the fun of the game when they happen. You also get significantly more chunk errors and glitched mobs on a server.
You think its fair that some players will no longer see any updates beyound 1.2.5 because in order too play the updates we have too suffer a year of SMP related SSP bugs, lag and performance issues? There needs too be a balance thats fair for everyone.
At the very least get the servers running correctly first. Fix the lag on local host servers and the performance issues with them. That shoulden't take too long and would be some middle ground.
And where is this mod support I've been hearing about?
I think you guys are holding your breathe over nothing. IF Mojang implements this correctly, you wont notice that much of a change to your single-player experience. I am pretty sure they have thought of people who do not want to go online, so I am sure the game will check for an available connection to begin with. There WILL be a whitelist system to keep people out, or you can just not invite anyone to play in your world. It's simple.
I am all for this change. A transparent, easy to use system of creating a world and inviting people you choose is a good idea. I have, in the past, had to copy my world files into another folder and start a server app to get it accessible as a multi-player map, then setup connection, then tell my friends how to setup. It's going to be awesome to just create a world, decide I'm done building or playing on my own and call a friend. Tell them to fire up Minecraft and start playing in my world.
As for those who are complaining about EXTRA time for mod releases...how can that be? With the mod APi being implemented, we don't have to worry about mods needing to be reworked to work with later releases AND you no longer have to worry about the mod working on multiplayer vs singleplayer.
For someone who doesn't have an internet connection, I am sure Mojang will do the right thing and make sure people can still play without that internet connection. Sadly, this MAY not be true, there are plenty of games I have purchased that refuse to work since I cannot "validate" I am the owner of the game without being online, which now happens rarely. It's still annoying, yes. I will agree. But I have a feeling Mojang will do the right thing.
I have also been playing Minecraft since Alpha. Yes, there have been moments I did not agree with additions or removals, but as a whole, the game is still a great game. For instance, people were upset (so was I) that the adventure update did not turn out like we all wanted. I'm still here and still playing. The same people who are complaining about these points and stating they'll stay on 1.2.5, were also the ones who have stated they were going to stay on 1.6... ... ...
As for the mod support everyone is saying they have been waiting for...not an easy thing to implement, and Jeb has stated that there will not be a version labeled 1.3 UNTIL the Mod API and SMP/SSP merger is done and good. Expect snapshots for a bit longer.
My only gripe right now is I can't test the server ability the way they envision it yet. I cannot give proper feedback.
MCX360 has no currently known multiplayer bugs, why? Because it and pocket edition are built on the running from localhost method. Many games run single player games from a localhost just for the simplicity of programming it.
Of course this immensely benefits multiplayer and allows for inviting friends to SSP, but it also affects solo SSP as you will get more updates and more support. If mojang is only working on one game as opposed to the current 2, then they can pay more attention to the bugs/improvements that need to be fixed/made in the game.
I'm glad they have finally done what they should have done from the start.
SMP is buggy, but those bugs can be fixed. This is in general, a positive change. Stop being so selfish, multiplayer needs to be fixed just as much as single player.
If you want SSP to be less buggy, you can help by reporting bugs.
TIP: If you aren't a programmer, don't complain about mojang's choice. You have no idea what you're talking about.
C++11 Software Architect / Library Developer
I'm gonna kill boost. -me
Phew. These asinine responses are not good for my blood pressure, let me tells yeh. I really appreciate Flameheart's efforts to placate and reason with all these hooligans, though.
TIP: If you don't know the people talking, then shut your mouth, as you don't have the first damn clue if they know what they are talking about or not. Assumptions , get you nowhere.
I think the fact that these people he's referring to are making this out to be a bad decision provides enough information to assume they know NOTHEENG.
But really now, if implemented correctly, this could be the best thing that happened to Minecraft. I'll wait for the full 1.3 release to come around before I go flapping my face-hole about any bugs or annoyances.
And that is why some things never get fixed because people don't say a thing about the bugs to begin with...idiots.
No real cons at all? are you stupid? Read back to my other posts to see the cons. And.. lol.. misunderstanding.. I understand it all perfectly, and I still do.. not.. want.. server intergration to my single player worlds. I don't get why fanboys can't grasp the concept not everyone wants this. I do not want anything of the sort going on. If I wanted a possibility of having people in my worlds, guess what? I'd get a server for that. But, single player is just that,. SINGLE. Having an ability to pause the game, ect. Just read back.
Keep the multi far far seperate from singleplayer. It is that simple. Speed of updates, is no issue to me. Better mod support is of no issue to me. I use two mods and that's it. TMI and Zombe. Whenever MC Updates, I just wait for them to update before I do, it's not that hard. Half of the bug fixes they do, causes more bugs, or breaks things that are actualy useful. Either way.. I've said this over and over already. You want my reasons why, go through my post history.
Those flailing about with ad hominem attacks are the ones lacking in relevant education/experience/maturity and, although I know they don't care, should probably stop embarrassing themselves. If they can't see why these changes are surely to be a positive for MC but refuse to turn off their right brain long enough to read and understand the explanations provided, I've no time for the lot of them.
Perhaps "flapping my face-hole about bugs and annoyances" was a poor choice of words. People should definitely be pointing these things out (that's what the snapshots are for, of course), but there's a difference between just alluding to them and spelling THE END OF MINECRAFT AS WE KNOW IT.
But they're issues to the developers of the game, and modders everywhere. Kind of a big deal, y'know.
SCENARIOS for singleplay.
1)It's like 10 or 20 years in the future....
You: "I'm feeling nostalgic. I want to play Minecraft, like old times."
Server: "Sorry, Minecraft servers went down years ago. Nothing is forever."
You: "You lie, can still run PC games from the early 90s on emulators."
Server: "Guess you'll need to figure out some kinds of hack then."
2) You: "I want to finish those last 3 skyscrapers."
Server: Sorry, servers are down, system maintenance."
You: "It's been an hour, maintenance should be over by now."
Server: Sorry, we're having different server problems now."
3)You: "I'm going to build a giant mushroom village today."
Server: "No you're not. Either your modem died or you forgot to pay your internet bill."
You: But I'm broke until next Friday."
Server: "Too bad, no Minecraft for a week."
You: "Grr! This isn't an MMORPG! It's singleplayer!"
Basically, those of us who don't like multiplayer don't want multiplayer problems. We want to play offline when our internet & cable are dead, we don't want to wait 5 minutes let alone 1 hour to be able to access our solo campaign. We don't want to be constantly booted out of our world because the servers are having a fit.
The Irony....
Your telling SSP players to not be selfish when they could be forced too play a version of SSP that has latency issues due too poor server code, many muiltiplayer bugs and severe performance issues. When previously they didn't have ANY of them problems. All to improve the game for SMP players.
The update is the scrapping of true SSP too focus on SMP and all we get in this thread is SMP players insulting SSP players for posting about all the issues they are suddenly going to have too deal with. You guys need to put yourselves in their shoes and show consideration for a significant amount of the player base. Minecraft started as a SINGLE PLAYER GAME. There are a significant amount of players who only play minecraft in single player. Yet your view is that muiltiplayer should come first? At the cost of the quality of the single player experience?
To all you saying all the bugs, latency issues and performance issues will be fixed in the next update. Have you been here 2 years? Thats how long all of them issues have been here. If they were that easy too fix they would of done it before even considering a merge. The client too server code is in serious need of a rework consisdering even local servers have latency issues and performance problems. You can't say its going to be fixed, you can't say when its going too be fixed, its all complete speculation without any basis in reality. Your just happy SMP will get all the attention from now on and not looking at the facts.
They should of assigned a dev too directly rewriting the code for servers as this alone could fix most of the SMP problems you currently see. Hosting a server is a resource hog in comparison too running Minecraft SSP. Servers create their own latency and performance problems even on local host because the communication with clients is not working correctly and the server code is far from optimised. This is what needed looking at to get the SMP fixed.
The fixes and improvements are possible before the merge as the current SSP seems to play no part in it. It's SMP running on a local host server as evidenced by having exactly the same bugs, lag and performance issues as the current SMP client without any of the strengths of the current SSP. Therefore them issues could be fixed without having to force SMP local host mode on current SSP players.
The one usefull thing this snapshot has shown us is that many of the bugs are caused by the way the servers are coded and how they communicate with clients. When you see lag and stuttering on a local host server with just you playing on the same computer you know its the server code causing it or how the communication is handled between client/server.
When you see more resources being used when hosting a SMP local host server rather then running the originally SSP then you know the server code lacks optimization. That is something they NEED too fix before even thinking of going live with this update or a section of players will find that ssp is barely playable.
I am not sure where you get the idea that these bugs, performance and latency issues can't be fixed without forcing a local host for ssp. All of these issues excisted long before the snapshot. We should be given a option of running a server or not until the server code is completely fixed, optimization and the bugs gone.
I understand that writing in a local host server code into ssp has big advantages but currently i don't think its anywhere near ready. If thats what their intention is in the future update they need to make sure they don't force anything until its ready. SSP in its current form has no major bugs or performance issues like SMP. The devs need to take this into account. Your not going to make any SSP happy if we are stuck with a worse game for a few weeks/months.
There is no true merge. It's SMP on a local host server rebranded as SSP or thats exactly how it plays currently. If you fix the current issues with servers and SMP there won't be anymore bugs too fix. Why? because all SSP is in the snapshot is SMP. They are one in the same with the only difference being the server type. It's the same game! unless you can prove otherwise?
If you think its going to take a year for them too fix all the issues with servers and SMP then forcing players to play SMP on a local host server (the new SSP mode) is already going too ruin minecraft for a lot of players. Many of the SMP bugs break some of the features of minecraft. Some of the bugs completely ruin the fun of the game when they happen. You also get significantly more chunk errors and glitched mobs on a server.
You think its fair that some players will no longer see any updates beyound 1.2.5 because in order too play the updates we have too suffer a year of SMP related SSP bugs, lag and performance issues? There needs too be a balance thats fair for everyone.
At the very least get the servers running correctly first. Fix the lag on local host servers and the performance issues with them. That shoulden't take too long and would be some middle ground.