1.4.1

Changelog - RecipesAPI v1.4.1

Bug Resolution

• Disable Plugin: add check to plugin name disable in event handler

1.4.0

Changelog - RecipesAPI v1.4.0

New Features

• Result Item: You can now configure your result item in yml mode. You can specify it by base64 material or plugin based id like ingredients.
• RecipeConfiguration: you can now specify a path to check recipe to add more possibility to add recipes in configurations.

1.3.1

Changelog - RecipesAPI v1.3.1

New Features

• Instant Recipe Registration: Refactored the recipe registration system. Recipes are now added immediately without requiring any intermediate validation steps, enhancing the speed and smoothness of adding new entries.

Improvements

• Performance Optimization: Minor enhancements to query handling and data processing for improved API responsiveness.
• Increased Stability: Fixed several minor bugs to ensure a more stable experience.

Bug Fixes

• Resolved minor issues in error handling during recipe registration.

1.3.0

Changelog for RecipesAPI

Version 1.3.0

• Fixed: Support of FoliaLib and auto creation of folder and files for yml recipes
  Now Scheduler custom of Folialib must be added on RecipesAPI constructor

1.2.1

Changelog for RecipesAPI

Version 1.2.1

• Added: Support for using tag ingredients in YAML recipe files. This allows users to specify multiple material types using tags, making recipe creation more flexible and dynamic.

  • Example: You can now define ingredients in your YAML files like so:

    ingredients:
      - item: "tag:planks"
        sign: 'P'

    This will match any item that is part of the specified tag (e.g., all types of wooden planks).

1.2.0

Changelog - Version 1.2.0

🚀 Major Changes

• No More registerRecipes Method: It is no longer required to call the registerRecipes method at the end of your onEnable method. Recipes are now automatically registered when the API is initialized, making the process even simpler! 🎉

✨ New Features

• Custom Item Plugin Hooks: You can now create hooks for custom item plugins, allowing better integration and flexibility for your recipes.
• Built-in Support for ItemsAdder and Oraxen: ItemsAdder and Oraxen are now natively supported within the API. You can use custom items from these plugins directly in your recipes, whether as ingredients or results. 🛠️
  • To use custom items in YML recipes, simply prefix the item ID with the plugin name like so: item: "<plugin_name>:<item_id>". This format works for both recipe results and ingredients.

1.1.1

Changelog - Version 1.1.1

🚀 New Features

• Option to Disable YML Support for Recipes: YML file support for recipes can now be disabled by using the updated constructor RecipesAPI(JavaPlugin plugin, boolean debug, boolean enableYmlSupport). This provides flexibility for developers who prefer to handle recipes exclusively through Java code without relying on YML configuration files.

1.1.0

Changelog - Version 1.1.0

🚀 New Features

• YML File Support for Custom Recipes: You can now define custom recipes directly in configurable YML files. This makes it easier to manage and create recipes without needing to modify Java code. 📄
  • Recipes such as shapeless crafting, shaped crafting, and furnace smelting can be specified in the YML configuration.
  • ItemStack in YML: For custom ingredients, ItemStacks are defined using a Base64-encoded string representing the serialized ItemStack. This allows for precise and detailed customization of the items used in recipes.

🛠️ Bug Fixes

• Fixed Non-Strict ItemStack Matching: The previous version incorrectly handled non-strict ItemStack matching for ingredients, causing issues with recipe recognition. In this version:
  • Non-strict ItemStack: Recipes will now correctly match items without needing all exact metadata (just NBT data, Lore and CustomModelData).
  • Strict ItemStack: For strict recipes, every attribute (including item name, lore, and NBT data) must match exactly.

1.0.2

Javadoc finish