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.

If you have worked through the Common Issues page and your problem is still unresolved, open a GitHub issue on the Nebula Launcher repository. A well-prepared report gets your problem diagnosed and fixed much faster — the sections below explain exactly what to include and what to leave out.

​
Required information

Every report should provide all of the following. Omitting any one item often makes the issue impossible to reproduce or diagnose.
1

Phone model

Include the manufacturer and full model name, for example: Samsung Galaxy S23 or Google Pixel 8a. Nebula targets arm64-v8a Android devices, and some crashes are device- or chipset-specific.
2

Android version

Open Android Settings → About phone → Android version and include the full version string, for example: Android 14 or Android 13 (QPR2).
3

Nebula version

The Nebula version number is displayed inside the launcher. Include the full version string exactly as shown — do not estimate.
4

Among Us version name and version code

Include both the package version name and the version code. Nebula requires version name 2026.6.5, version code 7045 (displayed as 17.4a in-game). You can find the version code in Android Settings → Apps → Among Us → App info, or in the BepInEx log header.
5

Active profile and installed mod versions

State the name of the profile that was active when the problem occurred and list every mod installed in that profile along with each mod’s exact version number.
6

Stage at which the failure occurred

Describe whether the failure happened before the Among Us main menu appeared (during launch preparation, IL2CPP generation, or BepInEx initialization) or after it appeared (during gameplay, in a lobby, etc.). This narrows the search area significantly.
7

BepInEx log

Attach the full contents of LogOutput.log. See Where to find logs below for the exact path. Do not paste a partial snippet if you can avoid it — the full log captures initialization order and errors that a snippet hides.
8

Reproduction steps

Write out the exact sequence of actions that triggers the problem, starting from opening Nebula. For example: “1. Open Nebula → 2. Select the ‘TownOfUs’ profile → 3. Tap Launch → 4. Game closes after the BepInEx splash screen.” The clearer the steps, the faster the issue can be confirmed.

​
Where to find logs

The primary log file Nebula and BepInEx write to is: 
FusionCore/com.innersloth.spacemafia/BepInEx/LogOutput.log
You can open this file in two ways:
  • Nebula file browser — tap Browse Files on the main screen and navigate to FusionCore/com.innersloth.spacemafia/BepInEx/. Tap LogOutput.log to view it. Note that the built-in browser will refuse files that are too large for the editor; if that happens, use a third-party file manager instead.
  • Third-party file manager — any file manager that can read shared storage (for example, Files by Google or Solid Explorer) can navigate to the same path and open or share the file.
If the problem involves a crash during game launch, Logcat output captured via Android’s developer tools can also be valuable, especially for native-level crashes that BepInEx does not log itself.
Before attaching any log or screenshot to a GitHub issue, carefully remove all private information. This includes — but is not limited to — email addresses, account links, bearer tokens, session tokens, device tokens, and any other credentials or secrets. Treat these values exactly as you would treat a password: once posted publicly, they should be considered compromised. Review your log in a text editor and redact any sensitive values before uploading.

​
What NOT to include

The following must never appear in a public GitHub issue, screenshot, or comment:
  • Email addresses
  • Among Us account link tokens
  • Bearer tokens
  • Session tokens
  • Device tokens
  • Screenshots that display any of the above
If you realize you have accidentally posted any of these, edit or delete the comment immediately and rotate or revoke the affected credentials from your account settings.
The Nebula team cannot help diagnose crashes or mod-loading failures without a BepInEx log. Please always attach LogOutput.log when reporting these types of issues — a description of the symptom alone is rarely enough to identify the root cause.

Build docs developers (and LLMs) love

Get started for freeTalk to us