me.desht.pneumaticcraft.api.heat

Interface IHeatRegistry

All Known Implementing Classes:

HeatExchangerManager

public interface IHeatRegistry

Get an instance of this via PneumaticRegistry.IPneumaticCraftInterface.getHeatRegistry().

Method Summary

Modifier and Type	Method and Description
IHeatExchangerLogic	makeHeatExchangerLogic() Create a new ticking heat exchanger logic instance for use in tile entities (or potentially other ticking objects).
void	registerBlockExchanger(net.minecraft.block.Block block, double temperature, double thermalResistance) Register a block as a simple heat exchanger (temperature and thermal resistance only; no blockstate transitions).
void	registerHeatBehaviour(net.minecraft.util.ResourceLocation id, java.util.function.Supplier<? extends HeatBehaviour> heatBehaviour) Register a heat behaviour instance.

Method Detail

makeHeatExchangerLogic

IHeatExchangerLogic makeHeatExchangerLogic()

Create a new ticking heat exchanger logic instance for use in tile entities (or potentially other ticking objects).

Returns:

a heat exchanger logic

registerBlockExchanger

void registerBlockExchanger(net.minecraft.block.Block block,
                            double temperature,
                            double thermalResistance)

Register a block as a simple heat exchanger (temperature and thermal resistance only; no blockstate transitions). Don't call this directly; subscribe to HeatRegistrationEvent or use datapacks.

Note: the preferred way (and only way if you want blockstate transitions) to do this is with datapack recipes. See data/pneumaticcraft/recipes/block_heat_properties/*.json

Parameters:

block - the block

temperature - the block's temperature

thermalResistance - the thermal resistance, i.e. how quickly heat will be transferred

registerHeatBehaviour

void registerHeatBehaviour(net.minecraft.util.ResourceLocation id,
                           java.util.function.Supplier<? extends HeatBehaviour> heatBehaviour)

Register a heat behaviour instance. This can be called from your FMLCommonSetupEvent handler, but be sure to use ParallelDispatchEvent.enqueueWork(Runnable).

This is intended to add custom behaviours to certain tile entities, similar to how the vanilla furnace is handled. For general blockstate transitions (on excess heat added/removed), the correct way to do this is with datapack recipes. See data/pneumaticcraft/recipes/block_heat_properties/*.json for examples.

Parameters:

id - a unique for this heat behaviour

heatBehaviour - a heat behaviour supplier