Bukkit

In reply to tanisou:

 As of the latest release, there is full support for that with

@custommodeldata <number>

 Example:

@custommodeldata 1234567

In reply to bufhimat:

 Yes, see @ingredientcondition with the attribute custommodeldata

In reply to dan123yal:

 pIaybabe has the right idea, but I'll fill in the details.

Start my using /rmextract to get all the vanilla recipes exported to 'plugins/RecipeManager/recipes/disabled/<some file>.txt' and open that with an editor. Search for the recipe you want to find, which in this case is:

craft
iron_ingot + air + iron_ingot
iron_ingot + iron_ingot + iron_ingot
= minecart:0:1

 Copy that over to a file at 'plugins/RecipeManager/recipes/<your recipe file>.txt' and modify it with @remove such as:

craft
@remove
iron_ingot + air + iron_ingot
iron_ingot + iron_ingot + iron_ingot
= minecart:0:1

 That will then remove the minecart recipe once the server is started/reloaded.

If you're new to the plugin, I'd recommend looking at some of the html files within 'plugins/RecipeManager/' to get a better start, specifically the 'basic recipes.html', 'advanced recipes.html', and 'recipe flags.html'. As always though, feel free to ask if you have any other questions.

Just wanted to let everybody know that v2.15.0 has just been released (sitting in the approval queue atm, see github if you can't wait). It's been a long push, but we're finally here! Some quick info on the update:

I tried to make everything backwards compatible, but I focused on 1.12, 1.13, and 1.14. Was able to test all the way back to 1.8.8 though and it seems to be working, although I didn't get too in depth with anything there.

In 1.13 and 1.14, there are some major changes. Durability/data is no longer allowed in an ingredient (You can still use the ingredientcondition flag if you need to, but data is largely unsupported now, except for tools/weapons). For now, you will get warnings that can be ignored, but I'd recommend converting them over. "item aliases.yml" mostly contains 1.13 id conversions so that you may not even need to update anything from old id formats (but again, I'd recommend you do)

Instead though, you can define multiple ingredients per slot, which allows for much greater freedom in building recipes. Note that the combinations will still have to be unique across all recipes, but it should be much easier to define a large group of recipes that can accept more materials.

I did my best to get rid of the restrictions that occurred with shift clicking recipes. You should now be able to shift click craft to your heart's content. Speaking of hearts, max_health and other attributes is finally here in 1.13/1.14. See the ItemAttribute flag.

There are new recipe formats for campfire, blasting, smoking, and stonecutting, although stonecutting doesn't have support for flags yet and some of these behave a little strangely on /rmreload. I'd highly recommend restarting your server after making recipe changes for the best experience.

I'm sure there's a lot more that I'm missing, but I hope you guys enjoy and look forward to seeing what everybody can do with RecipeManager going forward. Thanks again for all the support along the way and look out for some new things coming along soon.

Finally, for those interested in some nerd stats. This update included 131 commits, 328 changed files with 46,792 additions and 38,425 deletions. (There may have been a restructure or two along the way)

Just a quick status update as it's been a while. I've been pushing pretty hard the last couple weeks and I am nearing a release in another week or two if everything goes correctly.

The current dev versions appear to fully support 1.12 through 1.14 (including new recipe support for some of the new blocks in 1.14)

The main things I have left are:

• Stonecutter recipe flag support (This may get cut due to API limitations, but basic recipes will still work)
• Documentation updates
• Tons of testing. This is mainly to make sure I haven't regressed any functionality

1.13 has been one of the most painful updates I've ever worked on, but I hope once this update gets completed, releases should return to a somewhat normal schedule. I appreciate all of your support as well as your patience with this update.

In reply to pIaybabe:

 I'm not sure what you mean by new text system. Can you provide an example or try clarifying that?

In reply to pIaybabe:

 I wasn't aware this was a thing, but I'll look into it and see if it's possible.

In reply to Entity587:

 Sorry for the late reply, seems there is just some naming issues with the materials:

craft
emerald + emerald block + emerald
monster_egg:35 + monster_egg:120 + monster_egg:35
iron ingot + totem + iron ingot
= dirt
@name Testing eggs

 If you run into other issues like this, take a look at "name index.html" in your RecipeManager folder and reference the "Material List" and the "Entity Type List"

Project Update: I know you guys are frustrated about the lack of 1.13 updates. I'm frustrated I haven't been able to work on it as much as I want. Real life hasn't slowed down like I had hoped it would by now, but I am still going to set aside some time to devote to plugin development again. An initial update may still take a long time, so I appreciate your patience.

If you rely on this plugin for your server, please send me a pm as I'd love to hear from you and how you're using the plugin and I know it would give me an extra boost of motivation to get back into this.

If you are a plugin developer or know someone who is and wants to help out, please feel free to reach out. I've been running this thing so long by myself and as I'm sure you've all seen, it's not always sustainable. I'm always open to contributors and ideas.

 Just a quick update since I've had a lot of people message me. Where's the 1.13 update?

I've been a lot busier in real life the last year so it has made it harder to focus on updates here. I spent a lot of that time writing Mock tests to help prevent bugs getting re-introduced and maintain stability across releases. Unfortunately, 1.13 is a massive update for RecipeManager and most of those tests no longer work due to internal api changes.

I have no intention of abandoning this project, but I also don't know how quickly I can get a release out that maintains the stability/functionality the old versions had. I should have put this message out sooner and for that I am sorry.

If there are plugin developers out there who think they might be interested in helping out, please pm me as I would appreciate any help.

I'll try to make sure updates happen here more often, but I'd ask everyone at this point to please be patient. This will be one of the biggest updates for RecipeManager we've ever had due to everything that has changed and it's going to take quite a bit of time and effort.