Home

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)

Changes in the MC 1.7 release

• The id config parameter is not required anymore, since id's are hidden in MC 1.7.
• The recipe pattern in the craftingRecipe recipe now uses the unique names of items instead of numerical id's, so things like "12345:5" should be changed to "someMod:someItem:5", and "264" to "diamond" (in case of vanilla item).
• The furnaceRecipe now uses inputnameid instead of inputid, with the same change from numerical id's to name id's like above.

Config example

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.

For a detailed description of the options, please look at Config file structure. Below you can find an example of the config file (for minecraft version 1.6)

{
    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, more details about that in Config file structure

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.