Questions on unit classes for Andy/Don

[DRG]

Originally Posted by Suhiir

One thing I've tried to be VERY careful about is making sure no existing unit is deleted (tho some are marked as "unused" and given "3" for rarity) and the availability dates match as closely as possible with those in the existing OOB is that it can be used with existing scenarios.

OK, you're really not going to be very happy reading this but these are newbie OOB designer assumptions / errors the could have save you hours of time and a lot of aggravation if this hadn't been kept a state secret.

1/ any unit you want to leave in JUST IN CASE a scenario uses it but don't want to show up in the game as a pick you make nation 99 *IF* you haven't built units and formations you only want available in higher formations and used 99 for those as well. ( load US OOB, click on database check utilities,click on FORMATION CHECKS then Broken links that shows all the little sub formations that only exist in a higher formation)

If you have none of those just making the unit nation 99 will hide it but a scenario will happily pick it up if it was already used by one

1B / Want to find out if any change you make affects any scenario using USMC ?? Load SCENHack. Press ALT+T and you will get a list of all scenarios that contain any deviate data. Not all problems that are found there are the result of errors, then may be the result of a scenario designer playing around with unit data. It's a judgment call what needs to be repaired and what doesn't

2/ Scenarios don't care what the availability date is once it's been put in a scenario. It's easy to check.. build a unit 1946 - 1980 then build a test scenario using that unit in 1975 then trim back the units availability to 1950. Unit will still show up in the scenario. There are a couple dozen people on this forum that could have told you that if we'd known this was a concern

Merry Christmas BTW

Don

[Suhiir]

Originally Posted by DRG

OK, you're really not going to be very happy reading this but these are newbie OOB designer assumptions / errors the could have save you hours of time and a lot of aggravation if this hadn't been kept a state secret.

1/ any unit you want to leave in JUST IN CASE a scenario uses it but don't want to show up in the game as a pick you make nation 99 *IF* you haven't built units and formations you only want available in higher formations and used 99 for those as well. ( load US OOB, click on database check utilities,click on FORMATION CHECKS then Broken links that shows all the little sub formations that only exist in a higher formation).
If you have none of those just making the unit nation 99 will hide it but a scenario will happily pick it up if it was already used by one

I didn't know about the 99 nation code.
I've been setting them to unit types (guards infantry etc) that aren't used in the OOB and/or giving them an X3.
In the future I'll keep 99 in mind, and it's good for anyone else similarly insane to know this anyway.

Originally Posted by DRG

1B / Want to find out if any change you make affects any scenario using USMC ?? Load SCENHack. Press ALT+T and you will get a list of all scenarios that contain any deviate data. Not all problems that are found there are the result of errors, then may be the result of a scenario designer playing around with unit data. It's a judgment call what needs to be repaired and what doesn't

Useful, thanks!

Originally Posted by DRG

2/ Scenarios don't care what the availability date is once it's been put in a scenario. It's easy to check.. build a unit 1946 - 1980 then build a test scenario using that unit in 1975 then trim back the units availability to 1950. Unit will still show up in the scenario. There are a couple dozen people on this forum that could have told you that if we'd known this was a concern

Merry Christmas BTW

Don

Yeah I know an existing scenario could care less as long as the unit number matches, I'm trying to avoid having TOW missiles show up in 1950 by keeping the dates as close as possible, in theory someone could (I hope) design a scenario with the stock OOB and someone else could run it using mine and everything will match up fairly well.

I NEVER claimed to be approaching this sanely!

Merry XMas & a Happy New Year to you too