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, thank you for the plugin, I'm looking toward your future work! I'm noticing that furnaces with the fortune enchant are putting out huge amounts of lime dye in addition to the dry kelp that should normally be produced when processing regular kelp. Is that intended behavior? If so, how do I turn it off? I already tried adding kelp and lime_dye to the fortune blacklist to no effect.
edit: Whitelist mode fixes that, however, then I can't have fortune work on everything I want because I get errors like these:
[02:16:24 WARN]: [EnchantedFurnace] No material by the name of "SALMON" could be found!
[02:16:24 INFO]: [EnchantedFurnace] Please use material names listed in https://hub.spigotmc.org/javadocs/spigot/org/bukkit/Material.html
Checking the link there, SALMON is the correct material to use.
In reply to cfinoc:
In reply to Jikoo_K:
Any changes in 1.13.2 that might prevent this plugin from working by any chance?
Was trying to update our server's build (locally first) from 1.13.1 to 1.13.2 and saw nothing bad related to EnchantableBlocks happening in the log, but my test furnace seemed to not work properly, actually it wouldn't work at all for some reason; the furnace UI opens up but it never lights no matter what kind of fuel I use. The unenchanted furnace works fine though.
Seeing that the latest build is for 1.13.1 excluding 1.13, my guess is that something else is amiss and I just haven't noticed it yet.
In reply to harl:
Please continue to work on this! I've been here using your plugins for years and I love how you're making this into a new plugin for other blocks other than furnaces! I love this plugin and want to see it succeed. I'm very excited to see what you do with this plugin it's one of the only plugins I use for my server.
Since you're adding other blocks maybe brewing stands should be next?
Keep up the hard work!
In reply to kamanabc123:
Excited to try out the new build! Do you foresee any issues (now or future) with migrating the furnaces.yml or would it be best to start everyone from scratch?
Thanks for your hard work!
In reply to mercurialmusic:
In reply to Jikoo_K:
In reply to krlsmnk:
@Jikoo_K
Can I/my friend (@StarWish_Sama) repost this plugin inside a Chinese forum but with your name and original download links? And I'd like to help translate this plugin! Could you get some .lang support and create a translation project on Crowdin?
Huge thanks!
In reply to SkyFuInMC:
Good morning ^^. Owner would you like add option in config file which will make coal faster burn item or the coal faster burn and lower burn the item. + Support for 1.13 maybe it work's hm..
Like Wood burn the terracotta 5 seconds and coal 3 seconds..
In reply to Forge_User_55234306:
Hello there O/
Some latest version bully test results for you?
EnchantedFurnace v1.6.10 + 60 other plugins.
Paper version git-Paper-1166 (MC: 1.12)
(Implementing API version 1.12-R0.1-SNAPSHOT)
20+ custom smelts.
This plugin wins. Job very well done!
Thanks for reading this, no errors to report which are any of your
plugin's fault anyway :D
TEST 1.
Does it cry or throw fits or skip anything under mad server load?
64 furnaces with 20 efficiency + 10 unbreaking arrayed in a
square (16 per side) rail/cart/hopper based autosmelter.
4 per transfer hopper settings and 8 tick check.
Furnaces all doing various normal and custom smelts. (RecipeManager).
At the time I had 60+ other plugins loaded, World Border doing
map flood fill and Dynmap generating a decent resolution map, all very CPU bully stuff. Your plugin performs 100% under serious pressure . Fact.
Did the Eco payments for smelts, particles and sound effects on all 64 furnaces,
Jobs was also paying Exp for smelted items 100% without and timings issues.
Mcmmo was leveling repair and giving bonus ingot smelts.
Smelting Speed for the whole 64 furnaces = >1.5 stacks per second.
Hmm... You win this time. Nicely.
TEST 2.
Can it work with Slimefun enhanced furnaces?
I enchanted 1 "Carbonado Furnace" with the same enchants as above.
20 Efficiency, 10 Unbreaking.
(Slimefun 4+ Enhanced Furnaces have speed/efficiency/luck buffs)
Result? 1 furnace. 1 stack. 1 second.
There is a big tissue though.
After enchanting any Slimefun enhanced furnace and placing it
when you break the enchanted enhanced furnace it it leaves a ghost
enchantedfurnace. So scary. Dropping a sand block into it's block space and
breaking the sand block causes an enchanted plain furnace to drop after getting
the enhanced furnace from same block space. The block is also locked after removing the Enchanted Slimefun Furnace, cannot place anything there.
It works great but it also causes a glitched ghost block and semi dupe function.
I have very fast block update speed on the server, max tick time tiles 55 is
better than average also for block update focus. Pretty sure this would happen
on all servers attempting to enchant Slimefun furnaces.
Possible future config update suggestion to fix this, if I may?
Deny-If-furnace-has-custom-name: true/false
or
use-only-named-furnaces: true
furnace-names:
- '&4Fusion Furnace&r'
- '&4Magma Furnace&r'
- '&4Carbon Furnace&r'
- '&4Tinder Furnace&r'
Frankly this bug was hardly a bug when it was expected. Slimefun
tends to ghost blocks fairly often when you try to get other plugins to
do stuff with it's recorded blocks. Some blockbreak event priority issue I think.
TEST 3.
Can i jam it up and confuse it?
Mad custom smelt chain - Cactus > Dye > Slimeball > Ironnugget
Array of 10 x 4 stacked furnaces feeding each below like:
5 chest/trapped chests full of cactus.
10 "fast" hoppers
10 furnaces 20 efficiency 10 unbreaking.
10 "fast" hoppers
10 Carbonado Furnaces 20 efficiency 10 unbreaking.
10 "fast" hoppers
10 furnaces 20 efficiency 10 unbreaking.
10 "fast" hoppers
5 chest/trapped chests.
No. It's totally jam proof. I resign. /salute
No suggestions. It's perfect. Thanks for reading.
In reply to Jabberwockie666:
Hello! Getting this error spammed pretty hard now with the latest Spigot build: https://pastebin.com/5F1Xmxjm
Also still getting the original error at startup:
https://pastebin.com/xkXVnWT0
Would definitely appreciate some help!
In reply to mercurialmusic: