Arch Linux User Repository

Package Automation

Starting with version 1.21.50.10, this AUR package uses an automated process for doing the following:

• Identifying when a new version of the Bedrock Minecraft Server has been released
• Downloading that new source zip file and getting its new hash plus version number
• Updating this AUR package PKGBUILD with a new source zip file hash, version, and URL

Disclaimers & Limitations

This automated process does NOT test the functionality of the new source code itself. The upstream vendor (Mojang) may release non-functional software or change how it must be installed.

In either case, this AUR package may successfully install, but the Bedrock Minecraft server may not launch or run properly.

The automation might fail to increment this package to the latest version if there is a major change to the release mechanism used by the upstream vendor of the source zip file (i.e. they move it to a totally new URL, they significantly change the layout of the download page, et cetera).

The current download page is hosted here:

• https://www.minecraft.net/en-us/download/server/bedrock

The "Minecraft Dedicated Server software for Ubuntu (Linux)" source zip file is the one that should be referenced in the PKGBUILD file for this AUR package.

Report an Issue

Please report any issues with the AUR package build automation, the AUR package PKGBUILD file contents, or the systemd unit files used to run the server in a comment here.

Issues with the upstream vendor's source code should be reported to the upstream vendor.

Learn More

If you are curious to see how the AUR package build automation works to automatically increment the package version each time there is a new release by the upstream vendor, please visit this page:

• https://gitlab.com/codrcodz/aur-minecraft-bedrock-server

Good ole M$, you will now see the following message in the console log on startup:

================ TELEMETRY MESSAGE ===================
Server Telemetry is currently not enabled.
Enabling this telemetry helps us improve the game.

To enable this feature, add the line 'emit-server-telemetry=true'
to the server.properties file in the handheld/src-server directory
======================================================

If you do wish to enable "telemetry", add the line to /opt/minecraft-bedrock-server/server.properties.

I got a little concerned when the email alert mentioned Java server but then I see you already corrected the wording.

Package Automation

Starting with version 1.21.50.10, this AUR package uses an automated process for doing the following:

• Identifying when a new version of the Bedrock Minecraft Server has been released
• Downloading that new source zip file and getting its new hash plus version number
• Updating this AUR package PKGBUILD with a new source zip file hash, version, and URL

Disclaimers & Limitations

This automated process does NOT test the functionality of the new source code itself. The upstream vendor (Mojang) may release non-functional software or change how it must be installed.

In either case, this AUR package may successfully install, but the Bedrock Minecraft server may not launch or run properly.

The automation might fail to increment this package to the latest version if there is a major change to the release mechanism used by the upstream vendor of the source zip file (i.e. they move it to a totally new URL, they significantly change the layout of the download page, et cetera).

The current download page is hosted here:

• https://www.minecraft.net/en-us/download/server/bedrock

The "Minecraft Dedicated Server software for Ubuntu (Linux)" source zip file is the one that should be referenced in the PKGBUILD file for this AUR package.

Report an Issue

Please report any issues with the AUR package build automation, the AUR package PKGBUILD file contents, or the systemd unit files used to run the server in a comment here.

Issues with the upstream vendor's source code should be reported to the upstream vendor.

Learn More

If you are curious to see how the AUR package build automation works to automatically increment the package version each time there is a new release by the upstream vendor, please visit this page:

• https://gitlab.com/codrcodz/aur-minecraft-bedrock-server

@d2_ricci and @NukeCode87,

I have created some automation for speeding up the AUR release process for this package.

Please visit this repository and review the README for details:

https://gitlab.com/codrcodz/aur-minecraft-bedrock-server

My next task will be to run the automation described in that README via a CI/CD pipeline that will be scheduled to run every hour.

Until then, one of us can use this automation from any Arch-based host to generate a new AUR release anytime there is a new source zip release from the upstream vendor.

Nice job all. My son is super happy.

I did not realize til now that we were using the azureedge.net instead of the direct minecraft.net link

