li.cil.oc.api.detail

Interface DriverAPI

public interface DriverAPI

Method Summary

Methods

Modifier and Type	Method and Description
void	add(Block driver) Registers a new driver for a block component.
void	add(Converter converter) Registers a new type converter.
void	add(Item driver) Registers a new driver for an item component.
Item	driverFor(net.minecraft.item.ItemStack stack) Looks up a driver for the specified item stack.
Block	driverFor(net.minecraft.world.World world, int x, int y, int z) Looks up a driver for the block at the specified position in the specified world.

Method Detail

add

void add(Block driver)

Registers a new driver for a block component.

Whenever the neighboring blocks of an Adapter block change, it checks if there exists a driver for the changed block, and if it is configured to interface that block type connects it to the component network.

This must be called in the init phase, not the pre- or post-init phases.

Parameters:

driver - the driver for a block component.

add

void add(Item driver)

Registers a new driver for an item component.

Item components can inserted into a computers component slots. They have to specify their type, to determine into which slots they can fit.

This must be called in the init phase, not the pre- or post-init phases.

Parameters:

driver - the driver for an item component.

add

void add(Converter converter)

Registers a new type converter.

Type converters are used to automatically convert values returned from callbacks to a "simple" format that can be pushed to any architecture.

This must be called in the init phase, not the pre- or post-init phases.

Parameters:

converter - the converter to register.

driverFor

Block driverFor(net.minecraft.world.World world,
              int x,
              int y,
              int z)

Looks up a driver for the block at the specified position in the specified world.

Note that several drivers for a single block can exist. Because of this block drivers are always encapsulated in a 'compound' driver, which is what will be returned here. In other words, you should will not get actual instances of drivers registered via add(li.cil.oc.api.driver.Block).

Parameters:

world - the world containing the block.

x - the X coordinate of the block.

y - the Y coordinate of the block.

z - the Z coordinate of the block.

Returns:

a driver for the block, or null if there is none.

driverFor

Item driverFor(net.minecraft.item.ItemStack stack)

Looks up a driver for the specified item stack.

Note that unlike for blocks, there can always only be one item driver per item. If there are multiple ones, the first one that was registered will be used.

Parameters:

stack - the item stack to get a driver for.

Returns:

a driver for the item, or null if there is none.