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.
enchantablefurnacecovers 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.
enchantablefurnacecovers 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.
Comments
-
Jikoo Owner
-
View User Profile
-
Send Message
Posted Aug 4, 2014@Jikoo_K
Yeah, i use LWC, but normally, we don't need to protect ours furnaces in the city of my server. So I put a warning until 1.2.2 :D. Thanks for reply
-
View User Profile
-
Send Message
Posted Aug 4, 2014@VDeC
Fixed in 1.2.2, tested with WorldGuard and PreciousStones.
Really, the protection plugins shouldn't be cancelling the events at default event priority, they should be cancelling on low or lowest so it's cancelled before the event reaches normal plugins.
Now, LWC, there's a proper protection plugin, furnaces were protected fine with that ;D
-
View User Profile
-
Send Message
Posted Aug 4, 2014I have a bug of compatibility with WorldGuard. Player can break enchanted furnace in protected region when they should not.
-
View User Profile
-
Send Message
Posted Aug 1, 2014@VDeC
Sadly, no, Bukkit's anvil API is far too incomplete. It's possible to a degree with some hackish workarounds, but the best technique would force this plugin to be version-specific.
-
View User Profile
-
Send Message
Posted Aug 1, 2014Hello, I saw in previous posts that enchant with an anvil is impossible without being in creativemode. Have you had time to find a solution to this in 3 months. This is a great plugin, but the randomness of enchantment table is problematic. Thank you :)
-
View User Profile
-
Send Message
Posted Jul 28, 2014@Victhetiger
Thanks! I'd like to take partial credit for the idea, I did only stumble on the original because I was looking for something similar in 1.6.4 :D
-
View User Profile
-
Send Message
Posted Jul 27, 2014This is Brilliant!
-
View User Profile
-
Send Message
Posted Jul 23, 2014@Jikoo_K
The reason i had asked for it was because even tho i had negated it in an earlier group and then applied to a later group down the chain, for some reason groups after that were still being denied access to it.
But, i found the error in my permissions and its all working fine now. Thank you.
-
View User Profile
-
Send Message
Posted Jul 23, 2014@marubal21
Negating it from your lowest group on the chain of inheritance already does that.
I see no reason to introduce a feature that already exists in every (decent) permissions plugin when the feature would require said permissions plugin to use.
No.
-
View User Profile
-
Send Message
Posted Jul 23, 2014If i understand correctly, by default everyone can enchant furnaces, and i know you can negate the permission to prevent players from enchanting furnaces. But would you consider, adding an option where by default i can set it so that no one gets the permission and instead it has to be given to the group/player for them to be able to enchant?
-
View User Profile
-
Send Message
Posted Jul 23, 2014EnchantedFurnace 1.2.1 is uploaded!
-
View User Profile
-
Send Message
Posted Jul 7, 2014@GamerBah I have no idea what the syntax of your permissions plugin is, but that looks like negation. Negate the node = no enchanting.
This should be 1.7.2 compatible in terms of enchantment functionality, but it was not possible to enchant normally unenchantable objects in a furnace without version-dependent stuff that I avoid for small plugins like this.
Check the build number of CB you're running (not just version!) - if it's lower than 3071, you will have to update to allow players to enchant furnaces in enchanting tables.
-
View User Profile
-
Send Message
Posted Jul 6, 2014I am running my server on Bukkit 1.7.2-R0.3, and I have added the permission node "-enchantedfurnace.enchant" to the groups and players, and yet nothing shows up in the enchantment table selection when I put the furnace in. Does that mean I am required to use 1.7.9?
-
View User Profile
-
Send Message
Posted Jun 23, 2014@AceScizor
I've never heard of a plugin that'd do that without being configured to, sorry I can't be of use there. Just glad it isn't my fault, I suppose.
The only thing I access furnace recipes for is finding out results for fortune furnaces with nothing in the result slot.
-
View User Profile
-
Send Message
Posted Jun 22, 2014Removed the plugin and the issue remained, must be another plugin. Sorry!
-
View User Profile
-
Send Message
Posted Jun 22, 2014Can smelt ores and stone but cannot smelt food items, help?
-
View User Profile
-
Send Message
Posted Jun 10, 2014EnchantedFurnace 1.2.0 is uploaded!
Craftbukkit #3071+ or Spigot #1336+ required for enchanting
If you are not running one of these builds, be sure to negate the node "enchantedfurnace.enchant" for all users and groups - this should allow EnchantedFurnace 1.2.0 to run without issues on lower builds.
-
View User Profile
-
Send Message
Posted Jun 3, 2014@Ikk200
What server version are you running? If it's below the versions specified above, update.
Failing that, could you have denied the permission enchantedfurnace.enchant either explicitly or through inheritance from a group?
-
View User Profile
-
Send Message
Posted Jun 3, 2014It works perfectly. However, when I try to manually enchant the furnace (via an Enchant Table) it doesn't work. It wont let me click the buttons to actually enchant it. (If I do /enchant and enchant it like that, it works fine.)
-
View User Profile
-
Send Message
Posted May 1, 2014@PotatoArmyHD
As said in the permissions section, the node for enchanting defaults to true. Negate it using your permissions plugin.