Package Details: spigot 1.20.5+b181-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, craftbukkit, minecraft-server
Submitter: Schala
Maintainer: edh
Last Packager: edh
Votes: 29
Popularity: 0.001520
First Submitted: 2013-10-09 23:27 (UTC)
Last Updated: 2024-04-23 18:27 (UTC)

Dependencies (11)

Required by (5)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 14 Next › Last »

ASzc commented on 2018-12-13 16:53 (UTC)

Upstream news post says build 84 of BuildTools is now required:

https://www.spigotmc.org/threads/buildtools-update-required-1-13-2.351162/

ASzc commented on 2018-12-13 16:47 (UTC)

Getting an error:

**** Your BuildTools is out of date and will not build the requested version. Please grab a new copy from https://www.spigotmc.org/go/buildtools-dl

http://ix.io/1vVL

edh commented on 2018-10-18 14:37 (UTC)

@tealeaf Ok, you convinced me. I will update the package soon. However, note that Arch ships the latest software but not unstable or beta releases by default. IMHO this version lies somewhere in between beta and stable hence my reluctance to update.

tealeaf commented on 2018-10-18 11:56 (UTC) (edited on 2018-10-18 11:56 (UTC) by tealeaf)

From my perspective I would say that this is the time to update -- I can't see that this status will ever change. There could always be bugs, and now there has been time for really serious ones to emerge.

I completely supported the delay in that initial testing period, but given that there are now no serious known conversion bugs, I think it's time to move on.

With respect to older plugins, that's a problem that occurs every time the server software is updated. Whilst 1.13 was a huge update, in this sense it's not really that different to other plugin incompatibilities.

It strikes me that as this is the current version, and especially given Arch's tendency towards the bleeding edge, at this point it feels that the onus should be on people seeking stability to hold back their installs, rather than requiring people who want to update to make the extra effort.

Just my opinion!

edh commented on 2018-10-18 11:28 (UTC)

@sflor I am not really sure whether now is the right time to update. To me the statement

Caution (1.13.x - Current): There are no known serious world conversion bugs. Some aspects of older worlds may not function correctly, but all player data remains intact. Native 1.13 plugins should be used, but older plugins will function as well as they are ever likely to. Caution is still advised as there may be undiscovered data loss bugs.

does not really sound reassuring. However, I am more than happy to receive more input from users whether an update is desired.

For now, I would advise you to just bump the pkgver and _build variable manually.

sflor commented on 2018-10-17 21:52 (UTC)

Are you going to update to 1.13 now that they've removed any critical warning?

edh commented on 2018-09-10 03:29 (UTC)

@Bernie_McGee Thanks for the bug report and the accompanying workaround. I will look into fixing the issue as soon as I can spare some time.

Bernie_McGee commented on 2018-09-07 18:12 (UTC)

If anyone is using this tool with Paper and has issues with the idle server daemon closing the server while players are online, add --nojline to your SERVER_START_CMD.

There seems to be an issue with the script parsing Paper's /list output due to part of it being bold. --nojline disables the "pretty" output and seems to be a good workaround.

edh commented on 2018-07-23 05:44 (UTC)

I will wait out the first release for now as there is no safe update route outline in the blog post. If you really feel like updating yourself and have read the above linked article, please simply adapt the _pkgver and the _build variable.

@jgottula Thank you very much for the heads up! However, there is no need to flag the package and leave a comment. One notification is sufficient.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 14 Next › Last »