BetterEnderChest is a plugin for CraftBukkit (Minecraft server mod) that adds functionality to the Ender Chest. The documentation of the plugin itself can be found on the home page. On this page there is some information about how to interact with this plugin.

This is easy, just call the appropriate method in the plugin manager and cast it to BetterEnderChest.

BetterEnderChest betterEnderChest = (BetterEnderChest) Bukkit.getPluginManager().getPlugin("BetterEnderChest");

You first need to get the appropriate ChestOwner and WorldGroup instances.

For a chest of a player, you can simply do:

ChestOwner chestOwner = plugin.getChestOwners().playerChest(OfflinePlayer player);

(Keep in mind that all Players are also OfflinePlayers, so passing a normal Player instance to this method will work.)

You can get the group containing a given world with the following method:

WorldGroup group = betterEnderChest.getWorldGroupManager().getGroupByWorld(World world);

This method will always return a valid group. If the server admin hasn't setup world groups, this method will just return the standard group.

You can use the above method to get the current group of a player:

WorldGroup group = betterEnderChest.getWorldGroupManager().getGroupByWorld(player.getWorld());

You can also get the group by the group name. This method will return null if the group doesn't exist. Group name is case-insensitve.

WorldGroup group = betterEnderChest.getWorldGroupManager().getGroupByGroupName(String groupName);

There is a constant BetterEnderChest.STANDARD_GROUP_NAME, but it is just the group name that saves directly in the /chests folder, instead of in some subfolder. The server owner may have removed the default group. To get the group of the main world you can better do:

World mainWorld = Bukkit.getServer().getWorlds().get(0);
WorldGroup mainGroup = betterEnderChest.getGroups().getGroupByWorld(mainWorld);

Now that you have the ChestOwner and WorldGroup instances, you can get the Inventory instance.

plugin.getChestCache().getInventory(chestOwner, worldGroup, new Consumer<Inventory>() {
    @Override
    public void consume(Inventory inventory) {
        // Do your things here
    }
});

BetterEnderChest will try to get the chest, which it may do on any thread. When it has found the chest, it goes back to the main thread to deliver the chest for the consume method. This means that the block of code in the consume method is always called on the main thread and that you don't need to worry about thread safety yourself.

If you feel a bit lost, this is everything you need to get the Ender Chest of an online player:

// Get the plugin
BetterEnderChest plugin = (BetterEnderChest) Bukkit.getPluginManager().getPlugin("BetterEnderChest");
// Get a ChestOwner instance for the player
ChestOwner chestOwner = plugin.getChestOwners().playerChest(player);
// Get the current group of the player
WorldGroup worldGroup = plugin.getWorldGroupManager().getGroupByWorld(player.getWorld());
// Get the chest
plugin.getChestCache().getInventory(chestOwner, worldGroup, new Consumer<Inventory>() {
    @Override
    public void consume(Inventory inventory) {
        // Do your things here

    }
});

If your plugin is directly making changes to the inventory (for example using inventory.addItem(...)), be sure to set its internal hasUnsavedChanges flag to true. If you don't do this, the chest won't get saved. If you do, BetterEnderChest will automatically save and unload the chest after a while.

BetterEnderInventoryHolder.of(inventory).setHasUnsavedChanges(true);

When a player clicks on a slot in the chest, BetterEnderChest will automatically set this flag to true.

BetterEnderChest includes a public chest and a default chest. The public chest is a chest shared by everyone; there is only one for each world group. The server admin can disable the normal private chests, and use the public chest instead.

Getting the public chest works in the same way as getting a private chest, you just need a different ChestOwner.

ChestOwner chestOwner = plugin.getChestOwners().publicChest();

Same for the default chest:

ChestOwner chestOwner = plugin.getChestOwners().defaultChest();

Sometimes, you just want to know what Ender inventory would show up if a player clicked on that block. There's a method for that:

BetterEnderChest plugin = (BetterEnderChest) Bukkit.getPluginManager().getPlugin("BetterEnderChest");
try {
    plugin.getChestOpener().getBlockInventory(Player player, Block block, new Consumer<Inventory>() {
        @Override
        public void consume(Inventory inventory) {
            // Do something
        }
    });
} catch (IllegalArgumentException e) {
    // Happens if you passed something else than an Ender Chest for the
    // block parameter. No need to catch this if you have checked the block.
} catch (NoPermissionException e) {
    // Player is missing the required permission node
} catch (ChestProtectedException e) {
    // Chest is protected by Lockette or LWC, and the player cannot
    // access it
}

For common tasks like showing an inventory, some premade consumers are available.

• plugin.getChestOpener().showInventory(Player player) to show an inventory to a player.
• plugin.getChestOpener().showAnimatedInventory(Player player, Block block): same as above, but also plays the chest opening animation. If the block parameter is not an Ender Chest block, the method fails silently.
• plugin.getChestOpener().showUnchangeableInventory(Player player) shows an inventory that the player cannot edit. This allows you to let the player view the chest, but not edit it.

You can use the consumers like this:

plugin.getChestCache().getInventory(chestOwner, worldGroup, plugin.getChestOpener().showInventory(player));

Create a new class that inherits BaseCommand. Then you can add your command using

plugin.getCommands().register(BaseCommand command);

Don't forget to look at the utility methods in BaseCommand, which can parse the [groupName/]inventoryName syntax.

BetterEnderChest uses Maven. However, it requires Spigot 1.8, which is not available in a public repo. A stripped version of Spigot that contains just the method/field/class signatures has been uploaded to my personal repo. This version contains no code and cannot be used to run the tests.

Spigot's BuildTools.jar automatically installs Spigot to your local Maven repo, so chances are you already have Spigot in your local Maven repo. To compile BetterEnderChest, just use:

mvn install

If the tests fail you can use:

mvn install -DskipTests

Pull requests are greatly appreciated. Just try to follow my formatting (spaces, not tabs and opening brackets on the same line) but don't worry too much if you mess up the style: I'll fix it after the request is pulled. If you are about to implement something big, please send me a PM on BukkitDev, so that we can discuss it first.