Hyprism: an unofficial cross-platform launcher and mod manager for Hytale

What Hyprism is, and what it is not

Hyprism is described as an open-source, unofficial, cross-platform Hytale launcher with isolated instances, mod discovery and profile management, and the readme puts a sharper version of that in italics: a multiplatform Hytale launcher with mod manager and more.

A launcher is the outer shell around a game rather than the game itself, and the useful part of a good one is what it lets you do that the official launcher does not. The three features named here are the ones worth reading closely.

Isolated instances means multiple separate game installations that do not interfere with each other. If you keep one pristine install for a server you want untouched, another with a heavy mod list, and a third for experimenting, isolation is what makes that possible. Without it, mods leak between installs and a broken mod takes out everything.

Mod discovery is the part that saves time. Rather than adding each mod file by hand to each instance, the launcher finds what is available and lets you work with a list. Profile management is the layer above that, treating a set of mods and settings as a named thing you can switch between rather than rebuilding each time.

Then there is the disclaimer, which comes first in the readme and is emphatic. Hyprism has no connection to PrismLauncher, and it is developed independently of the PrismLauncher project or its team. That is a clarification of a naming coincidence, since the two names are similar enough to invite confusion, and putting it in a prominent callout is the kind of thing a project does when it has been mistaken for something else.

The project is C#, licensed GPL-3.0, with the documentation site at hyprism.org and the last push on 2026-10-17.

A note about the current state of the source

There is a warning in the readme that deserves to be quoted rather than paraphrased, because it changes what you should do on arrival.

The launcher is switched to Avalonia UI. The current source code in main may contain bugs or errors. If you need the code from a previous version of the launcher, use the latest 3.x.x release, which is v3.0.3.

So the project is midway through a UI rewrite, and the main branch is the work in progress rather than the recommended starting point. That is an unusual thing to say at the top of a readme, and it is useful information, because the alternative is for you to build from main, hit a crash, and conclude the project is broken rather than in transition.

The release history backs the story. v4.0.0 came out on 2026-10-11, v3.0.3 on 2026-04-28 and v3.0.2 on 2026-04-24. So the 4.0 release is the Avalonia version and it is very recent, six days before the last push. The gap between v3.0.3 and v4.0.0 is where the rewrite happened.

That implies two sensible approaches depending on what you want. If you want to use the launcher rather than work on it, take v3.0.3, which the readme points to explicitly. If you want to contribute to the new interface, build from main and expect to be one of the people finding the bugs.

The documentation is published in English and Russian on the documentation site, with the sources living in Docs/content in the repository, and there is a Docs directory at the top level alongside AGENTS.md, a Contributing.md and a CODE_OF_CONDUCT.md. The AGENTS.md file is the current convention for shipping instructions to coding assistants, and its presence in a repository of this size says the project expects automated tooling to be pointed at it.

Installing, in one line per platform

There are four install routes, and three of them are one-line commands that fetch and run a script.

For Windows it is a PowerShell one-liner:

irm https://raw.githubusercontent.com/hyprismteam/Hyprism/main/Scripts/install-win.ps1 | iex

For Linux:

curl -fsSL https://raw.githubusercontent.com/hyprismteam/Hyprism/main/Scripts/install-linux.sh | sh

And for macOS:

curl -fsSL https://raw.githubusercontent.com/hyprismteam/Hyprism/main/Scripts/install-macos.sh | sh

The fourth route is not a script at all but a Nix flake run:

nix run 'github:hyprismteam/Hyprism?dir=Packaging/linux/flake#hyprism'

That last one is the most interesting, because it points at a Packaging directory in the repository with a flake inside it. The dir parameter tells nix which subdirectory holds the flake, and the #hyprism attribute selects the package from within it. So the packaging is a first class part of the repository rather than something bolted on, and a Nix user gets the application from the source tree without an install step at all.

The one-line installers are a common pattern and a common source of discomfort. Piping a script straight into a shell means the code is fetched and executed without review, and the branch it points at is main, so the script can change under you. The mitigations are that the URLs are on the project's own repository under Scripts, and that the alternative is always available: you can manually download from the Releases page, which the readme mentions first.

If you are the kind of person who reads scripts before running them, download the release artefact. If you are not, the one-liner is a reasonable trade for a launcher.

