ChestBank
Pages: < Configuration > | < Commands > | < Permissions >
PLEASE report all bugs and suggestions as tickets using the Bukkit ticket tracker above
IMPORTANT for users updating from before v2.1.0
Version 2.1.0 introduced a complete change to the how chest data is stored. Data is now stored in an SQLite database and no longer uses YAML (.yml) files. If you have a version of the plugin prior to 2.1.0 that was not using SQL for storage, please change your storage method to SQL BEFORE updating to 2.1.0
The Officialish ChestBank
A ChestBank is a chest that you can place items in, but no-one else can access. Everyone who opens the chest sees their own inventory. The inventory is shared across all ChestBanks, so you can access your account from multiple locations.
ChestBanks can be accessed via a physical ChestBank location AND/OR using the /chest command (depending on permissions)
Features
- 100% secure item banking system
- Create multiple networks of ChestBanks that share inventories
- Limit access to specific ChestBank networks by name (see permissions)
- Limit the maximum number of item stacks a user can store in a ChestBank
- Admin commands to snoop into other peoples accounts (use with caution)
- A ChestBank in a single chest contains a double chest's inventory
- Whitelist/Blacklist option to limit items allowed in the Chestbank
- Optional creation and access fees (requires Vault)
- Option to turn all ChestBanks into Ender Chests on creation
- Access your ChestBank using /chest (permissions permitting)
- Support for YML or SQLite, with a YML to SQLite converter for pre 1.11.0 updates
- (SQLite Only) Delete any accounts where the player has not logged in for X days
- NO SPOUT PLUGIN REQUIRED
Review
Thanks go to luigi_vampa for his updated YouTube Review of ChestBank.
Installation
Put the JAR file in your /plugins folder, assign permissions and reload/restart.
Configuration
See the < Configuration > page for details
Donations
To show your support and help me justify to my wife why I spend so much time on Minecraft, please donate using the Donate button in the top right corner of this page!
Other Projects
Take a look at my other plugins, including SimpleSpawn, MyChunk & ATMsigns.
Suggest a Project
Got an idea for a project? PM me and I'll give it a look!
@ellbristow
Hey if I give someone the permission chestbank.use.networks.(Network) it gives them permission to all and not just that network. Why is that? Please respond.
normal_limit: 2 elevated_limit: 15 vip_limit: 5
how can i add more permission ranks than the two you have the vip and normal i plan to need a 3rd one for a higher donor rank im making :P i tried it with elevated still only 5 slots
@Neo5555 The enderchest is saved on a per-player basis (and there's only one enderchest for each player that can be accessed via every actual enderchest in the same world). Thus, ChestBank basically acts like an improved enderchest already (it's available from everywhere and, with the right permissions in place, you can have as many as you like, for each world separately).
There's no enderchest that is shared between players and, similar to that, there's no ChestBank that is shared between players. You might have found out already that, even if you allow several players to access the same ChestBank network, they can still only ever see their own items on it. (If just that is what you're after, all you have to do is allow everyone access to all networks (they won't be able to steal anything because they simply won't see other players' items, but they'll be able to use the same actual chests to see their own stuff, which is also the only benefit of this over creating separate networks for each player).
[The network names are pretty much only relevant for chest placement, but not for accessing the "chests". Those are just two different sets of data saved (as you can see in the chests.yml, the only information saved with the networks are the positions of actual related chests, and the only information saved with each player are the items they have stored on each network, but they're not really dependent on each other.)]
The main difficulty with making the same ChestBank contents available to more than one player, is that the changes made to a ChestBank are saved only upon "closing" it. There would need to be one of at least two options to prevent contents from getting messed up:
(Determination between private networks and public networks would be needed too.)
Outline: I really like the idea of having shared public mobile chests, although it might make the mod more susceptible to errors. (Kurzfassung: Mir gefällt die Idee solcher gemeinsam nutzbaren mobilen Kisten sehr, allerdings könnte das Ganze dadurch auch fehleranfälliger werden.)
Hi can you add a command there makes the cest accessible for everyone like a enderchest. do you know what i mean? the plugin is almost perfect if you add so a command ;)
Spigot #485 ChestBank v1.10.1 After restart I have this error:
When using transactions, you get charged even if you don't add or take anything to the chest. Is this the intended functionality? Shouldn't it only charge for successful withdrawals/deposits?
I have permissionsEX and with this plugin, users can still access the chestbank even without any chestbank permissions?
Love this plugin, great work ellbristow! It is intuitive and makes item banking a cinch.
I have a request. That I could make a new chestbank network on command from the console, without having to designate a chest. For the purpose of automating new chestbank "account" creation.
Thanks for the wonderful plugin!
v1.10.1 has been uploaded pending approval. This version fixed the known bugs from 1.10.0 and adds some new requested features.
Change Log
Enjoy!
@BadJokeRay
Make sure you are not looking THROUGH a torch, pressure plate of similar. I will be tweakign this in the next build as I have had this issue myself.
I find that if you stand directly on top of the chest you are less likely to encounter this problem.
The plugin isn't working at all for me? :S
@alanthya
I have the exact same error, it seems like the plugin isn't updating the chests.yml correctly
I am having issues with player using this plugin to dupe. If they remove something from the chest bank, and the server reloads. The item is sill in their chestbank and inventory. Running CB 1.4.7 R1.0, and ChestBank v1.10.0.
Keeps saying you are not looking at a chest, when cleary I am.
@harl
Logblock can track it probably, I used to use something similar to this back in the day and Logblock would keep track of it. I think it's something like onBlockActivate or something, which any block that fires an event of some kind is registered as active. So I think you could track/log this plugin.
@LegndPowerdNube Theoretically, yes. Technically, they aren't actual chests either and, for the chestbanks to work as intended, it's irrelevant that the underlying blocks used are actual chests. Virtually any block could be used instead, it's just not configurable without changing the class file. Unless there's a way to actually log all actions specific to other mods without hooking into them, I don't see how logging chestbanks could be done, since that doesn't seem possible through the common Bukkit API. (I've tried CoreProtect and UltraLogger to log actions related to chestbanks, but they obviously weren't aware of them.)
Are the chests loggable since TECHNICALLY they aren't virtual?
IMPORTANT!
I have just noticed that the update procedure MAY not transfer the contents of written books correctly. I can't see why because there are no errors and both the old and new systems both stored the contents correctly.
My suggestion is that you ask players to remove written books from their chestbanks before updating to v1.10.0
Oh... and for those of you who can't wait for bukkit to approve the new upload... I updated the dropbox version :)It's been approved now so that link isn't needed :)
After a long rethink I have just uploaded v1.10.0 of ChestBank!
This new version introduces a complete re-write of the chests.yml file to make it more flexible and more readable.... but also a lot larger :S
On first load this version will convert your old chests.yml file to the new format (although I recommend you take a backup first to be safe).
As a result of the new file format, ChestBank now supports all items with ItemMeta data, including Fireworks, Coloured Armour, Enchantments Maps.... all of it! :D
As always, please report any and ALL bugs and suggestions as tickets using the built in Bukkit ticket tracker a the top of this page.
Enjoy!