Modules & Reloading

Everything Is a Module

uxmEssentials isn't one monolithic blob of features, it's 34 independent modules (bounded contexts) wired together. Homes is a module. The economy is a module. Moderation, holograms, NPCs, the scoreboard, the world manager: each is its own self-contained module.

This matters because of one simple rule:

So if you only want homes, warps and an economy, disable the rest and run a lean server. Nothing you switch off is loaded.

Turning a Module On or Off

Every module has its own config file, and the very first key in it is enabled. To switch a module off:

1. Open plugins/uxmEssentials/modules/<module>/config.conf.
2. Set enabled = false.
3. Reload it: /uxmess reload <module>.

# plugins/uxmEssentials/modules/holograms/config.conf
holograms {
    enabled = false
    ...
}

That's it — no modules.conf, no central switchboard. The enabled key inside each module's own file is the switch. Flip it back to true and reload to bring the module back. Disabling a module never deletes its data, so you can safely turn it off and on again.

The Management Commands

/uxmess reload <module> re-reads just that module's config, stops and restarts it off the main thread, and republishes its commands — no full server restart needed.

The admin root /uxmess also answers to /uxmessentials and /uxe.

The 34 Modules

Each module id is the exact token you use everywhere: the config path (modules/<id>/config.conf), the reload command (/uxmess reload <id>), and the tier permission node below.

What a Fresh Install Starts With

Most modules are on out of the box. Nine ship off, because each of them either changes something a server may already handle another way or needs something the plugin cannot assume you have:

Turning one on is the same two steps as turning anything off: set enabled = true in modules/<id>/config.conf, then /uxmess reload <id>. /uxmess status prints the live state of every module, so it is the quickest way to see where you stand.

Everything not in that table ships enabled.

Two Special Cases

A couple of things behave a little differently from the 34 toggleable modules:

• migration — the EssentialsX / Vault / LiteBans importer. It ships disabled because it's a one-shot admin tool: enable it for a cutover, run your import, then switch it back off. See Migrating from EssentialsX.
• management — the in-game management GUI framework that backs /uxmess gui and every module's admin panel. It's always on and isn't a toggleable module.

The Module Permission Node

Each module has a tier node used to gate its reload and inspect access:

uxmessentials.module.<id>        # e.g. uxmessentials.module.economy

This node defaults to op. It (together with uxmessentials.admin.reload) controls who can reload or inspect that specific module.

Next Steps

• 🧠 Core Concepts — modules, config, permissions and messages
• ⚙️ Per-Module Config — what's inside each module's file
• 📟 Commands Overview — every command, grouped by module
• 🔑 Permission Reference — module tiers and quota nodes