Credit to ebrad for the picture!
It’s time for the weekly snapshot. Mojang is continuing to work on separating the client from the server, and has fixed a bunch of stuff related to that transition. What else got added? Check it out below:
- Added cocoa plants to jungles
- Added a “large biomes” world type
- Added specific names for the different sandstone and smooth stone blocks
Improvements continue to pour into each snapshot with every passing week, and the new, improved SSP/SMP system continues to be streamlined, adopting a feel not unlike what MCX360 currently uses to connect players to one-another. Want to try this sleek update out?
Get the snapshot here:
Client: Download here
Server: Download here
The client now comes with both the client-side and the server-side JAR files. The file called “minecraft.jar” should be in your “.minecraft/bin” folder as usual, and the “minecraft_server.jar” file should be in a folder called “.minecraft/server”.
Indeed I do. I have 3 desktops running in my house so.. yeah. Anyways, I did see a couple things about port forwarding, but I assumed that was only necessary when doing a fully multiplayer server, not this new single player server. But there is just one probably with that; when i go into my router settings (just type in your router ip thing into the url box to see my settings) it requires a password to change anything. My dad set up this router (hes pretty good with computers but he doesn't write down anything) and lost the password. So it will be a huge hastle to reset the router settings, reconfigure, and eventually port forward. Basicaly, is there any other way? or is that it?
The single player server listens on a dynamically assigned TCP port... Check the server.log to see what it uses for each session. It starts and stops with the client on the same machine entering and leaving the world. My experience has been ports around 1422 to 1428 have been used, though this will vary on system software. It does not listen on 25565.
The single player server is passed parameters to launch it be the client, it does not rely on the server.properties file only.
(Theory) The single player server currently will not accept additional players attempting to connect. I mucked about with this yesterday on 12w19a for about an hour to come to this conclusion.
also, i rly like the large biomes feature. ive always felt minecraft biomes were way too small and unrealistic
I've never heard of needing to port-forward within a LAN, the whole purpose of port forwarding is to forward traffic on a port on your external IP to your internal private IP. You shouldn't have to mess with that.
Although the way is paved for setting up multiplayer locally (features are there), I don't think it is yet fully functional. In order to get my snapshot server going i had to still do it the old fashioned way and use the server executable. I found mine here (http://assets.minecr...raft_Server.exe). I found it on this page (http://www.mojang.co...napshot-12w19a/) It does say on there that the server jar files are in there but it doesn't say anything about it being functional. And if they were functional I don't see why they would have released another dedicated server client.
Just my $0.02.
Yeah this is my thought as well. The framework is there, but its not finished for it to function properly. Hence the server executable being released with 12w19a.
You can if you have a paid account. (Or until he releases 1.3 fully, and then you can play for 6 in-game days without one.)
When you get that bug, it means that A: Minecraft is open which you can fix by closing minecraft or B: The Java application is running. To fix that, open your task manager Ctrl+Alt+Delete etc. then go to processes and end any process that is named JAVAW.exe. That should fix it.
In case it helps, the single player server runs under "java" and not javaw on my win32 machine.
The minecraft_server.jar goes in the .minecraft folder under a new dirctory you create called "server".
The client minecraft.jar starts the minecraft server when you select and play a map in single player. You do not need to launch the minecraft server process independantly from the command line.
When you want to play multiplayer, start the server yourself and in each client select multiplayer with host and port for the minecraft server you started.