Libraries
A sourced directory of tools used in FTC robot software
Overview
A library is optional code maintained outside your project. It can save implementation time, but it also adds APIs, dependencies, version compatibility, and maintenance work. Read the project's current installation guide and check which SDK version it supports before adding it.
This directory covers tools with their own pages here. API examples and release numbers can change; each article links to the project's official documentation or source repository.
Path following and autonomous
- Pedro Pathing — build and follow a first field path with Pedro 3; the page includes a example.
- Road Runner — build a Road Runner 1.0 route with the official FTC Quickstart.
Robot architecture and control
- NextFTC — create , connect gamepad triggers, and run commands. The page includes a claw- example for v2.
- Mercurial v2 — run sequences and concurrent robot tasks with programs and fibers.
- Mercurial v1 — maintain commands and scheduling in an existing v1 project.
- FTCLib — compose and schedule commands with FTCLib's command framework.
- SolversLib — use the maintained FTCLib fork and run a first scheduler-driven sequence.
Tuning and development
- FTC Dashboard — add telemetry and tune live configuration variables with code.
- Panels — expose a live-tunable value and inspect robot telemetry.
- Sloth — deploy eligible TeamCode changes with its Gradle task; use a full install for dependencies and other unsupported changes.
- Slothboard — use Dairy's maintained Dashboard fork with hot-reloaded configuration and OpModes.
Vision
- EasyOpenCV — OpenCV pipelines integrated with FTC camera workflows. It is a community library; follow its upstream documentation and check compatibility with your SDK.
- VisionPortal and AprilTags — FTC SDK vision APIs and related guides.
Newer tools, source projects, and vision models have their own Community software guides.
Versions
These are the releases used by the guides. Different modules can have different version numbers; follow the setup for the library you choose.
| Project | Version used |
|---|---|
| NextFTC v2 | 0.2.1; 0.3.0-SNAPSHOT remains development code |
| FTCLib | 2.1.1; older stable release, slow release activity |
| SolversLib | 0.3.6; separately maintained fork |
| Pedro Pathing | 3.0.1 |
| Road Runner | Core/actions 1.0.1; FTC 0.1.25 |
| FTC Dashboard | 0.6.0 |
| Panels | FullPanels 1.0.18 |
| Sloth / Load | 0.3.2 |
| Slothboard | 0.3.2+0.6.0 |
| Mercurial v2 | MercurialFTC 2.0.1-beta1 |
| Mercurial v1 | 1.0.3; legacy |
| EasyOpenCV | 1.7.3; also used by FTC SDK 12 Vision |
Installation checks
- Confirm the FTC SDK version used by your robot project.
- Read the library's current official installation and migration instructions.
- Check that every repository and artifact in the Gradle example still exists.
- Add one library at a time and sync Gradle.
- Build and test on the before relying on it in a match.
A version number copied from an old article can stop resolving or pull incompatible code. Where versions change often, these pages link to the official release page instead of guessing a version.