# mcpelauncher for Linux and macOS Bedrock Minecraft

> mcpelauncher is an unofficial Linux and macOS launcher for Android editions of Minecraft: Bedrock Edition. It supports several CPU architectures, but its compatibility depends heavily on graphics capability, operating system version, and the selected Minecraft release.

**minecraft-linux/mcpelauncher-manifest** — The main repository for the Linux and Mac OS Bedrock edition Minecraft launcher.

- Repository: https://github.com/minecraft-linux/mcpelauncher-manifest
- Website: https://minecraft-linux.github.io
- Stars: 1,714 · Forks: 138
- Language: CMake
- License: GPL-3.0
- Published: 2026-10-16 · Updated: 2026-10-16 · Language: en
- Canonical page: https://hysenlabs.com/projects/minecraft-linux-mcpelauncher-manifest

## Why mcpelauncher targets Bedrock Edition on desktop systems

mcpelauncher addresses a specific platform gap: it provides an unofficial launcher for Android versions of Minecraft: Bedrock Edition on Linux and macOS. It is intended for players who want the launcher interface to log in, download Minecraft releases, and manage installed versions on a desktop operating system. The project is not presented as a replacement for every Minecraft edition. Its compatibility tables and bug list focus on Bedrock versions based on the Android edition, with documented coverage extending across older and newer releases depending on CPU architecture and graphics support.

The user interface is maintained in a separate repository, `minecraft-linux/mcpelauncher-ui-manifest`. This repository is the main mcpelauncher manifest and contains the CMake-based project structure for launcher components. That separation is worth noticing during evaluation because changes to the interface and changes to the launcher implementation do not necessarily belong in the same repository.

The README calls mcpelauncher an "unstable unofficial launcher." That description is important for adoption decisions. A desktop player may find the project useful, but should not treat the word unofficial as a minor packaging note. It identifies the project's relationship with Minecraft and acknowledges a higher tolerance for breakage, especially across the wide range of Linux distributions, CPU architectures, macOS releases, graphics drivers, and old Bedrock versions represented in its compatibility matrix.

## How mcpelauncher is organized and where version management occurs

The documented interface handles login, version downloads, and version management. The separate `minecraft-linux/mcpelauncher-ui-manifest` repository is identified by the README as the home of that user interface. The main repository instead exposes the launcher implementation through CMake-oriented directories such as `mcpelauncher-client`, `mcpelauncher-core`, `mcpelauncher-common`, `mcpelauncher-linux-bin`, and `mcpelauncher-mac-bin`.

This layout suggests a division between front-end concerns and platform or launcher components, but the README does not publish an internal data-flow diagram. It specifically says where login, downloading, and version management live. It does not document how credentials are stored, how downloads are resumed, how versions are verified, or how the launcher invokes the game. Those details should not be inferred merely from directory names.

Other entries indicate additional technical surfaces within the repository. Names such as `arg-parser`, `properties-parser`, `file-picker`, `game-window`, `sdl3`, `linux-gamepad`, `libc-shim`, and `simple-ipc` identify parsers, operating system interfaces, game presentation components, and IPC-related code areas. `mcpelauncher-linker`, `mcpelauncher-apkinfo`, and Android-related submodules also appear in the tree. However, the README does not explain each component's runtime role, supported configuration surface, or failure behavior.

For an engineer, this means the repository is more than a shell around a downloaded game package. It contains desktop launcher code, compatibility shims, input handling, window management, and platform binaries. It also means that understanding the complete system requires reading beyond this README. The available documentation is strongest on platform compatibility and known bugs, and much thinner on architecture, security boundaries, and operational controls.

## Installing mcpelauncher through documented distribution channels

The README does not contain a complete installation tutorial or a command for launching mcpelauncher. It directs users to the project wiki at `https://minecraft-linux.github.io` for information about compiling or installing the launcher. The old Read the Docs wiki is explicitly described as obsolete, so it should not be used as a current installation source.

For Flatpak users, the README provides a beta channel command. This installs the published Flathub beta package; it is not a locally compiled build.

