Nightbreak Setup and Content Management

This page is the shared setup guide for the Nightbreak-managed plugins.

It applies directly to:

• EliteMobs
• BetterStructures
• FreeMinecraftModels
• EternalTD

These plugins now share the same overall lifecycle:

1. Install the plugin and any hard dependencies.
2. Start the server once so files and menus are generated.
3. Run the plugin's first-time setup command if it has one.
4. Link a Nightbreak token with /nightbreaklogin <token>.
5. Use the plugin setup menu to browse, install, enable, disable, and update content.
6. Use the plugin bulk download/update commands when you want a faster initial bootstrap.

What MagmaCore Actually Shares

MagmaCore is the shared layer behind the Nightbreak-managed flow. It provides:

• the shared /nightbreaklogin <token> command
• the shared token storage in plugins/MagmaCore/nightbreak.yml
• shared setup-menu primitives used by plugin setup menus
• shared Nightbreak access, version, and download checks
• shared bulk-download logic that downloads files into the owning plugin's imports folder

The plugin-specific commands such as /em initialize or /bs setup are still implemented by each plugin. MagmaCore supplies the shared systems those commands use.

Shared First-Time Pattern

Most current Nightbreak-managed plugins expose:

Plugin	First-Time Command	Setup Menu	Bulk Install	Bulk Update
EliteMobs	/em initialize	/em setup	/em downloadall	/em updatecontent
BetterStructures	/bs initialize	/bs setup	/bs downloadall	/bs updatecontent
FreeMinecraftModels	/fmm initialize	/fmm setup	/fmm downloadall	/fmm updatecontent
EternalTD	/etd initialize	/etd setup	/etd downloadall	/etd updatecontent

initialize is a first-time guidance flow. It does not replace the plugin-specific setup menu or the content-management commands.

MagmaCore also has a separate plugin-startup initialization system, but that is not the same thing as the player-facing initialize commands documented here.

Recommended Server-Owner Flow

1. Install the plugin first

Drop the plugin jar and any required hard dependencies into plugins/, then start the server once.

2. Run the first-time setup flow

If the plugin exposes an initialize command, use it first. The current menus are designed to:

• mark first-time setup as complete
• point you to Nightbreak account linking
• direct you toward the current setup menu
• clarify when manual imports are still valid

The first-time menu behavior itself is shared, but the exact command name and follow-up logic remain plugin-specific.

3. Link your Nightbreak account

Go to the Nightbreak account page, get your server token, and run:

/nightbreaklogin <token>

The token is shared through MagmaCore, so one linked token can be reused by all compatible MagmaGuy plugins on that server.

4. Use the setup menu for day-to-day content management

The setup menus are the current source of truth for:

• package states
• access states
• installed vs downloaded content
• partially installed content that needs repair
• out-of-date content
• content filters by category

If you have a linked token, the setup menus are the recommended place to install and update content.

5. Use bulk install/update when you want speed

Use the downloadall command when you want to bootstrap a server quickly and the updatecontent command when you want to refresh everything that is outdated.

The shared bulk downloader only attempts Nightbreak-managed packages that:

• have a Nightbreak slug
• are accessible to the linked token
• are not downloaded yet, or are marked out of date

Most of the current plugins automatically reload themselves after successful bulk downloads.

Shared Concepts

Downloaded vs installed

A package can exist locally without being enabled. The exact meaning varies slightly by plugin, but the setup menu state matters more than whether a zip exists in imports.

Bulk downloads also land in the same plugin imports folder used by manual imports before the plugin-specific import/reload step finishes.

Access-aware content

Setup menus can now distinguish between content that:

• is available to your token
• needs to be purchased or unlocked
• is installed
• is only partially installed
• is downloaded but disabled
• is outdated

Manual imports are still valid

Nightbreak-managed plugins still support manual import workflows. Manual import is now the fallback path, not the default path. See Manual imports vs in-game management.

Plugins That Do Not Use This Flow

Not every plugin in this wiki uses Nightbreak-managed downloadable content.

• BetterFood does not use Nightbreak package management
• ResurrectionChest does not use Nightbreak package management
• WorldCannon does not use Nightbreak package management
• ResourcePackManager manages resource packs, not Nightbreak DLC packages