Multiworld guide - rutgerkok/BetterEnderChest GitHub Wiki

BetterEnderChest replaces the vanilla Ender Chests: when you right-click an Ender Chest, BetterEnderChest shows it's own inventory. Some servers have seperated the inventories between world groups using a plugin like MultiInv, Multiverse-Inventories, My Worlds or WorldInventories. BetterEnderChest will automatically set up the correct group structure if you have one. You don't need to change any settings in BetterEnderChest. If you are fine with both plugins having the same group structure, you won't need this page.

However, it is possible to set up a different structure in BetterEnderChest. This can be used to create interesting ways of transporting items. For example, a cave world and a normal world can have different inventories, but using Ender Chests items can be transported between them.

First of all, you need to set BetterEnderChest.manualWorldGroupManagement to true in the config.yml. After the first server restart or config reload (you can use the command /bec reload for this) two new setions will have appeared in your config.yml: the Groups section and the Imports section.

Lets take a look at the settings BetterEnderChest just created. In this example, I have installed MultiInv. I have two groups, a survival group with the worlds world, world_nether and world_the_end and a creative group with just one world: world_creative. BetterEnderChest has already imported these settings. The BetterEnderChest group section should look like this:

Groups:
  survival:
  - world
  - world_nether
  - world_the_end
  creative:
  - world_creative

BetterEnderChest lazily imports Ender Chest. When an Ender Chest is opened, BetterEnderChest first looks for a file in its own save format. When it cannot find a file, it will try to import the Ender Chest inventory from another plugin. In this example, we want BetterEnderChest to import from MultiInv. BetterEnderChest should already have created the correct settings to import each group from MultiInv.

Imports:
  survival: multiinv
  creative: multiinv

Group names should always match the ones in the inventory seperation plugin, otherwise the importing will fail. Names are case-insensitive, so if you have Nethergroup in MultiInv and nethergroup in BetterEnderChest, the importing should work.

Valid names are vanilla, none, multiinv, multiverse-inventories, my-worlds and worldinventories*. BetterEnderChest cannot import from other plugins. If you want me to provide support for another plugin, feel free to leave a comment or to open a ticket.

There are two cases where it is useful to have different world groups in BetterEnderChest and the inventory seperation plugin. Let's say you have two survival world groups: normalworlds with the worlds world, world_nether and world_the_end and caveworlds with only the world world_cave. The inventories are seperated between the caveworld and the other worlds, but you want to give your players some way to transfer items between those groups. In this case you should make one group. Our Groups and Imports section would look like this (remember, a group name in BetterEnderChest should be equal to the group name in the inventory seperation plugin, otherwise importing won't work):

Imports:
  normalworlds: multiinv
Groups:
  normalworlds:
  - world
  - world_nether
  - world_the_end
  - world_cave

The other case is that you wan't some worlds to have the same inventory, but different Ender Chests. Let's say that you are running on a server with three worlds, world, world_nether and world_the_end. You aren't using an inventory seperation plugin, but you still want seperated Ender Chests in all worlds. Your Imports and Groups section should look like this:

Imports:
  default: vanilla
  nether: none
  the_end: none
Groups:
  default:
  - world
  nether:
  - world_nether
  the_end:
  - world_the_end

Each world has been given their own group. Remember that there should never be more than one group that imports from vanilla - the Ender Chest would get imported twice, duplicating the items.

* There are two more importers, betterenderchest-flatfilenbt and betterenderchest-mysqlnbt. Those are used to import from flatfile when you have switched to a database, or the other way round.