New changes with CS scenario listings!

[RedDevil]

CONCLUSIONS:
1. The attempt to tidy up the CS Scenario Database is long overdue.
2. The new version falls short of the mark, with the confusion factor remaining high, with classifications containing no data and whose meaning is obscure.
3. No attempt is made to differentiate between Matrix and TS
4. The * and ** are not explained.
5. The Matrix game is EF, not EFII

1. yep it's been long overdue.

2. not sure what confusion you speak of? The listings are now divided into 3 main categories, rather than 13. You play EF2, you look in the EF listing for the scenario, you play WF, you look in the WF listing. can't be much simpler than that :)

3. And why does there need to be any differentiation? It's all the same game, just a consolidation. There will be no separation on Matrix or TS, all CS WW2 scenarios will categorized as EF2, WF, and RS.

4. The *'s are used to encourage the order in which the scenario appears in your Game list, All newer scenarios are given this designation to allow gamers to see the newer scenarios before the older ones when they search the list for a scenario.
Jason has asked that we promote his template for new scenario descriptions to attempt to gain consistency amongst all CS designers thus allowing gamers to find them easier and indexing them becomes easier. I have posted his template in this thread.
CS Scenario Template thread link

5. It's all EF2, East Front was the original Talonsoft game that has become obscure and evolved into EF2. Thus the name shall always be known as EF2. Matrix's naming it EF is simply a misprint :)

DG and VN are NOT going to be inclusive of the WW2 listings, they will carry their own categories. I'm sure they will continue to have a future here at TheBlitz

I cannot remove the old listings, otherwise ALL the games reported under those listings will disappear. They will need to remain listed, but not used.

Scenario data is and still can be entered by members who can take the time to do so. This includes old or missing data that has been left out by people who entered the scenario into the DB but didn't fill out everything.

Custom scenarios, will be the only ones needing compatibility testing with matrix versions, this should be done as needed and updated scenarios uploaded for downloading from the scenario listings pages.
Since Server access is limited to only a few persons, this process would not be done on a daily basis, but compiled for monthly updates.

Contact the ladder commanders when you have an updated file. It must include the scenario ID # and any pertaining information that needs entered into the description in order to correctly updated.