EnchantableBlocks
EnchantableBlocks (formerly EnchantedFurnace) adds effects for enchantments on blocks! Currently only furnaces are supported.
Get It Now
Builds are available on BukkitDev or in the releases.
Development builds are available for use at your own risk on AppVeyor in the Artifacts tab.
Features
Per-World Focus
All features are configurable per-world. Want an OP world? Not a problem. Want to disable blocks for a vanilla world? Absolutely. All block settings can be controlled by per-world overrides, falling through to default values when not specifically configured.
Enchantment Table Enchanting
EnchantableBlocks offers vanilla-style enchantment table usage for supported blocks. Disable certain enchantments, determine your own conflicts (i.e. silk touch/fortune), or modify enchantability either globally or for a specific world set.
Permission can be granted or denied per-implementation or as a whole. More specific overrides always take precedence.
Nodes are available as follows:
<plugin name>.enchant.table.<block name>
- Permission to enchant a specific block implementation by a plugin in an enchanting table
- Ex:
enchantableblocks.enchant.table.enchantablefurnace
- Note that this is not per-material! I.e.
enchantablefurnace
covers 3 material types.
<plugin name>.enchant.table
- Permission to enchant all block implementations by a plugin in an enchanting table
- Ex:
enchantableblocks.enchant.table
<plugin name>.enchant
- Permission to enchant all block implementations by a plugin in any enchantment source
- Ex:
enchantableblocks.enchant
Anvil Enchanting
EnchantableBlocks offers vanilla-style enchantment and combination for supported blocks in anvils. Supported blocks can be combined with either a matching block or an enchanted book to increase enchantment levels. Uses vanilla combination rules - higher level takes precedence, equal levels yield an increase of 1 level up to the level cap. The enchantment level cap is configurable per-enchantment. Enchantments can be disabled to prevent transfer, though this won't remove them from the base item. Conflicts are also determined separately for maximum configurability.
Permission can be granted or denied per-implementation or as a whole. More specific overrides always take precedence.
Nodes are available as follows:
<plugin name>.enchant.anvil.<block name>
- Permission to enchant a specific block implementation by a plugin in an anvil
- Ex:
enchantableblocks.enchant.anvil.enchantablefurnace
- Note that this is not per-material! I.e.
enchantablefurnace
covers 3 material types.
<plugin name>.enchant.anvil
- Permission to enchant all block implementations by a plugin in an anvil
- Ex:
enchantableblocks.enchant.anvil
<plugin name>.enchant
- Permission to enchant all block implementations by a plugin in any enchantment source
- Ex:
enchantableblocks.enchant
Enchantments
Furnaces
See the wiki for furnace enchantments.
Videos
A basic overview of features is available from shop1126.
Alternate English video courtesy of MusicTechnician.
Portuguese video courtesy of AbsintoJ.
Thank you all!
Permissions
- Please refer to the wiki.
Config
- Please refer to the wiki.
Hello, I assume you have discontinued support for the plugin? Are there any plans for updates to newer versions?
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.
how do I make it so that regular players can't enchant furnaces? the permits don't work, I didn't succeed. And yet, when melting, no additional items work for me, I added many different things: meat, plants, logs
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 Jikoo:
For permissions, I use LuckPerms, but the problem is in the permissions, firstly, by default, players can enchant, and secondly, even when I set the permission to false, they can still enchant (I checked not in the op)
what do you mean? I added new items to the fortunelist, or do you mean I changed lines that were not allowed? ok I'll update the plugin completely.
and by the way, are blocks from version 1 20 supported? for example shale ore
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).
Hello! Thanks as always for keeping this one going. Our players love it. Trying to figure out something in 1.18.1, though, which happened occasionally but very rarely in 1.17, but now multiple times a day. The issue doesn't seem to be in placing the block - the furnaces themselves seem to work quite well. Instead the issues arise when breaking the block - many are completely losing all enchants. This happens even after warning players not to quickly place and break, which we don't think they're doing (at least not in the number who are having trouble). The issues seem to occur regardless of added item names or additional lore, but it does seem to affect those more frequently. I'm not seeing any errors. Any suggestions?
Currently on git-Paper-99 (MC: 1.18.1). Thank you!
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.
It'd be cool if you could add custom base smelting time per item type.
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 Jikoo_K:
Didn't know that, thank you.
I wrote both POTATO and BAKED_POTATO on the config blacklist, and luck applies as it is. In this case, how do I fix it?
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.
For some reason it's not generating the config file (I've tried both reloading and restarting the server). I'm on paper 1.17, any idea what could be causing this?
In reply to sir_y0ink:
Without server logs, no. Check your logs on server start for errors. If you see something like "invalid plugin" try re-downloading the plugin, the file is probably corrupted.
In reply to Jikoo_K:
There're no errors, and I tried re-downloading before posting my previous commenting. It could be the way stuff downloads on the browser I use, I'll try chrome.
Edit: It created the plugin folder but not the config file
In reply to sir_y0ink:
Ah, looks like I accidentally removed the default config save on load while I was reworking the configuration for 3.0. You can find the defaults here. Unfortunately, you'll have to create the config.yml yourself and paste in the contents. I am on vacation for the next week and will not be around any computers, so my hands are tied.
In reply to Jikoo_K:
Alright, I debated trying that but I didn't know whether or not that would just mess it up further or not but I guess it makes sense.
hello
since the 1.17 came out, the fortune enchantment dosent work with raw iron and raw gold, it only works with food like chicken, porkchops etc.
Jikoo_K, pls fix
In reply to Jahmai_W:
Edit your configuration. If you bothered to read the changelog you'd know that raw metals are included in the default exclusion list to prevent users double dipping in fortune by using a fortune pickaxe and fortune furnace.