OOB Errors in scenario database?

[John Given]

Have come across a few cases of playing scenarios from the database here where OOB's have been incorrectly formed, i.e, where a Division HQ is misplaced and doesn't give any support to the other units, thus causing a lack of supply to the units.
Wonder how many occurences of this others have had?
A bit frustrating when halfway through a scenario, one discovers the incorrect oob organisation finishes off any chance they have of getting a result?
Perhaps stock scenarios need be checked out for such errors?

Hi TT, yes, I'm sure we've all noticed them.

If the scenario designer frequents the boards, you might want to PM him about the issue. try to be as specific about the issue as possible.

Three main issues with regard to your concern for scenarios that I have noticed;

1. HQ units not correctly set in the oob, meaning that the unit has no subordinate units 'under' it to supply. Conversely, this means that the subordinate units will have major supply issues since they have no HQ to 'draw' supply from.

2. 'Orphaned' leader-type units - leaders with no subordinates on the board, making them valuable only for giving the enemy victory points for killing them.

3. Random subordinate units not attached to any particular HQ (the orphan issue again). When you click the 'highlight HQ' feature, no HQ's highlight when you click the subordinate unit, and/or no matter what HQ you click, this particular subordinate unit does not highlight, meaning it hasn't been 'inserted' into the oob properly.

as far as checking out the various scenarios for errors? Lots of luck with that my friend - there must be over 1,000 total scenarios in the JTCS database by now.

Your best call is to contact the designer to correct it, or revise it yourself (be sure to give the scn, oob, map, and picture files associated with the glitched scenario a slightly different file name - you don't want to overwrite the originals).