Multiverse-Inventories Plugin FAQ

Make sure Multiverse-Core is installed and running first, since Multiverse-Inventories depends on it. Then create your world groups using the /mvinv group command, and assign worlds to those groups so the plugin knows which worlds share or separate inventories.

A world group is a set of worlds that share the same inventory, health, hunger, and experience settings. Worlds not assigned to any group stay isolated, so grouping is how you decide which worlds share stats and which don't.

Add both worlds to the same group with /mvinv group add, then use /mvinv toggle to enable the inventory sharer for that group. Any world in that group will then use the same items, armor, and experience.

Put the worlds in separate groups (or leave them ungrouped) and make sure the inventory sharer is disabled between them. Each world then keeps its own inventory, so items stay where they were earned.

The most common cause is forgetting to toggle the specific sharer (inventory, health, hunger, experience) for that group, or a world being in more than one group. Check /mvinv info for the world to confirm which group and sharers are active.

Yes. Each sharer is toggled independently per group, so you can enable experience sharing while leaving inventory, health, or hunger separate. Use /mvinv toggle with the specific sharer name for that group.

Use the /mvinv clear command targeting the player and the specific world, which wipes that world's stored inventory without touching their items elsewhere. This is useful when a player's per-world data gets corrupted or duplicated.

Running two inventory-separation plugins at once usually causes conflicts, since both try to control the same player data. Pick one to handle inventory separation and disable the overlapping features in the other.

The plugin stores per-world player data and loads it on world change, so the main cost is disk I/O when players switch worlds frequently. On most servers this is negligible, but heavy world-hopping or very large player counts can make saving noticeable.

Deleting a group doesn't delete the stored inventories, but worlds left ungrouped revert to their own separate data. If you remove a world entirely, its stored inventory data becomes orphaned and won't be accessible unless the world is restored.