Differences

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

--- dcx:simple_editor [2015/11/13 13:31] – vic
+++ dcx:simple_editor [2026/06/22 12:21] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ==== Simple Editor ====
-===This is the place to be===
+This is the place to be.
-Here you can finally use all the other libraries and map files and create your actual scenarios.
+Here you can import and use all the other libraries and map files and create your actual scenarios.
-It should be straight forward and it should be a modular experience.
+It should be relatively straight forward and it should be a modular experience.
+===The different tabs===
+{{:dcx:simple1.jpg|}}
+. [[dcx:simple_dashboard|Dashboard]]
+. [[dcx:simple_libraries|Libraries]] and [[dcx:simple_library_load|Load Library Pop-up]]
+. [[dcx:simple_map|Map]]
+. [[dcx:simple_units|Units]]
+. [[dcx:simple_regimes|Regimes]]
+. [[dcx:simple_tables|Tables]]
+. [[dcx:simple_debug|Debug]]
+===Tutorial videos===
 Simple Editor Tutorial: https://www.youtube.com/watch?v=UItnYR5h7Pk
@@ Line 13: / Line 33: @@
 Simple Editor : Basic Events Library Tutorial #2: https://youtu.be/q7IgY-UtswI
-==You can create here:==
+===You can create here:===
 -Regimes
-==You can import here:==
+===You can import here:===
 -Map file
 -Historical Unit Libs (and set them to a regime)
-Note: That if you reload a library and something has changed that the units on the map are automaticly reset to their model.
 -Trooptype Libs
@@ Line 33: / Line 51: @@
 -Event libs (for example supply and victory events)
+{{:dcx:systems1.jpg|}}
-==And tailor their use by ==
+Note: That if you reload a library and something has changed that the units on the map are automaticly reset to their model.
--tables
+===And tailor their use by ===
--libvars
+-tabular data + libvars (including drawing hex libvars on the map) (which you have to do to set victory conditions and supply rules)
+-drawing regime ownership on the map
-==You can add here:==
+-place units on the map and assign commanders to HQs
--extra small graphics (that can be passed to event libraries)
+-change victory points of the map
--extra event graphics (that can be passed to event libraries)
+-set initial commander pools
+===You can add here:===
-==You can set:==
+-extra small graphics (that can be passed to event libraries)
--regimes on the map
--change victory points
--commander pools
--initial units
--map libvars (for example to paint weather zones)
+-extra event graphics (that can be passed to event libraries)
 ==And finally you can share you work with:==
@@ Line 65: / Line 77: @@
 -the DCZIP creator that allows easy unpacking of all associated sound and graphic files for end the end-user.
+===Dashboard===
 All the while a dashboard check list keeps you posted what is still missing from your scenario.
+===Debug screen===
 And a debug screen is in the making to allow you to spot common mistakes or any possible data corruption.
-===Technical Details===
+I'll add more functions to it as issues might pop-up.
-==On startup==
-Has master loaded that was specified in the modfile at startup of game.
-==On loading a scenario for the simple editor from start menu==
-Will update with master if it is referenced. Master will be referenced if you created this scenario from the Simple Editor in the first place (and for example didnt unhook it in the advance editor)
-==On saving here==
-Will save it with current reference (or lack of reference) to a master.
-==To update the scenario with any possible changes in the masterfile==
-This should be automatic on loading. But if you unhooked the masterfile in the advanced editor you need to use that same advanced editor to reload the master.
-===Advice===
-==On wanting to have different troop complements per unit==
-For example you want 3rd Panzer Div to have exactly 55 PzIII's... To accomplish this you need to use the scramble table and subtract whatever is necc. from the ideal complement.
-Surpassing TOE's is not possible. Changing them on game start within their parameters is.