How To Export And Install A CK2Generator Campaign: A Practical 2026 Guide For Modders

How to Export and Install a CK2Generator Campaign starts here: the guide shows when to export, how to prepare files, and how to place the mod so Crusader Kings II reads it. It presumes a generated world is ready and the user has access to their CK2 install and Documents mod folder. The steps that follow are practical, tested, and focused on avoiding common mistakes that break mods.

What Is A CK2Generator Campaign And When Should You Export It?

A CK2Generator campaign is the exported mod version of a generated Crusader Kings II world. It turns the generator’s output, map, history, characters, and events, into a playable CK2 mod that the game can load. Export when generation finishes and the user wants a persistent, repeatable campaign that can be shared or reloaded later.

Why export now? Exporting writes a .mod descriptor and the mod data into the CK2 mod folder so the launcher recognizes it. If the user cancels generation early, they can rerun with the same seed to reproduce earlier start dates, but only export once satisfied with the world state. Exporting also provides a backup: it prevents accidental loss when changing generator options or updating the tool.

Common signs it’s time to export: the map has the desired borders, dynasties and titles look correct, and scripted events ran without fatal errors. If any part of the generated history still shows missing portraits, duplicate IDs, or glaring file errors, fix those before exporting to avoid a broken mod.

Practical warning: exporting unfinished or conflicting files can create a mod that crashes the game. It’s better to take a minute now to check logs than to troubleshoot a corrupted export later.

Preparing Your Campaign For Export: Files, Metadata, And Compatibility Checks

Confirm the export target and metadata first. The generator needs the path to the CK2 install and the user Documents mod folder. On Windows the path is typically Documents\Paradox Interactive\Crusader Kings II\mod, with analogous paths on Linux and Mac.

Check three items before export: the .mod descriptor, folder structure, and compatibility settings. The .mod file must match the mod folder name and include the correct path to the folder. The exported folder should contain history, common, gfx, and other CK2 data subfolders: missing subfolders often cause silent failures.

Run a compatibility pass: ensure the mod’s game version in the .mod file aligns with the installed CK2 version, and remove any duplicate or legacy files left from prior tests. If the user plans to share the mod, edit the descriptor to include a clear name, tags, and supported versions.

A common real-world mistake: a user exported with the wrong CK2 path in configuration and the generator placed the mod next to the program instead of in Documents. That created two copies and confused the launcher. Always double-check the generator’s configuration tab and set the CK2 install directory correctly.

If uncertain about general mod installation mechanics, the site’s primer on mod installs gives a quick, practical walkthrough that helps avoid path confusion.

Exporting And Installing A Campaign From CK2Generator — Overview

Exporting writes the generated world into a mod package (a .mod descriptor plus a mod folder). Installing places those artifacts into the CK2 user mod directory so the game can load them. The process divides into three clear tasks: export inside CK2Generator, copy or extract files into the mod folder if needed, and enable the mod inside the CK2 launcher.

Export produces two essentials: the .mod descriptor and the mod data folder. CK2 requires both to be present under Documents\Paradox Interactive\Crusader Kings II\mod. If the generator outputs an archive, extract it to preserve the folder layout. If files were previously installed, remove older copies first to prevent conflicts.

This overview prepares the user to follow exact steps and alternate installation methods, including manual placement and launcher activation. The following sub-sections detail each step with exact commands and checks to finish the job reliably.

Exporting A Campaign From CK2Generator: Exact Steps And Options

Export now: open CK2Generator, confirm generation finished, then select Export. The generator prompts for an export name and target location: set the mod name to a short, unique identifier and confirm the CK2 user mod path if asked.

Exact steps:

1. Open the generator’s configuration tab and confirm the CK2 install directory.
2. Choose the export option after generation completes.
3. Name the mod and verify the .mod descriptor content if the tool shows it.
4. If the generator creates an archive, extract it to the Documents mod folder, keeping the internal folder structure intact.

Options to consider: include a custom launcher image by placing a 256×256 png in the mod folder, and edit the descriptor to list supported versions. If the mod targets a specific CK2 patch, specifying that reduces launcher warnings. If the generator offers an incremental export, use it to avoid overwriting a large mod during frequent tests.

Honest lesson: one user repeatedly exported with a trailing space in the mod name: the .mod file and folder names mismatched and CK2 didn’t show the mod. Use simple, consistent naming to avoid this.

Manual Installation: Installing The Campaign Files Into Your CK2 Mod Folder

Fact: CK2 reads mods from the user Documents\Paradox Interactive\Crusader Kings II\mod folder. Manual installation means placing the .mod file and the matching mod folder side-by-side inside that folder.

Steps for manual install:

1. Locate the exported .mod file and its mod data folder from the generator export directory.
2. Move the .mod file into Documents\Paradox Interactive\Crusader Kings II\mod.
3. Move the mod data folder (the folder named in the .mod file) into the same mod directory.
4. If the export came zipped, extract it so the folder contains subfolders like history and common.

Practical tips: maintain folder names exactly as referenced by the .mod descriptor. If the .mod points to a folder name that differs by case or spacing, CK2 may fail to match them. Remove old copies of the same mod before copying new files to avoid duplicate-data conflicts and false crashes.

For a refresher on standard mod installation practices and troubleshooting, see the step-by-step install primer on the site which clarifies common path issues and extraction errors.

Activating And Verifying The Campaign In‑Game (Steam And Non‑Steam Tips)

Fact: after files are in the mod folder, CK2 must be launched and the mod enabled from the Mods menu. Both Steam and non‑Steam installs use the same user Documents mod path, so activation steps are identical.

How to enable:

1. Launch Crusader Kings II (via Steam or direct exe).
2. Open the Mods menu in the launcher.
3. Look for the mod by its launcher name: the displayed name can differ from the .mod filename.
4. Enable the checkbox and start the game.

Verify the campaign loaded by checking the start date, map borders, and dynasty lists against a quick screenshot taken from the generator. If the mod doesn’t appear, confirm the .mod and folder are in Documents\Paradox Interactive\Crusader Kings II\mod and that descriptor paths are correct.

Troubleshooting tips: if the mod starts but shows missing portraits or crashes, remove any old conflicting mods and try launching with only the generated mod enabled. If the user needs an example of similar mod installation and crash fixes, Nexus Mods documents compatibility steps that often apply when mods alter maps or core files.

Small but critical warning: updated game patches sometimes change file expectations. If a user exported a mod for an older CK2 version, set the descriptor to the compatible version or run the mod under the matching game patch to avoid subtle errors.

Conclusion

Exporting and installing a CK2Generator campaign is a short process when done in order: prepare metadata and paths, export cleanly, place the .mod and folder in Documents\Paradox Interactive\Crusader Kings II\mod, then enable the mod in the launcher. The most common failures come from path errors, mismatched names, and leftover old files, all avoidable with a quick pre-export checklist. For further help on mod basics, the site hosts a full install guide and related resources that walk users through the occasional edge case.