Building from source

The build requirements are short: the .NET 10.0 SDK, plus Node.js 22 and npm when working on the documentation.

That split is worth noticing. The application itself is .NET and the documentation site is a separate Node project, so the second requirement is only for people touching the docs. That is a common arrangement for a project that publishes its documentation as a site with sources in the repository.

The build commands are:

# Clone the repository
git clone https://github.com/hyprismteam/Hyprism.git
cd Hyprism

# Build the application and tests
dotnet build Hyprism.slnx

# Run the launcher
dotnet run --project Sources/Hyprism.Desktop/Hyprism.Desktop.csproj

Two details here are worth reading carefully. The solution file is Hyprism.slnx, which is the newer XML based solution format rather than the classic .sln, and the run command targets a specific project rather than the solution, which means you can launch the desktop application without building everything in the solution first. That matters when you are iterating on the launcher itself, because building the full solution pulls in the tests and any other projects.

The readme also states the architecture: Hyprism uses a .NET 10 Core library and a native Avalonia 12 desktop application. So there is a shared core of logic with a desktop front end on top, and the specific Avalonia version matters because that is the UI toolkit the rewrite is built on.

The repository layout backs that up. There is a Sources/ directory for the code, a Tests/ directory for the tests, Packaging/ for the platform packaging including the Linux flake, Scripts/ for the install scripts, and Docs/ for the documentation sources. The top level also has Hyprism.slnx as the solution file.

The legal notice, and the licence hygiene around it

The legal section of the readme is longer than most, and given what the software is, that is appropriate rather than defensive.

Hyprism is an unofficial, open-source launcher for Hytale. The project is not affiliated with, endorsed by, sponsored by, or approved by Hypixel Studios, Riot Games, or any of their affiliates.

On intellectual property, the readme notes that Hytale, Hypixel Studios and strictly related logos and assets are trademarks or registered trademarks of Hypixel Studios Inc, with all rights reserved by their respective owners, and that usage of the software is subject to the terms of the Hytale End-User License Agreement.

Then there is the section on game files and distribution, which is the part that shows the project has thought about the sharpest question. Hyprism acts solely as a client-side tool to facilitate the downloading and launching process, and does not host, modify, or distribute original game files directly.

The two authentication paths are spelled out. By default, Hyprism implements the standard Hytale authentication protocol, and users with a valid license can download unmodified game images directly from official servers, identical to the official launcher process. And for custom third-party mirrors, the readme is explicit that Hyprism does not include, provide, or pre-configure any third-party download mirrors, and that the software merely provides the technical capability for users to manually add custom mirror URLs at their own discretion.

The developers state that they constitute no control over the content hosted on any user-added external mirrors, and that responsibility for choosing a download source and complying with the Hytale EULA and applicable copyright law rests entirely with the end user.

That is a careful and defensible position. The default path uses the official authentication and the official servers, so the ordinary user is in the same position as with the official launcher. The mirror capability exists for users who need it, it is not preconfigured, and the responsibility is placed where it belongs.

The licence hygiene is also handled properly. Hyprism is GPL-3.0, with the full text in LICENSE, the licence texts for project assets in a Licenses directory, and REUSE.toml for machine-readable licensing and CI compliance. The logo and banner assets are CC BY-SA 4.0 with their text in Licenses/CC-BY-SA-4.0.txt. REUSE is the newer standard for tracking licensing of every file in a repository, and having a REUSE.toml alongside the licence files means the attribution metadata is machine-checkable rather than maintained by hand.

Third-party components are covered by MIT, Apache-2.0, BSD-style licences and CC-BY-4.0. The project is funded by donations through DonationAlerts and BuyMeACoffee, and the readme says the launcher is supported solely with free time and community feedback, which is a candid description of who maintains it.

Editorial conclusion

Adopt Hyprism if you play Hytale on more than one platform, run several modded profiles side by side, or want to manage mods without a platform specific tool each time. Do not adopt it expecting a stable release, because the readme says the current source on main may contain bugs and points you at the 3.x release if you need the previous version. Before you commit, read the legal notice, because the launcher is unofficial and the terms of the game's own licence apply to what you do with it, and check whether the official authentication path covers what you need.

Frequently asked questions

Official sources

1. hyprismteam/Hyprism on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases