The key
Every expansion carries anapiKey in meta.json: a secret created on NMCrate and bound to one expansion id. The app verifies it each time the expansion loads, including after every hot reload.
Verified and untrusted
Untrusted is the normal state while you are building something: nobody has reviewed it, and the Expansions page says so. It behaves exactly like a verified expansion otherwise.
Offline
Verification is a network call, so an expansion does not load while the app is offline. This applies to legacymain.js expansions too.
Packing a .lde
.lde (Lode Expansion) is the packaged form NMCrate distributes: your folder, compressed and encrypted. .nxe is the same format under its previous name. The app still installs and reads those, so nothing already published needs repacking.
Build one with compass, in the app’s console. Open it with the CLI button in the footer:
compass setup takes the id of the expansion to build, and builds only that one. Packing used to sweep up every folder in Expansions/, which shipped whatever else happened to be lying there.
An SDK expansion is packed only if:
meta.jsonandconfig.jsonare valid, and- every module builds, with every import resolving.
.lde that exists is one that at least loads. The problems that stopped a build are printed in the console. node_modules is left out, since it is only your editor’s types. The package is named after the folder, not the id.
Legacy main.js expansions build the same way, by the id in their metadata.
Open source packages
--open-source writes the zip without encrypting it. The extension and everything else stay the same, and the app loads it like any other package: it recognises a plain zip by its first bytes.
Use it when the source is the point, for a community expansion or an example. Don’t use it if your meta.json carries a key you’d rather people didn’t read. Packing does not minify or obfuscate anything either way, so encryption is a speed bump rather than protection.
Before you publish
idmatches the NMCrate expansion the key belongs to, and is not going to change afterwards.versionis bumped; that is what an update compares.permissionslists only what you actually use. Each one is a line the user reads.sdkVersionis the range you tested against.- The expansion loads from a clean copy of the folder, with no leftovers from your editor.
What an expansion may not do
Expansions add to Lode Studio. They may not stand in for the parts of it people pay for. An expansion must not:- unlock a paid feature, by patching, skipping or faking a licence, tier or account check (including what
sdk.app.user()reports); - rebuild a paid feature so people can use it without buying it: Premium edition features, team features such as live collaboration, or Echo plans;
- tamper with Lode Studio itself, its key verification, or its servers.
Not sure whether your idea overlaps a paid feature? Ask support before you build it.