RecipeManager

Workbench

RecipeManager 2

Complex recipes made easy !


Features

NOTE: I will refer to some .html files in here, those files can be found in your /plugins/RecipeManager/ folder after you loaded the plugin the first time. The html files will also be updated automatically on new versions.

  • Add new recipes:
    • Shaped or shapeless recipes with optionally multiple results;
    • Furnace recipes with optional custom cook time and optional special fuel;
    • Fuel recipes with custom burning time or even random time from speciifed range.
    • See 'basic recipes.html' for more info.
  • Making recipes more special with flags, featured flags:
    • @permission to limit a recipe (or result) to specific permission node(s);
    • @remove, @restrict and @overwrite to remove/restrict/overwrite existing recipes, including Minecraft recipes.
    • @ingredientcondition to make extra requirements from ingredients like enchantments, ranged data values, stack amounts, etc;
    • @keepitem to keep an ingredient from using up and optionally damaging it in the process;
    • @modmoney/@reqmoney and their experience and level counterparts to require/give/take money/exp/level from crafter;
    • @cooldown to limit the usage of the recipe;
    • And a lot more, see 'recipe flags.html' for all of them including documentation.
  • Flags can also be added to results to make them more special, some featured result flags:
    • @cloneingredient to clone an ingredient's features over to the result, like data value, amount, enchantments, etc;
    • @itemname and @itemlore to edit a result's display name and description with colors;
    • @potionitem and @fireworkitem to design your custom potions and fireworks;
    • @getrecipebook to get a RecipeBook as result, ones generated by this plugin with recipes in them;
    • And a lot more, see 'recipe flags.html' for all of them including documentation.
  • Flexible recipe files to add your recipes in:
    • You can use any kind of spacing and letter casing you want in recipe files, also supports comments;
    • Design your file names and folder structure as you want in the 'recipes' folder;
  • Auto-generated recipe books with high customization:
    • Pick which recipes to be added and to what volume;
    • Re-arrange them as you like;
    • Books that players have are automatically updated when edited by admin and reloaded;
    • For more information see 'recipe books.yml' file.
  • Other features:
    • Local documentation files for ease, the .html files that will be generated the first time you run the plugin;
    • Customizable settings, messages and item/data/enchant aliases in their respective YML files;
    • Supports Vault for economy and permission groups;
    • API for plugin developers, custom events and utility methods for most features;
    • MCStats / Metrics: http://mcstats.org/plugin/RecipeManager


Installing or updating

  1. Download the latest version of the plugin
  2. Place the RecipeManager.jar file in the plugins folder and start/restart the server
  3. Now the plugins/RecipeManager/ folder is created which contains configuration files (.yml) and documentation files (.html)

NOTE If you're upgrading from 1.x versions of RecipeManager, please first delete all files and folders except recipes folder from your RecipeManager folder before installing version 2, this will keep your folder clean because alot of files have been renamed and this way will be less confusing.

Also some recipes or flags might not work like in 1.x versions, please re-test your recipes.


Using the plugin

  • Run the plugin at least once to allow the .html files to be generated then start with 'basic recipes.html'.
  • Plugin settings can be configured in "plugins/RecipeManager/config.yml"
  • When you're done editing, type rmreload in server console to reload everything without a server restart.
  • Commands and permissions can be found in 'commands & permissions.html' file.


Tutorials, example recipes, tips and tricks

User-contributed resources in the Resources forum section.


Changelog

In the jar file, auto-extracted when first ran to plugins/RecipeManager/changelog.txt and on GitHub: https://github.com/haveric/RecipeManager2/blob/master/src/changelog.txt


Having problems, found bugs ?

If you have any issues or found some bugs, please create a ticket. But first you should check other tickets if the issue has been already reported. Also check the latest file's known caveats (under changelog) before posting a ticket.

Note: I don't support any previous versions other than the absolute latest, so if you used a older version, update and test again :P


Source code

Source code is on github, feel free to look at it, improve on it and provide feedback: https://github.com/haveric/RecipeManager2 If you need, you can use code from my project but please give credits.


Support project

If you feel I deserve:

https://www.paypalobjects.com/en_US/i/btn/btn_donate_SM.gif

