The dashboard functions as a checklist.

It tells you what this scenario (at least) still needs in order be functional.

Its not only a checklist, they function as a list of steps you could complete as well. Starting with step 1. loading a map.

It shows the name of the ruleset (aka the masterfile). You cannot change this from the simple editor.

If it shows 'VR' it means you are using the default VR ruleset (for experts: the VR_Ruleset.dcxmaster file)

Practically this means you should only import libraries or maps that use the same ruleset.

Step 1 of creating any scenario is loading a map.

Here you can use the 'load map' or 'reload map' button to chose a map to import.

Keep in mind that when using reload you can only choose a map of exactly the same dimensions as the current map.

Step 2 is importing one or more trooptype libraries. You'll have to that in the 'Library tab'.

Step 3 is importing one or more historical unit libraries. You'll have to that in the 'Library tab'.

Step 4 allows you to set some basic parameters concerning date and round length.

Remember the minimum round length is 1 day. There is not really a maximum, but I advise to keep things sane.

Step 5 asks you to name your scenario and your self.

More importantly it allows you to put in a scenario description for the end user.

Step 6 asks you to add 2 regimes. You can do that in the 'Regimes tab'

step 7 asks you to make sure there are victory points on the map. You can do that in the 'Map tab'

step 8 asks you to make sure an event library has been loaded that deals with handing out supply. You can load such a library in the 'Library tab' and configure it there and in the 'Tables tab'.

step 9 asks you to make sure an event library has been loaded that deals with determining a winner at some point. You can load such a library in the 'Library tab' and configure it there and in the 'Tables tab'.

This is the last step. It allows you to use the 'export .dczip' button which will put your scenario and any assets needed in a .dczip file that can than be easily shared with other DC:Community users (who can use the import .dczip in the main menu to install your files).

Keep in mind that you can also manually pack your files in either a regular .zip or renaming that regular .zip to .dczip.

Procedure of .dczip export button

a. You have to give the name of the .zip or .dczip file you are creating. You can save it anywhere even on the desktop.

b. You have to select the current scenario file in the file browser.

c. Optionally add more single files. This can be anything like a .pdf or a second scenario, or a library. adding a readme.txt will make the text inside the readme popup when somebody imports your dczip.

d. Optionally add a music/sfx directory. Make sure all files are directly under this directory and that this directory is directly inside the 'communitysounds/' directory.

e. The rest is automized. Any graphics referenced in your scenario that do not occur in the 'community', 'communitymodgraphics', 'systemgraphics' are added to the zip.

Thats it.

NB: If you are changing graphics through event code (that are not loaded by your scenario elsewhere - for example as event pictures) you'll have to make a manual .zip and this .dczip export function cannot help you.

Always a good idea to save.