[SamCarlberg]

Quick recap on command parameters:

Parameters are there so you can have one command perform multiple actions (rather than one command per action).

For example: there's a mechanism on your robot to kick boulders into the low goal, powered by a pneumatic piston and solenoid. In previous years, you would need a command for kicking and another for retracting the kicker, with their constructors looking something like this:

public KickCommand() {
    // constructor code
}
...
public RetractKickerCommand() {
    // constructor code
}

With parameters, you can have one command perform either action based on the parameter you give it

private final boolean m_extending;
public ControlKickerCommand(boolean extending) {
    m_extending = extending;
    // other constructor code
}

If a command sets one of two states, you would use a boolean parameter, like in the example above.

If a command needs a certain setpoint (like a PIDCommand), that should be a double or int

Strings don't have much use for robot control, but may see use in logging/debugging