```bash
flatpak install flathub-beta io.mrarm.mcpelauncher
```

The README notes a delay of approximately 1 to 24 hours for this Flatpak package relative to nightly builds. The expected result is installation of `io.mrarm.mcpelauncher` from `flathub-beta`. The README does not provide a separate command for starting the installed application, so no launch command can be confirmed from the available documentation.

The README also lists Debian, Ubuntu, and Fedora packages in the `minecraft-linux/pkg` repository, with a similar stated delay. Those package links provide a path for users who prefer distribution packages, but the README excerpt does not give package names or installation commands for them.

Nightly artifacts are listed under a `nightly` release tag. That page includes AppImage and DMG files, but the AppImage entry is marked deprecated. Accordingly, the documented Flatpak route is clearer for installation intent, while the wiki remains the authoritative destination for current compilation and broader installation guidance. A first real use would begin with logging in, downloading a supported Minecraft version, and launching it through the interface. The README confirms those interface capabilities but does not document the exact first-launch sequence.

## OpenGL ES requirements narrow hardware and release support

mcpelauncher supports several Linux and macOS architecture combinations, but the available Minecraft version depends on more than the operating system name. The Linux tables distinguish glibc systems running x86, x86_64, arm32, and arm64 CPUs. They also distinguish systems with OpenGL ES 2.0 from those with OpenGL ES 3.0 or newer.

For x86 systems, versions 1.13.0 through 1.20.20 are listed with OpenGL ES 2.0 or newer. Coverage through 1.21.73 requires OpenGL ES 3.0 or newer. The x86_64 rows add SSSE3, SSE4.1, SSE4.2, and POPCNT requirements. arm32 is limited to armv7 systems with PulseAudio and OpenGL ES 2.0 or newer, with versions through 1.18.10. The arm64 rows list armv7 or arm8 CPUs, PulseAudio, and different OpenGL ES thresholds and version ceilings.

The macOS support boundaries are equally specific. Older Intel systems are listed for macOS 10.10 through 10.14 and versions through 1.16.1X. Intel macOS 11 and later are listed through 1.21.73, but the warning says Rosetta 2 worked in macOS 11 and 12 and no longer in macOS 13. Apple M-series support begins at macOS 11.0, covers versions 1.19.70 through 1.21.73, and is marked experimental with modding limitations.

The README also warns that versions 1.20.30 and later require OpenGL ES 3.0 for hardware rendering on older hardware. This is a concrete release boundary. A system that can run an older Bedrock version may still fail to start a newer one after the relevant visual update.

## Software rendering offers a workaround with an explicit scope

mcpelauncher documents a way to continue running versions that no longer start with classic Fancy graphics on an OpenGL ES 3.0 system. The README points to issue 933 for details and describes two routes involving software rendering.

For Mesa 3D, the documented approach is to define `LIBGL_ALWAYS_SOFTWARE` as `1` for the launcher process. This does not change the project's compatibility matrix. It selects a software rendering path in the Mesa environment, so its performance cannot be inferred from the listed hardware requirements.

The second option is to replace the system `libEGl` drivers with those from Google ANGLE and configure ANGLE to use its SwiftShader backend. The README supplies a link to the ANGLE repository but does not provide installation or configuration commands. That makes this a more involved route whose exact setup is outside the excerpt.

Neither option should be read as a guarantee for every newer release. The documentation says the workaround may allow versions to run despite missing hardware rendering requirements, then refers readers to issue 933 for specifics. The relevant operational question is therefore not merely whether the CPU appears in the table. It is whether the graphics stack exposes the required OpenGL ES level, or whether the user is prepared to alter the rendering environment using one of these documented methods.

## Known Bedrock bugs constrain what users can expect

The README contains a version-specific bug table that materially affects adoption. Xbox login is listed as broken for Minecraft 1.13.0 through 1.16.1X, while it works in earlier launcher versions. For 1.16.20 and later, the macOS x86 launcher may have no sound unless it is compiled with PulseAudio. Versions 1.16.210 through 1.17.4X have reported crafting problems and texture offsets on x86 and x86_64 devices. The texture issue can be mitigated with the texture patch in profile settings, although that is only a mitigation rather than a general fix.

