At some point in the past, if you used an invalid classname with an addXcargo/global command (e.g. addMagazineCargoGlobal), the command would simply fail silently.
Now, the command causes a config error and, on DS, prevents the mission from loading.
Such commands also don't seem to have complete type validation. While most incorrect types are caught by a script error, type Any (nil, or variable initialised by private but not defined) is not, and also causes a config error.
Although people should not have been using invalid classes before, this change is not very backwards-compatible, as missions that encounter it cannot be played on DS, when they could before. If possible, it should be changed to either fail silently again (probably with RPT error), or display a script error, rather than crashing the whole mission.
