> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nebulaclient.net/llms.txt
> Use this file to discover all available pages before exploring further.
# Installation
> Launching Nebula for the first time.
## Requirements
| Requirement | Version |
| ---------------- | -------------- |
| Minecraft | 26.1.2 |
| Mod loader | Fabric 0.19.3+ |
| Java | 25+ |
| macOS (Mac only) | Tahoe or newer |
## Before You Start
Make sure you have bought Premium from the [official website](https://nebulaclient.net/pricing). The free **Basic** plan was discontinued and is no longer offered.
**[nebulaclient.net](https://nebulaclient.net/) is the only official website.** Nebula is not distributed anywhere else.
Any site, video, or Discord server offering a "free", "cracked", or "leaked" build of Nebula is distributing malware. These builds are RATs — they steal your Minecraft account, Discord token,
browser passwords, and crypto wallets. There is no working free version to find.
If you are unsure whether a download is legitimate, ask in the [official Discord](https://nebulaclient.net/discord) before running it.
## Installing Nebula
Go to your [User Profile](https://nebulaclient.net/profile) and click **Download** next to your username. Read the popup and press **Confirm Download**.
We recommend using [Prism Launcher](https://prismlauncher.org), which makes it easier to install and manage multiple game instances, versions, and mods.
If it's your first time using the launcher:
* Press **Add Instance** in the top left corner.
* Select Minecraft version **26.1.2**.
* Select the **Fabric** mod loader below and pick the version with a star next to it (usually the latest).
* Press **OK**.
Otherwise, you can edit your existing instance with those settings. **Make sure you have Fabric selected!**
Select your instance and press the **Edit** button on the right. A new menu pops up, where you go to the **Mods** tab on the right side.
Drag and drop the **NebulaLoader.jar** file you downloaded earlier.
On first launch after pressing **Launch**, your game will automatically close with a Nebula Client popup telling you to restart your game. This is normal, and it means you have done everything correctly so far.
It will automatically install the **Fabric API**, **Fabric Language Kotlin**, and **HM API** mods for you.
Launch your game again and you should see Nebula's custom main menu. Connect to the server and run the `/n`, `/nebula`, or `/nebulaclient` command to reveal the in-game GUI.
## Updating
Your Nebula loader automatically updates itself on every game startup. If there is a mandatory update that requires redownloading the mod, we always announce it in our Discord server.
## Troubleshooting
If your game is crashing, or you don't see Nebula Client in-game, make sure you have the versions listed in the **Requirements** section.
If you're still stuck, open a ticket in the `#🚑⎮support` channel of our [official Discord server](https://nebulaclient.net/discord).
Common errors and crashes:
Almost always your connection to our servers rather than anything you did wrong. Some ISPs, school and university networks, parental control filters, and some regions throttle or block the download.
Install [Cloudflare WARP](https://one.one.one.one/), turn it on and launch again. Any other VPN works too.
If an earlier attempt died halfway, the broken file has to be replaced before anything works, so keep launching until it finishes.
Use [Prism Launcher](https://prismlauncher.org). MultiMC works too. The Modrinth App, CurseForge and Lunar Client won't load Nebula at all.
Make a Fabric instance in Prism and drop your Nebula loader jar into that instance's mods folder.
Four things to check, in this order:
* Fabric has to actually be installed. Open **Edit -> Version** and look for it. An instance without Fabric launches perfectly fine and just ignores the loader.
* The first launch closes the game on purpose while it downloads Fabric API, Fabric Language Kotlin and HM API. Start it again.
* Some browsers save the loader as `.zip` or `.jar.txt`. It has to end in `.jar`.
* The mods folder that counts belongs to the instance you actually launch, not `%appdata%\.minecraft`.
Pull every other mod out and launch with only the Nebula loader. If that fixes it, put them back a handful at a time until it breaks again. **OneConfig** and **Taunahi** are both known to be incompatible.
Also check you haven't got two Nebula jars in there, or an old one sitting next to the current one.
Still crashing with nothing else installed? Check your Java version.
The popup tells you which version it expected and which one it found. Edit the instance to match. Nebula tracks one Minecraft version at a time, so a newer release won't work until we update for it.
If you typed the version by hand when creating the instance, double-check it.
Nebula isn't signed, so Windows Defender, Smart App Control, third party antivirus and macOS Gatekeeper all quarantine it from time to time, sometimes without telling you.
Add your instance folder to the exclusions, then download the loader again. A file that already got quarantined stays broken, so the exclusion on its own won't bring it back.
On a Mac, update to macOS Tahoe. Sonoma and Sequoia give you black screens and rendering crashes, and this fixes nearly every Mac report we get.
On Windows, update your GPU drivers. If the crash names LWJGL or GLFW, try a different LWJGL version in **Edit -> Settings -> Miscellaneous**.
Nebula couldn't read the Minecraft account the game started with. Check that the instance is running in online mode and that you picked the right account in Prism before hitting **Launch**.
The account has to own Minecraft, so demo and cracked accounts won't work.
Too many failed launches in a row will rate limit you. Wait about 15 minutes before trying again.
Your license is tied to one machine and something about that machine changed. A new PC, new hardware, a Windows reinstall, or booting into the other half of a dual boot will all do it.
Reset your HWID in your [profile settings](https://nebulaclient.net/profile/settings/account). It's free and self-serve, and can be done **once every 3 days**.
Some customizations change how your machine is identified, and then this keeps coming back on the same PC. Custom PowerShell prompt themes are the usual culprit. If a reset doesn't hold, say so in your ticket.
Your licence follows the hardware, not a Minecraft account, so there is nothing to link, and several Minecraft accounts on the same machine are fine.
Your loader jar carries a session with it, and that session eventually runs out. It usually turns up after you have not played for a while.
Download a fresh jar from your [profile page](https://nebulaclient.net/profile) and swap it for the old one in your mods folder.
If the download keeps giving you the same expired file, your browser is serving it from cache. Download it again in a private window.
Check how much RAM is allocated to the instance in **Edit -> Settings -> Memory**. Allocations under 2 GB cause progressive FPS loss and eventual crashes. 4-6 GB is a common amount. Don't give it more than you actually have free.