Compiled files

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.

What it is

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.

For players

  • Download your file from the Servers tab (a Compiled file button on every server you are on), from the Discord bot with /file, or from the website. On a phone the file is shared so you can send it to your PC.
  • Put it in the game's mods folder. A newer download replaces your older file, which stops working.
  • The file works on one PC. A manager can let it be bound to another one.
  • One game per account: while a compiled file is playing, the Nebula app shows it in the Library and keeps Play off. Starting a game with the app first makes the file close with a message.
  • The file updates itself: its working part is fetched from the panel every start and checked against Nebula's signature.

For managers

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.

What it enforces

  • Account. Banned, not whitelisted, suspended server or turned-off account: the game closes with the reason.
  • Game version. It only runs when the installed game (and, for Minecraft, loader and loader version) matches the version the server or the global store has set.
  • The server's rules. The Security rules of the scope apply (for example disable singleplayer and close the game if disconnected in Minecraft: a player who fails to connect or is disconnected only gets Reconnect and Exit, never back to the server list), and a session ended from Security shows its reason.
  • One instance. At most one game per account, across files and the app.
  • Never in a folder you can reach. Mods are only delivered inside the running game. Among Us mods stay in memory; Minecraft needs the jars on disk while the game loads and removes them when the game closes (and cleans up any left over at the next start).

Loaders, and the Fabric file

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:

LoaderHow the file works
Forge, NeoForgeStarts as an early service, before the loader reads the mods folder, and puts the mods in place. Nothing else to set up.
Quilt, FabricThese 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.

The Fabric file (Fabric servers only)

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.

Switches

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.

What it protects

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.

Honest limits

Nothing running on a player's PC can be made impossible to extract. Compiled files make stealing a mod much harder and always traceable, not impossible: a Minecraft mod has to exist as a jar while the game loads it, and a determined person with a debugger can read memory.
  • Minecraft: Forge, NeoForge, Quilt and Fabric. Vanilla and plugin servers (Paper and similar) have no mods to deliver, so no file is offered.
  • On Quilt and Fabric the normal file restarts the game once. If the start command can't be read, the file says so and points to the Fabric file.
  • Minecraft mod files are put in a private temporary folder (Fabric, Quilt) or the mods folder (Forge, NeoForge) while the game runs and removed when it closes.
  • Among Us: needs BepInEx on the PC, like any other mod.