Skip to main content

BetterStructures Content Packages

BetterStructures now treats official content as managed packages instead of a pure manual-import workflow.

Main Commands

CommandPurpose
/bs initializeFirst-time setup flow
/bs setupBrowse and manage package state
/bs downloadallDownloads the plugin update (if any) and all available content, then reloads
/bs downloadallcontentDownloads all available content only (no plugin update)
/bs updatecontentUpdates outdated content (alias: /bs updateallcontent)
/bs forcereinstallcontent <package|all>Re-downloads content even when the installed version is already current - the repair command for damaged or partially deleted packs
/bs recommendedpluginsLists companion plugins that pair well with BetterStructures
/nightbreaklogin <token>Shared Nightbreak token registration

These content commands come from the shared MagmaCore Nightbreak system bundled into BetterStructures, so the same lifecycle (token check, access check, download, auto-reload) is identical across MagmaGuy plugins.

Package Types

Each package declares a contentPackageType, and the setup menu offers one filter per type:

contentPackageTypeSetup menu filterFiles land in
STRUCTURE (default)Structure Packsplugins/BetterStructures/schematics/<folderNameV2>
MODULARModule Packsplugins/BetterStructures/modules/<folderNameV2>

Use /bs setup to filter and inspect packages instead of relying on old static lists.

Package Config Fields

Each package is described by a config in plugins/BetterStructures/content_packages. You rarely need to edit these by hand - they ship with the plugin and are how it tracks package state - but the fields are:

KeyDefaultDescription
isEnabledtrueWhether the package's content is active. Toggled for you when you install or uninstall from the setup menu.
nameDisplay name shown in the setup menu
descriptionLore lines shown in the setup menu
downloadLinkWhere the package is fetched from
version0Local content version, compared against the remote version to decide whether the package is out of date
folderNameV2Subfolder the package's files live in, under schematics or modules depending on the type
contentPackageTypeSTRUCTURESTRUCTURE or MODULAR
nightbreakSlugNightbreak identifier used for access checks, downloads, and as the selector for /bs forcereinstallcontent

Installing or uninstalling a STRUCTURE package also flips isEnabled on every schematic config inside its folder, then triggers a reload. MODULAR packages are toggled at the package level only.

Package States

Depending on the package and your token state, BetterStructures can distinguish between:

  • installed content
  • downloaded but not enabled content
  • outdated content
  • content that needs Nightbreak access

That means the setup menu is now the best way to confirm what the plugin believes is installed.

Manual Import Fallback

Manual imports still use:

plugins/BetterStructures/imports

Keep package zips intact, then reload BetterStructures if needed. Manual import is still supported, but it is no longer the main documented workflow.