SH3 Commander: "Invalid argument to date encode"

[Beery]

Originally Posted by Nopileo

...When creating the career with SH3 Commander, I set the date to January 1940, although when starting SH3 and selecting year and flotilla I started in September 1940. Could this cause any compatibility issues? I think I selected a VIIB boat as well in SH3 Commander, but again when starting the career I had a IID.

It shouldn't cause any problems that I can think of. All I can think of that would affect it would be the Flotilla.cfg file, but like I said before, that doesn't change enough in any SH3 Commander version of the file to do that sort of damage.

If any of these things are causing problems, would it be possible to make it so that SH3 Commander only lists options/boats/flotillas that are available relative to the other selections, like in SH3 itself?

I think that's a great idea, and maybe it's the route that we should go. However, it does limit the options for single missions. I've considered it before just from a simplicity standpoint, but the single mission thing has always been a consideration that has stalled the idea. Maybe we should institute such a limitation only when players choose the career mode in SH3 Commander. Single missions should get the full range of options, but career mode should probably limit us to what's allowed for use in a career. This would be a lot of programming work - SH3 Commander would have to read values in the Flotilla.cfg and Basic.cfg files, but it's probably worth it, and it might give us the added ability to actually change the career start date (right now we're limited to one set month per year, but it's so easy to adjust that with a simple adjustment in Flotilla.cfg). Having said that, I'm not the one who would be burdened with the work, LOL.