Skip to main content

Manual Imports vs In-Game Management

Nightbreak-managed plugins now prefer in-game setup and content management, but manual imports still exist as a fallback.

Use the setup menu plus a linked Nightbreak token when you want:

  • access-aware content browsing
  • one-click or menu-driven installation
  • bulk download and update commands
  • automatic outdated-package checks
  • a workflow that matches the current codebase

This is the preferred path for:

  • EliteMobs
  • BetterStructures
  • FreeMinecraftModels
  • EternalTD

Fallback: Manual Imports​

Manual imports are still useful when:

  • you already have package zips downloaded
  • you are moving files between servers
  • you want to work offline from Nightbreak during testing
  • a package is intentionally being distributed outside the in-game download path

Bulk Nightbreak downloads also end up in the plugin imports folder. The difference is that the in-game path handles the access checks and download step for you.

Import Folder Map​

PluginImport Folder
EliteMobsplugins/EliteMobs/imports
BetterStructuresplugins/BetterStructures/imports
FreeMinecraftModelsplugins/FreeMinecraftModels/imports
EternalTDplugins/EternalTD/imports

Manual Import Rules​

  • Keep the downloaded package zipped unless the plugin-specific docs say otherwise.
  • Put the package into the correct imports folder.
  • Reload or restart the plugin if the plugin-specific docs require it.
  • Re-open the setup menu afterward so you can confirm the install state.

The shared importer can process:

  • .zip packages placed in imports
  • certain already-unzipped folders if they include pack.meta
  • .bbmodel files for FreeMinecraftModels

Important Differences​

In-game path​

  • token aware
  • can show locked and outdated content
  • usually reloads automatically after bulk operations
  • reflects the current intended admin workflow

Manual path​

  • works without in-game download access
  • requires you to manage zip files yourself
  • may still require a plugin reload
  • can leave content in a downloaded-but-not-enabled state depending on the plugin
  • may expose package-shape issues that the in-game access flow would normally hide until install time