Upon the initialization of the PathfindingCommand, the robot checks if it is within 0.5 meters of the target pose. If it is, it sets the variable finish to true. This skips execute and returns true in isFinished. This is an issue since our team was planning to use PathPlanner's PathfindingCommand to visit different poses on the reef, and we simply cannot be within 0.5 meters of our intended pose and still be able to score.
Steps to reproduce the behavior:
- Run the PathfindingCommand while close to your intended destination.
We expected this to be able to reach our pose. Instead, the robot thought that it was close enough and didn't move.

- OS: Windows 11
- GUI Version: 2025.2.2
- PPLib Version: 2025.2.3
- PPLib Language: Java
I believe that creating a variable that can be changed in the Pathfinding class and then calling it in PathfindingCommand instead of having a static number could resolve this issue. It would preserve the default value while still allowing modification.
Upon the initialization of the PathfindingCommand, the robot checks if it is within 0.5 meters of the target pose. If it is, it sets the variable finish to true. This skips execute and returns true in isFinished. This is an issue since our team was planning to use PathPlanner's PathfindingCommand to visit different poses on the reef, and we simply cannot be within 0.5 meters of our intended pose and still be able to score.
Steps to reproduce the behavior:
We expected this to be able to reach our pose. Instead, the robot thought that it was close enough and didn't move.
I believe that creating a variable that can be changed in the Pathfinding class and then calling it in PathfindingCommand instead of having a static number could resolve this issue. It would preserve the default value while still allowing modification.