The same version range includes reported world corruption near water. From 1.18.30 onward, the armv7 port may not work correctly. From 1.19.50 onward, diagonal sprinting may fail on Intel CPUs, with the README linking the corresponding Mojang bug.

Two limitations apply across all listed versions. Xbox Live game invites cannot be received, and worlds hosted by this launcher may not be joinable by Xbox Live friends. Those are not minor launcher polish issues. They affect multiplayer coordination and remove expectations commonly associated with an official Bedrock client.

 That differs in approach because it follows Mojang's supported distribution path rather than running Android-edition builds through an unofficial compatibility layer. For users committed to Linux or macOS, however, mcpelauncher offers broader desktop launch and version-management options, with the documented bug table serving as the boundary for that choice.

## mcpelauncher maintenance, licensing, and upgrade work

The repository is not archived, and its last push was on 2026-10-16. Recent releases include `v1.8.4-qt6` and `v1.8.4` on 2026-09-17, followed by `v1.8.3-qt6` on 2026-09-16. These facts indicate recent repository activity, but they do not remove the README's explicit description of the launcher as unstable.

The project uses the GPL-3.0 license. That matters to engineers examining the source and to distributors considering how they package modified versions. The repository includes a `LICENSE` file and a CMake-oriented source tree, so source availability is part of the project's distribution model. This is not legal advice, and the README does not provide instructions for relicensing, third-party asset clearance, or compliance with particular distribution channels.

Upgrade cost is not limited to replacing one executable. Compatibility depends on the operating system, CPU instruction sets, OpenGL ES version, audio stack, architecture, and selected Bedrock release. Moving to a new Minecraft version can also cross a new graphics requirement, including the OpenGL ES 3.0 boundary documented for versions 1.20.30 and later. The separate UI repository means evaluators may need to inspect both repositories when determining whether a reported behavior belongs to the interface or launcher core.

Nightly packages are described as lagging by approximately 1 to 24 hours, and the AppImage option is deprecated. This makes release-channel choice part of maintenance planning. Flatpak beta users, distribution package users, and source builders may receive changes on different schedules.

## Conclusion

mcpelauncher is appropriate for Linux and macOS users who need to install and manage Bedrock Edition versions outside the official platforms and whose hardware falls within the documented matrix. It is a poor fit for unsupported architectures, systems without the required graphics APIs, or users who need reliable Xbox Live invitations and joining. Before adoption, verify the selected Minecraft version against the launcher version, confirm the required OpenGL ES level, and review the project wiki for installation or compilation instructions relevant to the target system.

## FAQ

### How do I install mcpelauncher on Linux with Flatpak?

The README documents the Flatpak beta installation command for `io.mrarm.mcpelauncher`. It notes an approximate 1 to 24 hour package delay and does not provide a separate application launch command.

### What hardware does mcpelauncher require for newer Minecraft versions?

For many supported systems, Minecraft versions through 1.21.73 require OpenGL ES 3.0 or newer. CPU instruction requirements vary by architecture, and Linux arm systems also require PulseAudio.

### Does mcpelauncher support Xbox Live invites and joining worlds?

No. The README lists inability to receive Xbox Live game invites as a limitation for all versions and warns that worlds hosted by this launcher may not be joinable by Xbox Live friends.

## Sources

- [License: GPL-3.0](https://github.com/minecraft-linux/mcpelauncher-manifest/blob/ng/LICENSE)
- [minecraft-linux/mcpelauncher-manifest on GitHub](https://github.com/minecraft-linux/mcpelauncher-manifest)
- [Project website](https://minecraft-linux.github.io)
- [README](https://github.com/minecraft-linux/mcpelauncher-manifest/blob/ng/README.md)
- [Releases](https://github.com/minecraft-linux/mcpelauncher-manifest/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/minecraft-linux-mcpelauncher-manifest