Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Nebula-Modmakers/Nebula-Launcher/llms.txt

Use this file to discover all available pages before exploring further.

This page covers the issues Nebula Launcher users run into most often. Find the symptom that matches your situation, expand it, and follow the steps. If none of these resolve your problem, see Reporting Issues for how to open a GitHub issue with the right information.
If this is your very first modded launch, long wait times are completely normal. The IL2CPP generation step alone can take up to 8 minutes. As long as the loading spinner is still moving, the app is working — do not close it.
When Among Us launches but none of your mods appear to be active, work through these checks in order:
  1. Confirm you launched from Nebula. If you tapped the standard Among Us icon on your home screen or app drawer, the game starts without any mod injection. Always press Launch inside Nebula Launcher.
  2. Check the active profile. Open the Profiles page and confirm the profile you want is selected. The selected profile is staged into the shared BepInEx plugin directory at launch time, so choosing the wrong profile means none of those mods are loaded.
  3. Verify the DLL files are present. Use Nebula’s built-in file browser to navigate to the plugin folder and confirm the expected .dll files are listed. If they are missing, reinstall or re-import the mod.
  4. Review the BepInEx log. Open FusionCore/com.innersloth.spacemafia/BepInEx/LogOutput.log in the file browser or a third-party file manager and look for plugin-loading errors or warnings near the top of the log.
  5. Confirm Android IL2CPP compatibility. A mod compiled for Windows or for the Mono backend will not run on Android. Make sure your mod explicitly supports Android, ARM64, and IL2CPP.
  6. Confirm the Among Us version. Nebula requires exactly Among Us 2026.6.5, version code 7045 (shown as 17.4a in-game). Mods must also be built for this exact game version.
Nebula checks the installed Among Us version before every launch. It requires exactly:
FieldValue
Package version name2026.6.5
Version code7045
In-game display17.4a
If the version name matches but the version code does not — or vice versa — the check still fails. You must install the specific build that satisfies both values at the same time. Nebula will tell you whether your current build is too old (upgrade) or too new (downgrade). Install the supported build from a source you are authorized to use, then return to Nebula.
IL2CPP generation is memory-intensive. On some devices, Android may terminate the game process before generation completes, which can look like a crash. This is normal during a first run. To recover:
  1. Reopen Nebula Launcher.
  2. Press Launch again.
  3. If Nebula reports that IL2CPP generation was interrupted, let the next attempt run completely without closing the app or the game.
  4. Leave the device alone during this stage — do not switch apps or lock the screen unnecessarily.
The second attempt commonly succeeds because some preparation work completed during the first attempt. Also ensure the device has sufficient free storage for the generated interop assemblies and sufficient free RAM before retrying.
Nebula should automatically return you to the login screen when it encounters an authentication error. If the spinner keeps running:
  • Check your internet connection. Nebula needs to reach the account server to authenticate.
  • Check email verification. If you registered recently, verify your email address before trying to sign in.
  • Check account activation. Deactivated accounts cannot authenticate regardless of credentials.
  • Check your password. Confirm you are entering the correct credentials.
  • Re-sign in. If the server has rejected your saved session (for example, because the device session expired or was revoked), the spinner may stall. Return to the login screen, clear any cached session if offered, and sign in again from scratch.
The correct response depends on which launch this is:On the very first launch — a long spinner is expected. Nebula and FusionCore must copy Unity data, detect the runtime version, potentially download an unstripped Unity library, extract the BepInEx runtime, and generate IL2CPP interop assemblies. This process can take up to 8 minutes. Do not close the app while the spinner is moving.On subsequent launches — if the spinner has been running for more than a few minutes and does not appear to be progressing, exit Nebula completely (remove it from the recent-apps list), reopen it, and press Launch again.The key rule: if the spinner is still moving, the app is not frozen — wait it out.
Nebula needs all-files access to manage the shared FusionCore runtime, profile, and mod folders. The prompt will keep appearing every time you open the app until Android reports that the permission has been fully granted. To stop it:
  1. When the prompt appears in Nebula, tap Grant Access.
  2. If that does not open the correct settings screen, go to Android Settings → Apps → Nebula Launcher → Permissions.
  3. Find Files and media (or All files access, depending on your Android version) and enable it for Nebula Launcher.
  4. Return to Nebula. The prompt should no longer appear.
If the prompt reappears after granting access, check that no battery-optimization or security app is revoking permissions in the background.
If Among Us closes immediately after the BepInEx splash or during early game initialization, a mod is likely causing the crash. To diagnose:
  1. Open the Profiles page and disable or remove the most recently added mod from the active profile.
  2. Press Launch and test whether the crash is gone.
  3. Repeat until you identify the offending mod.
Once you have identified it, confirm that the mod explicitly supports all of the following:
  • Platform: Android
  • Architecture: arm64-v8a
  • Backend: IL2CPP
  • Runtime: FusionCore
  • Game version: Among Us 2026.6.5, version code 7045
A mod that appears in the BepInEx log does not guarantee every feature works on Android — networking, native calls, asset loading, and platform-specific APIs may still fail silently or crash.
Online functionality depends on both the correct game version and a valid account link. Check each of the following:
  • Verify the Among Us version. Online features may behave differently or fail entirely if the installed build is not 2026.6.5 / version code 7045.
  • Re-link your Among Us account. Open Settings in Nebula and follow the account-linking flow again. Account links and tokens expire or become invalid over time.
  • Check token expiry. If your account link or bearer token has expired, online sessions will be rejected. Re-linking generates a fresh token.
  • Test without new mods. Disable any recently added gameplay or networking mods and test vanilla online play to determine whether the problem is game-side or mod-side.
  • Capture logs before reporting. Save the BepInEx log (FusionCore/com.innersloth.spacemafia/BepInEx/LogOutput.log) and any relevant Logcat output before opening an issue — online problems are very difficult to diagnose without them.
If none of the above resolved your problem, the next step is to open a GitHub issue with the right diagnostic information. See Reporting Issues for a full checklist of what to include.

Build docs developers (and LLMs) love

Get started for freeTalk to us