Ok, so I only saw one other post mention this in recent pages. Why can't I get into the Nether through MCEdit? I'm still on 1.8 and I'd like to delete my Nether for 1.9 stuff.
stable16 is posted. On Windows, the window should remember its position and maximized state. Chunks appear to load faster because ones behind the camera are skipped. Max view distance is increased. Using the mousewheel while dragging a cloned object now also moves the camera. To Goto a given X,Y,Z coordinate, press Control-G. The "Create New World" command lets you choose how large to make the world.
Like every other update, this one is probably dead-on-arrival for at least some of you, if not everyone. Even if the crash reporter kicks in it's still a good idea to post about it here anyway so I can get back to you if needed. If it suddenly works when it didn't before, post about that too.
The portable install on Mac was.... completely broken. I checked the code and it shouldn't have worked at all. In the latest release I changed it to place them in the folder containing the app bundle instead.
Hey, what's up with a portable install on Mac? I can see that the .ini and schematics folder get moved into the app bundle, but the program insists on recreating the Schematics folder in Documents. Oddly enough, the .ini file stays in the app bundle and is not created in Documents.
The problem was really weird. I use a program called Zipeg to unzip files because the built-in archive utility in Mac OS is far inferior to the one in Windows. However, Zipeg was somehow extracting the files improperly. Extracting with the built-in Mac utility made Minecraft work no problem.
Attempting to launch via Terminal reveals error -10810. Apparently this means the LaunchServices framework has run out of threads for processes to launch. Rebooting the machine does not help.
The Mac version of Minecraft does not open at all. I click it and nothing happens. So this forces me to play through the browser, but that's a pretty bad experience. Any idea what it might be?
Using a MacBook Pro with Snow Leopard (64-bit kernel on), 4GB RAM.
So even though the cave was completely lit (it was a very small cave, just a hideyhole for my first few days of that world), having some dirt as part of the floor allowed the zombie to spawn? Or the bed in general is just bugged?
I had a little cave dug out and I had closed wooden doors at each entrance. I made sure everything was lit before going to bed. I was woken up by a zombie at my bed. I fought it off and just to be sure, I further blocked the doors with dirt and the rest of the night passed without incident.
So do doors not stop mobs from spawning at your bed?
0
Nope, I get this.
0
0
Thank you for fixing! :biggrin.gif:
0
0
0
Attempting to launch via Terminal reveals error -10810. Apparently this means the LaunchServices framework has run out of threads for processes to launch. Rebooting the machine does not help.
0
0
Using a MacBook Pro with Snow Leopard (64-bit kernel on), 4GB RAM.
0
0
So do doors not stop mobs from spawning at your bed?
0
0
Oddly enough, Apple uses Broadcom for their wireless NIC, so at least that works.
Thanks for your help guys.
0
0
So so far, only my own computer can connect. It can connect via localhost, 127.0.0.1 or the computer's internal IP (192.168.0.7 in this case)
0