Package-level declarations

An abstract version of Component with more quality of life features.

A command that executes the provided runnable once. Easily decorated.

A state machine representing a complete action to be performed using any number of Components. Commands are usually run from the CommandScheduler, but can be run independently if desired. Commands can be chained together to form complex multi-step actions.

A type of command that uses multiple commands, joining all their requirements.

An interface that simplifies access to the CommandScheduler by implementing all its methods.

An OpMode that uses a CommandScheduler, and optionally, a Robot.

The main orchestrator for Commands and Components.

A class representing a basic unit of robot organization, encapsulating low-level robot hardware and providing methods to be used by Commands. The CommandScheduler uses components to ensure that multiple commands are not using the same hardware at the same time. Commands that use a component should include that component in their Command.requirements set.

A command whose properties can be defined externally. Useful for making simple inline commands or combining commands together.

A command that runs as soon as it is scheduled.

A command useful for adding listeners to other commands.

A command that runs commands in parallel until they all finish.

A command that runs commands in parallel until one of them finishes.

A command that runs another command multiple times.

A class that makes any command-based robot code a lot smoother and easier to understand.

A command that runs the specified command every time it is scheduled.

A command that runs commands in sequence.

A time-based command.

A command that waits the specified duration before finishing.