This release adds support for multiple customizable currency items. The intent of adding this support was support use cases where multiple items represent the same kind of currency, or different sizes of a currency and are represented with vanilla minecraft items or customized items.

In the other *bank plugins, there is support for specific currency types like iron, gold, emeralds and diamonds. These work well since you have increments of a single currency type. However, combining all of those types into a single plugin is not the intention of this plugin. It is possible, however because the concept is an item based economy, and since Vault only supports a single currency name, there is no practical naming convention that works.

This is because the name of the currency needs to be the name of the base currency. If you make iron nuggets the base currency then all other items are named that way. 10 gold nuggets would be referred to as 100 iron if you used a 10x value to the base currency, and that really doesn't make much sense.

However, there are cases where you want to use multiple custom currency items that are all similar in nature. You can certainly use this to create the same functionality as each of the other plugins.

You can also use for other item groups like hides (rabbit hide, leather), food (carrot, potato, beetroot, bread, etc.), maybe even heads (skull, zombie_head, player_head, etc.). You can use your imagination here.

But the real benefit of this plugin is to support custom currency items, and the default config.yml reflects that in the example configuration by defining custom items.

The way it works is that an item in Minecraft, in this case the poisonous potato, is given a CustomModelData tag that identifies it as something different than the normal poisonous potato. A resource pack is then used to display a different texture for that item.

The example sets up 4 custom items: wooden_coin, stone_coin, iron_coin and gold_coin. The wooden_coin is the base currency and represents a value of 1. All other coins are multiples of that base value.

The example also includes a resource pack that will provide textures for those custom items. You can disable the generation of the resource pack with a flag in the config.yml file. It just creates the file under the plugin's folder, it doesn't install it in any way.

If these settings are not to your liking, then custom items can be defined in the config.yml based on material type, display name, lore, enchantments, durability, unbreaking, and custom_model_data. This should support most implementations of custom item data.

If you have any questions, please post in the discussion forum.