Changelog:

• Fixed an issue where recipes were saved to the database and registered on the server but never added to the cache.
• Beta: Brewing stand "recipes" have been implemented. This feature is disabled by default. It includes a progress bar when looking at the brewing stand (also optional). Both options must be enabled in config.yml.
• Fixed an issue where furnaces refused to start smelting items before the fuel had begun burning.
• Improved detection of custom furnace recipes. In some versions after 1.20, metadata changes caused equals() and isSimilar() to become unreliable for comparing items in some situations.
• A new matching option has been added as an alternative to matchMeta. This method is designed to be more reliable, especially with item comparison issues introduced in newer versions. However, it does not check all item data (specially NBT data) and may be slightly less performant than matchMeta.

The brewing stand doesn't support traditional recipe registration, so brewing is fully handled through custom logic. You can watch this video for quick demonstration:

To use:

1. Enable the brewing feature in config.yml.
2. Define a custom ingredient for the top slot.
3. This unlocks the three bottom slots for custom potion targets or bottles (depending on whether the top slot item is a custom item).
4. For safety, use invalid vanilla brewing items in either the top slot or the bottom three slots to avoid interference.
5. Brewing still requires blaze powder as fuel.

If a valid custom ingredient is placed in the top slot first, inserting custom recipe items should behave just like any other item placed inside the brewing stand. Furthermore, no hopper support for custom recipes.