Package Details: spigot 1.16.3+b122-1

Git Clone URL: https://aur.archlinux.org/spigot.git (read-only, click to copy)
Package Base: spigot
Description: High performance Minecraft server implementation
Upstream URL: https://www.spigotmc.org/
Keywords: craftbukkit games minecraft minecraft-server
Licenses: LGPL
Conflicts: bukkit, craftbukkit, spigot-patcher
Provides: bukkit=1.16.3, craftbukkit=1.16.3, minecraft-server=1.16.3
Submitter: Schala
Maintainer: edh
Last Packager: edh
Votes: 28
Popularity: 0.28
First Submitted: 2013-10-09 23:27
Last Updated: 2020-10-03 09:47

Dependencies (11)

Required by (8)

Sources (8)

Latest Comments

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

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.

chan commented on 2020-08-21 03:12

@edh

It improved when I updated to 1.16.2+b121-1. Thank you for your prompt response.

edh commented on 2020-08-20 17:44

@chan Ah sorry, that's my fault. The error should be fixed now: I confused the username and the package name when switching to systemd's sysusers and tmpfiles.

chan commented on 2020-08-20 14:10

@theskycrawlers

Thank you. I tried "--forceUpgrade" but it didn't improve. The new finding is that when I run "spigot.jar" from the console it works, but it doesn't seem to work from systemd.

theskycrawlers commented on 2020-08-20 07:26

@chan

Try "--forceUpgrade" option for updating "world" data.

chan commented on 2020-08-20 01:59

After updating to 1.16.2, "systemctl start spigot" now exits immediately after booting. Is this just my environment?

The status is displayed as follows.

August 18 22:19:09 ?????? systemd[1]: Starting Spigot... August 18 22:19:09 ?????? spigot[2018]: Starting server... done August 18 22:19:09 ?????? systemd[1]: Started Spigot. August 18 22:19:36 ?????? spigot[5074]: The corresponding screen session for spigot was already dead. August 18 22:19:36 ?????? systemd[1]: spigot.service: Succeeded.

theskycrawlers commented on 2020-06-25 19:59

@xinayder

I read upstream release note at first. So, I start Spigot with "--forceUpgrade" option. It works correctly.

Thank you for your suggestion.

thanks,

theskycrawlers commented on 2020-06-25 18:59

@xinayder

Thank you for your fast(!) reply. Alright. I will post this issue to upstream (Spigot) forum.

thanks,

xinayder commented on 2020-06-25 18:55

@theskycrawlers You probably need to update your Nether dimension, as the update is focused on Nether and requires converting the world to the new format.

You should post this issue in the Spigot forums because, as you pointed yourself, there was no problem in building Spigot for 1.16.1, meaning if you have any problems with the server software itself it's not related to AUR.

theskycrawlers commented on 2020-06-25 18:51

Thank you for your works, maintainer.

I try to update spigot from "1.15.2+b112-1" to "1.16.1+b118-1". The package update itself looks like it worked. However, when I try to start the server, it always fails at the following log points.

Preparing start region for dimension minecraft:overworld

I often see that many of these errors are avoided by allocating more memory.However, despite seeming to have enough memory, the situation remains the same.

-Xms2G -Xmx8G

Should I have this issue in the spigot upstream forum?