Skip to main content

Add an existing world to an inventory group with a profile checkpoint

Applies to: Multiverse-Inventories; match the linked maintainer documentation to your installed platform and release.
Documentation checked .

Adding a world to a group can change which stored inventory players receive when they cross its boundary. Treat that membership change as a data migration. Choose the intended authoritative state before allowing anyone to travel through the newly grouped world.

Work through the change

  1. Close access to the affected route and take a completed checkpoint of world player data, Multiverse-Inventories profiles and the group configuration. Record the existing group membership and shares.
  2. On a staging copy, identify a test player with recognisable items in both the ungrouped world and the target group. Record which set you expect to keep when they first join the combined route.
  3. Use the installed add-worlds or group-management workflow documented by the maintainer. Change only that world’s membership, keeping unrelated share policies and optional features unchanged.
  4. Test first entry, return entry and reconnect with the test player. Inspect all configured data types, including armour, ender chest and experience where those shares matter to the group.

Check the result

The chosen profile should appear on every intended transition without duplicating or replacing it with an unexpected world-local state. Document the first-entry result because later successful trips can hide an incorrect initial migration. Keep regular players out until the staging result matches your policy.

Before admitting players, compare one named test profile across the old and proposed group memberships. Keep the original group definitions alongside the checkpoint. Adding a world changes which profile is selected; it should not be treated as a harmless menu-label edit for active inventories.

Recover or stop safely

Restore configuration and player profiles from the same checkpoint if the result differs from the intended authority. Removing the new membership alone may not restore data already saved during a trip. Avoid bulk migration commands without a separate tested recovery copy.

For the broader setup, read Separate creative and survival inventories with Multiverse-Inventories. Check the installed plugin version before applying syntax from the official Multiverse-Inventories documentation.

No comments to display