Thanks for the notice. I had an oversight there. Unfortunately, inside of Robot2.java there is no call to swerve, and thus, no call to that line of code. This issue still exists in Robot2.java when there is a P value to the motor even though there is a restoreFactoryDefaults before the edits to the configuration. Also, inside of getConfigCommand, the restoreFactoryDefault method is called correctly and even has a Timer.sleep() event to ensure that there are no issues with configurating the motor, which was highlighted as an issue in this thread. If the world was perfect and this code worked first try 
, then getConfigCommand would have been run, but I have commented it since then because I am going a bit insane. I appreciate the help 