A compiled file is one small file a player puts in their game's mods folder instead of using the Nebula app: a .dll for Among Us (BepInEx/plugins) and a .jar for Minecraft (mods; Forge, NeoForge, Quilt and Fabric). It contains no mods. It sends them itself, from the panel, while the game starts.
Every file is made for one Nebula account on one scope: a server, or a game's global mods. When the game starts the file asks the panel who it is for, which PC it is on and which game version is installed. The panel answers with only the mods that account may have, each encrypted for that one run. If anything is wrong the file closes the game and shows the reason once it has closed.
/file, or from the website. On a phone the file is shared so you can send it to your PC.Open the server in the app or on the website and use the Compiled file tab. It shows your own file, every file on the server (who, which PC, game version, playing now) and lets you deactivate any of them at any time, even while the game is running (it closes within seconds, with the reason you typed) or unbind the PC so the file can be used on another one. A file that is not bound to a PC yet is already useless to anyone who finds it.
The Minecraft file is one jar that knows every loader. How it gets the mods in depends on the loader, because each loader reads its mods at a different moment:
| Loader | How the file works |
|---|---|
| Forge, NeoForge | Starts as an early service, before the loader reads the mods folder, and puts the mods in place. Nothing else to set up. |
| Quilt, Fabric | These loaders read the mods folder before any mod runs, so a file in the folder is too late. The file starts the same game once more with itself as a Java agent and waits for it to end. The player sees one game; only the first, idle Java process is extra. |
On a Fabric server a second download appears below the normal one: the Fabric file. It is the same program, used as a Java agent: add -javaagent:"path to the file.jar" to the launcher's Java arguments once. The JVM runs it before Fabric has loaded anything, so the mods are handed straight to Fabric.
Why it is safer: the game isn't started twice, nothing is placed in the mods folder, and no other mod can see the file or swap it. The normal file needs no setting but has to restart the game once.
Each account can have one of each. Both follow every rule above, and either can be deactivated.
The owner of a server can turn compiled files off for that server, and Nebula admins can turn them off for the global mods or everywhere. A file that is switched off stops working at once.
Each mod is stamped with the account it was delivered to (so a leak can be traced), signed by the panel, delivered once per session and never offered to a file that is not bound, active and on the right version. The file itself holds only the account's key, so copying it to another PC does not work, and a deactivated file is worth nothing.