Arch Linux User Repository

To get an overview of the available options provided by the management script, be sure to have a look at the help page or read the according section on the ArchWiki article [1].

You can quit the console without shutting down the server by press ctrl+a d (first ctrl+a and after releasing the buttons press d; ctrl+b also works). This will detach your input from the server console. The attaching and detaching is done with tmux (previously GNU screen) since it lets you view and type into the console, send single commands to it and keep it alive without a connected user. Take a look at the the command overview at the ArchWiki [2] to get a feel for its power. (@carmelo12341)

[1] https://wiki.archlinux.org/title/Minecraft#Setup [2] https://wiki.archlinux.org/title/Tmux

@Trevelian

Thanks for the quick fix! I accidentally broke it when hardening the script :|

Hello,

I dont know why but since I update my system and minecraft-server today, it seems that "minecraftd idle_server_daemon" is not running the command to list the user and so stop the server after the "IDLE_IF_TIME" even if player are online. I will try to find out why ;-)

@bronze Regarding the JDK issue, I feel uncomfortable removing the version requirement. I think the best approach would be to add versions to the provides of the jdk package such that the version criteria are fulfilled for this package. What do you think?

Concerning the Minecraft server management script, yes it indeed has been moved to its own repository. However, all the configuration is done during "build" time. To be specific, make configures everything. See the corresponding Makefile. Because it currently needs to be adapted to a specific server at build time, it does not make sense to package it on its own in a separate package. The script really is just a small management script and IMHO it is not worth making some kind of pluggable library out of it that could be depended on. If you have an idea of how to provide a sensible management script package, I am happy to create and maintain it.

EDIT: In case you just want a dirty hack to not install the server but everything else, simply set /srv/minecraft to be ignored during installation by pacman, see https://wiki.archlinux.org/title/Pacman#Skip_files_from_being_installed_to_system .

I have JDK8 installed but this PKGBUILD still needs java-17-openjdk. I only need the script (and the minecraft user, etc. But not any of the servers). I see the management script has been moved to a dedicated repo. Is the management scrip in the AUR somewhere?

The management script to control this minecraft flavor was moved to a dedicated repository at GitHub:Edenhofer/minecraft-server. The script works for various flavors of minecraft. It is very minimalist yet versatile and feature-rich. For more information on how to configure and install the script separately, visit the above linked repository.

@Ionble Forking the management script off the minecraft-server has long been on my TODO list. I finally took the time to implement this. See the above notice for a link to the new repository.

Can you indicate the exact upstream of the script and systemd unit? So that I can build this package on other distros.

These exact commands (together with a save-all) are already issued, see here. Furthermore, an explicit $ sync is issued. My best guess is that save-all involves complications in addition to the mere saving and thus sync thus not catch them all, i.e. does not wait.

I am happy to incorporate any new ideas of how to rectify this situation but I am unfortunately not aware of a good solution. The only thing I can think of is incorporating a small delay between save-all and $ sync

When backing up a running server with minecraftd-backup, I noticed that the tar command had output "file changed as we read it". This suggests that files are being modified by the running server during the backup, and I'm a bit concerned that this would result in corruption when the backup is restored.

Would it be possible for the script to do save-off and save-all prior to doing the backup, and then do save-on afterward?

@Xarius No, the backup logic should not have changed. Note, triggering new backups is purely a systemd thing and the configuration is exclusively handled by systemd timers. As long as you configure them in /etc and not in /usr/lib/ your changes will not be overridden by an update.

Did something change with how backups are handled recently? I had them set to be hourly, and they reverted to being daily after the last update. But, now when I try to enable the backup system service, it claims it doesn't exist? Highly likely I'm just forgetting something simple here.