# Two of BedrockOnLinux's three newest release assets are not its own

> A Python launcher that fetches the Windows build of Minecraft Bedrock from the Microsoft Store under your own account and runs it under Wine. Its releases page doubles as a distribution channel for Xodus and a WineGDK prefix, and its licence is stated two ways.

**Wyze3306/BedrockOnLinux** — Run Minecraft Bedrock for Windows seamlessly on Linux.

- Repository: https://github.com/Wyze3306/BedrockOnLinux
- Website: https://wyze3306.github.io/BedrockOnLinux/
- Stars: 998 · Forks: 52
- Language: Python
- License: NOASSERTION
- Published: 2026-09-19 · Updated: 2026-09-19 · Language: en
- Canonical page: https://hysenlabs.com/projects/wyze3306-bedrockonlinux

## The releases page publishes two third-party builds

The three most recent release assets are not three versions of the launcher. The newest is tagged nightly and titled with the launcher version, a date and a short commit hash, reading BedrockOnLinux nightly 2.2.7 with a hash, published on 2026-10-02. The other two are not BedrockOnLinux at all. One is tagged with a component name, a commit hash and a build counter, and titled as a build of the xodus CLI from source. The third is titled as a WineGDK prefix and carries the same shape of tag, a commit hash and a build counter. Both landed on 2026-09-29, and the prefix was published about twenty minutes after the CLI build rather than before it, so the ordering is by when the pipeline finished rather than by component. The effect on a user is that the releases page is a combined distribution channel for the launcher, its downloader and its compatibility layer, and the tag names are not a version series you can pin in order. The page's own link text acknowledges this by offering both a latest-release link and a link to all releases.

## The licence is NOASSERTION in metadata and MIT on the page

The repository's licence field carries the value NOASSERTION, which is what a metadata reader reports when it cannot determine a licence rather than when one was declared. The page states the opposite: BedrockOnLinux is MIT licensed, pointing at a LICENSE file that is in the repository root. It adds a second clause that matters more for anyone auditing it, that the components it bundles keep their own licences, and the tree backs that up with a third_party/ directory next to src/, tests/, tools/, scripts/, flatpak/, a data/ directory and a bol/ directory. So the honest description is a two-part situation. The launcher's own licensing is asserted in prose and backed by a file, while the machine-readable field says nothing, and a tree with a third_party/ directory means some of what runs was not written by the author. Nothing in the repository says which of those statements a downstream packager should rely on, so the file itself is the thing to read.

## You are asked to sign in twice, and the page says why

The play instructions are three steps, and the first one is longer than the other two because the account question is not a bug. Open BedrockOnLinux and sign in with the Microsoft account that owns Minecraft. It is asked for twice: once to download the game from the Microsoft Store and once to play online, because the Store needs a session of its own. The instruction is to use the same account both times, and the launcher offers the second sign-in right after the first, and again if a download needs it. That is a specific and reasonable design decision, and it is the kind of detail that usually gets left out of READMEs. Two related facts follow from the same place. The first launch downloads the game and everything it needs, so it takes a while, after which it starts straight away, and an older version can be installed too, which the page calls handy when a server has not updated yet. And the sign-in happens from inside Minecraft, exactly as on Windows, so nothing goes through a third party.

## The OptiScaler path places a DLL and is labelled experimental

One feature is flagged as experimental on the page, and it is the one with the largest surface. The launcher can install a tested OptiScaler v10 setup for Minecraft RTX under Wine and vkd3d-proton, and the page specifies what that includes: the physical nvngx.dll workaround needed to expose Bedrock's native DLSS input on the tested non-NVIDIA setup. Two commands drive it:

```bash
bedrock-on-linux optiscaler install
bedrock-on-linux optiscaler status
```

Three things are worth separating here. The OptiScaler binary is downloaded from upstream and is not bundled with the project, so a network fetch supplies a component that ends up executing inside the game. The mechanism is a physical file placed into the Wine prefix, which is a file write into a directory that also holds the game itself. And the qualification is narrow: it was tested on a non-NVIDIA setup, which is the case where the DLSS interface has to be substituted. Frame generation stays opt-in in the OptiScaler overlay rather than being enabled by the install. The exact setup, management commands, tested pipeline and compatibility notes are pointed at a separate document rather than repeated here.

## Five formats, three artefact prefixes, one architecture

The install table gives one line per format, and the file names do not follow a single convention. AppImage is `./BedrockOnLinux-*-x86_64.AppImage` with a capitalised name and a dash separator. The Debian package is `bedrock-on-linux_*_amd64.deb`, all lower case with a hyphen and a low line. The RPM is `bedrock-on-linux-*.x86_64.rpm`, lower case with two hyphens. The Flatpak is `./BedrockOnLinux-*-x86_64.flatpak`, back to the capitalised form. And Nix has no artefact name at all, because it is a flake reference:

```bash
nix run github:Wyze3306/BedrockOnLinux
```

