Skip to content

Installation

For the usual visual workflow, open BLine Web and install BLine-Lib in the robot project. The editor and robot library are separate: editing a path does not require robot code, and code-generated paths do not require the editor.

1. Open BLine Web

Browser

Open bline.run in a desktop-class browser. No installation is required. Upcoming versions are previewed at beta.bline.run.

The browser editor stores projects in browser-local persistent storage. Use Project → Import / Export → Export Autos Folder… to produce robot-ready files and Export Project Archive… for a portable editor backup.

Do not rely on browser storage as your only copy

Browser data belongs to that browser profile and site origin. Export the project into version control regularly.

Moved from bline-web.pages.dev

BLine Web previously lived at bline-web.pages.dev and web-beta.bline-web.pages.dev. Opening either old address once in a browser moves the projects and field images saved there to bline.run, then opens the same page on bline.run. Projects already saved on bline.run are kept. If the old address reports that your projects couldn't be moved, choose Try again, or export the project there and import it at bline.run. A robot folder chosen for exports in the browser must be chosen again on bline.run.

Desktop

The desktop build can edit an FRC repository or autos folder directly. These downloads are pinned to the current editor, v1.0.0. The tutorials and editor visuals on this site still describe v0.1.0-alpha.12; the 2027 Beta 1 and Beta 2 guides cover what changed.

Download Windows x64

Download Linux x64

Use the v1.0.0 release assets if a download link is unavailable. BLine Web currently warns that mobile support is limited; use a laptop or desktop for path authoring.

When the desktop app asks for a folder, choose either:

  • the robot repository root, if it contains src/main/deploy; or
  • src/main/deploy/autos directly.

The app resolves a selected robot repository to src/main/deploy/autos and creates missing config.json, paths/, and editor metadata as needed.

2. Install BLine-Lib

The current robot-library release is v0.9.2 for WPILib 2026 and Java 17. It loads paths exported by BLine Web v1.0.0. Settings added in the 2027 editor, tank drive direction and Progress handoffs, take effect only with the 2027 library.

Vendor JSON

  1. Open the FRC robot project in WPILib VS Code.
  2. Open the Command Palette with Ctrl+Shift+P or Cmd+Shift+P.
  3. Run WPILib: Manage Vendor Libraries.
  4. Choose Install new libraries (online).
  5. Paste:
https://bline-metrics.edan-liahovetsky.workers.dev/vendor/BLine-Lib.json

If that endpoint is unavailable, use the direct source file:

https://raw.githubusercontent.com/edanliahovetsky/BLine-Lib/main/BLine-Lib.json

Both URLs describe the same current release. Reinstall from the same URL when upgrading the pinned vendor dependency.

Gradle alternative

Add JitPack and pin the release tag:

repositories {
    maven { url 'https://jitpack.io' }
}

dependencies {
    implementation 'com.github.edanliahovetsky:BLine-Lib:v0.9.2'
}

Use an exact tag in a competition project. A snapshot of main can change without warning.

3. Verify the library

This import should resolve after Gradle refreshes:

import frc.robot.lib.BLine.*;

Build the robot project before proceeding. If the dependency does not resolve, see Common Issues.

WPILib 2027 beta

BLine-Lib v2027.0.0-beta.3 is a separate prerelease for WPILib 2027.0.0-alpha-7 and Java 25. In that project, install this vendor URL through WPILib: Manage Vendor Libraries → Install new libraries (online):

https://raw.githubusercontent.com/edanliahovetsky/BLine-Lib/wpilib-2027/BLine-Lib-2027.json

Keep only one BLine vendordep: remove the stable BLine-Lib.json when migrating. The beta vendor file selects com.github.edanliahovetsky:BLine-Lib:v2027.0.0-beta.3 from JitPack. Build the robot project after installation.

The 2027 beta's root package is bline, for example import bline.commands.FollowPath;. The stable 2026 line keeps frc.robot.lib.BLine. When updating from an earlier 2027 beta, replace frc.robot.lib.BLine. with bline. in your imports; class names, subpackages, and signatures are unchanged.

Follow the 2027 setup and migration guide for its imports, Commands v2/v3 adapters, and drivetrain setup, and author paths in BLine Web v1.0.0. The Java examples elsewhere on this site and the hosted Javadoc describe the stable 2026 API. Use the beta's packaged Javadoc for its API reference.

Legacy BLine-GUI

Maintaining an older PySide project

BLine-GUI is the legacy editor. Current BLine Web can import and migrate legacy path/autos data; re-export and verify the result before deploying it. New tutorials and visuals document BLine Web. See the legacy repository only when maintaining that older workflow.

Next

Continue with First Path Tutorial to configure the editor, export a path, wire the drivetrain, and run it safely.