Raspberry Pi Minecraft Server Script With Startup Service 1.13

Minecraft Update Aquatic
Minecraft Update Aquatic

Based on the comments and feedback from my older guides I have added many requested features and fixes. It has changed so much since 1.12’s World of Color that my old guide is now obsolete and it’s time for the 1.13 Aquatic era update!

This script and guide are written to help you get a great performing Raspberry Pi Minecraft server up and running in only a few minutes.

I play on my server with 3-4 players on Survival mode without any difficulty on default settings (vanilla view distance of 10 and normal entity spawns/ranges). Above that number of players you will want to look into hardware with more memory but if you just want to play with a few friends it will be an excellent experience!

Features

  • Sets up fully operational Minecraft server in a couple of minutes
  • Raspbian / Ubuntu / Debian distributions supported
  • Installs and configures OpenJDK 9 (or OpenJDK 11 if available)
  • Sets up Minecraft as a system service with option to autostart at boot
  • Automatic backups to minecraft/backups when server restarts
  • Updates automatically to the latest version when server is started
  • Easy control of server with start.sh, stop.sh and restart.sh scripts
  • Optional scheduled daily restart of Pi using cron
  • Optional configuration of video memory to 16MB (default 64MB) and overclocking MicroSD reader to 100Hz (default 50Hz) for maximum performance

Requirements

  • Raspberry Pi model with 1024MB of RAM. Basically a Raspberry Pi 2B or higher. (No Zero unfortunately, 512MB is not enough RAM to do this, I’ve tried!)
  • Headless Linux distribution such as Raspbian Stretch Lite, Ubuntu Server 18.04.2, or any Debian based distribution (GUI distros can be used at the expense of available RAM and server performance)
  • Solid state drive highly recommended but not required.
    You can get a SSD setup on a Pi for less than most Micro SD cards cost. See my article here for details
  • If using MicroSD you want to be using a mid to high range card otherwise you will really be hurting on IO when the server is reading/writing chunks of terrain. Your card’s name should have lots of Pros/Ultras/Extremes in the title! Click here for MicroSD card benchmarks/recommendations.

Recommended Gear

Raspberry Pi 3B+ with 2.5A Power Supply

Sabrent USB 3.0 to SSD / 2.5-Inch SATA Adapter -AND- Kingston A400 SSD 120GB SATA 3 2.5” Solid State Drive

Or for a compact setup: SanDisk Extreme Pro 128GB USB Solid State Flash Drive

Choosing a Linux Distribution

The most important consideration when choosing which flavor of Linux to run the server on is simple: available RAM. Headless Linux distributions such as Raspbian Lite that don’t have a built in GUI have substantially more memory available for the Minecraft server.

Our biggest obstacle when running a Minecraft server on the Pi is available RAM since 1 GB is extremely low for this type of server. To have a playable experience you should not be running anything else on the Pi so all memory is available to be used.

After testing on many different distros I am finding Raspbian Lite and Ubuntu Server 18.04.2 32-bit to be the best choices. These distributions come with very few background processes and have rock solid support and performance.

64-bit vs 32-bit

There’s a lot of discussion in the Pi world about the up and coming aarch64 64-bit distributions vs. armhf 32-bit distributions. They have been and continue to improve dramatically. There are already use cases where 64-bit is far superior such as video encoding, advanced compression, etc.

So how about for running a Minecraft server? I have been testing extensively with Ubuntu Server 18.04 64-bit and the Debian Buster 64-bit. I have consistently had worse performance and stability than on 32-bit versions of the exact same distros.

But how can that be? It’s certainly true that Minecraft servers benefit in CPU performance from 64-bit versions of Java. The answer is actually incredibly simple: memory. The server running on a 64-bit Java Virtual Machine uses a minimum of about 100 MB more memory. This makes perfect sense because 64 bits > 32 bits by definition!

The Raspberry Pi’s 1 GB of memory has been the biggest obstacle for this project since the very beginning. Back when I first went into the Paper Minecraft developer IRC room and told them what I was trying to do I was practically laughed out of the chat room for even thinking of trying this. Most Minecraft server branches including vanilla can’t even start on the Pi because of the limited memory.

