Add-ons
Manage third-party behavior packs / resource packs (.zip, .mcpack, .mcaddon, etc.) installed into the current world. Aliases: addon ≡ packs.
Inbox
Path: <SFMC_ROOT>/packs/
The inbox is scanned before start bds; for day-to-day work prefer manual packs scan so you can handle conflicts and update sources.
Common commands
Full subcommands: Command reference.
World experiments diagnosis & toggles
Many modern Bedrock add-ons (custom block geometry, entity cameras, native scripts, or newer gameplay features) depend on experimental features enabled in level.dat. packs doctor provides native, safe inspection and configuration for known experiments:
Every modification automatically creates a backup (level.dat.bak), recalculates the 8-byte little-endian header length, and commits via atomic file replacement to ensure world safety.
Install and conflicts
After a successful install, entries are written to world_behavior_packs.json / world_resource_packs.json (enabled by default). Restart BDS for changes to take effect.
When the target already has the same uuid or formatted folder name:
Same uuid with a higher semver can be silently overwritten to the original folder name.
CurseForge updates
Bind installed BPs to CurseForge projects; check or apply updates at start or on demand.
Environment variable CURSEFORGE_API_KEY overrides the API key.
Implementation details (probe scoring, RP bump strategy, providers): CurseForge add-on updates (technical).
Uninstall
packs uninstall: disable, remove from world directory (or --purge to delete), clear bindings and inbox fingerprints; by default also removes paired RP when uninstalling a BP (--no-paired to skip).
Source archives under packs/_done are kept after uninstall.