This page is the high-level system index for the base OpenComputers distribution documented in this repository. Instead of listing raw asset paths, it explains how the bundled OpenComputers content is organized and where to look for the APIs that matter during Lua development.
The opencomputers system covers the content that ships with the core OpenComputers mod, including:
- Core runtime libraries such as
computer,component, andevent - Built-in components such as GPUs, screens, filesystems, robots, and redstone devices
- OpenOS commands and bundled userland programs
- Documentation pages for standard blocks, items, upgrades, and gameplay systems
When you are writing Lua code for OpenComputers, you usually need one of these sections:
core-runtime/Use this for machine-global runtime libraries such ascomputer.components/Use this for component callbacks exposed by blocks, cards, upgrades, and devices.commands/Use this for bundled shell commands from OpenOS, Plan9k, SecureOS, and related systems.libraries/Use this for reusable Lua modules bundled with the operating systems.systems/Use this for overview pages like this one that explain how a larger subsystem is structured.
These are always the first stop when you need machine-level behavior:
computer: memory, uptime, energy, users, architecturecomponent: component lookup and proxy accessevent: signal queue and event handlingunicode: Unicode-safe string helpers
These pages describe the APIs most OpenComputers programs touch regularly:
- Display and input:
gpu,screen,keyboard - Storage:
filesystem,drive,eeprom - Robotics and movement:
robot,navigation,inventory_controller,tractor_beam - Networking:
modem,internet, linked and wireless cards - Sensors and world access:
geolyzer,motion_sensor,waypoint - Automation:
redstone,transposer,tank_controller
The base mod also ships with a large amount of userland content:
- OpenOS shell commands such as
ls,cp,find,ps, andfree - Libraries used by those commands and by normal Lua programs
- Installer scripts and bundled examples
- This page is intentionally an overview page, not a raw source inventory.
- Detailed API signatures belong on the specific component, command, or library pages.
- If you are looking for a specific callable interface, prefer the matching page under
components/,commands/,libraries/, orcore-runtime/.
- New to OpenComputers scripting:
Start with
core-runtime/computer.md,core-runtime/events.md, and the main component pages forgpu,screen, andfilesystem. - Writing robot automation:
Start with
components/robot.md,components/opencomputers-robot-proxy.md,components/navigation.mdrelated pages, and inventory or redstone helpers. - Debugging system behavior: Check the relevant component page first, then the matching command or library page if the behavior is exposed through OpenOS tools.