Custom Mealery

Description

A very simple mod that allows you to configure your own food and meals by just making a simple config file for them. (Requires Forge)

GitHub repository

Details about each config option can be found at the wiki.

When first starting the mod, a "_template.json" file will be created inside the "config/custommealery" folder. This will contain an example of all the possible configuration options for food, this file can be seen below. (Example for the MC 1.6 release, please look at the wiki for details about the changes in the 1.7 release.)

{
    id: 590,
    nameid: "shinyBread",
    name: "Shiny Bread",
    texture: "minecraft:diamond",
    colorOverlay: {
        red: 150,
        green: 255,
        blue, 100,
    },
    eatTime: 12,
    healAmount: 2,
    saturationModifier: 0.3,

    isWolfsFavoriteMeat: false,
    rarity: "epic",
    hasEffect: true,

    isAlwaysEdible: true,
    maxStackSize: 1,
    damageValue: 8,

    potionEffects: 
    [
        {
            potionid: 1,
            probability: 1.0,
            duration: 3,
            amplifier: 2
        },

        {
            potionid: 2,
            probability: 1.0,
            duration: 5,
            amplifier: 2
        }
    ],

    craftingRecipe: {
        recipeResultAmount: 4,
        recipe:
        [
            "264,264,264",
            "264,3,264",
            "264,264,264"
        ]
    },

    furnaceRecipe: {
            recipeResultAmount: 4,
            inputid: 264,
            inputmeta: 1,
            experience: 4
    }

}

Only the first three values (id, nameid, name) must be available, the others are optional.

When you define your own food, you can use any folder structure you want, as long as it resides in the "config/custommealery" folder and ends with ".json". (All files not ending with ".json" or with "_" as a prefix will be ignored.)
Icons can be added by adding a png file with the name nameid as filename, and it must reside in the same folder as your json file for that food item. Icons can optionally also be defined by referring to texture packs.

So if you for example make a meal with the nameid 'shinyBread', a possible folder structure could be:

config/custommealery/breads/shinyBread.json
config/custommealery/breads/shinyBread.png
config/custommealery/breads/shinyBread.png.mcmeta

Note: as you can see here, mcmeta files are also allowed, so animated icons are possible!

Idea by Jadedcat.

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