Drag rows to define transport layer order. Availability follows the selected family and current runtime data.
Load a supported family to inspect live parameters, preview controls, and map application rules.
Preview rendering and final export resolution are independent. Final export is capped at 8K (7680 × 4320).
Use this checklist when you want the shortest safe editing path.
Before editing, look at the chips at the top of the map. Mode shows the active tool, View shows the map state you are seeing, and Split shows how many countries have split ownership. If any chip looks wrong, switch to the correct scenario or project first.
Before a large edit or before loading another project, save a backup: open Project Management and download the current project JSON. Loading a project replaces the current map, notes, and export settings.
After loading a project, check the Inspector again. Confirm the target country and active owner, then review frontlines, reference image alignment, and export settings. When these match your plan, continue with Activate, Scenario Actions, or Export.
Use this section when the scenario uses HGO source data, HGO flags, or HGO country-name variants.
HGO preview helps you inspect the HGO source layer beside the active scenario map. It is best used before ownership, label, or color decisions.
The Inspector can show HGO names, flag options, and ideology labels for the selected country. Treat these as identity choices for display and review.
Use Appearance for map readability and Transport for routes, ports, airports, and network context.
Appearance covers borders, ocean, rivers, city points, physical regions, day-night lighting, textures, and presets. These controls change how the same scenario reads on screen and in export.
Transport controls the overview layer for airports, ports, rail, and roads. The visual mode changes whether you read distribution, network shape, or coverage.
Use these tools for ownership edits, batch changes, annotations, and source-aligned visual work.
The Inspector tells you what country or feature is selected. The Active Owner tells paint and ownership actions which country receives the edit.
Scenario Actions, Quick Fill, special zones, frontlines, operational graphics, and unit counters help you move from single-country edits to a readable campaign map.
Use Project tools as a publish checklist: save the project, add strategic context, align references, then export.
Contains Download Project, Load Project, selected file status, and import safety checks.
Contains derived frontlines, operational lines, operation graphics, and unit counters. These are project-local strategic annotations for export and handoff.
Contains local image upload, opacity, scale, horizontal offset, and vertical offset controls. The project stores alignment values, while the image file must be uploaded again after reload.
Contains target selection, format, export resolution, preview, layer order, text stacks, and image adjustments. Final export is capped at 8K.
Treat saving and exporting as two separate handoff steps: save the editable project first, then export the publishable image or layer package.
Use Download Project to save the current editable state: scenario choice, ownership edits, appearance, transport, strategic annotations, reference alignment values, and export settings.
Use Open workbench to choose the output target, format, resolution, layer order, text stacks, and image adjustments. Export creates the final image, per-layer PNG set, or bake pack; it does not replace the editable project JSON.
Before sending files out, keep one editable project JSON and one exported output from the same reviewed state. This keeps later fixes traceable.
Loading the base map and TNO 1962 assets before interaction unlocks.