Install addons from the Browser
Discover and install public addons in one click from the Emrald Addon Browser.
The Addon Browser is Emrald's marketplace for public addons. It lists every addon any developer has marked public, with one-click install into the environment of your choice.
Where to find it
Two entry points:
- Top nav → Addons — opens emrald.xyz/addons, the global marketplace.
- Project → Environment → Addons tab → "Browse" — same page, but shortcut from inside a project.
What you'll see
The Browser is a searchable grid of addon cards. Each card shows:
| Field | What it tells you |
|---|---|
| Ident | The unique package identifier (e.g. yourorg.hitman). Format is org.name. |
| Author | The Steam display name of the addon's creator. |
| Install count | How many environments across all Emrald projects have this addon installed. A rough popularity signal. |
Use the search box to filter by ident or author.
Pretty metadata like screenshots, descriptions, and version notes come from sbox.game (the s&box workshop). The Browser fetches it from there on demand, so it always reflects the latest version published by the author.
Install an addon
- Find the addon you want and click Install.
- The install dialog asks you to pick a target:
- Project — the project to install into (limited to projects where you're Owner or Admin).
- Environment — which of the project's three environments will receive the addon.
- Click Install. The addon is registered against that environment immediately and starts loading on every server in that env via WebSocket.
That's it — public addons install in one click. No tokens, no files to upload.
You need Admin role (or Owner) in a project to install addons. Viewers don't see the Install button enabled.
After install
Open your project → Environments → pick the env → Addons tab. The new addon appears in the list with two controls:
| Control | What it does |
|---|---|
| Enable toggle | Turn the addon on / off without uninstalling. Off = its variables and permissions are still in the catalog but don't load on the server. |
| Remove (trash icon) | Uninstall the addon. Wipes any variable overrides and permission grants tied to this addon's ident. |
The addon's variables and permissions immediately appear in their respective tabs, ready to be configured.
Per-environment installs
Addons are installed per-environment, not per-project. This means you can:
- Try a new addon on
Developmentonly, before promoting it. - Run a different addon set on
Stagingfor QA. - Use Changes to merge the install + its config into
Productiononce you're happy.
When an addon updates
Addon developers publish updates by publishing a new version of their workshop package. Emrald picks up the new version automatically on the next server load — there's no "update addon" button to click in the panel.
If a new version changes a variable's type or removes a previously-declared key, your existing overrides will get flagged in the Variables tab (yellow Type changed or red Value invalid badges). See Environment variables → Warning states.
Public vs private
The Browser only shows public addons (those the creator marked isPublic = true). For private or unlisted addons — typically distributed directly by the creator to a specific operator — use the manual install flow.
Removing an addon
Click the trash icon next to it in the Addons tab. Confirm. The addon is uninstalled from this environment; all its variable overrides and permission grants in this env are removed.
Other environments are unaffected — uninstall is per-env.
Next steps
- Install addons manually — for private or unlisted addons
- Environment variables — configure the new addon's settings
- Permissions — grant the new addon's capabilities to your groups