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 a mod is not listed in the Nebula Mod Store, you can import it directly from a file on your device. Nebula accepts raw DLL files and ZIP-based NPKG packages, validates what it can, and copies the contents into the active profile’s plugins folder. Because manual imports skip the store’s curation process, you are responsible for confirming that any file you import is genuinely compatible with Android before using it.

​
Supported formats

Nebula supports two file types for manual import:
  • DLL files (.dll) — copied directly into the root of the active profile’s plugins/ folder. No additional validation beyond what the file system allows is performed. The DLL must be a valid ARM64 IL2CPP assembly or it will fail to load at runtime.
  • NPKG files (.npkg or .zip) — ZIP archives that contain a manifest.json alongside a payload/ directory. Nebula reads and validates the manifest before extracting files. NPKG packages must declare their platform targets, file list, and SPDX licenses. All individual files are SHA-256 verified during extraction. File destinations must stay inside the plugins/ directory.

​
How to import

1

Tap Import on the main screen

On the main screen, tap the Import button (or the upload icon). This opens Nebula’s file picker.
2

Select a file

Navigate to the .dll, .npkg, or .zip file you want to install and tap it to select it.
3

Nebula validates and copies the file

For DLL files, Nebula copies the file directly into the active profile’s plugin folder. For NPKG/ZIP packages, Nebula reads the manifest, checks file hashes, and extracts the payload into the active profile. If validation fails, no files are written.
4

Confirm the import succeeded

Return to the main screen and check the Installed Mods list. The imported file or package should appear in the plugin entries list. If it does not appear, check that the file is a valid format and try again.

​
Compatibility requirements

A Windows mod DLL is not compatible with Android even if it appears to load without error. A mod can initialize successfully while still having entirely broken menus, networking, native calls (P/Invoke), asset loading, voice chat integrations, or gameplay logic. Only import mods that are explicitly marked as Android / ARM64 / IL2CPP / FusionCore compatible. If the mod’s documentation does not mention Android, do not assume it works.
For a mod to work correctly in Nebula, it must be built to support all of the following targets simultaneously:
RequirementRequired value
Operating systemAndroid
ArchitectureARM64 (arm64-v8a)
RuntimeIL2CPP
Mod loaderFusionCore (BepInEx Fusion)
Among Us version2026.6.5 (version code 7045, in-game 17.4a)
A mod that satisfies only some of these — for example, one that targets IL2CPP on Windows — is not compatible. Desktop Among Us uses x86/x64 architecture and a different binary format. The DLL will not execute correctly on an ARM64 device. See the Compatibility page for a detailed explanation of why Windows mods fail on Android and what kinds of runtime errors to expect.

​
Shared FusionCore storage

After Nebula stages your active profile at launch, the plugin files are placed into the shared FusionCore storage area: 
FusionCore/com.innersloth.spacemafia/
This directory contains the shared BepInEx runtime, configuration, the staged active plugins, generated IL2CPP interop assemblies, and logs. You can browse these files using Nebula’s built-in file browser. Manually editing or deleting files in this area outside of Nebula is not recommended.

Build docs developers (and LLMs) love

Get started for freeTalk to us