Package Details: spigot 1.17+b128-1

Git Clone URL: (read-only, click to copy)
Package Base: spigot
Description: High performance Minecraft server implementation
Upstream URL:
Keywords: craftbukkit games minecraft minecraft-server
Licenses: LGPL
Conflicts: bukkit, craftbukkit, spigot-patcher
Provides: bukkit=1.17, craftbukkit=1.17, minecraft-server=1.17
Submitter: Schala
Maintainer: edh
Last Packager: edh
Votes: 29
Popularity: 0.027945
First Submitted: 2013-10-09 23:27
Last Updated: 2021-06-17 18:02

Dependencies (11)

Required by (8)

Sources (8)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Majora320 commented on 2021-06-17 05:32

Looks like Java 16 is now mainlined :)

toasterbath commented on 2021-06-12 19:36

I was able to build newest (1.17) spigot with this PKGBUILD patch:

diff --git a/PKGBUILD b/PKGBUILD
index 7763acd..ae2edf1 100755
@@ -2,15 +2,15 @@
 # Submitter: Schala Zeal <>

 pkgdesc="High performance Minecraft server implementation"
-depends=("java-runtime-headless>=8" 'screen' 'sudo' 'fontconfig' 'bash' 'awk' 'sed')
+depends=("java-runtime-headless>=16" 'screen' 'sudo' 'fontconfig' 'bash' 'awk' 'sed')
 optdepends=("tar: needed in order to create world backups"
        "netcat: required in order to suspend an idle server")
 makedepends=("java-environment>=8" 'git')
@@ -26,7 +26,7 @@ source=("BuildTools-${_pkgver}+b${_build}.jar::

beware, you need java runtime >= 16, I installed amazon-corretto-16 from AUR in this case.

edh commented on 2021-06-12 09:02

Just as a heads-up, I will wait until java-runtime-headless>=16 hits the stable Arch repositories before publishing the next release of spigot to the AUR. Please be patient until then.

edh commented on 2020-11-21 16:08

You'll see this message if you attempt to stop a server that is already dead. At first glance this does not seem like an error.

Can you elaborate a little on what you are trying to do and which part of it does not work? Have you tried stopping and then restarting the service again on the command line via the spigot script?

Bujiraso commented on 2020-11-21 13:49

I started the server once and it ended abnormally and now all the systemd service does is this:

spigot[2940]: The corresponding screen session for spigot was already dead. 
systemd[1]: spigot.service: Succeeded.

Is there a way to fix it? Is this a bug?

edh commented on 2020-11-17 10:45

@heycrip haha no worries. You're welcome! Be sure to read/skim the wiki first next time though. And, once again, don't edit files in /usr/bin :D

heycrip commented on 2020-11-17 10:37

God I'm dumb :'). Need more coffee. Sorry about that and thanks.

edh commented on 2020-11-17 08:38

@heycrip What? Why would you change the /usr/bin/spigot script? There is a dedicated setting for this in /etc/conf.d/spigot . This is also documented in the ArchWiki.

P.S. please don't edit files in /usr/bin. That is generally a bad idea.

heycrip commented on 2020-11-17 08:24

When running spigot with a java -jar -Xms16G -Xmx16G, it uses 16G. However when I change the /usr/bin/spigot script to those values, the server shows a max of 1024M (using tps).

Am I missing something?

edh commented on 2020-10-03 09:52

Unfortunately there was a bug related to the new way users are created. It has been fixed in the new release of the package but for servers already featuring a craftbukkit user, manual intervention is needed: If you happen to encounter the error message This account is currently not available., you will need to update the login shell such that you can interact with the console again by running usermod -s /bin/bash craftbukkit as root.