Differences

This shows you the differences between two versions of the page.

--- dcx:simple_dashboard [2015/11/18 17:45] – created vic
+++ dcx:simple_dashboard [2026/06/22 12:21] (current) – external edit 127.0.0.1
@@ Line 3: / Line 3: @@
 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.
 {{:dcx:simple2.jpg|}}
-==1. Ruleset==
+==0. Ruleset==
+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.
+==1. Map==
+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.
+==2. Tooptype library==
+Step 2 is importing one or more trooptype libraries. You'll have to that in the 'Library tab'.
+==3. Historical library==
+Step 3 is importing one or more historical unit libraries. You'll have to that in the 'Library tab'.
+==4. Start data and round length==
+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.
+==5. Scenario title==
+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.
+==6. Regimes on map==
+Step 6 asks you to add 2 regimes. You can do that in the 'Regimes tab'
+==7. Victory points on map==
+step 7 asks you to make sure there are victory points on the map. You can do that in the 'Map tab'
+==8. Supply event present==
+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'.
+==9. Victory event present==
+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'.
+==10. Distribute ready?==
+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).
-==2. Map==
+Keep in mind that you can also manually pack your files in either a regular .zip or renaming that regular .zip to .dczip.
-==3. Tooptype library==
+**Procedure of .dczip export button**
-==4. Historical library==
+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.
-==5. Start data and round length==
+b. You have to select the current scenario file in the file browser.
-==6. Scenario title==
+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.
-==7. Regimes on map==
+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.
-==8. Victory points on map==
+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.
-==9. Supply event present==
+Thats it.
-==10. Victory event present==
+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.
-==11. Distribute ready?==
+==11. Save scenario==
-==12. Save scenario==
+Always a good idea to save.