For a dedicated Minecraft server on the Pi I very highly recommend staying 32-bit. You will have more available memory which means it will be much faster and more stable. Since memory is our bottleneck the increased CPU throughput does not help us and losing *any* of our memory is disastrous!

If the Raspberry Pi 4 has more memory like we all expect it to this recommendation will change completely. Even 2 GB of memory would make the extra memory that 64-bit uses a non-issue and the CPU throughput performance gains very desirable. For now though stay 32-bit for a Minecraft server!

Tested Distributions

Raspbian Lite – It’s Raspbian. It has very low memory usage and is the official distribution of the Raspberry Pi. The server runs very well on this. One downside is it does not have packages for OpenJDK 11 (OpenJDK 9 is the newest one in the Raspbian repository at time of writing). It’s overall a great choice.

Ubuntu Server 18.04.2 – Ubuntu Server is my favorite Linux distro. I use it for nearly all of my projects. The performance of the 32-bit armhf version is on par and in some ways superior to Raspbian due to the availability of OpenJDK 11 on Ubuntu. It’s a fantastic choice! Click here for my Ubuntu setup guide for Raspberry Pi. The 64-bit version is not a fantastic choice and not recommended because of the higher memory usage. Stick with 32-bit and you’ll be a happy camper with Ubuntu Server.

Debian Buster 64-bit – Debian is the distribution Raspbian is based on. This version is a preview of Debian “Buster” which is the successor to Stretch and will be the next version of Raspbian when it is released. I like this distribution but it is currently still unofficial and unsupported. Performance and stability was less than Ubuntu and Raspbian.

Benchmark Your Storage

Make sure your storage is running fast enough to be an effective Minecraft server. I wrote a benchmark for this purpose to make this extremely easy. To get accurate results make sure nothing is running when the benchmarking is taking place.

Run the benchmark by pasting/typing:

sudo systemctl stop minecraft
curl https://raw.githubusercontent.com/TheRemote/PiBenchmarks/master/Storage.sh | sudo bash

Ideally you will score around 1000 for a good quality Micro SD card (and much higher for solid state storage). A low score (< 700) here indicates here that it is probably time to upgrade to a solid state drive or a faster Micro SD card. Click here to view all the existing benchmarks.

You can still run the server if you’d like with a low storage score but be advised when operations like saving the server’s blocks take place the people online may experience quite a big of lag!

Installation

SSH into your Raspberry Pi and paste the following commands:

wget https://raw.githubusercontent.com/TheRemote/RaspberryPiMinecraft/master/SetupMinecraft.sh
chmod +x SetupMinecraft.sh
./SetupMinecraft.sh

The script will setup the Minecraft sever and ask you some questions on how to configure it. I’ll explain here what they mean.

“Set clock speed to 100 MHz? Requires reboot. (y/n)?” – Highly recommended but at your own risk. This will overclock your MicroSD card reader for you to 100 MHz giving you much faster read/writes on your server.

There are some cards (usually cheap ones) that can’t handle this overclock and will fail to boot afterward. If this happens don’t panic! You can simply undo the overclock by connecting the MicroSD/SSD to your computer and removing the line dtparam=sd_overclock=100 from /boot/config.txt. Save and reboot the Pi. Run MinecraftSetup.sh again and choose ‘no’ the next time.

“Change GPU shared memory to 16MB? Requires reboot. (y/n)?” – This is recommended for everyone. Unless you are running on a GUI distro you would be crazy not to do this! Since we are running a headless lite distribution we don’t need any more than the bare minimum of 16MB. That extra memory makes a gigantic difference when we are only working with 1 GB total.

“Enter amount of memory in megabytes to dedicate to the Minecraft server” – The amount of memory that will be dedicated to the Minecraft server. The more the better, but you must leave some room for the operating system background processes.

If you exceed the total available memory either the server will crash or the Pi will get incredibly slow to the point where your SSH session will start timing out. The setup script will make a recommendation to you which is your available memory – 10% for headroom. If you aren’t sure what to put just go with the recommended amount.

“Start Minecraft server at startup automatically (y/n)?” – This will set the Minecraft service to start automatically when your Pi boots. This is great because whenever you want to play you can just plug it in and go without having to SSH in.