I will try and get the next update with the suggestion from @nukecode87's suggestions.

@NukeCode87 that also worked for me.

I added those changes, along with some comments in the PKGBUILD file to aid contributors in the future, and I cut a new release.

Thanks for the help. Good team effort. I'll work on automating the update process for future releases.

This worked for me.

# Maintainer: Alan Beale <the.mrabz@gmail.com>

pkgname=minecraft-bedrock-server
pkgver=1.21.42.01
pkgrel=1
pkgdesc="Minecraft Bedrock Server for Windows 10 and Xbox One versions of Minecraft"
arch=('x86_64')
url="https://www.minecraft.net/en-us/download/server/bedrock"
license=('custom')
noextract=('bedrock-server-${pkgver}.zip')
backup=(opt/minecraft-bedrock-server/{server.properties,permissions.json,whitelist.json,allowlist.json})
makedepends=('unzip')
source=("https://www.minecraft.net/bedrockdedicatedserver/bin-linux/bedrock-server-${pkgver}.zip"
        'minecraft-bedrock-server.service'
        'minecraft-bedrock-server.sysusers'
        'minecraft-bedrock-server.tmpfiles')

sha256sums=('6d352cb588e6cfeacba5c272e3b4acb669526029fb8afb35f0861e6afb274776'
            'cc08effe04701f1ca16a1edd153d12a94ed498e9a3e68a004b74189eef9edb81'
            'a7070301958b58f804bb8dee8b66ef23ad7460403f7ba2cfffb549e29ad834d5'
            '829ff9e583408fcc1d0436a6896ecbd3128f893dcbc2b0147130219a13586ae3')

DLAGENTS=("https::/usr/bin/curl -A 'Mozilla' -fLC - --retry 3 --retry-delay 3 -o %o %u")

build() {
    unzip -q bedrock-server-${pkgver}.zip -d tmp
    rm bedrock-server-${pkgver}.zip
}

package() {
    install -d "$pkgdir"/opt/minecraft-bedrock-server
    cp -r -fHip "$srcdir"/tmp/* "$pkgdir"/opt/minecraft-bedrock-server
    install -Dm 644 minecraft-bedrock-server.service -t "$pkgdir"/usr/lib/systemd/system/
    install -Dm 644 minecraft-bedrock-server.sysusers "$pkgdir"/usr/lib/sysusers.d/minecraft-bedrock-server.conf
    install -Dm 644 minecraft-bedrock-server.tmpfiles "$pkgdir"/usr/lib/tmpfiles.d/minecraft-bedrock-server.conf
}

Reading through the Minecraft EULA, we are free to redistribute. Why not host it on a git repo with the Microsoft EULA posted there under that page?

I don't think we'd even need to repackage it. Just the pain of manually uploading it there and moving the upstream URL to the new git.

Seems the windows side was experiencing similar issues and posted an updated fix.

I'm still reading through what they changed to get it working. https://www.reddit.com/r/Minecraft/s/OXmCv0Nhw2

@Abzie, good to know. I rarely visited the download page directly except to send you some hash and version updates occasionally, so I didn't notice this.

I'll do some more testing with various DLAGENTs then. Managing a user agent string is a much smaller lift that writing a whole Selenium script thing. It is annoying and I do understand why you wouldn't want to take that on.

Thanks again for all your previous work @Abzie.

If anyone figures out the right DLAGENT string to use before I do, feel free to post it here and I will test it and update the package.

The checkbox has been a thing for some time, long before they restricted direct downloads, I doubt you need to bypass a checkbox.

@Abzie, thanks for that. I used a headless chrome browser during my testing which resulted in the download hanging, so at that point I assumed that it was the checkbox and not the DLAGENT, but it very well could have been the DLAGENT (or maybe you need both).

Either way, re-hosting the source zip elsewhere (Option 2) definitely bypasses this issue. If both the DLAGENT and checkbox need to be addressed, it makes Option 1 that much harder to implement.