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

@edh: A very strong preference for it over tmux, and it does the job. Could you elucidate on this bug you're talking about?

@Static_Rocket Awesome! I would be more than happy to merge your changes into this package if you would be interested in that. I think tmux should be preferred over GNU screen considering its more active development and the recent severe bug in GNU screen.

@Refutationalist Can you elaborate a little as to why you would prefer to use GNU screen for this package?

It would require about another day of tweaking but perhaps. It took a bit, but I attempted to replace the calls to screen with the closest equivalent tmux has to offer. I was hoping to make these modifications as patch friendly as possible. It would be simple to check what a user has installed and roll with whatever's available but it may be a little weird detecting if someone already has a tmux/screen session running when they have both tmux and screen installed.

But I guess that really doesn't matter. It could just default to screen if both screen and tmux are installed.

If tmux is added, could it be made possible to continue using screen if desired?

@edh I made a fork of this that uses tmux instead of screen. I was thinking about adding it to the AUR as a separate package but I figured I would ask and see if you wanted to look over it at all before that. Let me know if you're interested.

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

For those of you wishing to update to 1.17 before this PKGBUILD is updated, I did this temporary fix. First cd into /srv/minecraft or wherever your server files are and wget the newest official .jar file. You can relink minecraft_server.jar to what you just downloaded. The minecraft wiki says that the update requires java 16 but the main repository jdk-openjdk package is still for version 15. So you can use another AUR package to acquire openjdk16 and switch to that environment. Finally I chose to start the server in a gnu screen/tmux instance using java -Xms1024M -Xmx3072M -jar './minecraft_server.jar' nogui or whatever was in /etc/conf.d/minecraft.

@Xarius The full backup command reads ${SUDO_CMD} tar -C "${SERVER_ROOT}" -cf "${BACKUP_DEST}/${fname}" ${BACKUP_PATHS} --totals ${BACKUP_FLAGS} 2>&1 | grep -v "tar: Removing leading ". Thus by modifying ${BACKUP_FLAGS} in the config, you have full control over the arguments with which tar is called. You can change the current configuration to -I "..." and specify a program of your choosing with additional command line flags.

Is there any chance we could get an option in the config for how many threads to use when creating backups? I'd like to be able to reduce this number to avoid lag spikes while it executes. (i.e. Have the backup only use two threads rather than all of the available threads.)

@thatyou Sure, this can be done and would add two additional lines to minecraftd.tmpfiles but I don't get why this should be needed. The minecraft user at no point should edit the .jar file, right? Furthermore, it would add additional warnings to pacman's file ownership check (pacman -Qkk minecraft-server).