Minecraft Wiki talk:Issues/Weekly 12w18a

Discussion:Main Menu Button Names
a The single player text is misleading, as you are now actually hosting a Minecraft server. Singleplayer should now say something along the lines of Start Game and Multiplayer should say Join Game. NetherrackCreeper (talk) 16:40, 3 May 2012 (UTC)
 * It's a local server. And its so Mojang does not have to create two versions of each update, one for client, and one for the server. -ZuppaHD 01:52, 4 May 2012 (UTC)
 * "Host Server" and "Join Server" would be very misleading for new players or players who are not tech-savvie. Singleplayer still makes sense in that when you enter the game you are the only player there until you invite others. And besides, this is not a place for your opinions. --Mattrition 10:39, 4 May 2012 (UTC)
 * Those were just suggestions, the single player text should at least be changed. NetherrackCreeper (talk) 18:48, 4 May 2012 (UTC)
 * It could say "Start Game" and "Join Game" like in Pocket Edition. TorchicBlaziken 01:54, 5 May 2012 (UTC)
 * Yes it could, but again this isn't a forum. Discussion moved for the sake of clarity. --Mattrition 14:05, 5 May 2012 (UTC)
 * I support making "singleplayer" and "multiplayer" now being called "Start Game" and "Join Game" like in PE --Gil2455526 20:20, 6 May 2012 (UTC)

Discussion:Can't Connect to Singleplayer World
This is the discussion for two identical bug reports:

!sp When trying to open an old world or when trying to create a new world, the game displays a dirt screen, then "Connecting to server" before displaying "Could not connect to server; Connection refused: connect" --169.204.228.78 17:53, 3 May 2012 (UTC)
 * This does not crash minecraft, demoted to Major bug. heldplayer 20:18, 3 May 2012 (UTC)
 * I added a crash report that I found saved after receiving this error. But I suspect this happens for a number of reasons. --Mattrition 16:49, 5 May 2012 (UTC)
 * I believe that this is the same bug that I had, where it says "Cannot connect to server. Connection refused.", for when I tried it on a PC, I got that error, at practically the same circumstances. On both machines there is a chance that you will login. I have a log, but I'd have to post it after school.--Wormy14 11:26, 7 May 2012 (UTC)

undefinedsp When quitting and re-starting a world in single player in fast succession you will get an error: ''Cannot connect to server. Connection refused: connect''.
 * Moved to discussion because this is almost definitely the exact same issue. It's not completely reproducible that it happens when you quit and enter a world in quick succession, so I guess that was a bit of a coincidence. --Mattrition 12:23, 6 May 2012 (UTC)

a! I cannot connect to my own single player world. I guess it is because my computer hasn't port forwarded correctly since 1.1, but this is rediculous, I have to have an internet connection to play single player? --~DaleK 16:32, 3 May 2012 (UTC)
 * The client ZIP contains /two/ parts: a 'server' directory and a 'bin' directory. You have to have copied BOTH into the Minecraft client before you can play, even offline. Mojang is restructuring the game like this so that modders only have to make changes once, rather than once for the client version and again for the server version.
 * I know that, it appears my issue was quitting whilst generating the world, I had to delete it, and start a new world for it to work. --~DaleK 17:25, 3 May 2012 (UTC)
 * I Can't Connect Either And I Installed Both Parts... I'm Assuming It's The Port-Forwarding Thing Mention In The First Post.

Discussion:World Seed Not Appearing In Debug Info
undefined When you press F3 or Shift+F3, the seed does not appear for the world. I only tested it out on singleplayer. (Please note I don't know if this would be the correct section, and tag). alexkill51 - 3 May 2012
 * This is definitely a bug since Jens only wanted to hide the seed in multiplayer only but since this multiplayer integration update or however that's called it's impossible to see the seed of your own world in singleplayer i think this should be [!] but i'm not sure... anyone? --MCKMan 10:08, 4 May 2012 (UTC)
 * [!] is really for game-stopping bugs. Not being able to see the seed of your world isn't game-stopping. --Mattrition 10:38, 4 May 2012 (UTC)
 * I considered this as [!] because you won't be able to share your epic seeds anymore :/. --MCKMan 13:08, 4 May 2012 (UTC)
 * It's still not game-stopping. People can still play their games with and without sharing seeds. I consider this a satisfactory definition of bug categories. --Mattrition 13:58, 4 May 2012 (UTC)
 * Maybe make it so that ops can see the seed but other players can't? NetherrackCreeper (talk) 18:54, 4 May 2012 (UTC)
 * Or make localhost see the seed, that way it's more like it was before. 109.240.184.7 09:57, 5 May 2012 (UTC)
 * Great idea! --MCKMan 16:56, 5 May 2012 (UTC)

Lag spikes
undefined Me and some others have been having crippling lag at times while playing in multiplayer. these are images I took of the lag-o-meter. In case it is hard to read: the path is "root.tick.level.tickChunk.recheckGaps.tcp < tcc". some times the lag spike lasts about half a second, (as the screen shot ones were) and even more rarely many many seconds (I can easily count to ten on some of these, but they are rare and I tend not to be able to get to the f3 menu for them fast enough to take pictures). I know that the screen shots are 1.2.5, but they happened in the snapshot as well, it is just that testing in snapshots for me is rather hard, especially when I play SMP and the server is 1.2.5. marked as [!] because I have lost some players to this (three so far, on a server of 12...)
 * I'm rather new at using a mediawiki to report bugs, so please excuse me if I do this wrong, and edit in anyway that makes sense. Admalledd 05:51, 7 May 2012 (UTC)