NextFTC Robot/dev.nextftc.robot

Package-level declarations

The core robot architecture and command-based wrappers.

Robot Structure: NextRobot represents the root of your robot, containing multiple Mechanism instances. NextOpMode is the base class for your OpModes that seamlessly injects your NextRobot instance.
Scanning & Registration: RobotScanner and NextFTCOpModeScanner work alongside Sinister to automatically discover your robot implementations and register your custom OpModes to the FTC dashboard without manual @TeleOp or @Autonomous configuration clutter.
Event System: Trigger and EventLoop provide a WPILib-style API for binding commands to conditional states, allowing commands to run based on arbitrary boolean conditions.

Types

Mechanism

interface Mechanism

Represents a subsystem or mechanism on the robot (e.g., an arm, drivetrain, or intake).

NextRobot

interface NextRobot

The root container for your robot's hardware and mechanisms.

RobotState

object RobotState : OnCreateEventLoop

Holder for the NextFTC robot class and instance. This is initialized during the OnCreateEventLoop phase of the app lifecycle. The robot instance is created using the constructor found by RobotScanner.

Telemetry

object Telemetry

Unified telemetry routing system.

TelemetryBackend

interface TelemetryBackend

Defines a destination that can receive telemetry data. Implement this interface to create custom telemetry outputs (e.g., FtcDashboard, file logger).