The architecture is the same in every case and it is x86_64. There is no arm64 artefact in the table, the Nix example hardcodes the same system, and the requirements ask for a 64-bit Linux desktop with a Vulkan-capable card and driver. Nix is the only row with a committed lock file behind it and the only one with a declarative example, which adds an input for the project itself and points its nixpkgs at the host's:

```nix
    bedrock-on-linux = {
      url = "github:Wyze3306/BedrockOnLinux";
      inputs.nixpkgs.follows = "nixpkgs";
    };
```

followed by installing the default package for the host's architecture into the system package list.

## The legal section is a launcher that ships nothing

The Legal section is short and does the most work on the page. BedrockOnLinux ships no Minecraft game files. The game is downloaded from Microsoft's own servers, under your own account's licence, by Xodus, so you have to own Minecraft and the terms that come with it still apply. The project is MIT licensed with a LICENSE file, the bundled components keep their own licences, and it is an independent project not affiliated with or supported by Mojang or Microsoft. That last sentence is the one to hold on to, because the compatibility work in the previous section, the WineGDK prefix and the vkd3d-proton path, is exactly the kind of thing that sits close to a support boundary. The other half of the story is the offline mode, which is unusually clearly stated: you can play without an account, single-player worlds and LAN games work offline, only the online features are out of reach, and achievements show up in the game but do not unlock yet. So the gap is stated rather than hidden, which is more than most launchers manage.

## doctor, repair, and a support request with a never-send rule

Two commands cover the failure cases, and the page is precise about what each one touches. If something goes wrong, the built-in check looks at your system and tells you what is wrong:

```bash
bedrock-on-linux doctor
```

And if the game itself misbehaves after an update or a crash, `bedrock-on-linux repair` rebuilds the Windows environment without touching your worlds, which is the guarantee that matters when the thing being rebuilt is the prefix that also holds your save data. Logs are one click away in Settings, and the same commands are available from the AppImage or Flatpak through their own entry point, so the CLI is not tied to a system install. The support instructions carry a rule worth quoting rather than paraphrasing: open an issue with the launcher version, the distribution, the GPU and the log, but never your account details. The controller story fits the same pattern, with the d-pad or left stick moving the highlight, A selecting, B going back, the shoulder buttons changing tab and Start playing, plus a menu item that creates a direct launch shortcut in the app menu or in Steam, which is the one to use on a Steam Deck.

## Conclusion

BedrockOnLinux is a reasonable choice for a Linux desktop that has a Vulkan driver and a Microsoft account that already owns the game, and the licensing position is the cleanest part of the design: it ships no game files, downloads from Microsoft's own servers under your own licence, and says plainly that it is not affiliated with Mojang or Microsoft. It is not a fit for an arm64 machine, since every artefact is x86_64, and the Offline story has a visible hole because achievements render but do not unlock. Three things to check before you install. Read the releases page carefully, because two of the three most recent assets are a build of the upstream Xodus CLI and a WineGDK prefix rather than a launcher build, so the newest download is not automatically the launcher you want. Treat the OptiScaler path as what the page calls it, experimental, since it fetches a binary from upstream and places a DLL into the prefix, and it was tested on a non-NVIDIA setup. And settle the licence question yourself, because the metadata records nothing and only the page asserts MIT.

## FAQ

### How do I install Minecraft Bedrock on Linux?

BedrockOnLinux ships as an AppImage, a .deb, an .rpm, a Flatpak and a Nix flake, and the first step is to download the file for your platform from the latest release. The page also lists a one-line start command for each format.

### How can I play Minecraft Bedrock on Linux?

BedrockOnLinux downloads the Windows version of the game from the Microsoft Store under your own account, then you sign in to Microsoft from inside Minecraft exactly as on Windows, so Friends, public servers, Realms and the Marketplace work and nothing goes through a third party.

### Does BedrockOnLinux work without a Microsoft account?

Partly. Single-player worlds and LAN games work offline with no account, and only the online features are out of reach. Achievements show up in the game but do not unlock yet.

### What does bedrock-on-linux doctor do?

It is a built-in check that looks at your system and tells you what is wrong. A separate repair command rebuilds the Windows environment without touching your worlds, and both are also available from the AppImage and Flatpak entry points.

### Which CPU architectures does BedrockOnLinux ship for?

x86_64. Every artefact name in the install table carries x86_64, the Nix flake example sets the system to x86_64-linux, and the requirements ask for a 64-bit Linux desktop with a Vulkan-capable graphics card and driver.

## Sources

- [Issues](https://github.com/Wyze3306/BedrockOnLinux/issues)
- [Project website](https://wyze3306.github.io/BedrockOnLinux/)
- [README](https://github.com/Wyze3306/BedrockOnLinux/blob/main/README.md)
- [Releases](https://github.com/Wyze3306/BedrockOnLinux/releases)
- [Wyze3306/BedrockOnLinux on GitHub](https://github.com/Wyze3306/BedrockOnLinux)

---

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