Miscellaneous Features

This page is for features which don’t deserve their own page and/or don’t fit into another page

• Recipe Components
• Configuration

Recipe Components

KubeJS handles recipes through recipe schemas, which are made up of recipe components, essentially a mirror to a recipe type’s json (de)serialization process. For the most part recipe schemas are made through addons, but KubeJS does have a startup event for registering custom recipe schemas in your scripts.

This is not meant to be a tutorial on how to use that event, merely an acknowledgement of the recipe components KubeJS TFC adds to the event

Provided Components

KubeJS TFC adds 6 recipe component types

• tfc:outputItemStackProvider: An output ItemProviderComponent, used by recipes which support ISP outputs
• tfc:otherItemStackProvider: An ItemProviderComponent, used by recipes which support ISP intermediates
• tfc:fluidIngredient: A FluidIngredientComponent, used by recipes which support fluid ingredients
• tfc:fluidStackIngredient: A FluidStackIngredientComponent, used by recipes which support fluid stack ingredients
• tfc:alloyPart: An AlloyPartComponent, used by alloy recipes for their alloy parts
• tfc:blockIngredient: A BlockIngredientComponent, used by recipes which support block ingredients

Configuration

In KubeJS’s dev.properties file there is an option for debugInfo, if set to true, KubeJS TFC will print various debug info to the log

Additionally in the dev.properties file there is a new property, tfc/insertSelfTestsIntoConsole, which will insert TFC’s self test warnings into the KubeJS console if enabled, allowing for warnings about certain recipe ingredients not being tagged properly to be visible