Remote Chests

This plugin allows you to easily access chests placed at any location with a simple command. You can easily able to enable or disable chests that can be access remotely. A handy tool for admins if you find yourself always going back and forth opening chests.

Installation:
This plugin needs no external dependencies or addons. Simply drop the plugin into your plugins folder and start it up. Upon startup, a chests.yml file will be created which will store all the accessible remote chests.

Usage:
The idea for this plugin is that it's lightweight, and easy to use. Just look at a chest and run /rc create <name>. You can set this name to whatever you please and then you're easily able to open that chest with /rc open <name> . If you feel like you want to remove a chest's remote access, jst run /rc delete <name> . This does not remove the chest, only remote access to it.

Permissions:
The permissions are as followed:
- remotechests.open - Allows you to open remote chests made by you
- remotechests.open.others - Allows you to open remote chests made by other people
- remotechests.create - Allows you to create remote chests
- remotechests.delete - Allows you to delete remote chests made by you
- remotechests.delete.others - Allows you to delete remote chests made by other people.

Possible Additions in Later Versions:
- Rework the plugin to be more like a server perk rather than just an admin tool.
- Allow players to have chests bound to them.
- messages.yml or languages.yml file.
- Maybe add a way to link remote chests to an item in your inventory. Possibly like a remote backpack?

Downloads:
✓ 10
✓ 20
✓ 50
✘ 75
✘ 100
✘ 250
✘ 500 - wow

Source:
This plugin is open source and the source code for it can be found here . I will gladly accept code contributions through GitHub and if you need any help compiling the source or making changes, read the section below.

Support:
If you have any problems running this plugin or need any assistance, please feel free to reach out to me on Discord at Redned#9473 or create an issue on the GitHub page .

If you have any questions or need to report an error or bug, please do so in the discussion section or on GitHub. The review section is not a place for this.