查看“模组制作”的源代码

{{version|3.2}}

'''Modding''', or creating [[mods]], is the act of modifying the behavior of the base game (often referred as ''vanilla''), either for personal use, or to release publicly to other players, for instance via the [[Steam Workshop]].

As for all Paradox games, [[Crusader Kings II]] is moddable to a great extent.

Motivations of modders may vary widely: better translation to native language, more events or decisions, better map, major overhaul, etc.

Modding is not magic or heresy, anybody can learn to build a mod, and this guide is intended to lower the entry barriers to the world of CKII modding.

Yet, however good the documentation, there is still a learning curve to it, and it cannot replace the need to read some working vanilla code and do lots of trial and error!

==Guidelines==

*'''Create a mod for your modifications''': [[Creating a mod|create a personal mod]] even for small changes, and never modify directly game files in Steam CKII folder, as they may be overwritten without warning.
*'''Use a good text editor''' to edit files and search into multiple files. See [[#Text editors|text editors]].
*'''Validate your mod''' with [[The Validator]], it will save you a lot of pain and time [[troubleshooting]] crashes and bugs.
*'''Minimize overwrites of vanilla files''' by adding separate files and [[#Game structure|loading from folders]] whenever possible, to improve mod compatibility and maintenance.
*'''Use a proper merge tool''', to [[Merging guide|merge between folders]], and update modified vanilla files to a new vanilla patch.
*'''Backup your work''' to avoid losing everything. In case of a modding team, consider using a source control system like [https://github.com/ GitHub] to act as backup and also manage collaboration.
*'''Use ANSI (Windows-1252) encoding''' for text files.
*'''Indent properly''' to easily spot unclosed curly braced. Vanilla uses 1 tab for indentation rather than spaces.
*'''Use comments''' starting with # character, to remember reasons for writing tricky stuff.

==Text editors==

Here are text editors with CK2 language support:

* [http://notepad-plus-plus.org/ Notepad++]: [[forum:745679|CKII language file]]
* [https://www.sublimetext.com/ Sublime Text]: [[forum:1084658|Syntax highlighting for Sublime Text 3]]
* [https://atom.io/ Atom]: [https://atom.io/packages/language-crusader-kings--i-i language-crusader-kings--i-i]

==Mod structure==

{{Ambox|type=notice|text=If creating a mod for the first time, see the detailed guide about [[creating a mod]].}}
Mods are located in folder ''~\Paradox Interactive\Crusader Kings II\mod'', which must contain:
*the .mod file, to tell the launcher what to do with the mod-folder.
*the mod folder or zip containing the mod data. The mod data must have the same [[#Game structure|file and folder structure]] as if it was along with CK2game.exe in the game directory. Note that folder and file names are case sensitive on Mac and Linux.

The name of the .mod file must not contain any white-spaces, otherwise it will not auto-select when re-starting the launcher.

The content of the .mod file is:

{| class="wikitable"
!Key
!Required?
!Effect
!Example
|-
|name
|'''Yes'''
|Defines the name that shows up in the launcher
|name = "My Mod"
|-
|path
|'''Yes'''
|Defines which folder is the mod's folder. It is relative to ''~\Documents\Paradox Interactive\Crusader Kings II\'' folder.
|path = "mod/MyMod"
|-
|user_dir
|No
|Tells the launcher to store saved games and temporary files in a specific folder. This can be useful for mods incompatible with vanilla saves (because of new titles, flags, religions, cultures, buildings, etc.), so that things don't get mixed up.
'''Warning''': do not set user_dir for sub-mods of a main mod, as all user_dir of active mods are concatenated.
|user_dir = "MyMod"
|-
|archive
|No
|Defines a zip-file instead of a folder. Alternative to path. It is relative to ''~\Documents\Paradox Interactive\Crusader Kings II\'' folder. This is the format used for mods downloaded from the [[Steam Workshop]], but when uploading a mod to the workshop, path structure must be used instead.
|archive = "mod/mymod.zip"
|-
|replace_path
|No
|Tells the launcher to override everything in a folder, and load ONLY from the specified paths inside the mod. This is the only way to effectively remove stuff from vanilla, and is most often used for total conversion mods.
Notes: 
*'''replace_path works with folders, not files'''. To overwrite a file, just create a file with the same name in the mod.
*'''replace_path only affects files in the specified folder, not files in sub-folders within that folder'''. For instance, replacing "history" does not replace "history/characters" as well.
*To reduce mod size and improve mod compatibility, it is usually best to minimize the amount of folders that are replace_path.
*replace_path is ignored when installing mod in the old Crusader Kings II\mod folder, hence why user mod folder must be used.
*Unless you are sure you '''do''' need replace_path, you almost certainly don't.
|replace_path = "history" <br/>
replace_path = "history/characters"
|-
|dependencies
|No
|Tells the launcher that another mod has to be loaded before this one. The other mod will be loaded first, allowing the 2nd mod to override some files (otherwise the 1st mod would win). A dependency is not a hard requirement; you do not need a dependency loaded if the mod has one set. This is simply a way for the mod file to tell the launcher which files should be loaded first.
|dependencies = { "Another Mod" "Yet Another Mod" }
|-
|picture
|No
|Image under mod folder to serve as banner for [[Steam Workshop]] (will be displayed as 268px × 268px JPEG)
|picture = "MyMod.jpg"
|-
|tags
|No
|List of tags for [[Steam Workshop]]. Warning: don't forget quotes for tags that contain spaces.
|tags = { "Tag1" "Tag 2" }
|-
|supported_checksums
|No
|List of expected checksums for which scripting condition <code>supported_checksums</code> will evaluate to true. This can be used in [[event modding]] to display a warning to the player.
|supported_checksums = { ABCD EFGH }
|-
|}

Below are some examples mod files, depending on the category of the mod:

=== Small mod ===

Small mods are the most common, and should neither use <code>user_dir</code> nor <code>replace_path</code> in order to keep compatibility with other small mods.

<pre>
 name = "Small Mod"
 path = "mod/SmallMod"
 picture = "SmallMod.jpg"
 tags = { "Mods" "Small" }
</pre>

=== Big mod ===

Overhaul mods typically use <code>user_dir</code> as saves wouldn't be loadable outside of the mod anyway.
For [[Total_conversion_guide|total conversion]] mods, <code>replace_path</code> can be used to completely ignore vanilla directories that don't make sense in the context of the mod (history, flags, ...)

<pre>
 name = "Big Mod"
 path = "mod/BigMod"
 user_dir = "BigMod"
 replace_path = "history/provinces" 
 picture = "BigMod.jpg"
 tags = { "Mods" "Big" }
</pre>

=== Sub mod ===

Sub-mods of a main mod typically use <code>dependencies</code> to be able to override files from main mod.

<pre>
 name = "Sub Mod"
 path = "mod/SubMod"
 dependencies = { "Main Mod" }
 picture = "SubMod.jpg"
 tags = { "Mods" "Main Mod" }
</pre>

==Game data==

* [[Console commands]], useful for debugging mods.
* [[Defines]], which allow to influence some hardcoded vanilla behaviors
* [[Scopes]], [[conditions]], and [[commands]] used for [[scripting]]
* [[Modifiers]], used to influence calculations made by the game
* [[Map modding|Map data]]

==Game structure==

The game data is composed of hierarchy of folders, containing game files.

A mod follows the same folder structure as the base game, so that when loading the game the engine will combine files from vanilla and mod(s).
In most folders, the engine will load all the files within, which allows a mod to add new definitions (titles, religions, ...) without having to copy and modify vanilla files.
To make use of this, it is important to understand how the scripts are loaded both at file level and definition level.

The behavior when loading a mod is the following:
* Engine processes folders and files based on some hardcoded [[Troubleshooting#Loading|load order]].
* If current folder is defined as <code>replace_path</code>, all vanilla files in that folder will be ignored, and only mod files will be loaded (if any).
* If the mod folder and vanilla folder both contain files with same names, vanilla files will be ignored and mod version will be used.
* Inside a given folder, the order in which files are processed is usually alphanumerical on combined vanilla and mod file names, though some folders may have a different behavior.
* When encountering more than once the same definition (title, religion, decision, ...), the duplicate definition may:
**be ignored (first definition wins)
**fully override the previous definition (last definition wins)
**partially override the previous definition (definitions are merged/additive, which only makes sense if there is actually something to merge: hierarchy, list, etc.)
**coexist/break both (in which case duplicate IDs must be avoided)

Below is a list of CKII game files and folders, with associated modding guide, and loading behavior.

For loading behavior, the cell colours highlight whether the behaviour is the <span style="background-color:lightgreen">expected one</span>, <span style="background-color:gold">strange or requiring some attention</span>, or <span style="background-color:salmon">unexpected and to be avoided</span>.

{| class = "wikitable"
!File/Folder
!What it contains
!How to mod
!Loading behavior
|-
|.\'''common\'''
*achievements.txt
*defines.lua
*defines.txt
*hints.txt
*region_colors.txt
*static_modifiers.txt
*technology.txt
|General information
*Defines Steam [[Achievements]]
*POP, general, diplomatic, economic and military variables
*Defines playable start- and end-date
*Defines the displayed hints
*RGB code for each region
*All difficulty, rank and standard modifiers
*[[Technology]] data
|<br/>
[[Defines]]<br/>

<br/>
<br/>
[[Static modifiers]]<br/>
[[Technology modding]]<br/>
| N/A
|-
|.\common\'''alternate_start\'''
|
|[[Alternate start modding]]
|{{sup|?}} Merge
|-
|.\common\'''artifact_spawns\'''
|
|[[Artifact modding]]
|style = "background-color:lightgreen"| Merge.
|-
|.\common\'''artifacts\'''
| Definitions of [[artifact]]s
|[[Artifact modding]]
|style = "background-color:lightgreen"| Merge.
|-
|.\common\'''bloodlines\'''
|
|[[Bloodline modding]]
|
|-
|.\common\'''bookmarks\'''
|[[Bookmarks]] are configured here (scenarios/start dates)
|[[Bookmark modding]]
|style = "background-color:lightgreen"| Merge. Bookmarks are listed chronologically in-game, whatever the order in files.
|-
|.\common\'''buildings\'''
|[[Buildings]] folder, all buildings are stored here. 
|[[Building modding]]
|{{sup|?}} Merge
|-
|.\common\'''cb_types\'''
|[[Casus Belli]] folder, all Casus-belli are stored here.
|[[Casus Belli modding]]
|style = "background-color:gold"| Merge, but override of casus belli by re-using same name does not work (creates duplicate casus belli)
|-
|.\common\'''combat_tactics\'''
|Combat [[tactics]] definitions.
|[[Unit modding]]
|{{sup|?}} Merge
|-
|.\common\'''council_positions\'''
| Conditions for an A.I. councillor to adopt a certain category of voting behavior.
|[[Councillor modding]]
|{{sup|?}}
|-
|.\common\'''council_voting\'''
| A.I. rules for how councillors from a behavior category will vote
|[[Councillor modding]]
|{{sup|?}}
|-
|.\common\'''cultures\'''
|[[Cultures]] folder, all cultures are stored here. 
|[[Culture modding]]
|style = "background-color:lightgreen"| Merge. Since [[patch 2.4]] cultures are merged like religions, and a new culture may be added to a vanilla culture_group via a separate file.
|-
|.\common\'''death\'''
|[[Death]] definitions
|[[Death modding]]
|
|-
|.\common\'''death_text\'''
|Flavor text for succession screen
|[[Death modding]]
|
|-
|.\common\'''defines\'''
|[[Defines]].
|[[Defines]]
|{{sup|?}} Merge. Entries in files override common/defines.lua values.
|-
|.\common\'''disease\'''
|[[Diseases]] definitions.
|[[Disease modding]]
|{{sup|?}} Merge
|-
|.\common\'''dynasties\'''
|[[Dynasties]] folder, all dynasties are stored here.
|[[Dynasty modding]].
|style = "background-color:gold"| Merge. Duplicate dynasties loaded before vanilla (i.e., <code>000_</code>  prefix) will overwrite dynasty shields. Duplicates loaded after (i.e., <code>z_</code>  prefix) will overwrite dynasty names. To overwrite both, use duplicate files, one with a preceding prefix and one with a succeeding prefix.
|-
|.\common\'''event_modifiers\'''
|Event_modifiers folder, all event modifiers are stored here
|[[Modifiers]]
|style = "background-color:lightgreen"| Merge.
|-
|.\common\'''execution_methods\'''
|[[Execution]] methods
|[[Death modding]]
|{{sup|?}}
|-
|.\common\'''game_rules\'''
|[[Game rules]] definitions
|[[Game rules modding]]
|style = "background-color:lightgreen"| Merge. The rules are displayed in UI based on order of files (alphanumerical on file name), then order of rules within the file.
|-
|.\common\'''government_flavor\'''
|[[Government]] naming definitions
|[[Government modding]]
|{{sup|?}}
|-
|.\common\'''governments\'''
|[[Government]] definitions
|[[Government modding]]
|style = "background-color:lightgreen"|Merge. It is possible to define governments of the same government group in different files.
|-
|.\common\'''graphicalculturetypes\'''
|Graphicalculturetypes folder, all graphical culture types are stored here
|
|{{sup|?}} Merge
|-
|.\common\'''heir_text\'''
|Flavor text for succession screen
|[[Death modding]]
|
|-
|.\common\'''holding_types\'''
|Conditions for being allowed to build each holding type.
|[[Government modding]]
|{{sup|?}}. It is not possible to add new holding types.
|-
|.\common\'''job_actions\'''
|Defines [[councillors]] actions
|[[Councillor modding]]
|style = "background-color:lightgreen"| Merge.
|-
|.\common\'''job_titles\'''
|Defines councillors titles
|[[Councillor modding]]
|{{sup|?}}
|-
|.\common\'''landed_titles\'''
|Landed_titles folder, all landed titles are stored here. 
|[[Title modding]]
|style = "background-color:lightgreen"| Merge. Merging behaviour is "complicated and might not have been designed that way intentionally"<ref>[[Forum:774248/page-14#post-19100145]]</ref>
|-
|.\common\'''laws\'''
|
|[[Law modding]]
|style = "background-color:gold"| Merge. A law with the same name as an existing law will append conditions to the allow section, but not the potential section.
|-
|.\common\'''mercenaries\'''
|[[Mercenaries]] folder, all mercenaries are stored here
|
|{{sup|?}} Merge
|-
|.\common\'''minor_titles\'''
|Minor_titles folder, all minor (i.e. honorary) titles are stored here
|[[Minor title modding]]
|style = "background-color:gold"| Cannot be overridden, attempts to do so will result in multiple minor titles with the same tags, like traits
|-
|.\common\'''modifier_definitions\'''
|Defines dynamically defined modifiers, in particular special [[units]] modifiers.
|[[Unit modding]]
|{{sup|?}} Merge
|-
|.\common\'''nicknames\'''
|[[Nicknames]] folder, all nicknames are stored here
|
|style = "background-color:lightgreen"| Merge.
|-
|.\common\'''objectives\'''
|[[Objectives]] folder, all objectives (i.e. ambitions, factions, and plots) are stored here. 
|[[Objective modding]]
|{{sup|?}} Merge
|-
|.\common\'''offmap_powers\'''
*policies\
*statuses\
|Defines nations not represented on the map, but with a significant influence over it.
|[[Offmap power modding]]
|{{sup|?}} Merge. Does NOT require [[Jade Dragon]] DLC.
|-
|.\common\'''on_actions\'''
|On_actions folder, all on_actions are stored here
|[[Event modding]]
|style = "background-color:lightgreen"| Merge. Since [[patch 2.4]] on_actions are merged, with new events being added to the previous list for a particular on_action, instead of replacing the list.
|-
|.\common\'''opinion_modifiers\'''
|[[Opinion]] modifiers folder, all opinion modifiers are stored here
|[[Modifiers]]
|{{sup|?}} Merge
|-
|style = "background-color:lightgrey"|.\common\'''province_setup\'''
|style = "background-color:lightgrey"|Deprecated since [[patch 3.0]].
|style = "background-color:lightgrey"|
|style = "background-color:lightgrey"|
|-
|.\common\'''religion_features\'''
|
|[[Religion modding]]
|style = "background-color:gold"|{{sup|?}} Merge, but features with the same key get duplicated
|-
|.\common\'''religion_modifiers\'''
|Religion_modifiers folder, all religion modifiers are stored here.
|[[Modifiers]]
|{{sup|?}} Merge
|-
|.\common\'''religions\'''
|Religions folder, all religions are stored here. 
|[[Religion modding]] <br/>
|style = "background-color:lightgreen"| Merge. Vanilla religions can be overridden, without needing to duplicate the whole religion group. Restrictions: need to define reformed religion before the non-reformed. 
|-
|.\common\'''religious_titles\'''
|Religious_titles folder, all religious titles are stored here
|
|{{sup|?}} Merge
|-
|.\common\'''retinue_subunits\'''
|[[Retinue]] subunits folder, all retinue subunits are stored here
|
|style = "background-color:gold"|{{sup|?}} Merge, but retinues with the same key get duplicated
|-
|.\common\'''save_conversion\'''
|
|[[Save game compatibility]]
|{{sup|?}} 
|-
|.\common\'''scripted_effects\'''
|
|[[Scripted effect]]s
|{{sup|?}} Merge
|-
|.\common\'''scripted_score_value\'''
|
|[[Scripted score value]]
|{{sup|?}} Merge
|-
|.\common\'''scripted_triggers\'''
| 
|[[Scripted trigger]]s
|style = "background-color:gold"| Merge, but scripted triggers with same name append their conditions rather than replacing the original one.
|-
|.\common\'''societies\'''
| Definition of [[societies]]
|[[Society modding]]
|style = "background-color:gold"| Merge, but override of societies by re-using same name does not work (creates duplicate societies)
|-
|.\common\'''special_troops\'''
|Special [[units]] definitions
|[[Unit modding]]
|{{sup|?}} Merge
|-
|style = "background-color:lightgrey"|.\common\'''stories\'''
|style = "background-color:lightgrey"|Not used.
|style = "background-color:lightgrey"|
|style = "background-color:lightgrey"|N/A
|-
|.\common\'''succession_voting\'''
|
|[[Succession modding]]
|{{sup|?}} Merge
|-
|.\common\'''trade_routes\'''
|[[Trade route]] definitions.
|[[Trade route modding]]
|{{sup|?}}
|-
|.\common\'''traits\'''
|[[Traits]] folder, all traits are stored here. 
|[[Trait modding]]
|style = "background-color:gold"| Merge, but traits with same name will co-exist, and generated characters may get both versions of the trait at the same time. The last definition gets assigned to a character when using commands.
|-
|.\common\'''tributary_types\'''
|[[Tributary]] relationship definitions.
|[[Tributary modding]]
|{{sup|?}}
|-
|.\common\'''triggered_modifiers\'''
|Defines global modifiers that trigger under certain conditions
|[[Triggered modifiers]]
|{{sup|?}} Merge
|-
|.\'''connectui\'''
| Appears to be leftover interface for the discontinued Paradox Connect service (used in older Clausewitz games CK2 is based on).
| Unusable
|
|-
|.\'''decisions\'''
|[[Decisions]] folder, all decisions are stored here
|[[Decision modding]]
|style = "background-color:gold"| Merge, but override of decision by re-using same name does not work (breaks the decision effect, that does nothing)
|-
|.\'''dlc\'''
|Contains DLC information and zipped content files
|[[DLC files]]
|N/A
|-
|.\'''dlc_metadata\'''
|?
|
|?
|-
|.\'''eu4_converter\'''
|[[Europa Universalis 4 Save Converter]] folder, all files related to the EUIV converter are stored here. 
Note: vanilla files were moved inside ''/dlc/dlc030.zip''
|[[EU4 Converter modding]]
|{{sup|?}}
|-
|.\'''events\'''
|Events folder, all events are stored here. 
|[[Event modding]]
|style = "background-color:gold"| Merge. If redefining an event in a file loaded alphabetically after the original file, the event will be fully overridden. 
Developers have discouraged this practice, as that engine behavior is not guaranteed to remain in the future (source ?)
|-
|.\'''gfx\'''
*ambitions\
*characters\
*coats_of_arms\
*cursors\
*eurfonts\
*event_pictures\
*flags\
*fonts\
*FX\
*interface\
*loadingscreens\
*mapitems\
*models\
*polishfonts\
*titles\
*traits\
|Graphics folder, all graphics are stored here.
|[[Graphics modding]]
Graphics are mapped to a logical name (GFX_xxx) inside .\interface\*.gfx files <br/>
'''Warning''': a missing flag for a title in flags\ will cause wrong flags to appear for most titles, due to a shift.
|
|-
|.\'''history\'''
|Historical data for characters, titles, provinces and wars for the possible start dates. This is a likely the text export of an internal database, which is sometime mentioned in the patch notes.<ref>http://www.ckiiwiki.com/Patch_2.0#Database</ref>
|[[History modding]]
|N/A
|-
|.\history\'''characters\'''
|Historical characters, optionally associated to a dynasty from \common\dynasties\ folder.
|[[Character modding]]
|style = "background-color:gold"| {{sup|?}} Merge. Duplicate character IDs break the character history and must be avoided.
|-
|style = "background-color:lightgrey"|.\history\'''diplomacy\'''
|style = "background-color:lightgrey"|Not used
|style = "background-color:lightgrey"|N/A
|style = "background-color:lightgrey"|N/A
|-
|.\history\'''offmap_powers\'''
|History of offmap powers (holder, status, ...)
|[[Offmap power modding]]
|{{sup|?}} Merge
|-
|.\history\'''provinces\'''
|History of provinces (holdings built, change of culture or religion)
|[[Province modding]]
|{{sup|?}} Merge
|-
|.\history\'''technology\'''
|Initial technology of provinces, depending on the start date.
|[[Technology modding]]
|{{sup|?}}
|-
|.\history\'''titles\'''
|History of titles (list of successive holders)
|Note: titles that should be deactivated at game start (ex: reformed religion heads) must have an history file that disables the title.
|{{sup|?}} Merge
|-
|.\history\'''wars\'''
|Important on-going wars (attacker, defender, Casus Belli, war score, ...), usually for historical bookmarks.
|
|{{sup|?}} Merge
|-
|.\'''interface\'''
*generalstuff.gfx
*sound.sfx
|Interface graphics
|[[Interface modding]]
*[[Sound modding]]
|style = "background-color:gold"| 
* Loading of *.gfx files is in alphanumerical order. Last spriteType definition loaded overrides previous ones with same name, if any (i.e. use zz_ file prefix to override vanilla sprites). 
* Only '''sound.sfx''' is taken into account, other .sfx files are ignored.
|-
|.\interface\'''coat_of_arms\'''
| 
|[[Coats of arms modding]]
|style = "background-color:gold"| Coat of arms definitions can be split across multiple files. No support for appending existing definitions from a different file.
|-
|.\interface\'''portrait_offsets\'''
| .txt files with external offsets for portrait frames
|[[Portrait modding]]
| 
|-
|.\interface\'''portrait_properties\'''
| Dynamic rules to select portrait properties values
|[[Portrait modding]]
| {{sup|?}}
|-
|.\interface\'''portrait\'''
| Definitions of spriteType and portraitType elements for portraits.
|[[Portrait modding]]
| Merge
|-
|.\'''launcher\'''
|Launcher graphics and configuration
|
|N/A
|-
|.\'''localisation\'''
|All text data for things like country names and event description, has options for other languages
|[[Localisation]]
|style = "background-color:lightgreen"|  Full override. If duplicates are in different files, first file loaded wins (i.e. use 00_ file prefix to override vanilla keys). If in same file, last duplicate in file wins. '''Warning''': files must end with '''.csv''' extension, or they will not be taken into account.
|-
|.\localisation\'''customizable_localisation\'''
| Custom [[Localisation#Commands|localisation commands]] definitions
|[[Localisation#Custom commands]]
|{{sup|?}} Merge. 
|-
|.\'''map\'''
*adjacencies.csv
*default.map
*definition.csv
*geographical_region.txt
*positions.txt
*provinces.bmp
*rivers.bmp
*terrain.bmp
*topology.bmp
*trees.bmp
*world_normal_height.bmp
|Map settings, province shapes, continents, regions etc.
|[[Map modding]]
|N/A
|-
|.\'''map\statics'''
|Map external frame size, and positions of fixed 3D map elements (wonders, etc.)
|[[Map modding]]
|
|-
|.\'''map\terrain'''
|
|[[Map modding]]
|
|-
|.\'''mod\'''
|Dummy mod folder, do not store mods here, use local mod folder
|[[Mod file]]
|style = "background-color:salmon"| Breaks mods, as configurations like replace_path are ignored.
|-
|.\'''music\'''
|[[Music]] used by the game
|[[Music modding]]
|{{sup|?}} All .txt files song elements are loaded.
|-
|.\'''sound\'''
|All sounds except music
|
|{{sup|?}}
|-
|.\'''tutorial\'''
|Tutorial configuration
|
|{{sup|?}}
|-
|}

==Specific guides==
{{hatnote|Only includes guides not already linked in the "How to mod" column above or otherwise.}}

* [[Troubleshooting]] - how to find errors in your mod
* [[Save-game editing]] - how to change a save game


* [[Patch 2.4 mod compatibility guide]] - how to migrate a mod from [[patch 2.3.6]] to [[patch 2.4.X]]
* [[Patch 2.5 mod compatibility guide]] - how to migrate a mod from [[patch 2.4.5]] to [[patch 2.5.X]]
* [[Patch 2.6 mod compatibility guide]] - how to migrate a mod from [[patch 2.5.2]] to [[patch 2.6.X]]
* [[Patch 2.7 mod compatibility guide]] - how to migrate a mod from [[patch 2.6.3]] to [[patch 2.7.X]]
* [[Patch 2.8 mod compatibility guide]] - how to migrate a mod from [[patch 2.7.2]] to [[patch 2.8.X]]
* [[Patch 3.0 mod compatibility guide]] - how to migrate a mod from [[patch 2.8.3.2]] to [[patch 3.0.X]]
* [[Patch 3.1 mod compatibility guide]] - how to migrate a mod from [[patch 3.0.X]] to [[patch 3.1.X]]
* [[Merging guide]] - how to merge mod files with a new vanilla patch


* [[Total conversion guide]] - Creating a total conversion mod
* [[Creating a mod exe installer guide]] - Advanced guide for creating a Windows installer

==Tools & utilities==

{{hatnote|These are utilities for modders. For player tools, see [[Mods#Utilities|utilities]].}}

* [http://notepad-plus-plus.org/ Notepad++] - Editor to change files, is better than normal editor
* [[forum:745679|Notepad++ language file for CKII]] - very helpful to read code
* [[The Validator]] - Support tool to find errors in files
* [[EU4:JoroDox mod making tool]] / [[forum:Tool-JoroDox-mod-making-tool.832866|Forum thread]] - View mod files & create CK2 compatible 3D models
* [[forum:651648|CK2 Cultures Parser]]
* [[forum:597290|Coat of Arms Builder]]
* [[Portrait Builder]] - Tool to preview character portraits
* [[forum:686024|Scenario Editor]]
* [[Titular Title Generator]]
* [http://www.textfixer.com/tools/alphabetize-text-words.php Text Fixer] - alphabetize your localisation file
* [[forum:984905|Paradox Province Color Picker]]

==Advanced tips==

*For the bigger mods using a source control management tool (Git, ...), it is handy to create a symbolic link between CKII mod folder and the working directory of the local repository, especially if the mod also has sub-mods. Note that you'll still need to copy the .mod file(s) manually, but they rarely change. Run the following command from the parent directory of main git folder, replacing:
** <mod_path_name> by the value of <code>path</code> attribute from .mod file
** <git_mod_folder> by the name of the sub-folder that contain mod data (folders common, decisions, events, etc...)
<pre>
mklink /J "%HOMEDRIVE%%HOMEPATH%\Documents\Paradox Interactive\Crusader Kings II\mod\<mod_path_name>" ".\<git_mod_folder>"
</pre>

===MOD调试===
毫无疑问，更多隐藏的控制台指令（在控制台输入help也不会显示的内容）对MOD测试会起到巨大的作用。
* observe - 让你进入观察者模式。此时你不再控制任何特定的角色——这会让游戏不受打断地自动运行。同时，所有隐藏特质、秘密信仰等对观察者都是可见的。
* run <filename.txt> - 直接运行特定脚本。脚本将从当前玩家控制角色的作用域开始执行。这个功能有助于测试复杂的脚本——你可以直接打开一个窗口编辑脚本，保存，重新载入，调整——省下重新打开游戏的时间。
* reloadevents - 重新载入和编译每一个事件（可能花费一会时间，取决于你的硬件）。对调试事件很有帮助，同样为你省下重新打开游戏的时间。
* reloadloc - 重新载入本地化文件，有助于确定文本是否显示在正确的位置上。

更多[[控制台指令]]可以在首页找到，用于实现杀掉某人之类的特定功能，这些对MOD测试同样必不可少。

==External links==

*[[Forum:589686|Modding - Quick questions]]
*[[Forum:847776|User mod Index/Guides/Utilities superthread]]

==See also==

*[[Mods]]
*[[Modding suggestions]]

==References==

<references />

{{ModdingNavbox}}
{{ModdingGuidesNavbox}}
[[Category:Modding|#]]