“Automatically reboot Pi and update server at 4am daily (y/n)?” – This will add a cron job to the server that reboots the Pi every day at 4am. This is great because every time the server restarts it backs up the server and updates to the latest version. See the “Scheduled Daily Reboots” section below for information on how to customize the time or remove the reboot.

That is it for the setup script. The server will finish configuring and start!

First Run

The first time you run the server it will take a little longer to start since it is generating all the server data. If you try to log in before it fully starts you will get a connection timeout error. Watch for the line: “Timings Reset”. This is the last line that prints when the server is ready to rock and roll. At this point you will be able to connect successfully.

The very first time you log into the server it will be slow for about 1-2 minutes. This is because since nobody has logged in before the server has to scramble to generate all the chunks within your view distance (10 by default) and send them to you/store them. During this time you may not be able to see very far and if you try to destroy blocks there will be noticeable lag from when they break to when they actually disappear.

Don’t panic! This will go away within a couple of minutes as the Pi catches up with all the first time login stuff it needs to do. Performance stabilizes and it will feel very much like the offline experience after that.

If you are hosting for a few friends I’d recommend logging in for the first time right after you set up the server instead of having several people nail a blank server at first startup. This gets it out of the way and when everyone is ready to log in the starting area chunks will be fully fleshed out and the Pi just has to read them. It’s an order of magnitude faster for the Pi to read chunks than to generate and store chunks.

In my experience after the initial login exploring new parts of the server doesn’t cause any lag even though new chunks are being generated. The reason for this is that when you’re walking it’s really only having to generate a new chunk as you get close to the border instead of a huge square area of chunks in all directions and all at the same time like during the first login.

Start, Stop and Restart Server

The server can be started, stopped and restarted two different ways. You can use the provided scripts in the Minecraft folder or you can use systemctl. Here are the commands:

cd ~/minecraft
./start.sh
./stop.sh
./restart.sh

-OR-

sudo systemctl start minecraft
sudo systemctl stop minecraft
sudo systemctl restart minecraft

Automatic Backups

The server backs up each time it starts. This helps you recover easily if something goes wrong. This system works best if you configured the server to restart daily since it means you will have a backup every day.

To access these backups type:

cd ~/minecraft/backups
ls

When a backup is made the filename will be the date and time the backup was taken. If you need to restore a backup it’s very easy. Substitute the timestamp in my example to the backup you want to roll back to. Type:

cd ~/minecraft
./stop.sh
rm -rf world world_nether world_the_end
tar -xf backups/2019.02.15.22.06.30.tar.gz
./start.sh

Your world has now been restored! It’s a good idea to download these backups off the Pi periodically just in case the Pi’s storage fails.

Scheduled Daily Reboots

The daily reboots are scheduled using cron. It’s very easy to customize the time your server restarts.

To change the time that the server restarts type: crontab -e

This will open a window that will ask you to select a text editor (I find nano to be the easiest) and will show the cronjobs scheduled on the Pi. The Minecraft one will look like the following:

0 4 * * * /home/ubuntu/minecraft/restart.sh

There are 5 fields here. The default restart time is set to reboot at 0 minutes of the 4th hour of the day (4 AM). The other 3 fields are left as * to represent every day of every month. Make any desired changes here and press Ctrl+X to exit nano and update the cronjob.

To remove the daily reboot simply delete the line and save.

Reconfigure / Update Scripts

The scripts can always be reconfigured and updated by downloading the latest SetupMinecraft.sh and running the installer again. It will update all of the scripts in the Minecraft directory and reinstall the startup service for you.

Running SetupMinecraft.sh again will also give you a chance to reconfigure options such as the memory dedicated to the server, daily reboots, starting the server on boot, etc.

This will not overwrite your world or any other data so it is safe to run!

Port Forwarding

If everyone on your server is on the same LAN or WiFi network as you then you don’t need to do this. If you want people to connect from outside your local network then you need to set up port forwarding on your router.

The process for this is different for every router so the best thing to do is just look at your router and find the model # and put that in google with port forwarding for easy instructions on how to do it for your specific router.

You want to forward port 25565. The type of connection is TCP if your router asks. Once you do this people will be able to connect to your Minecraft server through your public IP address. This is different than your local IP which is usually a 192.x.x.x or 10.x.x.x. If you don’t know what that is just go to google and type “what’s my ip” and Google will kindly tell you!

