Bukkit

In reply to edricdylan:

 This is probably another plugin not respecting EB's modifications to events - nothing I can do on my end. See https://github.com/Jikoo/EnchantableBlocks/issues/61

In reply to vaigron505:

 First bullet point of the update notes has your answer:

• Update to 1.20.6/1.21
  • 1.20.5 and lower are not supported. Bukkit's Enchantment constants were renamed.

If you want to run a lower server version, use a lower EB version. 4.0.0 probably works fine.

In reply to starhold_:

 This plugin is largely based on the Bukkit API and the internals it touches are relatively stable with fallbacks. It generally does not need to be updated with every single Minecraft version. If you're having problems, please submit an issue to the issue tracker.

In reply to saidul_7:

 Not sure exactly what you're trying to say, you may want to use a different translator or explain in more detail.

Sounds like you're struggling with permissions? Unfortunately due to the sheer number of permissions plugins I can't really help you there. The permissions are all documented, so you'll need to figure out how to use your permissions plugin to negate them. You can even negate permissions for broader strokes of users with Bukkit's inbuilt permissions.yml.

Permissions only affect the application of enchantments. Anyone who can obtain a supported enchanted block can place and use it to its full effect. Tracking an item's source is very resource-heavy and can lead to problems with item stacking. The only reason bonus fortune resources would not work for you (assuming you're using a fortune furnace) would be if you edited the fortuneList or fortuneListIsBlacklist configuration entries.

In reply to saidul_7:

 Re: permissions: One of the unit tests ensures that players without permission can't enchant, so somehow one of the permissions is being granted by your setup. You can use /luckperms check to help figure out why your permissions are evaluating true, and /luckperms verbose to see which permissions EB is checking.

 Re: Fortune functionality: Depending on your configuration, you may have disabled certain recipes getting bonus output. By default, only sponges and cracked stone bricks are disabled. Anything with a recipe is supported, so deepslate ores should work fine (assuming they are not disabled by your configuration).

In reply to mercurialmusic:

 Not sure unless Paper has broken block drops again or another plugin is interfering. There's no difference internally for lore and names as far as this plugin goes, the users probably just care more about fancier furnaces and notice issues faster.

Paper changed how drops work to fix an issue with beehives that had the side effect of causing furnaces and other blocks with inventories to not drop their contents when replaced. The problem is that Spigot still does drop contents when the block is replaced, so the old way of dropping the item either would delete the items in the furnace on Paper or duplicate the items in the furnace on Spigot.

My current solution is to remove the block's data I have stored, store the correct item for the location, and when the block fires an event for dropping an item (which should occur immediately afterwards in the same tick), drop the correct item and attempt to locate and remove the default drop. The only way I could see this failing is if one of the events involved is cancelled by another plugin - as far as I'm aware individual worlds still tick on the main thread even if chunk loading is now async, so the cleanup task should not have an opportunity to run.

In reply to fulbi0:

 You can do that with a vanilla datapack. No interest in rewriting a vanilla feature from scratch, sorry.

In reply to 굿판타:

 Per #276, the correct default config is not created in the current release. You are likely editing the wrong configuration section, please manually update your config.