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.

Android compatibility is a hard technical constraint, not a preference setting or a toggle you can override. A mod built for Windows Among Us runs on a different processor architecture, links against different system libraries, and uses a fundamentally different .NET runtime from the one Nebula provides. Bringing the wrong mod into Nebula does not produce a clear error — it often produces a silent partial failure that is much harder to diagnose. Checking compatibility before you install is always faster than debugging a broken session after the fact.

​
Required mod targets

Every mod that runs in Nebula must meet all of the following requirements at the same time. A mod that satisfies only some of them is not compatible.

Operating System

AndroidThe mod must target Android, not Windows, macOS, or Linux. Most Among Us mods distributed for PC are Windows-only.

Architecture

arm64-v8aYour device runs a 64-bit ARM processor. x86 and x64 binaries from desktop mods cannot execute on ARM hardware.

Runtime

IL2CPPAmong Us on Android uses the IL2CPP scripting backend. Mods compiled for Mono or CoreCLR will not load correctly.

Mod Loader

FusionCore / BepInEx FusionNebula loads plugins through FusionCore and BepInEx Fusion. Mods packaged for other loaders or for vanilla BepInEx without Fusion support are not compatible.

Game Package

com.innersloth.spacemafiaThis is the Android package identifier for Among Us. Nebula and the NPKG format both check this value explicitly.

Game Version

2026.6.5 — version code 7045In-game this appears as 17.4a. Mods are compiled against specific Among Us interop assemblies; a version mismatch causes missing types and broken calls.

​
Why Windows mods don’t work on Android

Desktop Among Us mods are compiled for x86 or x64 processors and link against Windows system APIs (Win32, .NET on Windows). Android devices use ARM64 processors with a Linux-based kernel and a completely different set of system libraries. The processor cannot execute x86/x64 machine code natively, and the operating system does not provide the Windows APIs the mod expects. Beyond the hardware difference, desktop Among Us uses the Mono scripting backend, while Android Among Us uses IL2CPP. IL2CPP compiles C# code ahead of time into native ARM64 machine code and replaces the managed runtime with a C++ layer. A mod DLL compiled against Mono/CoreCLR types cannot bind to an IL2CPP process — the type system, memory layout, and method invocation model are all different. The result is that a Windows mod DLL physically cannot run on an Android device. If it appears to load without crashing immediately, it is not functioning correctly.

​
What can go wrong even with compatible mods

A mod that meets all the requirements above can still misbehave at runtime. Loading a plugin successfully does not guarantee that every feature works. Common partial failures include:
  • Broken menus — UI components that bind to game types may fail if internal type layouts changed between versions.
  • Broken networking — custom RPCs or network handlers can fail silently if the game’s networking layer behaves differently on Android.
  • Native call failures — P/Invoke calls to native libraries (.so files) fail if the targeted library is not present on Android or expects a different binary interface.
  • Asset loading failures — mods that embed or reference asset bundles built for Windows may fail to load those assets on Android.
  • Voice chat and platform integration — mods that integrate with PC-specific voice or platform SDKs require additional devices and testing environments to verify fully.
If a mod starts without an immediate crash but something feels wrong in-game, the BepInEx log (accessible through Nebula’s file browser at FusionCore/com.innersloth.spacemafia/) is the first place to look for plugin-loading errors and exceptions.

​
The mod catalog guarantee

Every mod available in the Nebula Mod Store has been checked against all of the requirements above before it appears in the catalog. The NPKG package format encodes the platform targets inside manifest.json, and Nebula’s installer verifies that os, architecture, runtime, and gamePackage all match the expected values before writing a single file. Mods in the store are also verified against the currently supported Among Us version code. When you install a mod from the store, you can trust that it has passed these checks. When you import a mod manually, that responsibility is yours. The store is always the recommended path for mods that are available there.
Before importing a mod manually, open its GitHub repository and look for an explicit statement that the mod supports Android, ARM64, IL2CPP, and FusionCore. If the README does not mention Android or only discusses Windows installation, the mod is almost certainly not compatible.

​
Version lock

Nebula enforces a strict version check before every game launch. The required values, taken directly from the app:
FieldValue
Package version name2026.6.5
Package version code7045
In-game display version17.4a
Android packagecom.innersloth.spacemafia
Both the version name and the version code must match. A build that reports the correct version name but a different version code is rejected. If your installed version of Among Us does not match, Nebula will tell you whether you need to upgrade or downgrade before the launch can proceed. This lock exists because mods are compiled against IL2CPP interop assemblies generated from a specific game build. Running a mod against the wrong Among Us version produces unpredictable failures — missing methods, changed offsets, or crashes during startup — that are difficult to distinguish from mod bugs. Keeping everyone on the same build makes problems much easier to reproduce and report.

Build docs developers (and LLMs) love

Get started for freeTalk to us