Description

This PR fixes a bug where the Auto Drier machine would continue to register recipes and allow crafting for items that have been explicitly disabled in Items.yml.

Previously, the registerDefaultRecipes method blindly registered all hardcoded recipes without checking the isDisabled() state of the output item. This meant that server owners could not effectively disable items like Jerky or other dried goods produced by this machine.

Proposed changes

• Modified AutoDrier.java to filter recipes during registration.
• Added a check using SlimefunItem.getByItem(output) to retrieve the Slimefun item data.
• Implemented a condition: if (sfItem != null && sfItem.isDisabled()), the loop now continues (skips), preventing the recipe from being registered to the machine and the display list.

Related Issues (if applicable)

Resolves #4333

Checklist

• I have fully tested the proposed changes and promise that they will not break everything into chaos.
• I have also tested the proposed changes in combination with various popular addons and can confirm my changes do not break them.
• I have made sure that the proposed changes do not break compatibility across the supported Minecraft versions (1.16.* - 1.20.*).
• I followed the existing code standards and didn't mess up the formatting.
• I did my best to add documentation to any public classes or methods I added.
• I have added Nonnull and Nullable annotations to my methods to indicate their behaviour for null values
• I added sufficient Unit Tests to cover my code.