Minecraft plugin Multiverse-Core

🔌 About Multiverse-Core

Multiverse-Core — is a Minecraft server plugin that provides comprehensive world management for Spigot and Paper servers. It lets server administrators create, import, configure and manage multiple worlds with per‑world properties, teleports and world‑specific rules. Multiverse-Core is widely used as a world management solution on modern Spigot/Paper networks and integrates with placeholder systems and optional economy hooks.

🎯 Purpose

Multiverse-Core solves the problem of running multiple distinct worlds on a single Minecraft server. Instead of separate server instances, Multiverse-Core lets you host survival, creative, minigame or custom worlds on one process and control: world creation, spawn handling, per‑world gamerules, player access and teleportation. Multiverse-Core is designed for Spigot/Paper‑based servers and aims to be performant and configurable. ()

⚙ Main features

• Create and import worlds (normal, nether, end, flat, single‑biome and custom generators). ()
• Per‑world settings: gamemode, difficulty, weather, player limits, alias, spawn location and more. ()
• Teleportation: teleport players between worlds, anchors, portals and coordinates with per‑world permissions. ()
• PlaceholderAPI integration for world placeholders (built‑in support in MV5). ()
• Economy entry‑fee and currency configuration (can reference external economy providers in world config). ()
• Purge entities, clone, regen, unload/remove worlds and manage gamerules/worldborders. ()
• Advanced command structure with tab completion, flags and async teleport improvements (MV5). ()

🧩 Who it's for

• Server owners running Spigot or Paper who need multiple distinct worlds on one Minecraft server.
• Admins and moderators who manage world lifecycle, access and teleports.
• Projects that require per‑world separation (SMP, Minigames, PvP arenas, RPG hubs).

🏗 Usage examples

• Create a flat arena world for minigames and set a player limit and custom alias.
• Import an existing world folder and configure its spawn, gamemode and player access.
• Charge an entry fee (economy hook) for special worlds and restrict access via permissions.

⚡ Highlights

• Mature world management used across many Spigot/Paper networks. ()
• Configurable worlds.yml and in‑game modify commands for quick changes. ()
• Placeholder support and integration points for other plugins. ()

⌨️ Commands

Note: This table lists core, documented /mv commands and their primary permission nodes. For the complete command reference see the official Multiverse docs. ()

🔐 Permissions

Source permission list and nodes are documented in the Multiverse "Big List O' Permissions". Server administrators should verify defaults with their permissions plugin (LuckPerms, etc.). ()

⚙ Installation

📥 Installing

• Download the Multiverse‑Core .jar from an official source (GitHub/CurseForge/Spigot). ()
• Place the .jar in your server's plugins/ folder.
• Fully restart the server (do not use /reload).
• After startup, Multiverse will generate its config and worlds.yml folder.

📦 Dependencies

• Multiverse-Core integrates with PlaceholderAPI (MV5 has official PAPI support) — enable register-papi-hook in config to expose placeholders. ()
• Economy features that use entry-fee or currency in worlds.yml may reference external economy providers (Vault‑style economy tokens). The worlds config shows currency references such as @vault-economy when configured. ()
• No mandatory dependency for basic world management (it runs on Spigot/Paper), but some optional integrations require additional plugins.

🧾 Configuration

• Multiverse generates configuration files and worlds.yml on first run. ()
• Many settings can be changed via /mv modify in‑game or by editing worlds.yml then restarting or reloading Multiverse.
• PlaceholderAPI integration is configurable in config.yml (e.g. register-papi-hook, default-locale, per-player-locale). ()
• Database: Multiverse-Core primarily uses YAML world config; advanced persistence integrations (e.g., Multiverse‑Inventories) may use external storage — check specific subplugin docs. ()

🧠 Additional information

Known conflicts

• Plugins that also take exclusive control of teleportation, world loading or player locations may conflict; test on staging before production. ()
• When using proxy networks (BungeeCord/Velocity), verify cross‑server requirements with your Multiverse add‑ons (some features are single‑server focused).

Limitations

• Designed for Spigot/Paper server cores; behavior on other server APIs is not guaranteed. ()
• Some features (economy entry fee, placeholder formats) depend on optional integrations being present and configured.

FAQ

Q1: Can I run multiple world types (flat, amplified, single‑biome)? A1: Yes — Multiverse supports creating different environment types and single‑biome worlds via create flags. ()

Q2: Does Multiverse provide PlaceholderAPI placeholders? A2: Yes — MV5 provides official PlaceholderAPI hooks and a list of %multiverse-core_*% placeholders. ()

Q3: Does Multiverse collect usage statistics (bStats)? A3: Information about telemetry (bStats) is not clearly stated in the core documentation available in the official sources; this information is absent in the primary docs. (Information not confirmed). ()

Q4: Is there an official Discord for support? A4: The project references community support channels (Discord) in official listings; check the official resource pages or GitHub for current invite details. ()

Support & contributions

• Source code and issue tracker: GitHub (Multiverse/Multiverse-Core). Documentation and command reference: the official Multiverse docs site. ()

🤝 When to use Multiverse-Core

Use Multiverse-Core when you need robust world management on a single Spigot or Paper Minecraft server: it is a battle‑tested solution for multi‑world architecture, with configurable world properties, teleportation controls, and integrations for placeholders and optional economy hooks. ()