Differences

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

--- dcx:advanced_design [2015/11/13 10:12] – vic
+++ dcx:advanced_design [2026/06/22 12:21] (current) – external edit 127.0.0.1
@@ Line 5: / Line 5: @@
 The other key is the documentation. Which at the moment is still sparse. But I will try to add more as we go.
+Below here we see the different kind of libraries and how they relate to the masterfile.
+{{:dcx:systems1.jpg|}}
 ===Advanced Libraries===
 If you want to create your own event libraries or officer card libraries you need to use the Advanced Editor to do so.
-* [[dcx:Event Library]|Creating event libraries]]
+* [[dcx:Event Library]|Creating event libraries]] (includes tutorial and an example library file)
 * [[dcx:Officer Card Library]|Creating officer card libraries]]
@@ Line 15: / Line 19: @@
 ===Technical Explanations===
-* [[dcx:Masterfile_import|What is overwritten when a mastefile is loaded?]]
+* [[dcx:Masterfile_involvement|With what file loads and saves can the masterfile be involved?]]
+* [[dcx:Library_overwrite|What is overwritten when a library is imported?]]
 * [[dcx:Library_import|How are library imports synchronized?]]
@@ Line 22: / Line 28: @@
 * [[dcx:ids_and_slots|Do you understand the difference between IDs# and Slot#?]]
+* [[dcx:scripting_hack|What is the scripting hack?]]
 ===Using a different masterfile : FORKING===
@@ Line 42: / Line 50: @@
 (4) When creating your fork and your master it might be wise to add a number of reserve slots for especially events. Sinces end-users might like to use the scripting hack approach above writing event libraries. If you do not have reserved events created in your master and add events later they might overwrite these 'hack style' event scripts added to scenarios by end-users.