Our team is using Pathplanner for autons, and we are having some trouble with the NamedCommands class. The named commands are in pathplanner and are being registered in robotcontainer. My first thought was that the autons were being initialized before the commands were registered, but after some digging, I realized that the NamedCommands.getCommand(), the method that prints out the error we were recieving, (“PathPlanner attempted to create a command '” + name + “’ that has not been registered with NamedCommands.registerCommand”), does not appear to be called until Autobuilder.buildAutoChooser(), which is the only place we’re building autons. Initially, the errors included commands that were only registered because I deployed the wrong code, but we deleted all of the files in /home/lvuser/whatever the path is/pathplanner and that fixed that issue. However, the warnings that none of our commands our getting set with NamedCommands persist. Curiously, the “startShooter” and “pivotZero” namedcommand is not generating an error, which implies that something may be wrong with the conveyor and infeed subsystems, but I am clueless as to what as they are initialized in the same place as the shooter and pivot. I would appreciate some help in determining why “follow2pchoice”, “runShooter”, “4pinfeed”, and “smartInfeed” are throwing the warning in NamedCommands.getCommand() that implies they are not being registered.
repo
The named commands are initialized in RobotContainer lines 126ff