OpenComputers: Rebooted - User contributions [en]

Component/contents

2026-09-15T22:01:34Z

SoraFirestorm: Remove link to Tunnel (page is now unified)

{| class="oc-contents-table"
! colspan="2" | [[Component|Components]]
|-
! Core Components
| [[Component/access point|Access Point]] - [[Component/computer|Computer]] - [[Component/drone|Drone]] - [[Component/drive|Drive]] - [[Component/EEPROM|EEPROM]] - [[Component/filesystem|Filesystem]] - [[Component/GPU|GPU]] - [[Component/microcontroller|Microcontroller]] - [[Component/modem|Modem]] - [[Component/redstone|Redstone]] - [[Component/robot|Robot]] - [[Component/transposer|Transposer]]
|-
! Others
| [[Component/component access|Component Access]] - [[Component/signals|Signals]]
|-
! Cross-Mod Integration
| [[Component/applied energistics|Applied Energistics]]
|}

Item/expansion card

2026-09-15T22:00:45Z

SoraFirestorm: Text replacement - "Item/linked card" to "Linked Card"

= Expansion Cards =

Expansion cards are components used to add functionalities to a device, for example a graphics card allows a computer to display content on a screen.

== Usage ==

Expansion cards can be inserted in the expansion cards slots present in all devices, once added they provide the computer a new component with functions you can access using the [[API/component|Component API]]

== Types ==

There are 8 types of expansion cards in OpenComputers, Some of them with more than one tier:

* [[Item/graphics card|Graphics Card]]
* [[Item/redstone card|Redstone Card]]
* [[Item/network card|Network Card]]
* [[Item/wireless network card|Wireless Network Card]]
* [[Linked Card|Linked Card]]
* [[Internet Card|Internet Card]]
* [[Data Card]]
* [[Debug Card|Debug Card]] (Creative Item)

Item/materials

2026-09-15T22:00:45Z

SoraFirestorm: Text replacement - "Item/linked card" to "Linked Card"

= Crafting Materials =

The following items are used to create basic and intermediate components for many of the components used to build [[Block/computer case|Computers]], [[Block/server rack|Servers]], [[Block/robot|Robots]], and [[Item/drone|Drones]].

=== Basic Components ===

Basic components are made of vanilla Minecraft components, and are used in creating intermediate components. A combination of basic and intermediate components are used in creating all of the various blocks and items available in OpenComputers.

= ==== Raw Circuit Board =

Raw Circuit Boards (8x) are made using:

* 1 x Clay
* 1 x Gold Ingot
* 1 x Cactus Green

[[File:rawcircuitboard.png|200px]]

= ==== Printed Circuit Board =

Printed Circuit Boards are made from smelting Raw Circuit Boards in a furnace.

[[File:printedcircuitboard.png|200px]]

= ==== Transistor =

Transistors (8x) are crafted using the following recipe:

* 3 x Iron Ingot
* 2 x Gold nugget/oreberry
* 1 x Redstone
* 1 x Paper

[[File:transistor.png|200px]]

= ==== Interweb =

The Interweb is made using the following recipe:

* 1 x Ender pearl
* 8 x String

[[File:interweb.png|200px]]

= ==== End Stone =

End Stone (OpenComputers version) is made using the following recipe:

* 5 x Ender pearl
* 4 x Chamelium block

[[File:endstone.png|200px]]

= ==== Disk Platter =

The Disk Platter is made using the following recipe:

* 4 x Iron nugget/oreberry

[[File:diskplatter.png|200px]]

= ==== Cutting Wire =

Cutting Wire is made using:

* 2 x Stick
* 1 x Iron Ingot

[Stick, Iron Nugget, Stick]

= ==== Diamond Chip =

Diamond Chips (6x) are made using:

