All Classes and Interfaces

Class
Description
Convenience base class for RPCMethod implementations.
 
The architecture of a virtual machine, based on the processor installed in it.
Implementing this interface allows providing positional information to the DeviceBusController.
Implementations of this interface that are registered with the registry for this type can be used as read-only base block devices for read-write block devices.
This is used to query for devices given a block face.
Device query for a block in the world.
Utility annotation to allow generating lists of RPCMethods using Callbacks.collectMethods(Object).
Provides automated extraction of RPCMethods from instances of classes with methods annotated with the Callback annotation.
The NeoForge capabilities OpenComputers II provides.
 
 
 
 
 
 
Base interface for objects that can be registered as devices on a DeviceBus.
A device bus provides the interface by which Devices can be made available to a DeviceBusController, which in turn is usually used by VMs to access these devices.
For each device bus there can be exactly one controller.
Reason for a bus scan.
Represents a single connection point on a device bus.
Implementations describe individual slot types.
Lists built-in device types for convenience.
The lookups we do energy interop through on Fabric.
Fabric specific interface, used to define an entrypoint that is invoked once all registries created by the mod exist and entries may be registered with them.
This interface serves as a marker for devices that load firmware.
The lookups we do fluid storage interop through on Fabric.
Allows reserving interrupts on the primary interrupt controller of a virtual machine during a VMDevice.mount(VMContext) call.
Wrapper for objects which may become invalid, such as Devices.
 
Utility annotation to allow generating lists of IOMethods using IOCallbacks.collectMethods(Object).
Provides automated extraction of IOMethods from instances of classes with methods annotated with the IOCallback annotation.
Provides an interface for an IO device, describing the methods that can be called on it and the name it can be detected by.
Declares the name a device is known by to a low-level guest, and documents the device.
The arguments a guest wrote for an IOCallback, with correctly decoding readers.
Represents a single method than can be exposed by an IODevice.
The results an IOCallback hands back to the guest, with correctly encoding writers.
Specialized device type provided by ItemDeviceProviders.
This is used to query for devices given an item stack.
Device query for an item stack.
The lookups we do item storage interop through on Fabric.
This interface is used to receive life-cycle callbacks on targets of an ObjectDevice.
The Fabric lookups OpenComputers II provides.
 
 
 
 
 
 
A memory allocator used to ensure sandbox limits when loading devices.
Allows adding MemoryMappedDevices to the memory map of a virtual machine during a VMDevice.mount(VMContext) call.
This interface provides interaction with the network bus.
A reflection based implementation of RPCDevice using the Callback annotation to discover RPCMethods in a target object via Callbacks.collectMethods(Object), and equally of IODevice using the IOCallback annotation to discover IOMethods in a target object via IOCallbacks.collectMethods(Object).
This annotation may be used to propagate the name of parameters and to provide VM visible documentation of this parameter for methods annotated with the Callback annotation.
This interface may be provided as a capability by item components to signal to the containing BlockEntity that they wish to emit a redstone signal.
ResourceKeys for registries created by the mod.
This interface may be implemented by entities hosting devices to allow modules installed in them to interact with them.
A more restrictive version of Side, intended for robot operation APIs.
A device's handle on the computer it was mounted in.
Provides an interface for an RPC device, describing the methods that can be called on it and the type names it can be detected by/is compatible with.
Names and documents the high-level API of a class carrying Callback methods.
Describes an invocation context for an RPCMethod.
Represents a single method that can be exposed by a RPCDevice.
A group of overloaded RPCMethods, i.e.
Describes a single parameter of a RPCMethod.
A Gson type adapter for a type used as a parameter or return value of an RPCMethod.
This enum indicates a side of a block device.
This interface provides access to a list of Players that are currently using a terminal or similar provided by the owner of this capability.
Provides access to a virtual machine to low level devices.
Allows adding MemoryMappedDevices directly to the underlying virtual machine.
VMDevices may signal the result of their VMDevice.mount(VMContext) operations.
May be fired by devices while handling VMInitializingEvent to indicate that initialization failed.
Fired exactly once, when the VM first starts running.
Allows registering for VM lifecycle events.
Fired when the VM is about to pause, typically before state is persisted.
Fired when the VM resumed running, either when first starting up, when resuming after being loaded, or after a VMPausingEvent.
Provides access to the execution state of a running virtual machine.