Json Recipes

Description

Advantages of my version:

• JSON Format - easy to read and use, used everywhere else in Minecraft.
• Full NBT support. Throw any NBT tags on your items.
• OreDictionary support. Use ANY copper for your recipe.
• Aliases system. You can easily link back to some item(like renamed enchanted and damaged golden sword) by short and simple string. Same for fluids and recipe types(BuildCraft|Core-refinery => refinery, etc)
• Nice and easy API for modders to use.

Coming Soon:

• Some of the big mods support(Like IC2, BuildCraft, etc).
• Recipes loaded from resource packs.
• Some kind of nice JSON editor, probably in-game one.

Disadvantages:

• My version is still pretty raw, bugs can be found.
• Not everybody can properly understand how to use JSON.

What means Verified?

• Compatibility: The mod should be compatible with the latest version of Minecraft and be clearly labeled with its supported versions.
• Functionality: The mod should work as advertised and not cause any game-breaking bugs or crashes.
• Security: The mod should not contain any malicious code or attempts to steal personal information.
• Performance: The mod should not cause a significant decrease in the game's performance, such as by causing lag or reducing frame rates.
• Originality: The mod should be original and not a copy of someone else's work.
• Up-to-date: The mod should be regularly updated to fix bugs, improve performance, and maintain compatibility with the latest version of Minecraft.
• Support: The mod should have an active developer who provides support and troubleshooting assistance to users.
• License: The mod should be released under a clear and open source license that allows others to use, modify, and redistribute the code.
• Documentation: The mod should come with clear and detailed documentation on how to install and use it.

How to Install