Wired vs. Wireless

Going with an ethernet (wired) connection is going to be faster and more reliable. There’s so much wireless traffic and other interference in the air that running your server on WiFi is not recommended.

Even if it is working great 99% of the time it can ruin your experience very quickly if the WiFi drops for a couple of seconds and you get blown up by a creeper!

All that being said, the server works fine on wireless. The script will work fine as is with a wireless connection.

Conclusion

OpenJDK 9’s new garbage collector has made running a server on the Raspberry Pi feel great! We can run at the default view distance of 10 with default entity settings.

If you have any feedback or suggestions let me know in the comment section. A lot of the new developments in this script were directly from comments to the older articles.

Have fun!

Comments 56

  • Hello! Thank you so much for making this guide! This helped so much! I was wondering though, do you know of a way to add plugins to the server and choose a map? I know there are other ways that include those options, but they didn’t work for me, and this was a lot simpler! Thank you so much for your help, have a nice day!

    • Hey Puppy,

      Glad you enjoyed the guide!

      The good news is that this server supports plugins. The server supports Spigot/Bukkit plugins. There’s tens of thousands of them! https://dev.bukkit.org/bukkit-plugins and https://www.spigotmc.org/resources/categories/bukkit.4/ are two good repositories of plugins. Installing these is pretty much as simple as downloading the plugin and extracting it to your ~/minecraft/plugins directory.

      As far as choosing maps there’s a few different ways to do it. The most popular way is by specifying a seed. If you browse Google for Minecraft 1.13 seeds you can get a bunch of them. To you use a seed you will go to the minecraft directory and edit server.properties by typing nano server.properties. In that file you will see a line that looks like seed=x. If you put the seed in here before you start your server it will generate that world from the seed! You can also use programs such as MCEdit to edit the world in a map editor and use that for your server.

      Let me know if you run into any trouble or have any more questions!

      -James

  • What a fantastic script, thank you.
    After the 1st reboot that followed on from things like overclocking the SD card, a server was up and running with the server output appearing on the screen and accepting commands as expected. The option to overclock the SD card, automatically run the server at startup and doing the reboot at 4am were all accepted.
    But after closing the Raspberry Pi 3B+ down after the next switch on I can’t see the server running and can’t find it to play. The IP address of 192.168.0.149 was checked, and I saw that about 15 seconds after the command prompt appeared, the cursor moved to the far left (instead of being after the $ sign), and “screen -r minecraft” failed to find a screen to resume.
    Running ./start.sh did start the server.
    I admit to installing the GUI then using raspi-config to boot to command only before doing the server installation. Is this the cause of the server not runing at bootup?

    • Hey Greenbandit,

      I downloaded Raspbian full to do some testing and found some problems in the script when ran on Raspbian full vs. the Lite version. This has to do with how the networking services start in full vs. lite.
      I have updated the scripts with several fixes thanks to your feedback. This will improve reliability on both versions. If you download the latest SetupMinecraft all the fixes are in there!

      -James

      • James,
        That has sorted it on my system. This is awesome.
        I can now install Raspbian (Full), then use raspi­config to get the Raspberry Pi to boot to command before running your setup script thus giving me the ability to go back to the desktop between minecraft sessions to edit files or whatever if I ever want to (because I am not that good at using the command line for the clever stuff). And the minecraft server now runs as intended after a reboot.
        Here’s an idea. My router is set to have a limited DHCP address range to leave room for fixed IPs on my LAN, so since I am aiming towards leaving the Pi on 24/7 for my boys I manually edited /etc/dhcp.conf to give eth0 & wlan0 a fixed IP address. Would it be worthwhile adding such an option to the setup script to ensure that the IP address doesn’t ever change? Since I didn’t setup my wifi during the initial Raspbian setup, the (commented out) wlan0 section in /etc/dhcp.conf was not created, but it did work when manually added.

  • Hi, when going through the setup, it always ends with “Setup is complete. Starting Minecraft server…” pauses for a few seconds, and then says
    “There is no screen to be resumed matching minecraft.” Any ideas?

  • “Setup is complete. Starting Minecraft server…
    There is no screen to be resumed matching minecraft.”
    Help! I have tried executing start.sh a couple times, but the server never seems to start. Any help is appreciated.

    • Hey Wyatt,

      Let’s find out! There’s two log files and one of them should tell us what is going wrong. Go ahead and do a
      cd ~/minecraft/logs and then do:
      nano latest.log

      The other log can be viewed by typing sudo journalctl -u minecraft. I don’t suspect you’ll see anything unusual in this one since it sounds like it is making it to the end of the start.sh script.

      Let’s see what it says in your latest.log file. Can you also post which Pi you are using?

      Thanks,
      -James

  • James,
    I remain grateful for your setup script.
    A RPi minecraft server received a lot of use last weekend from 4 LAN players and it has worked great. In contrast to a previous setup based on a vanilla server, this didn’t show signs of lag even with the view distance at the default 10 whereas the vanilla server needed the view distance at 6 to make it playable on the world we were using.
    But I’m puzzled why backups are not working. I can see the “mkdir backups” line in the setup script, but there was no backups directory until I manually created one. After a 4am reboot though, there is no backup visible to user=pi in /minecraft/backups. Is this my finger trouble? Out of interest, which part of the scripts is it that makes the backup?

    • Hey again Greenbanditz! I’m glad it’s working great on vanilla settings! That was my experience as well as before Java 9 came out I had to turn down the view distance and some other settings to get good performance.

      The backup is made in start.sh with this line:

      # Create backup
      echo “Backing up server (to minecraft/backups folder)”
      tar -pzvcf backups/$(date +%Y.%m.%d.%H.%M.%S).tar.gz world world_nether world_the_end

      Can you check your start.sh and make sure that it has this line? If you had updated from a previous version it may not have pulled it down from the github repository.

      If your start.sh is missing that line download the latest SetupMinecraft.sh which now will update all of the scripts in the Minecraft directory. This will get everything up to date!

      There is one other possibility. Did you change the world name of your world? It assumes that your folders are world, world_nether and world_the_end. If you have changed it I may need to add a line that reads from server.properties what the world name is so that if people are changing it then backups are still taken.

      -James

      • James,
        Sorted.
        I had an earlier start.sh that did not have the backup line in it, it was not a problem due to a renamed world.
        I now have backups being made to the SD card. Backups to a USB stick is the next task to ensure the world is not lost if the SD card goes down. 🙂

        I remain really grateful for your help and excellent scripts.

        • Awesome! That’s definitely the best way to do it. I may update the script to let people choose a backup directory to make setting this up easier in the future but I’m glad you got yours working!

          -James

  • Hey James, this is great and I’m loving that I can host a server on my Pi instead of keeping my beefy PC running. Now my friend and I have a game we can play together, and he can log on whenever he likes.

    I’m using with the Lite version as recommended, but found that my server does not start automatically at startup anymore. I couldn’t find a file in the ~/minecraft directory where these settings would be – any advice? Should I just try reinstalling?

    • Hey Kieran,

      I have fixed this in the latest version. It broke due to a broken ca-certificates-java package in Raspbian. I’ve just added the capability for SetupMinecraft to update your scripts to the latest version without reinstalling.

      Simply do:
      cd ~
      rm SetupMinecraft.sh
      wget -O SetupMinecraft.sh https://raw.githubusercontent.com/TheRemote/RaspberryPiMinecraft/master/SetupMinecraft.sh
      chmod +x SetupMinecraft.sh
      ./SetupMinecraft.sh

      This will update all of the start/stop scripts to the latest version. It will also reinstall the startup service. If it is still having trouble we will dig a little deeper by checking ~/minecraft/logs/latest.log.

      Let me know how it goes!
      -James

      • You’re a legend, James! The server didn’t end up rebooting at 4AM, but that’s fine for me now because I don’t have to manually restart it myself at 4AM. I’ll keep it running and see what happens overnight to see if it restarts this time.

        • That’s awesome to hear Kieren, keep us posted!

          Make sure your Pi isn’t still set to the wrong time zone (I think the default time zone is the UK)

  • Hello James,
    I also suffer from the “There is no screen to be resumed matching minecraft”-problem. The server was running fine for some weeks and then stopped to work at all (after some stupid server “maintenance” . Never touch a running system…).
    I tried a new install on a blank SD-card and a fresh download of raspbian lite but there seems to be a problem with the installation of java. Again “… no screen …” but without a working java there will be no server running and therefore no screen to resume…
    I hope the java-issue will be fixed soon.
    You did a great job! Thank You! Without Your work I wouldn’t ever have set up a minecraft server on a RaspberryPi.

    • Hey Achim,

      I found the problem. It turns out there is a problem with the Raspbian ca-certificates-java package right now and it’s not installing correctly. Specifically it gives: Error: missing `client’ JVM at `/usr/lib/jvm/java-9-openjdk-armhf/lib/client/libjvm.so’.

      I have just committed a workaround to SetupMinecraft.sh. Do a:

      rm SetupMinecraft.sh
      wget -O SetupMinecraft.sh https://raw.githubusercontent.com/TheRemote/RaspberryPiMinecraft/master/SetupMinecraft.sh
      chmod +x SetupMinecraft.sh
      ./SetupMinecraft.sh

      and Java will now install correctly! The workaround specifically was a soft link from the client to the server JVM folder. The SetupMinecraft script now does this for you but the manual fix is:
      sudo ln -s /usr/lib/jvm/java-9-openjdk-armhf/lib/server /usr/lib/jvm/java-9-openjdk-armhf/lib/client
      sudo apt-get install openjdk-9-jre-headless -y

      Thanks for reporting the issue!

  • Hey James,
    Your solution works fine for me. I used the manual fix on my server and a friend of mine set up a new server which also works out of the box.
    Thank You! We really appreciate the way You share Your knowledge with us.

  • Maybe I have missed something but the server was installed in /root/. Is that intended?

    • Hey Arne,

      Did you sudo when you installed the script? It can be ran as root and will go into the root folder if you sudo or run the Setup as root. The intended location is your user’s home folder (~).

      If you didn’t run the Setup as root can you let me know what distro you are using so I can test it?

      -James

  • Thank you so much for this! It worked great for me and my friend for a week (much better than my own attempt at getting a paperMC server on a RPi) but now they keep getting disconnected with “[name] disconnected: timed out”. It happens quite randomly. I have searched for the error online and i could only find that it is their issue. Is this the case or is there something wrong with my internet?

    Thanks!

    Also, how do i switch screens back to the raspbian terminal (right now, i just reconnect my ssh connection and it puts me back there).

    • Hey Alex,

      To switch back to the Raspbian terminal press Ctrl+A and then Ctrl+D. You’ll see a message that says “[detached from 12710.pts-0.raspberrypi]” and be back at the terminal. To get back into the server after that you will just type screen -r minecraft.

      For the connection timed out message this is indeed a network problem. If it only just started happening the first thing I would try is to unplug your router for about 30 seconds and then plug it back in. If you have a separate cable modem or DSL modem do it for that one too. I’ve found consumer grade equipment does this from time to time. The problem could also be on his end so he should do the same thing to his network equipment. It may be that simple!

      If that doesn’t get it try having him run a continuous ping to the Raspberry Pi. Have him go to his command prompt and type ping -t x.x.x.x and it will continuously ping your Pi once per second. This is useful because you can see if you are getting latency spikes or timeouts there to help confirm that the entire network is dropping and not just his connection to the Minecraft server.

      Let me know what you find!

      -James

  • Hi James,

    I installed this on my 3B+ yesterday and it’s working great so far! I just have one question: I said no to the “start server at boot” thing while setting it up, but now I’ve changed my mind. Also, I’ve already built a lot of things and don’t want to lose them. Finally, the daily reboot prompt never came up while I was installing.

    Is it possible to run the setup script again without losing any data? Or Is there a simpler option to enable both the daily reboot and the start server on startup? Thanks!

    • Hey John,

      There absolutely is! Just run the SetupMinecraft.sh script again and it will let you reconfigure the start up service, daily reboot, etc. without touching any of the data!

      -James

      • Hey james,

        Thanks, I did it and it worked! One more question: Would it be possible to migrate this server from the pi onto another device with more power? I just discovered an old laptop of mine that may work better. I plan to install Ubuntu Server on it and use it as a dedicated minecraft server while i tinker with my Pi on other projects.

  • Hello james,
    Can I use the pi to build a forge mod server?

  • Hi James,

    saw some
    /home/pi/minecraft/restart.sh: 41: /home/pi/minecraft/restart.sh: StopChecks++: not found
    while testing some restart scenarios.
    Origins from the stanza
    # Wait up to 30 seconds for server to close

    in your script.

    In Raspbian Lite /bin/sh is pointing to /bin/dash what does not know ((StopChecks++)) to increment the variable.

    Replacing this by StopChecks=$((StopChecks+1)) removes the issue and should work on Ubuntu, too.

    Cheers
    Jason

  • Hi again,

    in addition to my last post I’d like to mention that by adding

    [Service]

    TimeoutStartSec=600

    to /etc/systemd/system/minecraft.service you may overcome a timeout when wget from updating to the most recent paperclip version takes some more time. Otherwise systemctl kills the minecraft server and you may wonder why it doesn’t run after the nightly reboot.

    Cheers
    Jason

  • Hi James,
    You can use Debian Buster for the RPI3 series to get Java 11 https://people.debian.org/~gwolf/raspberrypi3/20190206/20190206-raspberry-pi-3-buster-PREVIEW.img.xz

  • Hey James,

    I know, I know,
    1.14 just came out, but do you have any plans for a rebuild to upgrade to this?

    -Harrison

    • Hey Harrison,

      Most definitely! Right now I’m waiting for the Paper / Spigot version of 1.14 to drop which is usually pretty quick after these new releases.

      It should appear at https://papermc.io/downloads when it is available and I will update all of the code to use it!

      -James

  • I have an already existing server on PC, but I would like to port it to Raspberry Pi, would it be possible? (I also use CraftBukkit with a couple lag fixing plugins.)

    • Absolutely! Since it’s the Java version there’s no portability issues between platforms. You’d just put your server.properties and world folder on the Pi.

      The plugins would be the same. You could even copy the plugins from your existing server. Paper is in the same source tree as Bukkit and Spigot so it should be very easy to do this!

  • Ok, that clears things up. Thanks!

  • So I have this up and running. How do you go about connecting to it from the Android version of Minecraft?

  • For the automatic backups to work does my world have to be named “world”?

    • At the moment it does. I should probably change this though because it would be easy to make it use the world name from server.properties. I’ll add this in soon!

  • Hi amazing setup btw. But i have a problem with installing plugins. Im trying to download worldedit 1.13+(https://dev.bukkit.org/projects/worldedit/files/2663452) on the server. But when i go to the directory plugins and type wget https://dev.bukkit.org/projects/worldedit/files/2663452/worldedit-bukkit-7.0.0-beta-05.jar and it is downloaded. The plugin doesnt work. Already restarted the server, any ideas????

  • Hello,

    I am struggling with my pie server. I have tried a few different sets of instructions and the build seams to go well, but I can not find my server from my windows Minecraft screen. I have tried the wired and the wireless IP. The only tutorial that has worked so far is if I run a Pocket Edition Server.

    Any thoughts?

  • I saw a version of paper that was 1.14 . Are you working on a new bash file or is there an easy way for the server to update itself.

    • Hey Dylan,

      I’ve updated the script to get 1.14.1. If you run the SetupMinecraft script again it will retrieve 1.14.1.

      -James

  • Hi, is it possible to downgrade to 1.13.2? if so, how to downgrade? I’d like to run dynamap on my server.

    • Sure, if you’d like to downgrade open up start.sh and replace 1.14.1 with 1.13.2 and it will change your server to that version!

  • Hello James,
    I’m also suffering from the “There is no screen to be resumed matching minecraft”-problem. I had reinstalled a clean version of raspbian lite a couple of times so far with no luck.
    I followed the advice you gave Achim ealier in the year although it seems to have had no effect.
    Thank you for the work nonetheless!!

    • So I just managed to get around this by connecting my Pi to a different network for initial setup. Although now I’m having problems with this:

      [13:27:08 WARN]: Can’t keep up! Is the server overloaded? Running 24630ms or 492 ticks behind

      The number of tickets will increase and decrease until the server crashes.
      Any ideas?

Leave a Reply to GreenbanditMZ Cancel reply

Your email address will not be published. Required fields are marked *