Minecraft – Running the CraftBukkit Server for minecraft

minecraft-bukkitminecraft-java-editionminecraft-java-edition-server

I recently download Craft Bukkit for running a multiplayer minecraft server, and according to tutorial I created a run.bat file in the note pad with following code to run the server

java -Xms1024M -Xmx1024M -jar craftbukkit.jar -o true
PAUSE

and according to tutorial's the server should start but insted of it the following error message appears
enter image description here

I dont know what is wrong cause the same thing happens with other server builds i try to run so please help me.

Best Answer

You have to rename the downloaded craftbukkit file from

craftbukkit-1.x.x-xx.x.jar

craftbukkit.jar

The .bat command expects a file called craftbukkit.jar, if it doesn't find it, you get that error.

Also check what @SevenSidedDie said.

Related Solutions

Minecraft – Terminal script for Minecraft server autosave

My recommended solution for this kind of thing tends to be "Use The System!".

If you have the option, enabling Time Machine from system preferences to create a full disk backup every hour is usually a good idea, and if you don't have the opportunity, you might want to consider getting an external disk and implementing that approach.

If that is completely out of the question for whatever reason, the alternative is using cron.

Setting up the interval running is easy enough, a simple man crontab should give you the information you need on that; but having a script to actually do the backup might be useful:

#!/bin/sh
cd ~/Desktop/MinecraftServer # or the path to your minecraft server directory
rm -rf world.bak
cp -r world world.bak

Save this as a "minecraft_server_backup.sh" and chmod +x it.

This particular script only keeps the most recent backup, and additionally, it doesn't actually check if the server is running before making a backup.

Minecraft – Problem setting up a 1.8.3 Minecraft server

This is barely an answer, but it did "solve" the problem.

I flattened the VM and installed Server 2008 R2 instead.

As far as I know everything was configured in exactly the same way, and I don't doubt that you can get this running on 2012. I guess something just went wrong at some point during the install process or something.

At any rate, I've got a nice shiny new 1.8.3 up and server running now - thanks for your help!