Differences

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

--- dcx:simple_dashboard [2015/11/18 18:16] – vic
+++ dcx:simple_dashboard [2026/06/22 12:21] (current) – external edit 127.0.0.1
@@ Line 68: / Line 68: @@
 **Procedure of .dczip export button**
-a. You have to select the current scenario file in the file browser.
+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. Optionally add more single files
+b. You have to select the current scenario file in the file browser.
-c. Then any graphics referenced in your scenario that do not occur in the 'community', 'communitymodgraphics', 'systemgraphics' are added to the zip.
+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 using custom sound or changing graphics through event code (that are not loaded by the data in your scenario elsewhere) you'll have to make manual .zip and this .dczip export function cannot help you.
+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. Save scenario==
 Always a good idea to save.