The Minecraft counterpart of Nebula's Secure and Secure+ badges for Among Us. You mark your mod in its MANIFEST.MF; Nebula detects the marker when the jar is uploaded and shows the badge. Works for Fabric, Quilt, Forge and NeoForge mods.
| Level | Marker in META-INF/MANIFEST.MF | What it means |
|---|---|---|
| Normal | none | Delivered by Nebula like any mod. A server's mods go to its Nebula Server agent, a player's mods go to their launcher. |
| Secure | Nebula-Secure: true | For Nebula only. Your mod can check nebula.managed and refuse to run when it was not delivered by Nebula. |
| Secure+ | Nebula-InMemory: true | Secure, and a client-side mod that is never given to a server or to whoever hosts it. Only players' games get it. |
| Client-only | environment: client in fabric.mod.json / quilt.mod.json, or Nebula-Side: client | The mod does nothing on a server, so Nebula never sends it to one. |
mods folder only while the game or server runs, and removed when it stops. Anything that was already in that folder is moved to nebula-stash and never loaded.Add the marker to your jar's manifest. With Gradle (Fabric Loom, Quilt Loom, ForgeGradle, NeoGradle):
jar {
manifest {
attributes(
'Nebula-Secure': 'true'
)
}
}
With Maven (maven-jar-plugin):
<manifestEntries>
<Nebula-Secure>true</Nebula-Secure>
</manifestEntries>
Nebula starts every game and every server it runs with -Dnebula.managed=true. A copy someone drops into their own game does not have it, so your mod can switch itself off:
// Fabric / Quilt
public class MyMod implements ModInitializer {
@Override public void onInitialize() {
if (!"true".equals(System.getProperty("nebula.managed"))) {
throw new IllegalStateException("My Mod is only available through Nebula.");
}
// ... your setup
}
}
// Forge / NeoForge: do the same check in the @Mod class constructor.
Add Nebula-InMemory instead of (or as well as) Nebula-Secure:
jar {
manifest {
attributes(
'Nebula-InMemory': 'true'
)
}
}
A Secure+ mod is a client-side mod. Nebula gives it to players' games only: the Nebula Server agent is never sent it, so the person who hosts the server never holds a copy. Design it so the server does not need it, which means a Fabric/Quilt "environment": "client" mod or a Forge/NeoForge mod that is client-side only.
Secure+ implies Secure: the nebula.managed check is available too, and the upload shows the Secure+ badge.
A mod that only matters on a player's game is never sent to a server, with or without a Nebula marker. Nebula reads "environment": "client" from fabric.mod.json (Quilt: "minecraft": { "environment": "client" }), or this manifest line for any loader:
Nebula-Side: client
A server's mods are delivered to its Nebula Server agent, encrypted and signed, held in memory and written into the mods (or plugins) folder only when the server starts. Once the server has loaded its mods, it holds the jars open itself, and the agent takes the files out of the folder at once. From then on there is no mod file to copy from the folder, and nothing is left there when the server stops.
In a Minecraft server's Server tab (web panel, desktop launcher and Android) there is a switch, Take the mod files out once loaded. It is on by default. Turn it off only if a mod misbehaves because its file is gone after loading (a mod that reopens its own jar later); the mod then stays in the folder while the server runs, like before, and is still removed when the server stops.
When a jar is uploaded Nebula reads META-INF/MANIFEST.MF and the loader's descriptor. It shows the Secure or Secure+ badge from the markers, and marks the mod client-only when the descriptor says so. It is never a manual claim: the badge always comes from the file.