Bukkit

RecipeBook - Custom recipes within an inventory!
Version 1.0.4

RecipeBook has only been tested on Minecraft 1.12 with Spigot.
In addition, to the testing, Java 8 on Linux was used, so errors can occur when using Java 7 or Windows. To test the permission I used PEX.

Description

Normally, you will use the Crafting Table to craft, but it has its limitations. Let us remove those limitations and extend it! Recipes are usually only based on the material, but with this, the requirements of a recipe can be set check for display name or material. This adds a new level to craft items.
Imagine it is a quest or progression system. You need a certain set of items before you'll be rewarded. For example, you need two Diamond Sword and you'll receive a Diamond Sword +1 (with sharpness I) and continues to that concept.

Information

In the recipe section of the config file, you cannot use '&'.
- The reason is serialization and deserialization.

For colours, you'll have to use the '§' character.

In addition, the config file has already-made recipes to help you out (hopefully), but if it is confusing I have made a homemade template (look inside pages), which actually has an order.

With version 1.0.3, features have been removed. The main menu and categories will now extend itself to a new page, if it exceeds the limit.

Two recipes inside same category cannot have same name, unless you add different colours. However, this will lead to a problem with the extended permission system, because they will have the exact same name. This also applies to categories.

Features

• A lot of customization.
• Localization is changeable.
• Recipe requirements can either be based on material, display-name or both!
• Rewards can be coloured, have a lore and even enchantments above the usually minecraft standards.

Still not convinced? Go into images and take a look.

Commands

/rb <option>

• Reload [r]
  
  • Reloads the config file
• Menu [m]
  
  • Opens the Menu.

Permission

• recipebook.*
  • Gives access to all the recipebook commands. Does not include bypass.
• recipebook.reload
  • Allows you to reload the config file.
• recipebook.menu
  • Allows you to open the menu.
• recipebook.sign.use
  • Allows you to use signs.
• recipebook.sign.create
  • Allows you to create signs.
• recipebook.bypass
  • Allows you to bypass the requirements from the craft command.
• recipebook.category.*
  • Allows you to open all categories.
• recipebook.recipe.*
  • Allows you to craft all recipes.

The last two permissions can be extended by using their respecitive category name or recipe.

When using these extended permissions, no need to include color codes.

• recipebook.category.<category name>
  • Grants access to particular category.
• recipebook.recipe.<category name>.*
  • Grants access to all recipes in specified category.
    
• recipebook.recipe.<category name>.<recipe name>
  • Grants access to that particular recipe inside specified category.

Signs

If you do not use this feature disable it in the config file to increase the performance.
Every sign in Minecraft has four lines in total. This means the feature is very limited to the length of the selected category and recipe.

1. [RecipeBook] (not case-sensitive)
2. <Category name> (case and color sensitive)
3. <Recipe Name> (case and color sensitive)
4. <Recipe Name>

Line 3 and 4 are combined. They need to match their respecitive names, similar to the menu. Whenever you create a sign with the first line being acceptable, you can add colours with the '&' character. By using this feature, naming categories and recipes might be a bad idea.

Suggestion?

If you have any suggestions or feedback, I will be glad to hear them in the comment section.

Thanks!

Problems?

Use the internal issue tracker.