Thanks for your support !

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of haveric haveric Oct 21, 2014 at 05:29 UTC - 0 likes

    @midlander23: Go

    I used the following recipes which work for me. My guess is that however you are creating the Goblin Tooth and Copper does not match how these are being created. Perhaps it is simply matching the symbols of & vs. §, but I can't be sure without seeing your other recipes.

    CRAFT Goblin Tooth
    371 + 371
    = 371
    @name &e&oGoblin Tooth
    @lore &f&oUsed to craft Goblin stuff. 
    
    CRAFT Copper
    266
    266
    = 266
    @name &c&oCopper
    @lore &f&oUsed to craft Goblin stuff.
    
    CRAFT goblin chestplate 
    371 + AIR + 371
    266 + 371 + 266
    371 + 266 + 371
    = CHAINMAIL_CHESTPLATE
    @ingredientcondition 371 | name &e&oGoblin Tooth | lore &f&oUsed to craft Goblin stuff. 
    @ingredientcondition 266 | name &c&oCopper | lore &f&oUsed to craft Goblin stuff. 
    @name §7[Common] §rGoblin Chain Mail 
    @lore &f- §7Level: 3 
    @lore &f- §7Class: Warrior,Rogue,Ranger 
    @lore &f- §7Armour: 7% 
    @enchant durability 1500
    

    Here's some pics showing that the recipe works.

  • Avatar of CommodoreAlpha CommodoreAlpha Oct 20, 2014 at 21:57 UTC - 0 likes

    @haveric: Go

    Quote from haveric:

    What other plugin are you using to create these recipes? What recipes do you have defined with RecipeManager and what recipes do you have defined in other plugins?

    I'll PM you my "recipes" folder shortly after posting this. And sorry about the late response.

    The reason I won't post my plugins folder is because I use a massive amount of plugins and don't want to waste your time. Now you may think, "Well, if you're using 200 plugins you're bound to receive a plugin conflict," except that I have a good idea of which plugins mess with which things, so about 198 plugins are already out of the window.

    You may want to look at these two plugins, as I know for sure they meddle with recipes: http://dev.bukkit.org/bukkit-plugins/armor-abilities/ http://dev.bukkit.org/bukkit-plugins/mtoolworx/

    Off the top of my head, no other plugin meddles with recipes in a more complex manner.

    Now for a few notes: I am running a modded, Cauldron server, but this is likely not the cause of the issue at hand. I also happen to be running StackableItems (which may play a part in how items are handled within furnaces), and the "disable all preexisting recipes" option is true for me on this plugin.

    The first crash involved a furnace with a diamond hoe in the "item getting burned" slot (AKA not the fuel nor the results slot). Why was it there? See the "ToolWorx" plugin - it involves putting hoes in furnaces.

    The second crash strangely had a full stack of coal in the fuel slot, a full stack of baked potato in the reagent slot, and a full stack of pumpkin pie in the result slot. Actually, I don't remember where the baked potato and pumpkin pie stacks were, but it's either one of the two. Why this particular furnace caused a crash - I'm not sure. This furnace could have been as unsuspecting as somebody making a whole stack of pies, then putting in a whole stack of coal and baked potato when it finished.

    Sure, I'd love to include my server IP here. But it's under construction, and I wouldn't want to get sued for players wandering inside and getting hit by a random beam of steel floating about. And no, I doubt plugins would make very good lawyers either. I've never seen a plugin that forced you to sign a contract do so well.

  • Avatar of haveric haveric Oct 20, 2014 at 20:14 UTC - 0 likes

    @midlander23: Go

    Can you edit your comment to include the recipe inside of code tags like this?

    <<code>>
    Full recipe here
    <</code>>
    

    It would help make your recipe a little clearer. After that, I'll take a look, but this is probably something I'll have to test when I get some free time.

  • Avatar of midlander23 midlander23 Oct 20, 2014 at 17:04 UTC - 0 likes

    @haveric: Go

    Maybe I didn't explain my issue properly, what I wonder about is how I should make it to link one item crafted with custom ingredients so the result must be joined to a multiple lores custom ILS item. To make me more understable: This is the item I want as result of the crafting: Item:

    : org.bukkit.inventory.ItemStack

    type: CHAINMAIL_CHESTPLATE meta:

    : ItemMeta

    meta-type: UNSPECIFIC display-name: §7[Common] §rGoblin Chain Mail lore: - '§7Level: 3' - '§7Class: Warrior,Rogue,Ranger' - '' - '§7Armour: 7%' - '' - '§7Durability: 1500/1500' And this is the recipe I set and is apparently not accepting all the lores: CRAFT goblin chestplate 371 + AIR + 371 266 + 371 + 266 371 + 266 + 371

    CHAINMAIL_CHESTPLATE

    @ingredientcondition 371 | name &e&oGoblin Tooth | lore &f&oUsed to craft Goblin stuff. @ingredientcondition 266 | name &c&oCopper | lore &f&oUsed to craft Goblin stuff. @name §7[Common] §rGoblin Chain Mail @lore &f- §7Level: 3 @lore &f- §7Class: Warrior,Rogue,Ranger @lore &f- §7Armour: 7% @enchant durability 1500

    Sorry for the spam in here but I really like how your plugin and ILS one can work so I'd like to keep them both working. Hope you can help and a thousand of thanks again.

  • Avatar of haveric haveric Oct 20, 2014 at 16:39 UTC - 0 likes

    @midlander23: Go

    I believe you can chain lores in the @ingredientcondition flag. I can't test this right now, but feel free to try this out and let me know if it works. Each lore is basically checking all of the item's lore lines and checking if any contain the string given.

    CRAFT death jewel recipe
    wood + emerald + wood
    = leather_helmet
    @color 0 200 0
    @ingredientcondition emerald | name Death Jewel | lore &cDamage: +&425&c-&475.9 | lore something else here | lore another attribute
    
  • Avatar of midlander23 midlander23 Oct 20, 2014 at 15:50 UTC - 0 likes

    @haveric: Go

    It did :D. However, now I'm getting some problems at linking recipes from your plugin to lutiple lores' items from ILS, could you send me an example with multiple lores? Many thanks for your attention, it's really kind from you to answer all my questions .

  • Avatar of haveric haveric Oct 19, 2014 at 20:11 UTC - 0 likes

    @CommodoreAlpha: Go

    You always find the interesting bugs, @CommodoreAlpha

    What other plugin are you using to create these recipes? There's nothing in that error pointing to RecipeManager as causing the issue, although I suppose it could be an indirect cause from how recipes are setup.

    What recipes do you have defined with RecipeManager and what recipes do you have defined in other plugins? Feel free to pm me the plugins folder so I can test this more thoroughly.

  • Avatar of CommodoreAlpha CommodoreAlpha Oct 19, 2014 at 19:52 UTC - 0 likes

    I've gotten this server crash, and I've reported something like this before, to which you replied it was some sort of "illegal recipe". I confirmed this shortly afterwards, but paid no more attention to the issue as I thought such crashes would be rare.

    I teleported to the offending furnace and lo and behold, there was a diamond hoe in the furnace (it was the item being smelted) - something I never specified via RecipeManager, but something that was allowed for via another plugin.

    Well, I got another crash just now, and I strongly believe it to be a similar issue: an "illegal" recipe inside of a furnace. Is it possible to - instead of crashing the server - just somehow "ignore" these recipes, or at the very least clear the tile entity's data and notify the console?

  • Avatar of haveric haveric Oct 16, 2014 at 02:03 UTC - 0 likes

    @midlander23: Go

    This is going to be a guess because I don't use ILS but I would try something like this:

    CRAFT death jewel recipe
    wood + emerald + wood
    = leather_helmet
    @color 0 200 0
    @ingredientcondition emerald | name Death Jewel | lore &cDamage: +&425&c-&475.9 // Lore used on the damage tutorial [[http://dev.bukkit.org/bukkit-plugins/item-lore-stats/|here]]
    

    You'll have to modify the lore to match what you are adding, but I think this will work. Take a look at the 'recipe flags.html' file in your RecipeManager folder, it has more detail on how to use the @ingredientcondition to match your item.

    Let me know whether this works for you or not.

  • Avatar of midlander23 midlander23 Oct 15, 2014 at 15:17 UTC - 0 likes

    @haveric: Go

    no worries, many thanks for your help, that's exactly what I was looking for :D. I have another question the, how could I add a customized item by ILS as an element of a recipe. E.g: I created the Death Jewel with ILS, a simple emerald with a name and it's own lore. Then I want it to be part of a recipe, how can I? Thanks :)

Facts

Date created
Oct 11, 2011
Categories
Last update
Sep 05, 2014
Development stage
Release
Language
  • enUS
License
GNU Lesser General Public License version 3 (LGPLv3)
Curse link
RecipeManager
Downloads
37,974
Recent files
  • R: v2.1.1 for CB 1.7.9-R0.2 Sep 05, 2014
  • R: v2.1 for CB 1.7.9-R0.2 Aug 17, 2014
  • R: v2.0 for 1.5.2 May 30, 2013
  • B: v2.0beta for 1.5.2 May 24, 2013
  • A: v2.0alpha3 for 1.5.2 May 09, 2013

Authors

Relationships

Optional dependency
Vault