* 1 x [[Item/materials#cutting_wire|Cutting Wire]]
* 1 x Diamond

= ==== Keyboard Arrow Keys/Button Group/Numeric Keypad =

All of the following recipes use Stone buttons to create the [[Block/keyboard|Keyboard]] components.

Arrow keys:

[[File:kbarrows.png|200px]]

Button group:

[[File:kbbuttons.png|200px]]

Numeric keypad:

[[File:kbnumpad.png|200px]]

= ==== Chamelium =

Chamelium is a material used in 3D Printers, and is made using the following recipe:

* 4 x Gravel
* 1 x Charoal
* 3 x Redstone
* 1 x Bucket of Water

[[File:chamelium.png|200px]]

=== Intermediate Components ===

Intermediate components are made from basic components, as well as vanilla Minecraft components.

= ==== Microchips =

The Tier 1 Microchip is crafted (8x) using the following recipe:

<pre> * 1 x [[Item/materials#transistor|Transistor]]
* 2 x Redstone
* 6 x Iron nugget/oreberry
</pre>
[[File:t1microchip.png|200px]]

The Tier 2 Microchip is crafted (4x) using the following recipe:

<pre> * 1 x [[Item/materials#transistor|Transistor]]
* 2 x Redstone
* 6 x Gold nugget/oreberry
</pre>
[[File:t2microchip.png|200px]]

The Tier 3 Microchip is crafted (2x) using the following recipe:

<pre> * 1 x [[Item/materials#transistor|Transistor]]
* 2 x Redstone
* 6 x [[Item/materials#diamond_chip|Diamond Chip]]
</pre>
[[File:tier3microchip.png|200px]]

= ==== Card Base =

The Card Base is a key component in making various expansion cards, such as [[Item/graphics card|Graphics Cards]], [[Item/network card|Network Cards]], [[Linked Card|Linked Cards]], etc.

The following recipe is used in crafting the Card Base:

* 1 x [[Item/materials#printed circuit board|Printed Circuit Board]]
* 3 x Iron nugget/oreberry
* 1 x Gold nugget/oreberry

[[File:cardbase.png|200px]]

= ==== Control Unit (CU) =

The Control Unit is crafted using the following recipe:

<pre> * 1 x Clock
* 1 x Redstone
* 3 x [[Item/materials#transistor|Transistor]]
* 4 x Gold nugget/oreberry
</pre>
[[File:controlunit.png|200px]]

= ==== Arithmetic Logic Unit =

The Arithmetic Logic Unit is crafted using the following recipe:

* 1 x [[Item/materials#microchips|Microchip (Tier 1)]]
* 1 x Redstone
* 3 x [[Item/materials#transistor|Transistor]]
* 4 x Iron nugget/oreberry

[[File:logicunit.png|200px]]

== Contents ==

{{:Item/contents}}

Item/contents

2026-09-15T22:00:45Z

SoraFirestorm: Text replacement - "Item/linked card" to "Linked Card"

{| class="oc-contents-table"
! colspan="2" | Items
|-
! Components
| [[Data Card]] - [[Debug Card|Debug Card]] - [[Item/graphics card|Graphics Card]] - [[Internet Card|Internet Card]] - [[Linked Card|Linked Card]] - [[Item/network card|Network Card]] - [[Item/redstone card|Redstone Card]] - [[Item/wireless network card|Wireless Network Card]]
|-
! Storage Devices
| [[Item/floppy disk|Floppy Disk]] - [[Item/EEPROM|EEPROM]] - [[Item/hard disk drive|Hard Disk Drive]] - [[Item/memory|Memory]]
|-
! Upgrades
| [[Item/angel upgrade|Angel Upgrade]] - [[Item/battery upgrade|Battery Upgrade]] - [[Chunkloader Upgrade]] - [[Database Upgrade]] - [[Experience Upgrade|Experience Upgrade]] - [[Generator Upgrade|Generator Upgrade]] - [[Item/hover upgrade|Hover Upgrade]] - [[Inventory Controller Upgrade|Inventory Controller Upgrade]] - [[Item/inventory upgrade|Inventory Upgrade]] - [[Leash Upgrade|Leash Upgrade]] - [[Navigation Upgrade|Navigation Upgrade]] - [[Piston Upgrade|Piston Upgrade]] - [[Sign I/O Upgrade|Sign I/O Upgrade]] - [[Item/solar generator upgrade|Solar Generator Upgrade]] - [[Tank Upgrade|Tank Upgrade]] - [[Item/tank controller upgrade|Tank Controller Upgrade]] - [[Tractor Beam Upgrade|Tractor Beam Upgrade]]
|-
! Containers
| [[Item/card container|Card Container]] - [[Item/upgrade container|Upgrade Container]] - [[Block/disk drive|Disk Drive]]
|-
! Others
| [[Item/analyzer|Analyzer]] - [[Item/texture picker|Texture Picker]] - [[Item/component bus|Component Bus]] - [[Item/CPU|CPU]] - [[Item/apu|APU]] - [[Item/dronecase|Drone Case]] - [[Item/manual|Manual]] - [[Item/microcontrollercase|Microcontroller Case]] - [[Item/nanomachines|Nanomachines]] - [[Item/terminal|Remote Terminal]] - [[Item/terminal server|Terminal Server]] - [[Item/server|Server]] - [[Item/tablet case|Tablet Case]] - [[Item/tablet|Tablet]] - [[Item/materials|Crafting Materials]] - [[Item/ink cartridge|Ink Cartridge]] - [[Item/scrench|Scrench]] - [[Item/hover boots|Hover Boots]] - [[Item/grog|Grog]] - [[Item/loot disks|Loot Disks]]
|}

Linked Card

2026-09-15T21:58:52Z

SoraFirestorm: SoraFirestorm moved page Item/linked card to Linked Card without leaving a redirect: Page has been unified

= Linked Card =

[[File:linked_card.png|128px]]

This card is crafted in pairs. The two resulting cards are "linked", and can communicate with each other over any distance, even across dimensions. They behave similar to network cards, but as it is only point-to-point, no ports can be configured, and the connection is always open. They also consume more energy per sent packet.

You can recraft any 2 linked card and pair them together, creating a new link channel. You can get the current channel of a linked card either via its component api <code>getChannel</code>, or from the item data <code>linkChannel</code> using an [[Inventory Controller Upgrade]].

The Linked Card is crafted using the following recipe:

* 2 x Eye of Ender
* 2 x [[Item/network card|Network Card]]
* 2 x [[Item/materials|Microchip (Tier 3)]]
* 1 x [[Item/materials|Interweb]]

[[File:linkedcard.png|200px]]

= Component API =
Component name: <code>tunnel</code>.

This card generates <code>modem_message</code> signals of the same format network cards do.

Callbacks:
{{APICallback|name=send|signature=(data...)|description=
Sends the specified data to the card this one is linked to.
}}
{{APICallback|name=maxPacketSize|signature=():number|description=
Gets the maximum packet size (config setting).
}}
{{APICallback|name=getChannel|signature=():string|description=
Gets the tunnel address of the link card. This is also available in linkChannel using an inventory controller and getting the stack from an inventory slot.
}}
{{APICallback|name=getWakeMessage|signature=():string|description=
Gets the current wake-up message. When the network card detects the wake message (a string in the first argument of a network packet), on any port and the machine is off, the machine is started. This is the same functionality also provided by robots, cases, servers, drones, and tablets.
}}
{{APICallback|name=setWakeMessage|signature=(message: string, [fuzzy: boolean]):string|description=
Sets the wake-up message to the specified <code>string</code>. The message matching can be fuzzy (default is <code>false</code>). A fuzzy match ignores additional trailing arguments in the network packet.
}}

= Contents =

{{:Item/contents}}

Linked Card

2026-09-15T21:58:11Z

SoraFirestorm: Unify item and component API pages

Item/contents

2026-09-15T21:46:59Z

SoraFirestorm: Remove link to World Sensor (old integration that is unlikely to return)

{| class="oc-contents-table"
! colspan="2" | Items
|-
! Components
| [[Data Card]] - [[Debug Card|Debug Card]] - [[Item/graphics card|Graphics Card]] - [[Internet Card|Internet Card]] - [[Item/linked card|Linked Card]] - [[Item/network card|Network Card]] - [[Item/redstone card|Redstone Card]] - [[Item/wireless network card|Wireless Network Card]]
|-
! Storage Devices
| [[Item/floppy disk|Floppy Disk]] - [[Item/EEPROM|EEPROM]] - [[Item/hard disk drive|Hard Disk Drive]] - [[Item/memory|Memory]]
|-
! Upgrades
| [[Item/angel upgrade|Angel Upgrade]] - [[Item/battery upgrade|Battery Upgrade]] - [[Chunkloader Upgrade]] - [[Database Upgrade]] - [[Experience Upgrade|Experience Upgrade]] - [[Generator Upgrade|Generator Upgrade]] - [[Item/hover upgrade|Hover Upgrade]] - [[Inventory Controller Upgrade|Inventory Controller Upgrade]] - [[Item/inventory upgrade|Inventory Upgrade]] - [[Leash Upgrade|Leash Upgrade]] - [[Navigation Upgrade|Navigation Upgrade]] - [[Piston Upgrade|Piston Upgrade]] - [[Sign I/O Upgrade|Sign I/O Upgrade]] - [[Item/solar generator upgrade|Solar Generator Upgrade]] - [[Tank Upgrade|Tank Upgrade]] - [[Item/tank controller upgrade|Tank Controller Upgrade]] - [[Tractor Beam Upgrade|Tractor Beam Upgrade]]
|-
! Containers
| [[Item/card container|Card Container]] - [[Item/upgrade container|Upgrade Container]] - [[Block/disk drive|Disk Drive]]
|-
! Others
| [[Item/analyzer|Analyzer]] - [[Item/texture picker|Texture Picker]] - [[Item/component bus|Component Bus]] - [[Item/CPU|CPU]] - [[Item/apu|APU]] - [[Item/dronecase|Drone Case]] - [[Item/manual|Manual]] - [[Item/microcontrollercase|Microcontroller Case]] - [[Item/nanomachines|Nanomachines]] - [[Item/terminal|Remote Terminal]] - [[Item/terminal server|Terminal Server]] - [[Item/server|Server]] - [[Item/tablet case|Tablet Case]] - [[Item/tablet|Tablet]] - [[Item/materials|Crafting Materials]] - [[Item/ink cartridge|Ink Cartridge]] - [[Item/scrench|Scrench]] - [[Item/hover boots|Hover Boots]] - [[Item/grog|Grog]] - [[Item/loot disks|Loot Disks]]
|}

Component/contents

2026-09-15T21:45:54Z

SoraFirestorm: Remove link to Abstract Bus and World Sensor (old integrations that are unlikely to return)

{| class="oc-contents-table"
! colspan="2" | [[Component|Components]]
|-
! Core Components
| [[Component/access point|Access Point]] - [[Component/computer|Computer]] - [[Component/drone|Drone]] - [[Component/drive|Drive]] - [[Component/EEPROM|EEPROM]] - [[Component/filesystem|Filesystem]] - [[Component/GPU|GPU]] - [[Component/microcontroller|Microcontroller]] - [[Component/modem|Modem]] - [[Component/redstone|Redstone]] - [[Component/robot|Robot]] - [[Component/transposer|Transposer]] - [[Component/tunnel|Tunnel]]
|-
! Others
| [[Component/component access|Component Access]] - [[Component/signals|Signals]]
|-
! Cross-Mod Integration
| [[Component/applied energistics|Applied Energistics]]
|}

Component/contents

2026-09-15T21:26:39Z

SoraFirestorm: Remove link to Tractor Beam Upgrade (page is now unified)

{| class="oc-contents-table"
! colspan="2" | [[Component|Components]]
|-
! Core Components
| [[Component/abstract bus|Abstract Bus]] - [[Component/access point|Access Point]] - [[Component/computer|Computer]] - [[Component/drone|Drone]] - [[Component/drive|Drive]] - [[Component/EEPROM|EEPROM]] - [[Component/filesystem|Filesystem]] - [[Component/GPU|GPU]] - [[Component/microcontroller|Microcontroller]] - [[Component/modem|Modem]] - [[Component/redstone|Redstone]] - [[Component/robot|Robot]] - [[Component/transposer|Transposer]] - [[Component/tunnel|Tunnel]] - [[Component/world sensor|World Sensor]]
|-
! Others
| [[Component/component access|Component Access]] - [[Component/signals|Signals]]
|-
! Cross-Mod Integration
| [[Component/applied energistics|Applied Energistics]]
|}

Item/contents

2026-09-15T21:25:54Z

SoraFirestorm: Text replacement - "Item/tractor beam upgrade" to "Tractor Beam Upgrade"

{| class="oc-contents-table"
! colspan="2" | Items
|-
! Components
| [[Data Card]] - [[Debug Card|Debug Card]] - [[Item/graphics card|Graphics Card]] - [[Internet Card|Internet Card]] - [[Item/linked card|Linked Card]] - [[Item/network card|Network Card]] - [[Item/redstone card|Redstone Card]] - [[Item/wireless network card|Wireless Network Card]]
|-
! Storage Devices
| [[Item/floppy disk|Floppy Disk]] - [[Item/EEPROM|EEPROM]] - [[Item/hard disk drive|Hard Disk Drive]] - [[Item/memory|Memory]]
|-
! Upgrades
| [[Item/angel upgrade|Angel Upgrade]] - [[Item/battery upgrade|Battery Upgrade]] - [[Chunkloader Upgrade]] - [[Database Upgrade]] - [[Experience Upgrade|Experience Upgrade]] - [[Generator Upgrade|Generator Upgrade]] - [[Item/hover upgrade|Hover Upgrade]] - [[Inventory Controller Upgrade|Inventory Controller Upgrade]] - [[Item/inventory upgrade|Inventory Upgrade]] - [[Leash Upgrade|Leash Upgrade]] - [[Navigation Upgrade|Navigation Upgrade]] - [[Piston Upgrade|Piston Upgrade]] - [[Sign I/O Upgrade|Sign I/O Upgrade]] - [[Item/solar generator upgrade|Solar Generator Upgrade]] - [[Tank Upgrade|Tank Upgrade]] - [[Item/tank controller upgrade|Tank Controller Upgrade]] - [[Tractor Beam Upgrade|Tractor Beam Upgrade]] - [[Item/world sensor upgrade|World Sensor Upgrade]]
|-
! Containers
| [[Item/card container|Card Container]] - [[Item/upgrade container|Upgrade Container]] - [[Block/disk drive|Disk Drive]]
|-
! Others
| [[Item/analyzer|Analyzer]] - [[Item/texture picker|Texture Picker]] - [[Item/component bus|Component Bus]] - [[Item/CPU|CPU]] - [[Item/apu|APU]] - [[Item/dronecase|Drone Case]] - [[Item/manual|Manual]] - [[Item/microcontrollercase|Microcontroller Case]] - [[Item/nanomachines|Nanomachines]] - [[Item/terminal|Remote Terminal]] - [[Item/terminal server|Terminal Server]] - [[Item/server|Server]] - [[Item/tablet case|Tablet Case]] - [[Item/tablet|Tablet]] - [[Item/materials|Crafting Materials]] - [[Item/ink cartridge|Ink Cartridge]] - [[Item/scrench|Scrench]] - [[Item/hover boots|Hover Boots]] - [[Item/grog|Grog]] - [[Item/loot disks|Loot Disks]]
|}

Tractor Beam Upgrade

2026-09-15T21:25:06Z

SoraFirestorm: SoraFirestorm moved page Item/tractor beam upgrade to Tractor Beam Upgrade without leaving a redirect: Page has been unified

= Overview =

[[File:tractor_beam.png|128px]]

Allows robots to pick up items in their vicinity, not just directly in front of/above/below them using the API.

The Tractor Beam Upgrade is crafted using the following recipe:

* 4 x Gold Ingot
* 2 x Iron Ingot
* 1 x Capacitor
* 1 x Piston
* 1 x [[Item/materials|Microchip (Tier 3)]]

[[File:tractorbeam.png|200px]]

= Component API =
Component name: <code>tractor_beam</code>. Callbacks:
{{APICallback|name=suck|signature=(): boolean|description=
Tries to pick up a random item in the robots' vicinity (a 9x9 area with the robot at its center).
}}

-----
{{:Item/contents}}

Tractor Beam Upgrade

2026-09-15T21:24:13Z

SoraFirestorm: Unify item and component API pages

Component/agent

2026-09-15T21:17:34Z

SoraFirestorm: Text replacement - "Item/tank upgrade" to "Tank Upgrade"

=== InventoryController Trait API ===

* <code>inventorySize():number</code>

<pre>Returns the size of the device's internal inventory.
</pre>
* <code>select([slot:number]):number</code>

<pre>Get the currently selected slot; set the selected slot if specified.
</pre>
* <code>count([slot:number]):number</code>

<pre>Get the number of items in the specified slot, otherwise in the selected slot.
</pre>
* <code>space([slot:number]):number</code>

<pre>Get the remaining space in the specified slot, otherwise in the selected slot.
</pre>
* <code>compareTo(otherSlot:number):boolean</code>

<pre>Compare the contents of the selected slot (in the robot inventory) to the contents of the specified slot (also in the robot inventory).
</pre>
* <code>transferTo(toSlot:number[, amount:number]):boolean</code>

<pre>Move the specified amount of items from the selected slot into the specified slot. If no amount is specified, the entire stack is moved to the target slot.
</pre>
=== WorldControl Trait API ===

* <code>detect(side:number):boolean</code>

<pre>Detects the block on the given side, relative to the robot, and returns whether or not the robot can move into the block, as well as a general description of the block. Returns true if the block will prevent the robot from moving forward, false otherwise. Drones return true even if the block is passable.
</pre>
'''side''' - See the [[API/sides|Sides API]] for a list of possible sides.

=== TankWorldControl Trait API ===

* <code>compareFluid(side:number):boolean</code>

<pre>Compares fluid in the selected tank (requires a [[Tank Upgrade|Tank upgrade]]) to fluid in the world or in an external tank on the specified side of the robot.
</pre>
* <code>drain(side:number[, count:number]):boolean</code>

<pre>Extracts the specified amount of fluid from the world or a tank on the specified side of the robot. If no amount is specified, the robot will try to drain 1000mB. If the tank is unable to store the specified amount of fluid, the operation will fail (no fluid is lost in the process).
</pre>
* <code>fill(side:number[, count:number]):boolean</code>

<pre>Fills the specified amount of fluid from the selected tank (requires a [[Tank Upgrade|Tank upgrade]]) into the world or a tank in front of the robot. If no amount is specified, the robot will try to fill the target tank with 1000mB of fluid. If there is not enough fluid to fill a block, or not enough space in the target tank, the operation will fail with no fluids lost.
</pre>
=== Agent Trait API ===

* <code>name():string</code>

<pre>Get the name of the robot.
</pre>
* <code>swing(side:number):boolean[, string]</code>

<pre>Lets the robot use the currently equipped item in the tool slot against the block or space directly in front of the robot. Returns true if successful (may take time depending on block being interacted with - e.g.. Obsidian takes time to mine). Returns false if the operation fails with a description of why it failed.
</pre>
* <code>use(side: number[, sneaky: boolean[, duration: number]]): boolean[, string]</code>

<pre>Attempts to use the item currently equipped in the tool slot in the same way as if the player would make a right-click.
</pre>
'''side''' - if given the robot will try to 'right-click' only on the surface as specified by side, otherwise the robot will try all possible sides. See the [[API/sides|Sides API]] for a list of possible sides. '''sneaky''' - if set to <code>true</code> the robot will simulate a sneak-right-click (like if the player would be using shift during a right-click). Some items (like buckets) will behave differently if this is set to true. '''duration''' - how long the item is used. This is useful when using charging items like a bow. '''Returns:''' true if the robot could interact with the block or entity in front of it, false otherwise. If successful the secondary parameter describes what the robot interacted with and will be one of 'block_activated', 'item_placed', 'item_interacted' or 'item_used'. This function has a very broad use as the robot can simulate right-clicks with most items. The only difference to players is that the robot cannot use items that specifically require the user to be an entity as the robot is a block. So drinking potions, eating food or throwing an ender pearl will fail. This functions secondary return value can be used to determine what the result of the right-click caused. Which of the item results is returned is not always obvious and requires some testing beforehand. Also note that while robots are not affected by harmful potions they can be destroyed by explosions, so be careful when you place, throw or activate any form of explosives with this function. Possible values for the second return value:

= <code>block_activated</code> - a block was activated (like levers, switches or doors). =
= <code>item_interacted</code> - the equipped tool interacted with the world, for example sheers when used on a sheep. =
= <code>item_placed</code> - something was placed into the world. This is not only caused by placeable blocks, but as well by items that cause blocks or entities to appear in the world (like flint and stone or mob eggs). =
= <code>item_used</code> - the equipped was activated, like a splash-potion. =
= <code>air</code> - the equipped item requires a target but there was none. Note that if your robot has an Angel upgrade, this will never be returned, however some actions might still cause no effect. =

* <code>place(side: number[, sneaky: boolean]): boolean[, string]</code>

<pre>Tries to place the block in the currently selected inventory slot on the specified side of the robot (if the side is supported). If **sneaky** is set to true, the robot will simulate a sneak-placement (shift-click). Returns true if successfully placed. Returns false if the operation fails. If an unsupported value is provided as a parameter, the operation will fail with a description of why it failed.
</pre>
* <code>getLightColor():number</code>

<pre>Get the current color of the activity(robot) or flap(drone) light as an integer encoded RGB value (0xRRGGBB).
</pre>
* <code>setLightColor(value:number):number</code>

<pre>Set the color of the activity(robot) or flap(drone) light to the specified integer encoded RGB value (0xRRGGBB).
</pre>
=== TankControl Trait API ===

* <code>tankCount():number</code>

<pre>Returns the number of tanks installed in the robot.
</pre>
* <code>selectTank(tank:number)</code>

<pre>Selects the specified tank (if robot contains more than one [[Tank Upgrade|Tank upgrade]]). Any tank operations will use this tank.
</pre>
* <code>tankLevel([tank:number]):number</code>

<pre>Returns the fluid level in the specified tank. If no tank specified, returns the fluid level in the selected tank (using selectTank()).
</pre>
* <code>tankSpace([tank:number]):number</code>

<pre>Returns the remaining fluid capacity (empty space) in the specified tank. If not tank specified, returns the remaining capacity in the selected tank.
</pre>
* <code>compareFluidTo(tank:number):boolean</code>

<pre>Tests whether the fluid in the selected tank (in the robot inventory) is the same as in the specified tank (requires [[Tank Upgrade|Tank upgrade]]).
</pre>
* <code>transferFluidTo(tank:number[, count:number]):boolean</code>

<pre>Transfer the specified amount of fluid in the selected tank into the specified tank. If no volume is specified, the robot will attempt to transfer 1000mB.
</pre>
=== InventoryWorldController trait API ===

* <code>compare(side:number[, fuzzy:boolean=false]):boolean</code>

<pre>Compares the block on the specified side of the robot with the item in the currently selected slot and returns whether they are the same or not. Blocks are considered identical if the type and metadata match; additional ItemStack information is not checked. Empty blocks are considered as air blocks, which cannot be compared to an empty inventory slot; the detect() function can be used to determine if there is a block in front of the robot. For blocks that drop a different item, the compare() method won't work (eg: Diamond block dropping diamond items); for these cases, use silk-touch to obtain a block for comparison.
</pre>
* <code>drop(side:number[, count:number]):boolean</code>

<pre>Drops the specified number of items from the currently selected slot. Returns true if at least one item is dropped, false otherwise. If the block in front of the robot is an inventory, the robot will try to place the item into the inventory. If the inventory doesn't accept the item, the item is not dropped into the world (the operation will fail and return false). Robots themselves are considered blocks with an inventory, and items can be moved into them using the drop() function. The drop() function will not work on non-item inventories, such as fluid tanks (the use() function works for these cases).
</pre>
* <code>suck(side:number[, count:number]):boolean</code>

<pre>Tries to pick up the specified number of items and place it in the selected slot. If the selected slot is occupied, items will be placed in the first available slot. Returns the number of items sucked else false.
</pre>
=== Robot Component API ===

* <code>durability():number</code>

<pre>Get the durability of the currently equipped tool.
</pre>
* <code>move(direction:number):boolean</code>

<pre>Move in the specified direction. Valid movement sides are: front, back, top, bottom (see [[API/sides|Sides]]).
</pre>
* <code>turn(clockwise:boolean):boolean</code>

<pre>Rotate in the specified direction.
</pre>
=== Drone Component API ===

* <code>getStatusText():string</code>

<pre>Get the status text currently being displayed in the GUI.
</pre>
* <code>setStatusText(value:string):string</code>

<pre>Set the status text to display in the GUI, returns new value.
</pre>
* <code>move(dx:number, dy:number, dz:number)</code>

<pre>Change the target position by the specified offset.
</pre>
* <code>getOffset():number</code>

<pre>Get the current distance to the target position.
</pre>
* <code>getVelocity():number</code>

<pre>Get the current velocity in m/s.
</pre>
* <code>getMaxVelocity():number</code>

<pre>Get the maximum velocity, in m/s.
</pre>
* <code>getAcceleration():number</code>

<pre>Get the currently set acceleration.
</pre>
* <code>setAcceleration(value:number):number</code>

<pre>Try to set the acceleration to the specified value and return the new acceleration.
</pre>

Item/tank controller upgrade

2026-09-15T21:17:34Z

SoraFirestorm: Text replacement - "Item/tank upgrade" to "Tank Upgrade"

= Tank Controller Upgrade =

[[File:upgradetankcontroller.png|128px]]

'''Provides:''' [[Component/tank controller|Tank Controller]] API.

This upgrade allows filling or draining fluid container items within the robot's inventory, as well as inspecting fluid stacks. A [[Tank Upgrade|Tank Upgrade]] is recommended for this upgrade to be of proper use, as it operates on the selected internal tanks when draining or filling fluid container items.

The Tank Controller Upgrade is crafted using the following recipe:

* 4 x Gold Ingot
* 1 x Glass Bottle
* 1 x Dispenser
* 1 x Piston
* 1 x [[Item/materials|Microchip (Tier 2)]]
* 1 x [[Item/materials|Printed Circuit Board]]

[[File:tankcontroller.png|200px]]

== Contents ==

{{:Item/contents}}

Item/contents

2026-09-15T21:17:31Z

SoraFirestorm: Text replacement - "Item/tank upgrade" to "Tank Upgrade"

{| class="oc-contents-table"
! colspan="2" | Items
|-
! Components
| [[Data Card]] - [[Debug Card|Debug Card]] - [[Item/graphics card|Graphics Card]] - [[Internet Card|Internet Card]] - [[Item/linked card|Linked Card]] - [[Item/network card|Network Card]] - [[Item/redstone card|Redstone Card]] - [[Item/wireless network card|Wireless Network Card]]
|-
! Storage Devices
| [[Item/floppy disk|Floppy Disk]] - [[Item/EEPROM|EEPROM]] - [[Item/hard disk drive|Hard Disk Drive]] - [[Item/memory|Memory]]
|-
! Upgrades
| [[Item/angel upgrade|Angel Upgrade]] - [[Item/battery upgrade|Battery Upgrade]] - [[Chunkloader Upgrade]] - [[Database Upgrade]] - [[Experience Upgrade|Experience Upgrade]] - [[Generator Upgrade|Generator Upgrade]] - [[Item/hover upgrade|Hover Upgrade]] - [[Inventory Controller Upgrade|Inventory Controller Upgrade]] - [[Item/inventory upgrade|Inventory Upgrade]] - [[Leash Upgrade|Leash Upgrade]] - [[Navigation Upgrade|Navigation Upgrade]] - [[Piston Upgrade|Piston Upgrade]] - [[Sign I/O Upgrade|Sign I/O Upgrade]] - [[Item/solar generator upgrade|Solar Generator Upgrade]] - [[Tank Upgrade|Tank Upgrade]] - [[Item/tank controller upgrade|Tank Controller Upgrade]] - [[Item/tractor beam upgrade|Tractor Beam Upgrade]] - [[Item/world sensor upgrade|World Sensor Upgrade]]
|-
! Containers
| [[Item/card container|Card Container]] - [[Item/upgrade container|Upgrade Container]] - [[Block/disk drive|Disk Drive]]
|-
! Others
| [[Item/analyzer|Analyzer]] - [[Item/texture picker|Texture Picker]] - [[Item/component bus|Component Bus]] - [[Item/CPU|CPU]] - [[Item/apu|APU]] - [[Item/dronecase|Drone Case]] - [[Item/manual|Manual]] - [[Item/microcontrollercase|Microcontroller Case]] - [[Item/nanomachines|Nanomachines]] - [[Item/terminal|Remote Terminal]] - [[Item/terminal server|Terminal Server]] - [[Item/server|Server]] - [[Item/tablet case|Tablet Case]] - [[Item/tablet|Tablet]] - [[Item/materials|Crafting Materials]] - [[Item/ink cartridge|Ink Cartridge]] - [[Item/scrench|Scrench]] - [[Item/hover boots|Hover Boots]] - [[Item/grog|Grog]] - [[Item/loot disks|Loot Disks]]
|}

Tank Upgrade

2026-09-15T21:16:31Z

SoraFirestorm: SoraFirestorm moved page Item/tank upgrade to Tank Upgrade without leaving a redirect: Page has been unified

= Tank Upgrade =

[[File:upgradetank.png|128px]]

This upgrade provides an internal fluid tank to the robot, one per upgrade. Each tank can only store a single type of liquid at a time. When there are multiple tanks installed, one of the tanks can be selected (similar to slots in the robots inventory), and will then be used for a large number of operations.

For example, fluids are piped into / out of the selected tank when the robot is accessed externally (by pipes, such as the fluid pipes provided by BuildCraft, or Fluiducts in Thermal Expansion).

There are a number of methods provided in the [[API/robot|Robot API]] that allow manipulating the fluid tanks in a similar fashion to the robot's inventory. Fluids can be sucked from or filled into tanks or the world, and can be transferred inbetween tanks, and compared against each other.

Fluids stored in a tank upgrade are kept there when the upgrade is removed. Tank upgrades therefore act as persistent fluid storage. They do not yet act as generic fluid container items, meaning they cannot be filled/drained directly by other mods. This will be added in OC 1.4.

The Tank Upgrade is crafted using the following recipe:

* 4 x Wood Plank
* 1 x Cauldron
* 1 x Iron bars
* 1 x Dispensor
* 1 x Piston
* 1 x [[Item/materials|Microchip (Tier 1)]]

[[File:tank.png|200px]]

= Component API =

'''Component name:''' <code>tank_controller</code>
Callbacks:
{{APICallback|name=getTankCapacity|signature=(side:number):number or nil[, string]|description=
Get the capacity of the tank on the specified side of the robot. Back refers to the robot's own selected tank.
}}
{{APICallback|name=getTankLevel|signature=(side:number):number or nil[,string]|description=
Gets amount of fluid in tank on specified side.
}}
{{APICallback|name=getFluidInTank|signature=(side:number):table|description=
Get a description of the fluid in the the tank on the specified side of the robot. **Note:** sides.back deprecated, use getFluidInInternalTank()
}}
{{APICallback|name=getFluidInInternalTank|signature=(slot):table|description=
Get a description of fluid in the specified or selected slot of robot inventory.
}}
{{APICallback|name=drain|signature=([amount:number]):boolean|description=
Transfers fluid from a tank in the selected inventory slot to the selected tank. If the amount of fluid that would be generated from the item is too large to fit into the tank (for example buckets will usually generate 1000) nothing will happen, that is no fluid is lost.
}}
{{APICallback|name=fill|signature=([amount:number]):boolean|description=
Transfers fluid from the selected tank to a tank in the selected inventory slot. If the specified amount is too low (for example for buckets the minimum amount will usually be 1000) nothing will happen, that is no fluid is lost.
}}
{{APICallback|name=getTankCapacityInSlot|signature=(slot:number):number|description=
Gets capacity of tank in specified or selected slot of the robot inventory.
}}
{{APICallback|name=getTankLevelInSlot|signature=(slot:number):number|description=
Gets amount of fluid tank item in specified or selected slot of the robot inventory.
}}
{{APICallback|name=getFluidInTankInSlot|signature=(slot:number):table|description=
Gets description of fluid in tank item in the specified or selected slot of the robot inventory.
}}

= Contents =

{{:Item/contents}}

Component/contents

2026-09-15T21:15:57Z

SoraFirestorm: Remove link to Tank Upgrade (page is now unified)

{| class="oc-contents-table"
! colspan="2" | [[Component|Components]]
|-
! Core Components
| [[Component/abstract bus|Abstract Bus]] - [[Component/access point|Access Point]] - [[Component/computer|Computer]] - [[Component/drone|Drone]] - [[Component/drive|Drive]] - [[Component/EEPROM|EEPROM]] - [[Component/filesystem|Filesystem]] - [[Component/GPU|GPU]] - [[Component/microcontroller|Microcontroller]] - [[Component/modem|Modem]] - [[Component/redstone|Redstone]] - [[Component/robot|Robot]] - [[Component/tractor beam|Tractor Beam]] - [[Component/transposer|Transposer]] - [[Component/tunnel|Tunnel]] - [[Component/world sensor|World Sensor]]
|-
! Others
| [[Component/component access|Component Access]] - [[Component/signals|Signals]]
|-
! Cross-Mod Integration
| [[Component/applied energistics|Applied Energistics]]
|}

Tank Upgrade

2026-09-15T21:13:34Z

SoraFirestorm: Unify item and component API pages

Component/contents

2026-09-15T21:03:06Z

SoraFirestorm: Remove link to Sign I/O Upgrade (page is now unified)

{| class="oc-contents-table"
! colspan="2" | [[Component|Components]]
|-
! Core Components
| [[Component/abstract bus|Abstract Bus]] - [[Component/access point|Access Point]] - [[Component/computer|Computer]] - [[Component/drone|Drone]] - [[Component/drive|Drive]] - [[Component/EEPROM|EEPROM]] - [[Component/filesystem|Filesystem]] - [[Component/GPU|GPU]] - [[Component/microcontroller|Microcontroller]] - [[Component/modem|Modem]] - [[Component/redstone|Redstone]] - [[Component/robot|Robot]] - [[Component/tank controller|Tank Controller]] - [[Component/tractor beam|Tractor Beam]] - [[Component/transposer|Transposer]] - [[Component/tunnel|Tunnel]] - [[Component/world sensor|World Sensor]]
|-
! Others
| [[Component/component access|Component Access]] - [[Component/signals|Signals]]
|-
! Cross-Mod Integration
| [[Component/applied energistics|Applied Energistics]]
|}

Item/tablet

2026-09-15T21:02:26Z

SoraFirestorm: Text replacement - "Item/sign upgrade" to "Sign I/O Upgrade"

= Tablet =

[[File:tablet.png|128px|tablet.png]]

Tablets are built by placing a [[Item/tablet case|Tablet Case]] into an [[Block/assembler|Assembler]], configuring as desired and assembling it. Tablets act as portable computers that cannot directly interact with the world - for example [[Item/redstone card|Redstone Cards]] do ''not'' work in them. A number of upgrades, however, do, such as the [[Sign I/O Upgrade|Sign Upgrade]] or the [[Piston Upgrade|Piston Upgrade]].

You can sneak-click with a tablet in your hand to access the disk drive slot, and the power button to toggle the power off/on.

Tablets can be put into a [[Block/charger|Charger]] to refill their energy and to access the first hard disk built into the tablet from a computer connected to the charger - in this setup, the charger will act similar to a disk drive, with the tablet being the floppy disk. This can be very useful in case you forgot to install an OS on the hard drive built into the tablet, or after bricking a tablet's OS.

== Contents ==

{{:Item/contents}}

Item/contents

2026-09-15T21:02:26Z

SoraFirestorm: Text replacement - "Item/sign upgrade" to "Sign I/O Upgrade"

{| class="oc-contents-table"
! colspan="2" | Items
|-
! Components
| [[Data Card]] - [[Debug Card|Debug Card]] - [[Item/graphics card|Graphics Card]] - [[Internet Card|Internet Card]] - [[Item/linked card|Linked Card]] - [[Item/network card|Network Card]] - [[Item/redstone card|Redstone Card]] - [[Item/wireless network card|Wireless Network Card]]
|-
! Storage Devices
| [[Item/floppy disk|Floppy Disk]] - [[Item/EEPROM|EEPROM]] - [[Item/hard disk drive|Hard Disk Drive]] - [[Item/memory|Memory]]
|-
! Upgrades
| [[Item/angel upgrade|Angel Upgrade]] - [[Item/battery upgrade|Battery Upgrade]] - [[Chunkloader Upgrade]] - [[Database Upgrade]] - [[Experience Upgrade|Experience Upgrade]] - [[Generator Upgrade|Generator Upgrade]] - [[Item/hover upgrade|Hover Upgrade]] - [[Inventory Controller Upgrade|Inventory Controller Upgrade]] - [[Item/inventory upgrade|Inventory Upgrade]] - [[Leash Upgrade|Leash Upgrade]] - [[Navigation Upgrade|Navigation Upgrade]] - [[Piston Upgrade|Piston Upgrade]] - [[Sign I/O Upgrade|Sign I/O Upgrade]] - [[Item/solar generator upgrade|Solar Generator Upgrade]] - [[Item/tank upgrade|Tank Upgrade]] - [[Item/tank controller upgrade|Tank Controller Upgrade]] - [[Item/tractor beam upgrade|Tractor Beam Upgrade]] - [[Item/world sensor upgrade|World Sensor Upgrade]]
|-
! Containers
| [[Item/card container|Card Container]] - [[Item/upgrade container|Upgrade Container]] - [[Block/disk drive|Disk Drive]]
|-
! Others
| [[Item/analyzer|Analyzer]] - [[Item/texture picker|Texture Picker]] - [[Item/component bus|Component Bus]] - [[Item/CPU|CPU]] - [[Item/apu|APU]] - [[Item/dronecase|Drone Case]] - [[Item/manual|Manual]] - [[Item/microcontrollercase|Microcontroller Case]] - [[Item/nanomachines|Nanomachines]] - [[Item/terminal|Remote Terminal]] - [[Item/terminal server|Terminal Server]] - [[Item/server|Server]] - [[Item/tablet case|Tablet Case]] - [[Item/tablet|Tablet]] - [[Item/materials|Crafting Materials]] - [[Item/ink cartridge|Ink Cartridge]] - [[Item/scrench|Scrench]] - [[Item/hover boots|Hover Boots]] - [[Item/grog|Grog]] - [[Item/loot disks|Loot Disks]]
|}

Sign I/O Upgrade

2026-09-15T21:01:14Z

SoraFirestorm: SoraFirestorm moved page Item/sign upgrade to Sign I/O Upgrade without leaving a redirect: Page has been unified

= Sign I/O Upgrade =

[[File:sign_upgrade.png|128px]]

Allows the robot to read and write signs in the world.

The Sign I/O Upgrade is crafted using the following recipe:

* 4 x Iron Ingot
* 1 x Stick
* 1 x Ink Sac
* 2 x [[Item/materials|Microchip (Tier 1)]]
* 1 x Sticky Piston

[[File:signio.png|200px]]

= Component API =
Component name: <code>sign</code>. Callbacks:
{{APICallback|name=getValue|signature=(): string or nil, string|description=
Gets the text currently displayed on the sign in front of the robot, or nil and an error message if there is no sign in front of the robot.
}}
{{APICallback|name=setValue|signature=(value: string): string or nil, string|description=
Sets the text of the sign in front of the robot. Returns the new text on the sign (which may be a truncated version of the passed argument) or nil and an error message if there is no sign in front of the robot.
}}

= Contents =

{{:Item/contents}}

Sign I/O Upgrade

2026-09-15T21:00:49Z

SoraFirestorm: Unify item and component API pages

Component/contents

2026-09-15T20:55:11Z

SoraFirestorm: Remove link to Piston Upgrade (page is now unified)

{| class="oc-contents-table"
! colspan="2" | [[Component|Components]]
|-
! Core Components
| [[Component/abstract bus|Abstract Bus]] - [[Component/access point|Access Point]] - [[Component/computer|Computer]] - [[Component/drone|Drone]] - [[Component/drive|Drive]] - [[Component/EEPROM|EEPROM]] - [[Component/filesystem|Filesystem]] - [[Component/GPU|GPU]] - [[Component/microcontroller|Microcontroller]] - [[Component/modem|Modem]] - [[Component/redstone|Redstone]] - [[Component/robot|Robot]] - [[Component/sign|Sign]] - [[Component/tank controller|Tank Controller]] - [[Component/tractor beam|Tractor Beam]] - [[Component/transposer|Transposer]] - [[Component/tunnel|Tunnel]] - [[Component/world sensor|World Sensor]]
|-
! Others
| [[Component/component access|Component Access]] - [[Component/signals|Signals]]
|-
! Cross-Mod Integration
| [[Component/applied energistics|Applied Energistics]]
|}

Item/tablet

2026-09-15T20:52:45Z

SoraFirestorm: Text replacement - "Item/piston upgrade" to "Piston Upgrade"

= Tablet =

[[File:tablet.png|128px|tablet.png]]

Tablets are built by placing a [[Item/tablet case|Tablet Case]] into an [[Block/assembler|Assembler]], configuring as desired and assembling it. Tablets act as portable computers that cannot directly interact with the world - for example [[Item/redstone card|Redstone Cards]] do ''not'' work in them. A number of upgrades, however, do, such as the [[Item/sign upgrade|Sign Upgrade]] or the [[Piston Upgrade|Piston Upgrade]].

You can sneak-click with a tablet in your hand to access the disk drive slot, and the power button to toggle the power off/on.

Tablets can be put into a [[Block/charger|Charger]] to refill their energy and to access the first hard disk built into the tablet from a computer connected to the charger - in this setup, the charger will act similar to a disk drive, with the tablet being the floppy disk. This can be very useful in case you forgot to install an OS on the hard drive built into the tablet, or after bricking a tablet's OS.

== Contents ==

{{:Item/contents}}

Item/contents

2026-09-15T20:52:45Z

SoraFirestorm: Text replacement - "Item/piston upgrade" to "Piston Upgrade"

{| class="oc-contents-table"
! colspan="2" | Items
|-
! Components
| [[Data Card]] - [[Debug Card|Debug Card]] - [[Item/graphics card|Graphics Card]] - [[Internet Card|Internet Card]] - [[Item/linked card|Linked Card]] - [[Item/network card|Network Card]] - [[Item/redstone card|Redstone Card]] - [[Item/wireless network card|Wireless Network Card]]
|-
! Storage Devices
| [[Item/floppy disk|Floppy Disk]] - [[Item/EEPROM|EEPROM]] - [[Item/hard disk drive|Hard Disk Drive]] - [[Item/memory|Memory]]
|-
! Upgrades
| [[Item/angel upgrade|Angel Upgrade]] - [[Item/battery upgrade|Battery Upgrade]] - [[Chunkloader Upgrade]] - [[Database Upgrade]] - [[Experience Upgrade|Experience Upgrade]] - [[Generator Upgrade|Generator Upgrade]] - [[Item/hover upgrade|Hover Upgrade]] - [[Inventory Controller Upgrade|Inventory Controller Upgrade]] - [[Item/inventory upgrade|Inventory Upgrade]] - [[Leash Upgrade|Leash Upgrade]] - [[Navigation Upgrade|Navigation Upgrade]] - [[Piston Upgrade|Piston Upgrade]] - [[Item/sign upgrade|Sign I/O Upgrade]] - [[Item/solar generator upgrade|Solar Generator Upgrade]] - [[Item/tank upgrade|Tank Upgrade]] - [[Item/tank controller upgrade|Tank Controller Upgrade]] - [[Item/tractor beam upgrade|Tractor Beam Upgrade]] - [[Item/world sensor upgrade|World Sensor Upgrade]]
|-
! Containers
| [[Item/card container|Card Container]] - [[Item/upgrade container|Upgrade Container]] - [[Block/disk drive|Disk Drive]]
|-
! Others
| [[Item/analyzer|Analyzer]] - [[Item/texture picker|Texture Picker]] - [[Item/component bus|Component Bus]] - [[Item/CPU|CPU]] - [[Item/apu|APU]] - [[Item/dronecase|Drone Case]] - [[Item/manual|Manual]] - [[Item/microcontrollercase|Microcontroller Case]] - [[Item/nanomachines|Nanomachines]] - [[Item/terminal|Remote Terminal]] - [[Item/terminal server|Terminal Server]] - [[Item/server|Server]] - [[Item/tablet case|Tablet Case]] - [[Item/tablet|Tablet]] - [[Item/materials|Crafting Materials]] - [[Item/ink cartridge|Ink Cartridge]] - [[Item/scrench|Scrench]] - [[Item/hover boots|Hover Boots]] - [[Item/grog|Grog]] - [[Item/loot disks|Loot Disks]]
|}

Block/microcontroller

2026-09-15T20:52:44Z

SoraFirestorm: Text replacement - "Item/piston upgrade" to "Piston Upgrade"

= Microcontroller =

Microcontrollers are more restrictive versions of Computers. The key limitation is that they do not contain a slot for a [[Item/hard disk drive|Hard disk drive]], and rely solely on a programmed [[Item/EEPROM|EEPROM]] for specific functionality. They can '''not''' interact with external components!

Microcontrollers can be built by placing a [[Item/microcontrollercase|Microcontroller case]] in an [[Block/assembler|Assembler]]. Higher tier [[Item/microcontrollercase|Microcontroller cases]] can take more components and upgrades (as well as higher tier components and upgrades). Microcontrollers take a limited subset of upgrades, and do not contain Upgrade or Card container slots. [[Item/graphics card|Graphics cards]] cannot be placed into the expansion slots either.

MCUs do not automatically forward network messages. They do not distribute power. Network messages arriving on all sides will always be forwarded to the MCU. Which sides are used for sending can be controlled via the <code>microcontroller</code> component. A computer can access its external component if it is directly adjacent to the microcontroller.

The following code snippet illustrates one particular usage of Microcontrollers. The program detects redstone signals (requires a [[Item/redstone card|redstone card]]), and uses a [[Piston Upgrade|piston upgrade]] to push a block. <syntaxhighlight lang="lua">
local r,p = component.proxy(component.list("redstone")()), component.proxy(component.list("piston")())

while true do

computer.pullSignal(0.5)
if r.getInput(2) > 0 then
p.push()
end

end
</syntaxhighlight>

== Contents ==

{{:Block/contents}}

Piston Upgrade

2026-09-15T20:51:59Z

SoraFirestorm: SoraFirestorm moved page Item/piston upgrade to Piston Upgrade without leaving a redirect: Page has been unified

= Piston Upgrade =

[[File:upgradepiston.png|128px|upgradepiston.png]]

The piston upgrade can be used to push blocks in the world, in a pretty much identical manner to the way vanilla pistons push blocks.

The Piston Upgrade is crafted using the following recipe:

* 4 x Iron Ingot
* 2 x Stick
* 1 x Piston
* 1 x [[Item/materials|Printed Circuit Board]]
* 1 x [[Item/materials|Microchip (Tier 1)]]

[[File:piston.png|200px]]

= Component API =
Component name: <code>piston</code>. Callbacks:
{{APICallback|name=push|signature=(side:number):boolean|description=
Tries to push the block in front of the container of the upgrade.
}}

= Contents =

{{:Item/contents}}

Piston Upgrade

2026-09-15T20:51:39Z

SoraFirestorm: Unify item and component API pages

Linked Card

2026-09-15T20:46:29Z

SoraFirestorm: Fix link to Inventory Controller Upgrade

= Linked Card =

[[File:linked_card.png|128px]]

This card provides the [[Component/tunnel|tunnel]] component.

This card is crafted in pairs. The two resulting cards are "linked", and can communicate with each other over any distance, even across dimensions. They behave similar to network cards, except that no port has to be opened. They also consume more energy per sent packet.

You can recraft any 2 linked card and pair them together, creating a new link channel. You can get the current channel of a linked card either via its component api <code>getChannel</code>, or from the item data <code>linkChannel</code> using an [[Inventory Controller Upgrade]].

The Linked Card is crafted using the following recipe:

* 2 x Eye of Ender
* 2 x [[Item/network card|Network Card]]
* 2 x [[Item/materials|Microchip (Tier 3)]]
* 1 x [[Item/materials|Interweb]]

[[File:linkedcard.png|200px]]

== Contents ==

{{:Item/contents}}

Block/transposer

2026-09-15T20:45:19Z

SoraFirestorm: Fix link to Inventory Controller Upgrade

= Transposer =

[[File:trasnposer.png|128px]]

The transposer bridges the gap between redstone controlled hoppers and [[Block/robot|Robot]], allowing [[Block/computer case|computer]]-controlled transferal of items and fluids between adjacent blocks.

''Note that this block has no internal inventory.''

Besides moving things around, it can also be used to inspect the contents of the adjacent inventories, like an [[Block/adapter|Adapter]] with an [[Inventory Controller Upgrade]] could, and the contents of adjacent tanks, like and adapter with a [[Component/tank controller|Tank Controller]] could.

The transposer can also interactive with player inventory when player stands next to or on it.

The component proxy on a computer provides an api as described [[Component/transposer|here]]

Block/waypoint

2026-09-15T20:42:54Z

SoraFirestorm: Fix link to nav upgrade component

= Waypoint =

The waypoint block provides additional functionality for [[Block/robot|robots]] and [[Item/drone|drones]] with a [[Navigation Upgrade|navigation upgrade]]. The position of the waypoint reported is the block directly in front of the waypoint, as indicated by the particle effects. This allows the waypoint block to be placed above a chest, for instance, to be able to determine the position of the block directly above the chest.

Waypoints can be labeled and provided with a redstone signal. This allows for finer control when writing sorting programs, for instance.

The waypoint block can be located using the <code>findWaypoints()</code> function in the [[Navigation Upgrade#Component API|navigation]] component. This allows the [[Block/robot|robots]] or [[Item/drone|drone]] to find all waypoints within a certain range; the function returns the label of the waypoint, the position of the waypoint in relative coordinates, as well as the redstone level of the waypoint.

The Waypoint is crafted using the following recipe:

* 1 x [[Item/materials|Interweb]]
* 1 x [[Item/materials|Printed Circuit Board]]
* 2 x [[Item/materials|Transistor]]
* 4 x Iron ingot

[[File:waypoint.png|200px|waypoint.png]]

== Contents ==

{{:Block/contents}}

Component/contents

2026-09-15T20:39:55Z

SoraFirestorm: Remove link to Navigation Upgrade (page is now unified)

{| class="oc-contents-table"
! colspan="2" | [[Component|Components]]
|-
! Core Components
| [[Component/abstract bus|Abstract Bus]] - [[Component/access point|Access Point]] - [[Component/computer|Computer]] - [[Component/drone|Drone]] - [[Component/drive|Drive]] - [[Component/EEPROM|EEPROM]] - [[Component/filesystem|Filesystem]] - [[Component/GPU|GPU]] - [[Component/microcontroller|Microcontroller]] - [[Component/modem|Modem]] - [[Component/piston|Piston]] - [[Component/redstone|Redstone]] - [[Component/robot|Robot]] - [[Component/sign|Sign]] - [[Component/tank controller|Tank Controller]] - [[Component/tractor beam|Tractor Beam]] - [[Component/transposer|Transposer]] - [[Component/tunnel|Tunnel]] - [[Component/world sensor|World Sensor]]
|-
! Others
| [[Component/component access|Component Access]] - [[Component/signals|Signals]]
|-
! Cross-Mod Integration
| [[Component/applied energistics|Applied Energistics]]
|}

Item/contents

2026-09-15T20:39:23Z

SoraFirestorm: Text replacement - "Item/navigation upgrade" to "Navigation Upgrade"

{| class="oc-contents-table"
! colspan="2" | Items
|-
! Components
| [[Data Card]] - [[Debug Card|Debug Card]] - [[Item/graphics card|Graphics Card]] - [[Internet Card|Internet Card]] - [[Item/linked card|Linked Card]] - [[Item/network card|Network Card]] - [[Item/redstone card|Redstone Card]] - [[Item/wireless network card|Wireless Network Card]]
|-
! Storage Devices
| [[Item/floppy disk|Floppy Disk]] - [[Item/EEPROM|EEPROM]] - [[Item/hard disk drive|Hard Disk Drive]] - [[Item/memory|Memory]]
|-
! Upgrades
| [[Item/angel upgrade|Angel Upgrade]] - [[Item/battery upgrade|Battery Upgrade]] - [[Chunkloader Upgrade]] - [[Database Upgrade]] - [[Experience Upgrade|Experience Upgrade]] - [[Generator Upgrade|Generator Upgrade]] - [[Item/hover upgrade|Hover Upgrade]] - [[Inventory Controller Upgrade|Inventory Controller Upgrade]] - [[Item/inventory upgrade|Inventory Upgrade]] - [[Leash Upgrade|Leash Upgrade]] - [[Navigation Upgrade|Navigation Upgrade]] - [[Item/piston upgrade|Piston Upgrade]] - [[Item/sign upgrade|Sign I/O Upgrade]] - [[Item/solar generator upgrade|Solar Generator Upgrade]] - [[Item/tank upgrade|Tank Upgrade]] - [[Item/tank controller upgrade|Tank Controller Upgrade]] - [[Item/tractor beam upgrade|Tractor Beam Upgrade]] - [[Item/world sensor upgrade|World Sensor Upgrade]]
|-
! Containers
| [[Item/card container|Card Container]] - [[Item/upgrade container|Upgrade Container]] - [[Block/disk drive|Disk Drive]]
|-
! Others
| [[Item/analyzer|Analyzer]] - [[Item/texture picker|Texture Picker]] - [[Item/component bus|Component Bus]] - [[Item/CPU|CPU]] - [[Item/apu|APU]] - [[Item/dronecase|Drone Case]] - [[Item/manual|Manual]] - [[Item/microcontrollercase|Microcontroller Case]] - [[Item/nanomachines|Nanomachines]] - [[Item/terminal|Remote Terminal]] - [[Item/terminal server|Terminal Server]] - [[Item/server|Server]] - [[Item/tablet case|Tablet Case]] - [[Item/tablet|Tablet]] - [[Item/materials|Crafting Materials]] - [[Item/ink cartridge|Ink Cartridge]] - [[Item/scrench|Scrench]] - [[Item/hover boots|Hover Boots]] - [[Item/grog|Grog]] - [[Item/loot disks|Loot Disks]]
|}

Block/waypoint

2026-09-15T20:39:22Z

SoraFirestorm: Text replacement - "Item/navigation upgrade" to "Navigation Upgrade"

= Waypoint =

The waypoint block provides additional functionality for [[Block/robot|robots]] and [[Item/drone|drones]] with a [[Navigation Upgrade|navigation upgrade]]. The position of the waypoint reported is the block directly in front of the waypoint, as indicated by the particle effects. This allows the waypoint block to be placed above a chest, for instance, to be able to determine the position of the block directly above the chest.

Waypoints can be labeled and provided with a redstone signal. This allows for finer control when writing sorting programs, for instance.

The waypoint block can be located using the <code>findWaypoints()</code> function in the [[Component/navigation|navigation]] component. This allows the [[Block/robot|robots]] or [[Item/drone|drone]] to find all waypoints within a certain range; the function returns the label of the waypoint, the position of the waypoint in relative coordinates, as well as the redstone level of the waypoint.

The Waypoint is crafted using the following recipe:

* 1 x [[Item/materials|Interweb]]
* 1 x [[Item/materials|Printed Circuit Board]]
* 2 x [[Item/materials|Transistor]]
* 4 x Iron ingot

[[File:waypoint.png|200px|waypoint.png]]

== Contents ==

{{:Block/contents}}

Navigation Upgrade

2026-09-15T20:38:48Z

SoraFirestorm: SoraFirestorm moved page Item/navigation upgrade to Navigation Upgrade without leaving a redirect: Page has been unified

= Navigation Upgrade =

[[File:navigation_upgrade.png|128px]]

Allows the robot to tell its current position and facing. The position is relative to the center of the map that was used to craft the upgrade. The range in which the upgrade works depends on the size of the map that was used to craft the upgrade. The upgrade can be crafted together with another map to re-configure it and get the old map back.

The Navigation upgrade is crafted using the following recipe:

* 4 x Gold Ingot
* 1 x Compass
* 2 x [[Item/materials|Microchip (Tier 2)]]
* 1 x Map
* 1 x Potion / Filled Water Bottle

[[File:navigation.png|200px]]

= Component API =
Component name: <code>navigation</code>. Callbacks:
{{APICallback|name=getPosition|signature=(): number, number, number or nil, string|description=
Gets the current relative position of the robot. This is the position relative to the center of the map item that was used to craft the upgrade. Note that the upgrade can be re-crafted with another map to change it's point of reference. Returns nil and the string out of range if the robot is too far away from the point of reference (i.e. when it is out of bounds of the map that was used to craft the upgrade).
}}
{{APICallback|name=getFacing|signature=(): number|description=
Gets the current facing of the robot, as one of the sides constants.
}}
{{APICallback|name=getRange|signature=(): number|description=
Gets the effective range of the upgrade. If the absolute value of the relative X or Z coordinate becomes larger than this, <code>getPosition()</code> will fail.
}}
{{APICallback|name=findWaypoints|signature=(range: number): table|description=
Finds all [[Block/waypoint|waypoint blocks]] within the specified range.

This returns a table that contains other tables. The top table has only numbered indices corresponding to each detected beacon. In each of this entries is another table, each row various aspects of the specified beacon: "position", "redstone", "label".

* position returns a table with numbered indices in which 1 is x, 2 is y, and 3 is z. These numbers are the distance from the navigation component to the beacon in terms of block coordinates.
* redstone returns a single number that is the current strength of the redstone signal
* label returns a string that is the label of the beacon you can set by right clicking on it.

Below is an example of how the tables are set up. A single beacon's results are shown.
}}

{| class="wikitable"
! table: main
!
!
!
!
|-
| rowspan="5" | table: 1
| rowspan="3" | table: position
| 1:
| number: x distance
|
|-
| 2:
| number: y distance
|
|-
| 3:
| number: z distance
|
|-
| redstone
|
| number: redstone strength
|
|-
| label
|
| string: beacon label
|
|}

= Contents =

{{:Item/contents}}

Navigation Upgrade

2026-09-15T20:38:15Z

SoraFirestorm: Unify item and component API pages

Leash Upgrade

2026-09-15T20:31:04Z

SoraFirestorm: Remove reference to dead component page

= Leash Upgrade =

[[File:upgradeleash.png|128px]]

This upgrade allows certain devices (such as drones) to put animals on a leash. When leashed the device can pull the animals around, and even pull them up in the air. The leash will persist until it is manually released.

The Leash Upgrade is crafted using the following recipe:

* 4 x Leash
* 4 x Iron Ingot
* 1 x [[Item/materials|Control Unit]]

[[File:leash.png|200px]]

= Component API =
Component name: <code>leash</code>. Callbacks:
{{APICallback|name=leash|signature=(side:number):boolean|description=
Tries to put an entity on the specified side of the device onto a leash.
}}
{{APICallback|name=unleash|signature=()|description=
Unleashes all currently leashed entities.
}}

= Contents =

{{:Item/contents}}

Component/contents

2026-09-15T20:30:30Z

SoraFirestorm: Remove link to Leash Upgrade (page is now unified)

{| class="oc-contents-table"
! colspan="2" | [[Component|Components]]
|-
! Core Components
| [[Component/abstract bus|Abstract Bus]] - [[Component/access point|Access Point]] - [[Component/computer|Computer]] - [[Component/drone|Drone]] - [[Component/drive|Drive]] - [[Component/EEPROM|EEPROM]] - [[Component/filesystem|Filesystem]] - [[Component/GPU|GPU]] - [[Component/microcontroller|Microcontroller]] - [[Component/modem|Modem]] - [[Component/navigation|Navigation]] - [[Component/piston|Piston]] - [[Component/redstone|Redstone]] - [[Component/robot|Robot]] - [[Component/sign|Sign]] - [[Component/tank controller|Tank Controller]] - [[Component/tractor beam|Tractor Beam]] - [[Component/transposer|Transposer]] - [[Component/tunnel|Tunnel]] - [[Component/world sensor|World Sensor]]
|-
! Others
| [[Component/component access|Component Access]] - [[Component/signals|Signals]]
|-
! Cross-Mod Integration
| [[Component/applied energistics|Applied Energistics]]
|}

Item/dronecase

2026-09-15T20:29:08Z

SoraFirestorm: Text replacement - "Item/leash upgrade" to "Leash Upgrade"

= Drone Case =

[[File:dronecase0.png|128px]] [[File:dronecase1.png|128px]]

This item is used in an [[Block/assembler|Assembler]] to build [[Item/drone|Drones]], which are kind of to robots what microcontrollers are to computers. They are more limited, specialized versions. In this case they also have some additional functionality, though: they move differently (because they are entities) and have other options for interacting with the world, too, such as via using the [[Leash Upgrade|Leash Upgrade]].

The Drone Case (Tier 1) is crafted using the following recipe:

* 4 x End Stone
* 1 x [[Item/microcontrollercase|Microcontroller Case (Tier 1)]]
* 1 x Compass
* 2 x [[Item/materials|Microchip (Tier 1)]]
* 1 x [[Item/component bus|Component Bus (Tier 2)]]

[[File:t1dronecase.png|200px|t1dronecase.png]]

The Drone Case (Tier 2) is crafted using the following recipe:

* 4 x End Stone
* 1 x [[Item/microcontrollercase|Microcontroller Case (Tier 2)]]
* 1 x Compass
* 2 x [[Item/materials|Microchip (Tier 2)]]
* 1 x [[Item/component bus|Component Bus (Tier 3)]]

[[File:t2dronecase.png|200px|t2dronecase.png]]

== Contents ==

{{:Item/contents}}

Item/contents

2026-09-15T20:29:06Z

SoraFirestorm: Text replacement - "Item/leash upgrade" to "Leash Upgrade"

{| class="oc-contents-table"
! colspan="2" | Items
|-
! Components
| [[Data Card]] - [[Debug Card|Debug Card]] - [[Item/graphics card|Graphics Card]] - [[Internet Card|Internet Card]] - [[Item/linked card|Linked Card]] - [[Item/network card|Network Card]] - [[Item/redstone card|Redstone Card]] - [[Item/wireless network card|Wireless Network Card]]
|-
! Storage Devices
| [[Item/floppy disk|Floppy Disk]] - [[Item/EEPROM|EEPROM]] - [[Item/hard disk drive|Hard Disk Drive]] - [[Item/memory|Memory]]
|-
! Upgrades
| [[Item/angel upgrade|Angel Upgrade]] - [[Item/battery upgrade|Battery Upgrade]] - [[Chunkloader Upgrade]] - [[Database Upgrade]] - [[Experience Upgrade|Experience Upgrade]] - [[Generator Upgrade|Generator Upgrade]] - [[Item/hover upgrade|Hover Upgrade]] - [[Inventory Controller Upgrade|Inventory Controller Upgrade]] - [[Item/inventory upgrade|Inventory Upgrade]] - [[Leash Upgrade|Leash Upgrade]] - [[Item/navigation upgrade|Navigation Upgrade]] - [[Item/piston upgrade|Piston Upgrade]] - [[Item/sign upgrade|Sign I/O Upgrade]] - [[Item/solar generator upgrade|Solar Generator Upgrade]] - [[Item/tank upgrade|Tank Upgrade]] - [[Item/tank controller upgrade|Tank Controller Upgrade]] - [[Item/tractor beam upgrade|Tractor Beam Upgrade]] - [[Item/world sensor upgrade|World Sensor Upgrade]]
|-
! Containers
| [[Item/card container|Card Container]] - [[Item/upgrade container|Upgrade Container]] - [[Block/disk drive|Disk Drive]]
|-
! Others
| [[Item/analyzer|Analyzer]] - [[Item/texture picker|Texture Picker]] - [[Item/component bus|Component Bus]] - [[Item/CPU|CPU]] - [[Item/apu|APU]] - [[Item/dronecase|Drone Case]] - [[Item/manual|Manual]] - [[Item/microcontrollercase|Microcontroller Case]] - [[Item/nanomachines|Nanomachines]] - [[Item/terminal|Remote Terminal]] - [[Item/terminal server|Terminal Server]] - [[Item/server|Server]] - [[Item/tablet case|Tablet Case]] - [[Item/tablet|Tablet]] - [[Item/materials|Crafting Materials]] - [[Item/ink cartridge|Ink Cartridge]] - [[Item/scrench|Scrench]] - [[Item/hover boots|Hover Boots]] - [[Item/grog|Grog]] - [[Item/loot disks|Loot Disks]]
|}

Leash Upgrade

2026-09-15T20:28:12Z

SoraFirestorm: SoraFirestorm moved page Item/leash upgrade to Leash Upgrade without leaving a redirect: Page has been unified

= Leash Upgrade =

[[File:upgradeleash.png|128px]]

'''Provides:''' [[Component/leash|Leash]] component.

This upgrade allows certain devices (such as drones) to put animals on a leash. When leashed the device can pull the animals around, and even pull them up in the air. The leash will persist until it is manually released.

The Leash Upgrade is crafted using the following recipe:

* 4 x Leash
* 4 x Iron Ingot
* 1 x [[Item/materials|Control Unit]]

[[File:leash.png|200px]]

= Component API =
Component name: <code>leash</code>. Callbacks:
{{APICallback|name=leash|signature=(side:number):boolean|description=
Tries to put an entity on the specified side of the device onto a leash.
}}
{{APICallback|name=unleash|signature=()|description=
Unleashes all currently leashed entities.
}}

= Contents =

{{:Item/contents}}

Leash Upgrade

2026-09-15T20:27:53Z

SoraFirestorm: Unify item and component API pages

Component/component access

2026-09-10T22:11:47Z

SoraFirestorm: Reflow

= Component Access =

This page describes how to get access to a [[Component|component's API]] from Lua. To recap: components are blocks or items that provide some API to Lua programs running on computers connected to said component.

== Addresses ==

Components all have an address. This address is a UUID, a unique identifier. In most cases it is OK to abbreviate these addresses. For example to get the full address from an abbreviated one you can use <code>component.get</code>. To get the address of any block in particular, you can use the [[Item/analyzer|Analyzer]] by holding the control key while right clicking the block.

To get a list of all components attached to your computer you can do this:
<syntaxhighlight lang="lua">
Lua 5.2.3 Copyright (C) 1994-2013 Lua.org, PUC-Rio
lua> local component = require("component")
lua> for k,v in component.list() do print(k, v) end
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx keyboard
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx screen
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx gpu
...
</syntaxhighlight>

Note that item components will usually keep their address even when removed from a computer. So when removing a hard drive and inserting it back in, it will have the same address as before. This is ''not'' the case for block components, they will always get a new address after being broken and placed again.

Optionally you can filter components list like this:

This code will add every component which name contains "adar" such as computronics radar or warpDrive radar to the local radars table <syntaxhighlight lang="lua">
local component = require("component")
local radars = {}

for address, name in component.list("adar", false) do
table.insert(radars, component.proxy(address))
end
</syntaxhighlight>

This code will add all connected warpDrive radars only to the local radars table
<syntaxhighlight lang="lua">
local component = require("component")
local radars = {}

for address, name in component.list("warpdriveRadar", true) do
table.insert(radars, component.proxy(address))
end
</syntaxhighlight>

== Primary Components ==

The [[API/component|component API]] keeps track of one component of each type as a "primary" component. If there are multiple components of the same type, which one will be the primary component is random. You can access the primary component of a specific type via <code>component.xxx</code>, where <code>xxx</code> is the type. For example:
<syntaxhighlight lang="lua">
lua> =component.gpu.address
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
</syntaxhighlight>

Alternatively you can use <code>component.getPrimary("xxx")</code>. Just keep in mind that this will throw an error if there is no primary component for the specified type, so you may wish to check that with <code>component.isAvailable("xxx")</code> first. Having it throw an error is usually clearer than getting a nil dereference later on.

This system is in mainly place to allow the OS to pick the screen to initially output to.

== Proxies ==

So now that we know how to get the address of components, let's see how we can interact with them. There are two ways to go about this. One is to call <code>component.invoke(address, method, ...)</code>. For example:
<syntaxhighlight lang="lua">
local component = require("component")
component.invoke(modemAddress, "broadcast", port, data)
</syntaxhighlight>

The preferred way will usually be to get a proxy, however. A proxy is simply a table that provides one function for each API callback, named after that callback. In addition, each proxy has two fields: <code>address</code>, which holds the address of the wrapped component, and <code>type</code>, which holds the type of the component. You can get a proxy like this:
<syntaxhighlight lang="lua">
local component = require("component")
local proxy = component.proxy(address)

-- The call above using the proxy:
proxy.broadcast(port, data)

-- The common proxy fields:
print(proxy.address) -- address passed to component.proxy above
print(proxy.type) -- "modem"
</syntaxhighlight>

Note that each primary component you access via <code>component.getPrimary</code> or <code>component.xxx</code> is in fact a proxy.

== Direct Calls ==

Some component callbacks can be performed as "direct calls". Direct calls are performed in the computer's worker thread, meaning they will return instantly. Normal calls are delegated to the main server thread, to avoid race conditions and other threading issues, which also means that normal calls will take up to one tick (i.e. 50 ms). Just to be clear: this only applies to component APIs.

== Signals ==

An important part of interacting with components are [[Component/signals|Signals]]. These can be queued by components to notify computers of external changes and events. For example, user input is forwarded to computers via signals. Computers can also queue their own signals, which can be useful for code-reuse, or just notifying other parts of your code asynchronously.

== Contents ==

{{:Component/contents}}

Component/contents

2026-09-10T22:07:58Z

SoraFirestorm: Remove link to Inventory Controller Upgrade (page is now unified)

{| class="oc-contents-table"
! colspan="2" | [[Component|Components]]
|-
! Core Components
| [[Component/abstract bus|Abstract Bus]] - [[Component/access point|Access Point]] - [[Component/computer|Computer]] - [[Component/drone|Drone]] - [[Component/drive|Drive]] - [[Component/EEPROM|EEPROM]] - [[Component/filesystem|Filesystem]] - [[Component/GPU|GPU]] - [[Component/leash|Leash]] - [[Component/microcontroller|Microcontroller]] - [[Component/modem|Modem]] - [[Component/navigation|Navigation]] - [[Component/piston|Piston]] - [[Component/redstone|Redstone]] - [[Component/robot|Robot]] - [[Component/sign|Sign]] - [[Component/tank controller|Tank Controller]] - [[Component/tractor beam|Tractor Beam]] - [[Component/transposer|Transposer]] - [[Component/tunnel|Tunnel]] - [[Component/world sensor|World Sensor]]
|-
! Others
| [[Component/component access|Component Access]] - [[Component/signals|Signals]]
|-
! Cross-Mod Integration
| [[Component/applied energistics|Applied Energistics]]
|}

API/robot

2026-09-10T22:07:22Z

SoraFirestorm: Fix links to Inventory Controller Upgrade

= Robot API =

This API wraps the functionality of the '''component''' [[Component/robot|robot]] to allow more intuitive interaction with the robot.

This is the api you are using when in your lua code you call

<source lang="lua">local robot_api = require("robot")
robot_api.forward()
</source>
As opposed to using the robot component api directly, via the component interface

<source lang="lua">local component = require("component")
local robot_component_api = component.robot -- if using openos, else component.proxy(component.list("robot")())
robot_component_api.move(sides.front)
</source>
While the component robot has more generic functions like <code>move([side: number])</code> or <code>drop([side: number])</code>, this API has more intuitive and failsafe functions like <code>turnRight</code>, <code>dropDown</code>, <code>forward</code>. Which one you use is up to you, you can even use both at the same time.

Note that a Robot is also computer like any other with just an additional robot component included, so the normal [[API|APIs]] are available as usual.

See [[Block/robot|Robot Block]] for additional information on the actual Robot.

=== Slot alignment ===

{{:Component/inventory slots}}

=== Movement ===

Robots are capable of complex movements, but some you may want to understand some nuances.

= ==== Hovering =

Robots have a flight-height limitation. The general movement rules for robots go like this:

* 1. Robots may only move if the start or target position is valid (e.g. to allow building bridges). - 2. The position below a robot is always valid (can always move down). - 3. Positions up to <code>flightHeight</code> above a solid block are valid (limited flight capabilities, default is 8). - 4. Any position that has an adjacent block with a solid face towards the position is valid (robots can "climb"). Here's an image visualizing that (minus the second rule, because that'd just clutter it).

[[File:robot_flight.png|robot_flight.png]]

Violating these rules will result in a the error <code>impossible move</code> to be returned

You can install hover upgrades to increase (tier 1) and pretty much circumvent (tier 2) this limitation. Or you can disable this in the config, by setting <code>limitFlightHeight</code> to 256 or so.

[https://github.com/MightyPirates/OpenComputers/issues/1113#issuecomment-97731965 source]

=== API Exclusive Methods ===

* <code>robot.name(): string</code> Returns the robot's name. The name of a Robot is set initially during it's creation and cannot be changed programmatically. However you can change it using an anvil if you want. - <code>robot.detect(): boolean, string</code> Detects what is directly in front of the robot and returns if the robot could move through it as well as a generic description. '''Returns:''' <code>true</code> if the robot if whatever is in front of the robot would prevent him from moving forward (a block or an entity) (Note: Drones return <code>true</code> even if the block is <code>passable</code>), <code>false</code> otherwise. The second parameter describes what is in front in general and is one of either <code>entity</code>, <code>solid</code>, <code>replaceable</code>, <code>liquid</code>, <code>passable</code> or <code>air</code>. - <code>robot.detectUp(): boolean, string</code> As <code>robot.detect()</code> except that it scans the block directly above the robot. - <code>robot.detectDown(): boolean, string</code> As <code>robot.detect()</code> except that it scans the block directly below the robot. - <code>robot.select([slot: number]): number</code> Selects the given inventory slot (if specified) and returns the current inventory slot. '''slot''' - the slot to select. If this parameter is omitted, no slot is selected. '''Returns''' the currently selected slot. Either the one specified (if successfully selected) or the one that was previously selected. - <code>robot.inventorySize(): number</code> '''Returns''' the amount of select-able internal robot inventory slots. To get the number of inventory upgrade use: x = robot.inventorySize() / 16. - <code>robot.count([slot: number]): number</code> Returns the amount of items currently in the specified or selected slot. '''slot''' - specifies the slot to count the items in. If omitted the currently selected slot is counted instead. '''Returns''' the amount of items in the slot specified or the currently selected slot if no slot was given. - <code>robot.space([slot: number]): number</code> Returns the amount of items that can still be added to the specified slot until it is filled up. '''slot''' - specifies the slot to count the items in. If omitted the currently selected slot is counted instead. '''Returns''' the amount of items that can still be added to the the slot specified or the currently selected slot until it is considered full. This function helps to determine how many items of a type can be added to a specific slot. While for example cobblestone can pile up to 64 items per slot, empty buckets can only stack up to 16 and other blocks like doors can only take 1 item per slot. - <code>robot.transferTo(slot: number[, count: number]): boolean</code> Moves all or up to ''count'' items from the currently selected slot to the specified slot. '''slot''' - specifies the slot move the items from the currently selected slot to. '''count''' - if specified only up to this many items are moved, otherwise the entire stack is moved. '''Returns''' <code>true</code> if exchanging the content between those slots was successful, <code>false</code> otherwise. If there are items in the target slot then this function attempts to swap the items in those slots. This only succeeds if you move all items away from the current slot or if the current slot was empty anyways. Note that this will always return true if the specified slot is the same as the currently selected slot, or if both slots are empty, even though no items are effectively moved. - <code>robot.compareTo(slot: number): boolean</code> Compares the item of the currently selected slot to the item of the slot specified and returns whether they are equal or not. '''slot''' - specifies the slot to compare the current slot to. '''Returns''' <code>true</code> if the item type in the specified slot and the currently selected slot are equal, <code>false</code> otherwise. Two items are considered the 'same' if their item type and metadata are the same. Stack size or any additional mod-specific item informations (like for example the content of two floppy disks) are not checked. - <code>robot.compare(): boolean</code> Compares the block in front of the robot with the item in the currently selected slot and returns whether they are the same or not. Blocks are considered the 'same' if their type and metadata are the same. Stack size or any additional informations (like for example the inventory of a container) are not checked. Note that empty space in front of the robot is considered an 'air block' by the game, which cannot be put into an inventory slot and therefore compared by normal means. An empty slot and an air block are '''not''' the same. You can use <code>robot.detect()</code> beforehand to determine if there is actually a block in front of the robot. Also keep in mind that blocks that drop items need to be compared to the actual same block that is in the world. For example stone blocks drop as cobblestone and diamond ores drop diamond items, which are not the same for this function. Use silk-touch items to retrieve the actual block in the world for comparison. - <code>robot.compareUp(): boolean</code> As <code>robot.compare</code> just for the block directly above the robot. - <code>robot.compareDown(): boolean</code> As <code>robot.compare</code> just for the block directly below the robot. - <code>robot.drop([count: number]): boolean</code> Tries to drop items from the currently selected inventory slot in '''front''' of the robot. Note that if you are trying to drop items into an inventory below you, this is the wrong method. Use <code>dropDown</code> for that case. This method, <code>drop</code>, will drop the items to the '''front'''. '''count''' - specifies how many items to drop. If omitted or if count exceeds the amount of items in the currently selected slot, then all items in the currently selected slot are dropped. '''Returns''' <code>true</code> if at least one item was dropped, <code>false</code> otherwise. If the block or entity (like chests or mine-carts with a chest) immediately in front of the robot has an accessible item inventory, the robot will try to put those items into this inventory instead of throwing them into the world. If the block in front has an inventory but the item could not be moved into it for any reason, then this function returns false and does not move any items. Where the item will be put on depends on the inventory and the side the robot is facing. Furnaces for example receive items to smelt from the top side. Also note that robots are considered "blocks with an inventory" as well and therefore items can be moved into robot slots as with any other inventory as well. This function cannot interact with non-item inventories (like for example fluid tanks) and will not consider them an inventory and therefore items will be thrown into the world instead. You need to use the <code>robot.use</code> function to interact with those types of blocks. Note that this will always return false, if the currently selected slot contains no items at all. - <code>robot.dropUp(): boolean</code> As <code>robot.drop</code> just for the block directly above the robot. - <code>robot.dropDown(): boolean</code> As <code>robot.drop</code> just for the block directly below the robot. - <code>robot.suck([count: number]): boolean</code> Tries to pick up items from directly in front of the robot and puts it into the selected slot or (if occupied) first possible slot. '''count''' - limits the amount of items to pick up by this many. If omitted a maximum of one stack is taken. '''Returns''' <code>true</code> if at least one item was picked up, false otherwise. This is basically the inverse of <code>robot.drop</code> and will interact with item inventories in the same way. However this will only take the first item available in that inventory. For more precise inventory management you need to install an [[Inventory Controller Upgrade|inventory controller upgrade]] into the robot. If there are multiple items in front of the robot, this will pick them up based on the distance to the robot. This will skip items that cannot be picked up for whatever reason and try other items first before returning <code>false</code>. If the currently selected slot contains a different item than the one the robot tries to pick up, the robot will attempt to place the item in the next possible slots ''after'' the selected one that are either free or contain identical items with less than the maximum stack size for those items. This will distribute the items to pick up over several slots if necessary. If no slot after the selected one is able to contain the items the robot tries to put up, this function will fail, even if there are slots ''before'' the currently selected slot that could hold those items. - <code>robot.suckUp([count: number]): boolean</code> As <code>robot.suck</code> except that it tries to pick up items from directly above the robot. - <code>robot.suckDown([count: number]): boolean</code> As <code>robot.suck</code> except that it tries to pick up items from directly below the robot. - <code>robot.place([side: number[, sneaky: boolean]]): boolean[, string]</code> Tries to place the block in the currently selected inventory slot in front of the robot. '''side''' - if specified this determines the surface on which the robot attempts to place the block for example to place torches to a specific side. If omitted the robot will try all possible sides. See the [[API/sides|Sides API]] for a list of possible sides. '''sneaky''' - if set to <code>true</code> the robot will simulate a sneak-placement (like if the player would be using shift during placement), which is usually not necessary and only included for compatibility to other mods. '''Returns:''' <code>true</code> if an item could be placed, <code>false</code> otherwise. If placement failed, the secondary return parameter will describe why the placement failed. A robot can only place blocks to the side of another solid block, they cannot place blocks "into the air" without an [[Item/angel upgrade|Angel upgrade]]. This can be changed in the config file. Note that trying to place an empty inventory slot will always fail. - <code>robot.placeUp([side: number[, sneaky: boolean]]): boolean[, string]</code> As <code>robot.place</code> except that the robot tries to place the item into the space directly above it. - <code>robot.placeDown([side: number[, sneaky: boolean]]): boolean[, string]</code> As <code>robot.place</code> except that the robot tries to place the item into the space directly below it. - <code>robot.durability(): number, number, number or nil, string</code> Returns the durability of the item currently in the tool slot, followed by its current durability, followed by its maximum durability. If no item is equipped or the item has no durability this returns <code>nil</code> and an error message describing why no durability could be returned. The error message is one of <code>no tool equipped</code> or <code>tool cannot be damaged</code>. - <code>robot.swing([side: number, [sneaky:boolean]]): boolean[, string]</code> Makes the robot use the item currently in the tool slot against the block or space immediately in front of the robot in the same way as if a player would make a left-click. '''side''' - if given the robot will try to 'left-click' only on the surface as specified by side, otherwise the robot will try all possible sides. See the [[API/sides|Sides API]] for a list of possible sides. '''Returns:''' true if the robot could interact with the block or entity in front of it, false otherwise. If successful the secondary parameter describes what the robot interacted with and will be one of 'entity', 'block' or 'fire'. This can be used to mine blocks or fight entities in the same way as if the player did a left-click. Note that tools and weapons do lose durability in the same way as if a player would use them and need to be replaced eventually. Items mined or dropped of mobs will be put into the inventory if possible, otherwise they will be dropped to the ground. Note that even though the action is performed immediately (like a block being destroyed) this function will wait for a while appropriate to the action performed to simulate the time it would take a player to do the same action. This is most noticeable if you try to mine obsidian blocks: they are destroyed and put into the inventory immediately, but the function will wait for a few seconds. If this is used to mine blocks, then the tool equipped needs to be sufficient to actually mine the block in front. If for example a wooden pick-axe is used on an obsidian block this will return false. Everything (including an empty slot) can be used to fight mobs, but the damage will be based on the item used. Equally everything can be used to extinguish fire, and items with durability will not lose any if done so. - <code>robot.swingUp([side: number, [sneaky:boolean]]): boolean[, string]</code> As <code>robot.swing</code> except that the block or entity directly above the robot will be the target. - <code>robot.swingDown([side: number, [sneaky:boolean]]): boolean[, string]</code> As <code>robot.swing</code> except that the block or entity directly below the robot will be the target. - <code>robot.use([side: number[, sneaky: boolean[, duration: number]]]): boolean[, string]</code> Attempts to use the item currently equipped in the tool slot in the same way as if the player would make a right-click. '''side''' - if given the robot will try to 'right-click' only on the surface as specified by side, otherwise the robot will try all possible sides. See the [[API/sides|Sides API]] for a list of possible sides. '''sneaky''' - if set to <code>true</code> the robot will simulate a sneak-right-click (like if the player would be using shift during a right-click). Some items (like buckets) will behave differently if this is set to true. '''duration''' - how long the item is used. This is useful when using charging items like a bow. '''Returns:''' true if the robot could interact with the block or entity in front of it, false otherwise. If successful the secondary parameter describes what the robot interacted with and will be one of 'block_activated', 'item_placed', 'item_interacted' or 'item_used'. This function has a very broad use as the robot can simulate right-clicks with most items. The only difference to players is that the robot cannot use items that specifically require the user to be an entity as the robot is a block. So drinking potions, eating food or throwing an ender pearl will fail. This functions secondary return value can be used to determine what the result of the right-click caused. Which of the item results is returned is not always obvious and requires some testing beforehand. Also note that while robots are not affected by harmful potions they can be destroyed by explosions, so be careful when you place, throw or activate any form of explosives with this function. Possible values for the second return value:

= <code>block_activated</code> - a block was activated (like levers, switches or doors). =
= <code>item_interacted</code> - the equipped tool interacted with the world, for example sheers when used on a sheep. =
= <code>item_placed</code> - something was placed into the world. This is not only caused by placeable blocks, but as well by items that cause blocks or entities to appear in the world (like flint and stone or mob eggs). =
= <code>item_used</code> - the equipped was activated, like a splash-potion. =
= <code>air</code> - the equipped item requires a target but there was none. Note that if your robot has an Angel upgrade, this will never be returned, however some actions might still cause no effect. =

* <code>robot.useUp([side: number[, sneaky: boolean[, duration: number]]]): boolean[, string]</code> As <code>robot.use</code> except that the item is used aiming at the area above the robot. - <code>robot.useDown([side: number[, sneaky: boolean[, duration: number]]]): boolean[, string]</code> As <code>robot.use</code> except that the item is used aiming at the area below the robot. - <code>robot.forward(): boolean[, string]</code> Tries to move the robot forward. '''Returns:''' <code>true</code> if the robot successfully moved, <code>nil</code> otherwise. If movement fails a secondary result will be returned describing why it failed, which will either be 'impossible move', 'not enough energy' or the description of the obstacle as <code>robot.detect</code> would return. The result 'not enough energy' is rarely returned as being low on energy usually causes the robot to shut down beforehand. The result 'impossible move' is kind of a fall-back result and will be returned for example if the robot tries to move into an area of the world that is currently not loaded. - <code>robot.back(): boolean[, string]</code> As <code>robot.forward()</code> except that the robot tries to move backward. - <code>robot.up(): boolean[, string]</code> As <code>robot.forward()</code> except that the robot tries to move upwards. - <code>robot.down(): boolean[, string]</code> As <code>robot.forward()</code> except that the robot tries to move downwards. - <code>robot.turnLeft()</code> Turns the robot 90° to the left. Note that this can only fail if the robot has not enough energy to perform the turn but has not yet shut down because of it. - <code>robot.turnRight()</code> As <code>robot.turnLeft</code> except that the robot turns 90° to the right. - <code>robot.turnAround()</code> This is the same as calling <code>robot.turnRight</code> twice. - <s><code>robot.level(): number</code></s> '''Deprecated since OC 1.3''' use <code>component.experience.level()</code> instead (only available if the [[Experience Upgrade|experience upgrade]] is installed). Returns the current level of the robot, with the fractional part being the percentual progress towards the next level. For example, if this returns <code>1.5</code>, then the robot is level one, and 50% towards achieving level two. - <code>robot.tankCount():number</code>

<pre>The number of tanks installed in the robot.
</pre>
* <code>robot.selectTank(tank)</code>

<pre>Select the specified tank. This determines which tank most operations operate on.
</pre>
* <code>robot.tankLevel([tank:number]):number</code>

<pre>The the current fluid level in the specified tank, or, if none is specified, the selected tank.
</pre>
* <code>robot.tankSpace():number</code>

<pre>The the remaining fluid capacity in the specified tank, or, if none is specified, the selected tank.
</pre>
* <code>robot.compareFluidTo(tank:number):boolean</code>

<pre>Tests whether the fluid in the selected tank is the same as in the specified tank.
</pre>
* <code>robot.transferFluidTo(tank:number[, count:number]):boolean</code>

<pre>Transfers the specified amount of fluid from the selected tank into the specified tank. If no volume is specified, tries to transfer 1000 mB.
</pre>
* <code>robot.compareFluid():boolean</code>

<pre>Tests whether the fluid in the selected tank is the same as in the world or the tank in front of the robot.
</pre>
* <code>robot.compareFluidUp():boolean</code>

<pre>Like compareFluid, but operates on the block above the robot.
</pre>
* <code>robot.compareFluidDown():boolean</code>

<pre>Like compareFluid, but operates on the block below the robot.
</pre>
* <code>robot.drain([count:number]):boolean</code>

<pre>Extracts the specified amount of fluid from the world or the tank in front of the robot. When no amount is specified, will try to drain 1000 mB. When the drained fluid is in the world and it cannot be fully stored in the selected tank, the operation fails, i.e. no fluid is lost.
</pre>
* <code>robot.drainUp([count:number]):boolean</code>

<pre>Like drain, but operates on the block above the robot.
</pre>
* <code>robot.drainDown([count:number]):boolean</code>

<pre>Like drain, but operates on the block below the robot.
</pre>
* <code>robot.fill([count:number]):boolean</code>

<pre>Injects the specified amount of fluid from the selected tank into the the world or the tank in front of the robot. When no amount is specified, will try to eject 1000 mB. When there is not enough fluid to fill a block, or the target tank does not have enough room, the operation fails, i.e. no fluid is lost.
</pre>
* <code>robot.fillUp([count:number]):boolean</code>

<pre>Like fill, but operates on the block above the robot.
</pre>
* <code>robot.fillDown([count:number]):boolean</code>

<pre>Like fill, but operates on the block below the robot.
</pre>
== Contents ==

{{:API/contents}}

Crafting Upgrade

2026-09-10T22:07:21Z

SoraFirestorm: Fix links to Inventory Controller Upgrade

= Crafting Upgrade =

[[File:crafting_upgrade.png|128px]]

When activated the robot considers the top-left area the crafting area and will attempt to craft any layed-out crafting recipe in that area. The requirements for a successful crafting attempt are exactly the same as if you would attempt to craft the item in a crafting table.

[[File:crafting_area.png|Crafting area]]
''(free slots are the crafting area)''

It is recommended (but not required) to use this upgrade in combination with an [[Inventory Controller Upgrade|Inventory Controller Upgrade]]. It allows to read the names and types of items and therefore makes it a lot easier to find the required crafting resources.

The Crafting upgrade is crafted using the following recipe:

* 1 x Crafting Table
* 4 x Iron Ingot
* 2 x [[Item/materials|Microchip (Tier 1)]]
* 1 x [[Item/materials|Printed Circuit Board]]

[[File:craftupgrade.png|200px]]

= Component API =
Component name: <code>crafting</code>
{{APICallback|name=craft|signature=([count: number]): boolean|description=
Crafts up to <code>count</code> numbers or a full stack. In any case the robot will never craft more than one full stack of crafting result items at once. Returns <code>true</code> if at least one item was crafted, <code>false</code> otherwise.

Note that if you specify an amount of items to be crafted that is lower than the minimum resulting stack size (i.E. order to craft 1 stick, but minimum result stack size is 4), then nothing will be crafted, however this will still return true.

If successful the crafting result will be placed in the currently selected slot, or (if occupied by something else) will be placed into the next slot containing similar items or in the next free slot. This can be one of the slots of the crafting area, which would make it impossible to craft the same item again until that area is cleared.
}}

== Contents ==

{{:Item/contents}}

Database Upgrade

2026-09-10T22:07:19Z

SoraFirestorm: Fix links to Inventory Controller Upgrade

= Overview =

[[File:upgradedatabase0.png|128px]][[File:upgradedatabase1.png|128px]][[File:upgradedatabase2.png|128px]]

Provides the <code>database</code> component.

This upgrade can be used to store item stack information. It can be configured by open its GUI by right clicking holding it in your hand and placing items in it (no actual items are stored in the item, clicking with an item in the grid will store a "ghost" stack). Alternatively, a few components allow configuring the database programmatically, such as the [[Inventory Controller Upgrade|Inventory Controller Upgrade]] and the [[Geolyzer|Geolyzer]].

The Database Upgrade (Tier 1) is crafted using the following recipe:

* 4 x Iron Ingot
* 2 x [[Item/materials|Microchip (Tier 1)]]
* 1 x [[Item/hard disk drive|Hard Disk Drive (Tier 1)]]
* 1 x [[Item/analyzer|Analyzer]]
* 1 x [[Item/materials|Printed Circuit Board]]

[[File:t1database.png|200px]]

The Database Upgrade (Tier 2) is crafted using the following recipe:

* 4 x Iron Ingot
* 2 x [[Item/materials|Microchip (Tier 2)]]
* 1 x [[Item/hard disk drive|Hard Disk Drive (Tier 2)]]
* 1 x [[Item/analyzer|Analyzer]]
* 1 x [[Item/materials|Printed Circuit Board]]

[[File:t2database.png|200px]]

The Database Upgrade (Tier 3) is crafted using the following recipe:

* 4 x Iron Ingot
* 2 x [[Item/materials|Microchip (Tier 3)]]
* 1 x [[Item/hard disk drive|Hard Disk Drive (Tier 3)]]
* 1 x [[Item/analyzer|Analyzer]]
* 1 x [[Item/materials|Printed Circuit Board]]

[[File:t3database.png|200px]]

= Component API =
Component name: <code>database</code>.
{{APICallback|name=get|signature=(slot:number):table|description=
Get the representation of the item stack stored in the specified slot.
}}
{{APICallback|name=computeHash|signature=(slot:number):string|description=
Computes a hash value for the item stack in the specified slot. This value is guaranteed to be the same for identical item stacks, allowing comparison of item stacks across a network (by comparing the hash values).
}}
{{APICallback|name=indexOf|signature=(hash:string):number|description=
Get the index of an item stack with the specified hash. Returns a negative value if no such stack was found.
}}
{{APICallback|name=clear|signature=(slot:number):boolean|description=
Clears the specified slot. Returns true if there was something in the slot before.
}}
{{APICallback|name=copy|signature=(fromSlot:number, toSlot:number[, address:string]):boolean|description=
Copies an entry to another slot, optionally to another database. Returns true if something was overwritten.
}}
{{APICallback|name=clone|signature=(address:string):number|description=
Copies the data stored in this database to another database with the specified address.
}}

= Example =

<syntaxhighlight lang="lua">
local component = require("component")
local sides = require("sides")

local db = component.database -- primary database component
local invcontrol = component.inventory_controller -- primary inventory controller

-- define slot numbers
dbSlot = 1 invSlot = 1

-- compare item inside remote inventory to item in first slot of database
if db.get(dbSlot).label == invcontrol.getStackInSlot(sides.north, invSlot).label then
-- items match, do stuff with it.
else
-- items don't match, do nothing, or do something else.
end
</syntaxhighlight>

= Contents =

{{:Item/contents}}

Item/contents

2026-09-10T22:07:18Z

SoraFirestorm: Fix links to Inventory Controller Upgrade

{| class="oc-contents-table"
! colspan="2" | Items
|-
! Components
| [[Data Card]] - [[Debug Card|Debug Card]] - [[Item/graphics card|Graphics Card]] - [[Internet Card|Internet Card]] - [[Item/linked card|Linked Card]] - [[Item/network card|Network Card]] - [[Item/redstone card|Redstone Card]] - [[Item/wireless network card|Wireless Network Card]]
|-
! Storage Devices
| [[Item/floppy disk|Floppy Disk]] - [[Item/EEPROM|EEPROM]] - [[Item/hard disk drive|Hard Disk Drive]] - [[Item/memory|Memory]]
|-
! Upgrades
| [[Item/angel upgrade|Angel Upgrade]] - [[Item/battery upgrade|Battery Upgrade]] - [[Chunkloader Upgrade]] - [[Database Upgrade]] - [[Experience Upgrade|Experience Upgrade]] - [[Generator Upgrade|Generator Upgrade]] - [[Item/hover upgrade|Hover Upgrade]] - [[Inventory Controller Upgrade|Inventory Controller Upgrade]] - [[Item/inventory upgrade|Inventory Upgrade]] - [[Item/leash upgrade|Leash Upgrade]] - [[Item/navigation upgrade|Navigation Upgrade]] - [[Item/piston upgrade|Piston Upgrade]] - [[Item/sign upgrade|Sign I/O Upgrade]] - [[Item/solar generator upgrade|Solar Generator Upgrade]] - [[Item/tank upgrade|Tank Upgrade]] - [[Item/tank controller upgrade|Tank Controller Upgrade]] - [[Item/tractor beam upgrade|Tractor Beam Upgrade]] - [[Item/world sensor upgrade|World Sensor Upgrade]]
|-
! Containers
| [[Item/card container|Card Container]] - [[Item/upgrade container|Upgrade Container]] - [[Block/disk drive|Disk Drive]]
|-
! Others
| [[Item/analyzer|Analyzer]] - [[Item/texture picker|Texture Picker]] - [[Item/component bus|Component Bus]] - [[Item/CPU|CPU]] - [[Item/apu|APU]] - [[Item/dronecase|Drone Case]] - [[Item/manual|Manual]] - [[Item/microcontrollercase|Microcontroller Case]] - [[Item/nanomachines|Nanomachines]] - [[Item/terminal|Remote Terminal]] - [[Item/terminal server|Terminal Server]] - [[Item/server|Server]] - [[Item/tablet case|Tablet Case]] - [[Item/tablet|Tablet]] - [[Item/materials|Crafting Materials]] - [[Item/ink cartridge|Ink Cartridge]] - [[Item/scrench|Scrench]] - [[Item/hover boots|Hover Boots]] - [[Item/grog|Grog]] - [[Item/loot disks|Loot Disks]]
|}

Inventory Controller Upgrade

2026-09-10T22:05:19Z

SoraFirestorm: SoraFirestorm moved page Item/inventory controller upgrade to Inventory Controller Upgrade without leaving a redirect: Page has been unified

= Inventory Controller Upgrade =

[[File:inventory_controller_upgrade.png|128px]]

This upgrade allows the robot to interact in a more controlled fashion with inventories in the world.

Robots with this upgrade can read additional item information, suck and drop items from and into specific slots of an inventory and equip items on their own. This is particularly useful for interacting with advanced machines, where items have to go into specific slots, but can also come in handy for sorting systems or automated crafting.

The Inventory Controller upgrade is crafted using the following recipe:

* 4 x Gold Ingot
* 1 x Piston
* 1 x Dropper
* 1 x [[Item/analyzer|Analyzer]]
* 1 x [[Item/materials|Microchip (Tier 2)]]
* 1 x [[Item/materials|Printed Circuit Board]]

[[File:invcontroller.png|200px]]

= Component API =
Component name: <code>inventory_controller</code>

Callbacks:
{{APICallback|name=getInventorySize|signature=(side: number): number or nil[, string]|description=
Returns the size of the inventory at the specified side. '''side''' - must be a valid side. '''Returns:''' the size of the inventory, or <code>nil</code> followed by a description why this function failed (usually <code>no inventory</code>).
}}
{{APICallback|name=getStackInSlot|signature=(side:number, slot:number):table|description=
Returns a table describing the item in the specified slot or nil. Deprecated for getting info about robot's own inventory, see <code>getStackInInternalSlot</code>.

'''side''' - must be a valid side.
'''slot''' - the slot to analyze. This does not check the inventory size and will consider slots outside the inventory bounds to be empty.
'''Returns:''' <code>nil</code> if the slot was empty (or outside the inventory's bounds), a table otherwise with the following information about the item in that slot:
* '''damage''':number - the current damage value of the item.
* '''maxDamage''':number - the maximum damage this item can have before it breaks.
* '''size''':number - the current stack size of the item.
* '''maxSize''':number - the maximum stack size of this item.
* '''id''':number - the Minecraft id of the item. Note that this field is only included if <code>insertIdsInConverters=true</code> in the configs, and can vary between servers!
* '''name''':string - the '''untranslated''' item name, which is an internal Minecraft value like <code>oc:item.FloppyDisk</code>
* '''label''':string - the '''translated''' item name
* '''hasTag''':boolean - whether or not the item has an NBT tag associated with it.
}}
{{APICallback|name=getStackInInternalSlot|signature=(slot:number):table|description=
Gets Itemstack description of item in specified or selected slot (if no input provided) of robot inventory.
}}
{{APICallback|name=dropIntoSlot|signature=(side:number, slot:number[, count:number]):boolean[, string]|description=
Puts up to count items from the currently selected slot into the specified slot of the inventory at the specified side. '''side''' - a valid side. '''slot''' - the slot to drop the item into. '''count''' - how many items to transfer. '''Returns:''' <code>true</code> if at least one item was moved, <code>false</code> and a secondary result that describes the error otherwise. Note that the robot cannot drop items into it's own inventory, attempting to do so will cause this to throw an error. You need to use <code>robot.transferTo</code> from the [[API/robot|Robot API]] to do so.
}}
{{APICallback|name=suckFromSlot|signature=(side:number, slot:number[, count:number]):boolean|description=
Takes up to count items from the specified slot of the inventory at the specified side and puts them into the currently selected slot. '''side''' - a valid side. '''slot''' - the slot to take the item from. '''count''' - how many items to transfer. '''Returns:''' <code>true</code> if at least one item was moved, <code>false</code> otherwise. If the currently selected slot is occupied, then the items will be stacked with similar items in the robot's inventory or moved to the next free slot if available. If no slot is available this operation will fail. Note that the robot cannot suck items from it's own inventory, attempting to do so will cause this to throw an error. You need to use <code>robot.transferTo</code> from the [[API/robot|Robot API]] to do so.
}}
{{APICallback|name=equip|signature=():boolean|description=
Swaps the content of the robot's tool slot with the content of the currently selected inventory slot. '''Returns:''' <code>true</code> if the items were swapped, <code>false</code> otherwise. This operation usually succeeds. Note that you can put any kind of item into the robot's tool slot, not only tools, even items that the robot cannot use at all.
}}
{{APICallback|name=store|signature=(side:number, slot:number, dbAddress:string, dbSlot:number):boolean|description=
Stores the Itemstack description of the item from the specified slot in an inventory on the specified side, into a specified database slot with the specified address.
}}
{{APICallback|name=storeInternal|signature=(slot:number, dbAddress:string, dBslot:number):boolean|description=
Stores Itemstack description of item in specified robot inventory slot into specified database slot with the specified database address.
}}
{{APICallback|name=compareToDatabase|signature=(slot:number, dBaddress:string, dBslot:number):boolean|description=
Compare Itemstack description in specified slot with one in specified slot of a database with specified address. Returns **true** if items match.
}}
{{APICallback|name=compareStacks|signature=(side:number, slotA:number, slotB:number):boolean|description=
Checks to see if Itemstack descriptions in specified slotA and slotB of inventory on specified side match. Returns **true** if identical.
}}
{{APICallback|name=getSlotMaxStackSize|signature=(side:number, slot:number):number|description=
Gets maximum number of items in specified slot in inventory on the specified side.
}}
{{APICallback|name=getSlotStackSize|signature=(side:number, slot:number):number|description=
Gets number of items in specified slot in inventory on the specified side.
}}

= Example =

Print meta-info about the item in the position indicated by [[API/robot|slot]]

<syntaxhighlight lang="lua">
local component = require("component")
local sides = require("sides")

local slot = 1
local item = component.inventory_controller.getStackInInternalSlot(slot)

if item then
print("Item name: ", item.name)
print("Item count: ", item.size)
print("Item damage: ", item.damage)
else
print("Slot " .. slot .. " is empty")
end
</syntaxhighlight>

= Contents =

{{:Item/contents}}