@Flutterwry

There's still no API for potions so I can't really support them and neither is hooking into game code an option because I don't want the plugin to not work in future game versions because of changed internals (like 1.x versions did).

But it is ok to use another plugin and if you have any incompatibility issues, please tell me and I will try to fix them :}

@Marcoral

Please use:

<<code java>>
your recipe here
<</code>>

To post recipes or disable your markup in the post... or use pastebin if you want to post serval without making a huge comment :P

But I belive I removed support for 0% chance because I added @displayresult flag which you can use to set whatever result you want (or use first to use the first one that is craftable by the player).

And no the chest was added in the 2.x versions to inform the user that the recipe has multiple possible results. You could also use @secret to make certain results a secret but if you want a specific item to show then use @displayresult.

Only recipes that have more than one result will show that chest.

Using 'false' or nothing in messages.yml's nodes mostly disables chat messages, if I were to allow disabling of that message the chest would still appear with the ingredients as lore but with a blank name xD

Also I haven't fully tested if all messages.yml disabling work so if you find any that should be disableable but it's not then please inform me.

@Tealk123

Weird... I'll post a reply in this ticket: http://dev.bukkit.org/bukkit-mods/recipemanager/tickets/138-new-version-null/ please continue the discussion there :}

@Fuusko

Ehh... furnaces don't smelt wood planks by default (they use them as fuel though), but if that is a recipe added by a mod or a plugin you could define the recipe and use @remove flag.

To find the exact recipe definition, use 'rmextract' and find the recipe you want in the extracted file, then copy it into a file outside of the disabled folder (because recipe files are ignored in that folder).

@CommodoreAlpha

No, do not change it, that's the "last changed" version, I said that in the comment right next to it.

@Tealk123

That doesn't answer all my questions but anyway, I'll see if I can replicate, altough I never had that problem.

@Marcoral

A rewrite was necessary because the old version had impropper ways that had issues with other plugins and I've lost track of the code too so it was very hard to modify it further.

Old recipes should work, some flags have been changed and result definition of enchantments have been replaced with a diferent syntax.

The old version is still in the files tab but it doesn't work, I never made a 'developer version' of that, other people quickly fixed some paths that were changed with Bukkit versioning and must be continuously changed on every game version.

That version also had alot of issues with other plugins and with itself as well, if you get annoyed by updating a few recipes, then you'll get verry annoyed when they don't work properly due to incompatibilities or missing features (since it was built on MC 1.3.2).

You should read the recipe errors you get and fix them, if you can't understand a recipe error feel free to post it and I'll help you.

Also the plugin can't have any effect on the FTP, that's to be discussed with your host.

@CronosusCZ

Hmm, that's not the exact recipe as defined in the game, I used 'rmextract' and the minecart item has data value 0, here's the working recipe:

craft
@restrict <red>Access denied!
TNT
MINECART:0
= EXPLOSIVE_MINECART

But it should've told you that the recipe was not found, which it doesn't, adding that now.

On the other issue, that is an error caused by another error, or at least that happens in my tests, I haven't yet figured out the cause, I'll fix it when I figure it out.

@Tealk123

It's an issue, any errors in the console ? Have you changed config.yml ? Are you using CraftBukkit ?

I need to replicate that issue :}

@Acet0ne

Yes, see @ingredientcondition flag in 'recipe flags.html'.

@CronosusCZ

The recipe is correct, I've just tested it and it works just fine.

Grab the newest version when it's approved.

@Faldonboy

Ingredients are identifiers of recipes, flags don't affect that, those are post-processing.

For craft/combine recipes it's possible by using @ingrcond on results, but on smelting recipes it's not possible at the moment because it's a single-result recipe... I'll experiment (again) with multi-results and see if I can find a suitable setup, but I can't promise anything.

Or if Bukkit decides to pull my pull request on data values on furnace recipes (which sits there almost a year now and recently updated it too), then it would be possible without the flag.

EDIT: v2.0 is uploaded and awaits approval !

@CronosusCZ

Are you giving yourself all permissions ? Each flag has an optional skipping permission that allows certain users to skip them...

Well, I'm going to invert the use of those permissions, recipemanager.flag.* with default asigned to all and if removed will prevent flag from being usable on that player.

Because apparently too many people give themselves all possible permissions with plugins that handle that improperly, adding permissions that are asigned to nobody as default.

In short, just remove your recipemanager.skipflags.* permission.

Edit: if you're going to use v2.0 (non-beta) directly then don't worry about this anymore.