Pockets

v1.1.4 It has been almost a Year since releasing. I have finally settled in Germany and will once again have some time to get back into plugin development. Starting off slowly, I have simply updated Yearmarked to use the latest Spigot API version 1.12.2-R0.1-SNAPSHOT. For developers: I also have successfully pushed my core library ( Blocktyper) for my plugin projects to maven central. That means you can start using my library to create your own plugins by simply including blocktyper as a maven dependency.

v1.1.3 Whitelists/Blacklists Each item can have a whitelist or blacklist defined. A global blacklist can also be defined. An item whitelist will override the global blacklist. All items are supported Complex items like Granite (Stone-1) are now supported. Just append a dash or hyphen to the end of the material name followed by the appropriate data value. Many thanks to ' CalamityGreen' for the blacklist/whitelist idea. Tagged code release here. Below is the new 'global-blacklist' config setting as well as 4 new pocket items demonstrating all of the new configurations. Don't forget to add the material-setting keys to your 'materials-which-can-have-pockets' list if you want to use them as pockets. I just included them in the config to show off the new configurations without messing with your old configurations. The new config will kick any bedrock out of your pockets the next time they close however if you do not remove the 'global-blacklist' setting first. Code (Text): global-blacklist: BEDROCK material-settings: STONE-1: limit: 12 allow-pocket-in-pocket: true whitelist: - STONE-1 FURNACE: limit: 1 allow-pocket-in-pocket: false whitelist: - COAL - COAL_BLOCK TNT: limit: 1 allow-pocket-in-pocket: false blacklist: - FLINT_AND_STEEL - LAVA_BUCKET BEDROCK: limit: 12 allow-pocket-in-pocket: false whitelist: - BEDROCK Enjoy!

In all previous versions, there was nothing stopping a user from crafting a pocket into an item that already had one. This would make them lose their pocket contents and it is a waste of a pocket. This is no longer possible. Thanks to l3enn for this suggestion. This release also solved an issue that can happen with storing too much data in NBT tags of an item. While coding Blueprinter, I actually had an issue which corrupted a chunk, so it is highly advisable to upgrade to this version. A player would have to store thousands of stacks in the pocket for the issue to happen, but hey ... better safe than sorry. Release snapshot

Disabled all user interaction while ' Your Pockets' inventory is open Tagged code release here.

Version 1.1.0 The following commands will all open an inventory showing your pockets. The pockets are displayed in ascending order of how full they are. Code (Text): commands: pockets: description: Opens an inventory showing your pockets. taschen: description: Öffnet ein Inventar, das Ihre Taschen anzeigt. bolsillos: description: Abre un inventario que muestra sus bolsillos. poches: description: Ouvre un inventaire qui affiche vos poches. карманы: description: Открывает перечень, который отображает ваши карманы. There was also an error log fix. Thanks to " X00LA" for reporting this issue. Tagged code release here. P.S. I just realized that you can do some weird stuff in this inventory if you use it for anything except opening pockets. I am going to fix this now. #shortestReleaseEver

v1.0.9 New Features: 1. Drop items into pockets without opening the pocket. 2. Go back to inventory by shift-right clicking the open pocket (i.e. "Back Button") 3. Dynamically translate the Pocket item into the user's language. 4. All messages are configurable in config for any language (locale code). Code snapshot here.

NBT Tags Today " l3enn" pointed out that potions could not be stored in pockets as they would lose their state. I am happy to report that the update I have been working on for the last 3 days inadvertently solved this issue. I was working on converting to NBT tags instead of using hidden lore for the last 3 days. It was very important to me that your old items would be seamlessly converted to the new system. Mostly it was just a fun challenge. Anyway, I learned a lot about what you can do with NBT tags. I used a reflection based library that you can checkout here. Essentially item copies are used in order to work with the NBT data, so the code no longer has an object reference to the ItemStack with the pocket when you are in the pocket inventory. I had to reference the inventory and position where the pocket was when you opened it. If anyone wants to test destroying a chest while a friend is looking in the pocket that exists in that chest, that would be cool. Caveats: Books which have been written in and enchanted books do not seem to store the required data in NBT tags, so I do not allow users to store books in pockets.

Spanish language update. Thanks to l3enn for the translations.

Added French Language Support. This is from Google translate. Please let me know how bad they are.. and send corrections

Lore/Enchantment Transfer: When crafting a pocket into an existing item, if that item had any lore or enchantments or a custom name, that data will be transferred to the newly crafted item. Remember that the item needs to be fully repaired before you can craft with it. Dynamic language for Pocket Name : The word "Pocket" is now controlled by the player's language settings. German, Russian and English are supported in default config file for the pocket recipe, but you can add your own as well. The pocket item is stuck with the language it is crafted with initially, but the actual word "Pocket" on the gear can dynamically change to the correct language when items are added or removed. So if a Russian loots a German's chest piece, the word "Pocket" will dynamically change once the Russian interacts with the pocket. Russian messaging support : Thanks to CalamityGreen for the Russian translations.

Removed some excess logging. Thanks to l3enn for pointing this out.

Updated German translations. Vielen Dank X00LA

Language setting are controlled by the player. They can choose between German and English currently. If they choose an unsupported language it will default to the locale in the config file. If that is not set, it will revert to your Essentials locale setting if you have Essentials installed.

The following config setting are now available for controlling who has access to general pocket use and additionally who has access to pocket-in-pocket (infinite storage) use. require-permissions-general-pocket-use: false permissions-for-general-pocket-use: pockets.general require-permissions-pocket-in-pocket-use: false permissions-for-pocket-in-pocket-use: pockets.pocket-in-pocket