# Configuration file

general {
    # If true, prints the final list of all Campfire Recipes and Campfire State Changers on config (re)load. Use this to make sure everything worked. (Though you could just check in NEI.)
    B:"#Debug: Print Campfire Recipes"=false

    # If true, warnings about invalid inputs for Custom Recipes, Auto Recipe Discovery Blacklist, Signal Fire Blocks, Dispenser Behaviours Blacklist, Custom Campfire Extinguishers/Ignitors won't print to console.
    B:"#Debug: Suppress Input Error Warnings"=false

    # If true, regular campfires can be crafted only using charcoal. In vanilla either coal or charcoal can be used, but breaking campfires always drops charcoal. If for some reason you don't want players to be able to turn coal into charcoal, turn this on.
    B:"Charcoal Only"=false

    # If true, soul campfires can be crafted only using soul soil from Netherlicious. In vanilla either soul sand or soul soil can be used, but breaking campfires always drops soul soil. If for some reason you don't want players to be able to turn soul sand into soul soil, turn this on. This won't do anything if Netherlicious isn't installed!
    B:"Soul Soil Only (Netherlicious)"=false

    # Hoppers and other forms of automation will be able to insert items into these types of campfires from the sides.
    S:Automation=both

    # The unlit version of this type of campfire is the default one, instead of the lit one. Requires restart to change recipes.
    S:"Unlit by Default"=neither

    # Campfires of this type will remember the state they're in when broken and drop in the corresponding item form. As in, breaking a lit campfire always drops a lit campfire, and breaking an unlit campfire always drops an unlit campfire, regardless of the setting of Unlit by Default.
    S:"Remember Lit/Unlit State"=neither

    # Campfires of this type need Silk Touch to drop themselves when broken.
    S:"Silk Touch Needed"=both

    # Campfires of this type will be put out by rain. It's rather slow...
    S:"Put Out by Rain"=neither

    # The list of blocks that, when placed below a campfire, make its particles go higher. It's pattern validated. Format is "ore:oreName" or "modid:name" or "modid:name:meta". If meta is not given, all metas of the block work.
    S:"Signal Fire Blocks" <
        minecraft:hay_block
     >

    # The amount of time, in ticks, until campfires burn out. Setting to -1 disables burn out and lets them last forever. The first value is the setting for regular campfires, the second value is the setting for soul campfires. Varies a little bit around the given values. By default, signal fires won't burn out. See Burn Out (Signal Fires).
    I:"Burn Out Timers" <
        -1
        -1
     >

    # Campfires of this type will burn out after their burn out timer has passed, even if they're signal fires. Doesn't affect campfires that have their burn out timer disabled.
    S:"Burn Out (Signal Fires)"=neither

    # The chance for a campfire block to be destroyed when its burn timer ends. 0.0 means 0%, 1.0 means 100%. The first value is the setting for regular campfires, the second value is the setting for soul campfires. When they're destroyed, campfires will drop their inventory and their drops from being broken without Silk Touch.
    D:"Burn to Nothing Chances" <
        0.0
        0.0
     >

    # When receiving redstone power, campfires of this type will have coloured smoke particles based on the block below them. (The colour is based on map colours.) Mix with custom Signal Fire Blocks for best results. Credit: https://www.curseforge.com/minecraft/mc-mods/colorful-campfire-smoke
    S:"Colorful Campfire Smoke"=neither

    # The items the campfire will drop when broken without Silk Touch. The first entry is for regular campfires and the second entry is for soul campfires. If you leave it empty or the item isn't found, the default items will be used instead. The default item for regular campfires is two charcoal. The default item for soul campfires is one soul sand. It's pattern validated. The general simple setup is "modid:name:meta@number", with ":meta" defaulting to 0 if not included, and "@number" defaulting to 1. It can a bit more complicated than this, if you wish. Check the file in your config folder named campfirebackport.readme1.6.cfg (or the github) for # [Custom Output].
    S:"Campfire Drops" <
        
        netherlicious:SoulSoil
     >

    # Lit campfires of this type will periodically apply a regeneration effect to nearby players.
    S:"Regeneration Campfires"=neither

    # First value is regen level, from 0 to 31. Second value is the timer on the regen effect to apply (in ticks). Third value is the radius from the campfire, from 0 to 100. Fourth value is the time between each application of regeneration (in ticks). Varies a little bit around this value.
    I:"Regeneration Settings (Regular Campfires)" <
        0
        50
        5
        900
     >

    # First value is regen level, from 0 to 31. Second value is the timer on the regen effect to apply (in ticks). Third value is the radius from the campfire, from 0 to 100. Fourth value is the time between each application of regeneration (in ticks). Varies a little bit around this value.
    I:"Regeneration Settings (Soul Campfires)" <
        1
        50
        10
        700
     >

    # Campfires of this type will look through every single furnace recipe to find ones that result in an ItemFood, and add those to its list.
    S:"Auto Recipe Discovery"=both

    # Prevents Auto Recipe Discovery from adding furnace recipes that use these inputs to the recipe list. It's pattern validated. Format is "ore:oreName" or 'modid:name" or "modid:name:meta". If meta is not given, all metas of the item are blocked.
    S:"Auto Recipe Discovery Blacklist" <
     >

    # The list of Custom Recipes for the regular campfire. It's pattern validated. Here's the general simple setup: First, an item in the format "modid:name:meta@number", with ":meta" defaulting to 0 if not included, and "@number" defaulting to 1. Then put a /. Next is the output, in the same format as input. The next part is optional: a /, then a number for the cooking time in ticks. If not included, defaults to 600. Take a look at the default recipes. It actually can be way more complicated than this, if you wish. Check the file in your config folder named campfirebackport.readme1.6.cfg (or the github) for # [Custom Recipes].
    S:"Custom Recipes (Regular)" <
        minecraft:porkchop/minecraft:cooked_porkchop
        minecraft:beef/minecraft:cooked_beef
        minecraft:chicken/minecraft:cooked_chicken
        minecraft:potato/minecraft:baked_potato
        minecraft:fish:0/minecraft:cooked_fished:0
        minecraft:fish:1/minecraft:cooked_fished:1
     >

    # The list of Custom Recipes for the soul campfire. It's pattern validated. Here's the general simple setup: First, an item in the format "modid:name:meta@number", with ":meta" defaulting to 0 if not included, and "@number" defaulting to 1. Then put a /. Next is the output, in the same format as input. The next part is optional: a /, then a number for the cooking time in ticks. If not included, defaults to 600. Take a look at the default recipes. It actually can be way more complicated than this, if you wish. Check the file in your config folder named campfirebackport.readme1.6.cfg (or the github) for # [Custom Recipes].
    S:"Custom Recipes (Soul)" <
     >

    # Allows you to make campfires of one type inherit Custom Recipes from the other type. That way you don't have to type them all out twice.
    S:"Custom Recipe Inheritance"=soul inherits regular

    # The list of Custom Extinguishers for the regular campfire. It's pattern validated. Here's the general simple setup: First, put "left" for a left click action or "right" for a right click action. Then put a /. Next, an item in the format "modid:name:meta@number", with ":meta" defaulting to 0 if not included, and "@number" defaulting to 1. Then put a /. Next, put "stackable" if the item should decrease in stack size or "damageable" if the item should be damaged. The next part is optional: a >, then the output, in the same format as input. Take a look at the default Extinguishers. It actually can be way more complicated than this, if you wish. Check the file in your config folder named campfirebackport.readme1.6.cfg (or the github) for # [Custom Extinguishers/Ignitors].
    S:"Custom Extinguishers (Regular)" <
        right/minecraft:water_bucket/stackable>minecraft:bucket
        right+dispensable/tool:shovel/damageable
        right/[Fluid:"water",MinAmount:1000]/none
     >

    # The list of Custom Extinguishers for the soul campfire. It's pattern validated. Here's the general simple setup: First, put "left" for a left click action or "right" for a right click action. Then put a /. Next, an item in the format "modid:name:meta@number", with ":meta" defaulting to 0 if not included, and "@number" defaulting to 1. Then put a /. Next, put "stackable" if the item should decrease in stack size or "damageable" if the item should be damaged. The next part is optional: a >, then the output, in the same format as input. Take a look at the default Extinguishers. It actually can be way more complicated than this, if you wish. Check the file in your config folder named campfirebackport.readme1.6.cfg (or the github) for # [Custom Extinguishers/Ignitors].
    S:"Custom Extinguishers (Soul)" <
     >

    # Allows you to make campfires of one type inherit Custom Extinguishers from the other type. That way you don't have to type them all out twice.
    S:"Custom Extinguishers Inheritance"=soul inherits regular

    # The list of Custom Ignitors for the regular campfire. It's pattern validated. Here's the general simple setup: First, put "left" for a left click action or "right" for a right click action. Then put a /. Next, an item in the format "modid:name:meta@number", with ":meta" defaulting to 0 if not included, and "@number" defaulting to 1. Then put a /. Next, put "stackable" if the item should decrease in stack size or "damageable" if the item should be damaged. The next part is optional: a >, then the output, in the same format as input. Take a look at the default Ignitors. It actually can be way more complicated than this, if you wish. Check the file in your config folder named campfirebackport.readme1.6.cfg (or the github) for # [Custom Extinguishers/Ignitors].
    S:"Custom Ignitors (Regular)" <
        right/minecraft:flint_and_steel/damageable
        right/minecraft:fire_charge/stackable
        left+dispensable/class:net.minecraft.item.ItemSword[ench:20,1]/damageable
        left/[ench:20,1]/damageable
        left/[Tinkers:[I:{Fiery:1}]]/damageable
        left/[Tinkers:[B:{Lava:1}]]/damageable
     >

    # The list of Custom Ignitors for the soul campfire. It's pattern validated. Here's the general simple setup: First, put "left" for a left click action or "right" for a right click action. Then put a /. Next, an item in the format "modid:name:meta@number", with ":meta" defaulting to 0 if not included, and "@number" defaulting to 1. Then put a /. Next, put "stackable" if the item should decrease in stack size or "damageable" if the item should be damaged. The next part is optional: a >, then the output, in the same format as input. Take a look at the default Ignitors. It actually can be way more complicated than this, if you wish. Check the file in your config folder named campfirebackport.readme1.6.cfg (or the github) for # [Custom Extinguishers/Ignitors].
    S:"Custom Ignitors (Soul)" <
     >

    # Allows you to make campfires of one type inherit Custom Ignitors from the other type. That way you don't have to type them all out twice.
    S:"Custom Ignitors Inheritance"=soul inherits regular

    # Prevents these items from receiving dispenser behaviours from Custom Extinguishers/Ignitors that are dispensable. It's pattern validated. Format is "modid:name".
    S:"Dispenser Behaviours Blacklist" <
        minecraft:wooden_shovel
        minecraft:wooden_sword
     >
    B:"#Debug: Print Dispenser Behaviours"=false
    B:"Dispenser Behaviours"=true
    S:"Dispenser Behaviours Whitelist" <
     >
}


