QUOTE (huffysama @ Aug 11 2009, 08:07 PM) <{POST_SNAPBACK}>
The problem doesn't affect 0 through 5 because Mission Computer is compensating for those (labeling them as one less than their STR number). However the higher level cargos are all (or at least mostly) messed up. I'd look in the all cargo types STR and put in the number that's one less than the cargo type you want.
That's what MissionComputer already does; the list you're seeing is generated automatically, and its behaviour seems to match what the standard scenario expects. (For example, mïsn 569 'Charter Flight' requests cargo type 6, which MissionComputer's pop-up menu identifies as 'Passengers', and mïsn 151 'Take Mu'Randa to Sol' requests 29, identified as 'Mu'Randa' in the pop-up menu.)
Since you referred to 'Documents', which isn't a standard cargo type in EV Nova , I think your problem actually has nothing to do with cargo type numbers, but is the result of the format issues I mentioned in my previous post. EV Nova 1.1 changed its file format to a new type, and I'm still finding features in MissionComputer that were broken by the change. The cargo type pop-up menu is one of them, so I think you're seeing the defaults, which are left over from EV Override. 'Documents' is a cargo type in that game, and it has the same number as 'Prisoner' in EV Nova , so that explains what you described happening.
Since the new version no longer invites users to modify its data files, it should be a sufficient solution to hard-code the default cargo types for EV Nova into MissionComputer; they'll always be overriden anyway if there's a STR# resource ID 4000 in the current file.