KubeJS 1.16

This page shows everything you need to know about adjusting the recipes with the help of KubeJS.

Recipe IDs

Since all processing recipes have the same format, all methods can be applied to all 4 machines. They only differ in their ids which are the following:

aggregator -> Fluix Aggregator
centrifuge -> Pulse Centrifuge
energizer -> Crystal Energizer
etcher -> Circuit Etcher

Recipe Structure

Each recipe consists of up to 3 input ingredients, an output stack, a processing time and an energy cost. The Centrifuge and the Energizer only support one input since they only have one input slot.

Inputs are ingredients so they support tags.
Inputs need to be unique. A machine does not accept the same two items in different input slots. This is necessary to allow easy automation.

The recipe processing time defines the number of ticks it takes to craft the whole recipe. The energy cost defines how much energy the machine consumes for the whole recipe, not per tick.

Methods

Since the 1.16 mod does not directly implement a KubeJS plugin, you can use the event.custom() format for adding recipes.

event.custom({
    type: 'lazierae2:aggregator', // always needed, available ids in Recipe IDs section
    process_time: 150, // processing time in ticks as Integer
    energy_cost: 250, // energy cost for the whole recipe in FE as Integer
    output: {
        item: 'appliedenergistics2:fluix_crystal', // output id as String
        amount: 2 // output amount as Integer
    },
    input: [
        {
            tag: "forge:gems/quartz" // input 1 as Ingredient
        },
        {
            tag: "forge:dusts/redstone" // input 2 as Ingredient
        },
        {
            item: "appliedenergistics2:charged_certus_quartz_crystal" // input 3 as Ingredient
        }
    ]
});

Examples

Examples can be found here.