Minecraft plugin Multiverse-Inventories

🔌 About Multiverse-Inventories

Multiverse-Inventories — is a plugin for Minecraft servers that provides separate, per-world inventories and related player data for servers using Multiverse. The plugin makes it possible to run multiple gamemodes or world‑specific progressions on a single Spigot/Paper/Bukkit server without requiring proxy-level inventory sync.

🎯 Purpose

Multiverse-Inventories addresses the need to keep player inventories, experience, and optionally game modes separated between worlds. This solves the common problem of cross‑world item leakage or shared progression when a server hosts multiple distinct worlds. Multiverse-Inventories lets server operators isolate player data per world or per configured groups of worlds. ()

⚙ Main features

• Per‑world (and grouped-world) inventories and player data separation. ()
• Designed as an add‑on for Multiverse Core (used together with Multiverse core features). ()
• Supports common server platforms (Bukkit/Spigot/Paper) as listed in official releases. ()

🧩 Who it’s for

• Server owners running multiple worlds needing isolated inventories.
• Survival, RPG or multi‑gamemode servers using Multiverse to separate world behavior.
• Administrators who prefer per‑server (not cross‑server) inventory separation.

🏗 Examples of use

• A server with separate Survival and Creative worlds where players keep different inventories per world.
• A hub network where mini‑games are separate worlds with dedicated inventories.

⚡ Quick notes

• Multiverse-Inventories is an add‑on to Multiverse Core and expects Multiverse Core installed. ()
• The plugin creates its own plugin folder and configuration files (config.yml is present in the repository). ()

⌨️ Commands

Note: The /mvinv view command is explicitly mentioned in recent release notes; the full, authoritative command list and usage details are maintained in the plugin documentation and repository. ()

🔐 Permissions

⚙ Installation

📥 Installing

• Download the plugin JAR from an official source (see URLs).
• Place the .jar into your server's plugins/ folder.
• Fully restart the server (do not rely on /reload).
• Check console for successful load messages. ()

📦 Dependencies

• Multiverse-Core — required (Multiverse-Inventories is an add‑on for Multiverse Core). ()
• No other runtime dependencies are documented in the official release notes; do not assume Vault/PlaceholderAPI unless specifically required by your configured features. If a feature requires an external plugin, it will be listed in the plugin docs. ()

🧾 Configuration

• The plugin generates its configuration files (config.yml) under its plugin folder on first run. ()
• Whether additional configuration is required depends on intended usage (world groups, inventories behaviour).
• Information about database support (MySQL/SQLite) is not explicitly documented in the main release notes; consult the repository/docs for persistence options. ()

🧠 Additional information

Known issues & conflicts

• There are reported issues and bug reports in the repository’s issue tracker related to loading errors on some server versions; test Multiverse-Inventories on a staging server before production deployment. ()
• Inventory migration between servers may require a dedicated importer/migration tool (community tools exist, e.g., an importer on Spigot). ()

Limitations

• Multiverse-Inventories separates data per server world; it is not a network‑wide cross‑server inventory synchronizer by default. For cross‑server inventory sharing you will need a dedicated networked solution. ()

FAQ

Q1: Do I need Multiverse Core? A: Yes — Multiverse-Inventories is an add‑on and requires Multiverse Core to manage worlds. ()

Q2: Will inventories sync across Bungee/Velocity backends? A: No — Multiverse-Inventories is intended for per‑server world separation. For cross‑server sync use a networked solution. ()

Q3: Where are player inventories stored? A: The plugin creates its own data/config folder; see the plugin folder created at first run. For exact storage format consult the repository/docs. ()

Q4: Does the plugin collect analytics (bStats)? A: The official release notes/README do not clearly document bStats usage; check the repository files for metrics/telemetry integrations. ()

Support & docs See the plugin repository and official documentation for detailed setup, advanced configuration and full command/permission lists. ()