ORIGINAL: STUCKER868
Understood however the "not losing sleep" post is insulting because it makes my question seem worthless or unimportant. I asked a simple question and anyone who would post that is just trolling. Now as far at the Utah herself goes, perhaps a little bit of code concerning her alone would have solved the problem. I understand it's more work but it makes sense if you are wanting the most historical accurate OB in the history of gaming (and really you are right, there is nothing more to do with her).... other then trivia.
I'll let crsutton speak to what he meant. I didn't take it as an insult to the ship or you. Just a comment on the immensity of the game.
To the other, I don't think you understand the game's architecture. Ships aren't unique in the OOB. They just occupy a slot in the DB. Any ship could be moved into any slot by using the editor (Or removed. Or copied.) That's what people mean when they speak of "data" in the modding sense. Players can control data through the editor. It's how ALL of the mods, from DBB to RA to the various scenarios were done and continue to be. To do what you propose would mean going into the EXE file, which only a dev can do. It would mean hard-coding to a specific DB slot # where the Utah lives in the stock scenarios and then hoping that a player didn't use the editor to stick some other ship in that slot, either on purpose or by accident. Specific ships aren't called out in the EXE so far as I know. It would be very, very dangerous.