"SH3Gen" Campaign enhancement (version 0.6.0)

[GlobalExplorer]

Great!

We should start very simple. If you can provide me with some info about the most important targets in HT1.47, it should be my task to come up with a convincing demo. Once this is accomplished, we can think about the concept another time, and more seriously.

For the beginning, an unformatted text file with 10-20 units would do. I would analyze it and make a list of all the different types of entities I find, as well as make a proposal for the metadata format. In the interest of analysis, it might be better if you try to write down one example of every type of unit you can thnk of, but of course not every single entity of this class. One is already enough.

IMO, the most important types of units would be:

- suppliers (docked or milchcows)
- commerce raiders (Atlantis)
- warships and taskgroups (Weserübung etc)
- concentrations of landing crafts or troop ships (d-day)
-german and italian convoys (north africa)
- concentrations of U-Boats (wolfpacks)

For some reason, atm I can't think of any more, but there are loads.

All should be from static layer (SCR), because I think this information should be reliable.

The info should always contain:

[Group/UnitId from Campaign_SCR, so I can match the info, this is very important!]
Name=<Historic or fictional name>
Class/Type=try to verbalize the type of unit
Why is is there?
What type of action does perform (i.e. warship patrol, commerce raiding, etc), could also be put into Class/Type
Anthing else I didn't think of.

I don't need info about waypoints, EntryDate, ExitDate, etc, because this is already in Campaign_SCR, and we should never duplicate data.

As I said, lets keep it very simple. I have already been approached with some grand ideas, but I prefer to work on something that will work, and without the user having to understand it.

The metadata strategy always works, because the application will check if the metadata file is available, and if it's not, work as usual.