How to use the output
Movement (goToPoint/splineToPoint) always targets the
Neuron Pathing library directly (drive/localizer). The
shoot/intake/gate/turret actions are this season's DECODE shooter pipeline and still
call into this year's Robot facade (robot.gate,
robot.intake, Turret.TurretState, ...): generate code
without them (or replace the action catalog, see the comment above
const ACTIONS) for a different game.
Method mode: paste the method into an OpMode in your season repo that has
drive/localizer + driveToTarget()/waitMs()
(see NeuronSplineAuto.java) and, if you used any shooter actions,
robot/alliance + shoot()/farShoot()/
pulseOuttake() helpers too.
Full OpMode mode: save as its own .java file; it bundles
every auto in the Autos card into one self-contained, selectable OpMode
(DPAD up/down to pick, X = Blue, B = Red) with all of the above scaffolding included,
ready to drop into your season's TeamCode/.../opmodes/.
Import opmode (.java) (Autos card): load a previously generated OpMode back
into the planner: each case → method() becomes an editable auto, its
setPosition becomes the start pose, and goToPoint/
splineToPoint calls become steps. for loops become
🔁 Repeat blocks and if/else become ❓ If/Else blocks; the
simulator actually loops and picks the branch each iteration (e.g. i % 2 == 0).
Spline reversed is preserved from the file (shown as pinned); clear the
pill to let it auto-derive. Anything unrecognized (including your own subsystem calls) is
kept verbatim as a custom line.