-
Notifications
You must be signed in to change notification settings - Fork 435
Items
For those that don't like images: the wiki has moved to a new place, http://ocdoc.cil.li/.
This wiki will no longer be updated.
This page lists all items OpenComputers adds to the game. Please check the recipes via NEI. Alternatively, here you can find a graphical representation of the recipes here. They are sorted alphabetically as far as I can tell.
Component items are items that when installed in a computer case or robot can be interacted with from Lua. See the page on this topic for more information.
Used to change what's displayed on screens. Computers can control the buffer of a bound screen via the GPU's API.
- Maximum resolution: 50x16/80x25/160x50.
- Maximum color depth: 1/4/8.
- Operations/tick: 1,1,4,2,2/2,4,8,4,4/4,8,16,8,8.
The operations refer to, from left to right: copy
, fill
, set
, setBackground
and setForeground
. The number indicates the number direct calls that can be made to each of these functions on the graphics card per tick before an indirect call has to be made. See the page on component interaction for more information on direct calls.
Allows reading and emitting redstone signals around the computer or robot. This uses the same API as the Redstone I/O block.
The second tier of this card allows interaction with other mods' redstone extensions. If the respective mods are also installed, this supports simple and bundled redstone signals for RedLogic and/or MineFactory Reloaded's RedNet. It also supports wireless redstone interaction with both the Chickenbones and the SlimeVoid versions of Wireless Redstone.
Allows distant computers connected by other blocks (such as cable) to communicate by sending messages to each other.
See the network card component's API to see how to send and receive messages.
This is an upgrade to normal network cards that allows wireless sending of network messages in addition to normal ones.
Make sure to set the signal strength or no wireless packet will be sent, but keep in mind that sending wireless messages requires energy (configurable).
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.
This card provides access to 'the interwebs'. It allows making HTTP requests and opening TCP sockets, unless disabled in the config. See the Internet API.
While technically also components, you'll usually interact with components using the filesystem API or a couple of built-in programs (such as ls
and mkdir
) instead of using their component API directly.
Per default, storage devices get auto-mounted in the /mnt
directory, under a directory representing the first couple of letters of their component address. You can mount any storage device at multiple locations using the filesystem API or the mount
program.
Small and cheap storage device that can be inserted into disk drives, tier three computer cases and robots.
Hard disk drives (HDDs) come in three tiers, with increasing storage capacity (each tier's capacity is configurable). They can store more data than a simple floppy, but are also more expensive to craft. They can also only be installed in computer cases and servers. They can only be installed in robots during the assembly phase. (Prior to 1.3: They can not be installed in robots.)
Memory (RAM) comes in five tiers, with increasing sizes (each tier's size is configurable). They fall into the three item tiers like so: {1, 1.5}, {2, 2.5}, {3, 3.5}. Memory isn't really a component, since it does not provide any Lua callbacks, but it can be installed into computer cases to increase the available RAM of the computer, which allows running more complex programs.
Upgrades are normal components, but the can only be used by robots in the robot's upgrade slot.
This upgrade provides inventory space to a robot. You will usually want to install at least one of these in a robot. Each upgrade provides an additional 16 inventory slots, up to a maximum of 64 slots. Thus, adding more than 4 inventory upgrades has no effect.
Since version 1.3.
This upgrade allows the robot to interact in a more controlled fashion with inventories in the world. Robots with this upgrade can suck and drop items from and into specific slots in an inventory. 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.
Additionally, this upgrade allows the robot to take more control over its own inventory, and change its equipped item on its own.
Since version 1.3.
This upgrade allows robots to place blocks in thin air, without a reference block, similar to a certain block by a certain mod this upgrade may or may not have been inspired by.
Since version 1.2.6.
Enables robots to use the top left area of their inventory for crafting objects. Items have to be aligned as they would be in a crafting table.
See the component API on how to use it.
Can be used to generate energy from fuel on the go. Burns items to generate energy over time, based on their fuel value.
Note that fuel can only be inserted into the generator via its API, so you'll have to charge your robot up to a certain level using a charger block first.
Per default the generator's efficiency is at 80% of a BuildCraft Stirling Engine, i.e. it consumes the fuel at the same pace a Stirling Engine would, but only outputs 80% of the energy a Stirling Engine would.
Generates a little bit of energy during the day if the robot is under clear skies.
Allows the robot to read and write signs in the world.
See the component API on how to use it.
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. Component/Navigation
This upgrade allows robots to act as a one-chunk chunkloader, allowing them to continue to operate even when no player is nearby / some other chunkloader is active.
Since version 1.3.
This upgrade increases the internal energy buffer of robots, allowing them to operate longer without having to return to a charger. Storage is increased by 10000/15000/20000.
Since version 1.3.
Containers are special items that can be built into robots to allow changing components in the robot on the fly. They are basically specialized inventory slots.
Note that besides the items listed here, the Disk Drive also acts as a container, providing a dynamic floppy slot.
This upgrade provides a card slot supporting a card up the tier of the container. For example, a tier two card container can take a tier two card.
Since version 1.3.
This upgrade provides an upgrade slot supporting an upgrade up the tier of the container. For example, a tier two upgrade container can take a tier two upgrade.
Since version 1.3.
CPUs, while not acting as components, are required to make a computer start up. They also control the number of components that can be connected to a computer before it will not start anymore / crash.
Used to display information about blocks, such as their address and component name. Also displays the error that caused a computer to crash if it did not shut down normally.
Note that if you hold Ctrl
while analyzing a block, that block's address will be copied to your clipboard (if the block has an address, that is).
A Server can contain components like a Computer Case. Open a Server by having it selected in your hotbar and rightclicking (like opening an Ender Pouch, for example). A configured server can be placed into a Server Rack, where it can then be powered on and perform like a normal computer. Servers can be controlled using a Remote Terminal, which will act like a portable Screen+Keyboard combo for the server.
The Remote Terminal can be bound to a single server, to allow controlling it from anywhere within the range configured in the Server Rack containing the Server.
There are also a number of items that are exclusively used for crafting. As mentioned above, please consult your local NEI installation for recipes.