li.cil.oc.api.machine

Interface Robot

All Superinterfaces:

Rotatable

public interface Robot
extends Rotatable

This interface allows interaction with robots.

It is intended to be used by components when installed in a robot. In that case, the robot in question is the tile entity passed to item driver when asked to create the component's environment.

Method Summary

Methods

Modifier and Type	Method and Description
net.minecraft.entity.player.EntityPlayer	player() Returns the fake player used to represent the robot as an entity for certain actions that require one.
void	saveUpgrade() Deprecated.
int	selectedSlot() Gets the index of the currently selected slot in the robot's inventory.

Methods inherited from interface li.cil.oc.api.Rotatable

facing

Method Detail

player

net.minecraft.entity.player.EntityPlayer player()

Returns the fake player used to represent the robot as an entity for certain actions that require one.

This will automatically be positioned and rotated to represent the robot's current position and rotation in the world. Use this to trigger events involving the robot that require a player entity, and for interacting with the robots' inventory.

Note that the inventory of each robot is structured such that the first four slots are the "equipment" slots, from left to right, i.e. slot one is the tool slot, slot two is the card slot, three the disk slot and slot four is for upgrades. The inventory proper starts after that.

Returns:

the fake player for the robot.

selectedSlot

int selectedSlot()

Gets the index of the currently selected slot in the robot's inventory.

Returns:

the index of the currently selected slot.

saveUpgrade

@Deprecated
void saveUpgrade()

Deprecated.

Causes the currently installed upgrade to be saved and synchronized.

If no upgrade is installed in the robot this does nothing.

This is intended for upgrade components, to allow them to update their client side representation for rendering purposes. The component will be saved to its item's NBT tag compound, as it would be when the game is saved, and then re-sent to the client. Keep the number of calls to this function low, since each call causes a network packet to be sent.

This is somewhat of a 'meh, it works' approach that I'm not really happy with and plan to replace with something cleaner. Don't use unless you absolutely really have to.