Custom Recipe Types

Registering Custom Recipe Types

To display your custom recipe types in mods, you can implement the RecipeTypeMappingSupplier.

While it can be added to guides using the standard GuideME extension mechanism, this interface can also be exposed as a Java ServiceLoader service, which enables its use in all guides.

This is important since your recipe types can show up in other guides through the use of data packs.

The following example adds custom recipe layout implementations for the AE2 custom recipe types. You do not need to use a custom block subclass necessarily, since RecipeTypeMappings just expects a factory of the form Function<RecipeHolder<T>, LytBlock> for each recipe type.

package appeng.client.guidebook;

// ...

public class RecipeTypeContributions implements RecipeTypeMappingSupplier {
    @Override
    public void collect(RecipeTypeMappings mappings) {
        mappings.add(AERecipeTypes.CHARGER, LytChargerRecipe::new);
    }

    private static LytStandardRecipeBox<ChargerRecipe> charging(RecipeHolder<ChargerRecipe> holder) {
        return LytStandardRecipeBox.builder()
                .icon(AEBlocks.CHARGER)
                .title(AEBlocks.CHARGER.asItem().getDescription().getString())
                .input(holder.value().getIngredient())
                .outputFromResultOf(holder)
                .build(holder);
    }
}

To make GuideME load this extension, add its fully qualified class name to a file with the following path in your project: src/main/resources/META-INF/services/guideme.compiler.tags.RecipeTypeMappingSupplier.

Custom Layout Blocks

While your recipe can be any custom layout block, GuideME offers a builder to quickly build recipe blocks that adhere to the standard input, arrow, output pattern.