EliteMobs Setup

This guide is for the current EliteMobs 10 code line.

Requirements

• Minecraft 1.21.4 or newer (plugin.yml declares api-version: 1.21.4)
• Java 21+
• Spigot, Paper, or a compatible fork

EliteMobs refuses to start on anything older than Minecraft 1.21.0 — it logs a warning and disables itself. Older servers need a pre-9.0 EliteMobs build.

First Boot

Start the server once, then restart it if EliteMobs updates server-side health-cap settings on first boot.

On startup EliteMobs reads settings.attribute.maxHealth.max from spigot.yml. If that value is missing, non-finite, or lower than 2048, EliteMobs raises it to 2048 and saves spigot.yml for you. Elite health scaling needs that headroom, so restart after the value is written. If the save fails, the console tells you to raise the value manually.

Recommended Workflow

1. Install EliteMobs and start the server once.
2. Run /em initialize.
3. Link a Nightbreak token with /nightbreaklogin <token>.
4. Open /em setup.
5. Use /em downloadall if you want to bootstrap official content quickly.
6. Use /em updatecontent when installed packages are marked outdated.

initialize vs setup

• /em initialize is the first-time onboarding flow.
• /em setup is the ongoing content-management interface.

Do not treat them as interchangeable.

What /em initialize asks

The first-time menu offers an info button plus three presets. Every preset marks setup as done, reloads the plugin, and then prints the follow-up links (Nightbreak login, download-all, setup guide, Discord, wiki):

Preset	Effect
Recommended	Natural elite spawning on
Content only	Natural elite spawning off, timed events off — only downloaded content (dungeons, bosses, NPCs) is active
No progression (not recommended)	Natural elite spawning off, skill system off, EliteMobs loot off. Intended for servers that only want EliteMobs content alongside something like BetterStructures

What /em setup shows

/em setup is the shared MagmaCore setup menu. It lists every EliteMobs content package with its install/update state, and MagmaCore prepends three standard entries:

• Plugin update — downloads a newer EliteMobs jar (applied after restart)
• Recommended plugins — companion plugins with install links, also available as /em recommendedplugins
• Auto-update toggle — writes nightbreak.autoDownloadPluginUpdates in config.yml

It also adds a "download all content" entry and three filters: Dungeons, Events, and Custom Models. Meta-packages hide their child packages so the list stays readable.

Content Commands

Command	What it does
/em downloadall	Plugin update plus every accessible missing or outdated package
/em downloadallcontent	Every accessible missing or outdated package, no plugin update
/em updatecontent (alias /em updateallcontent)	Only packages that are already installed and outdated
/em downloadpluginupdate	Just the EliteMobs jar
/em forcereinstallcontent <package|all>	Re-downloads content you already have, for repairing a broken install
/em setup toggle <package>	Installs or uninstalls a single downloaded package

Downloaded plugin jars and content updates only take effect after a server restart. Automatic plugin downloads (nightbreak.autoDownloadPluginUpdates: true) need a valid account token and an active supporter membership.

Manual Imports

Manual imports still use:

plugins/EliteMobs/imports

That path remains valid, but the Nightbreak-aware setup flow is now the primary documented path.

See:

• Content management
• Manual imports vs in-game management