The default values of MissionParameters are only evaluated at GUI level. If a client instantiates a mission that declares an optional mission parameter with specified default value, without passing this optional parameter, the value will be null and not the default value. This seems not to be very intuitive to me. I would expect that the default value is used if the parameter is omitted when instantiating the mission.

At least we should document the actual behavior for each mole.