Repository navigation
Help
| Table of Contents |
|---|
| Set Up |
| The Tool |
| Export |
| Usage |
| What Else |
Everything is pretty self-explanatory. Create a .csv file with the following pattern:
County;County Capital;Barony 1;Barony 2;Barony 3;Barony 4;[...];Barony 6;
Carcosa;Carcosa;Alar;Hastur;Ys;;;;;
Miskatonic;Arkhem;Salem;Ipswich;Kingsport;Beverly;;
Diamond City;Diamond City;Bunker Hill;Sanctuary Hills;Vault 81;Concord;Covenant;Abernathy Farm;
Stormfalls;Stormfalls;Hightown;Caldera;Johnslanding;Baymarket;
Smallvillage;Smallvillage;Sometown;Lastfarm;;
The first entry is the name of the county, every subsequent entry is the individual baronies (make sure each line ends with a ; or else really awkward formatting will occur, but it should still work in-game).
The best way is to have a separate excel spreadsheet for the project with all the important information, an example can be seen here or here.
Hint: The
.csvis case-sensitive. I highly recommend to proper capitalisation or else the final localisation in-game will look weird, but you don't have to.
Hint: To help set up
.csvfiles, see this entry on the wiki; Localisation#Editing. For Atom.io users, there's this helpful package: tablr (p.s. use @mfripp's great fix)
Start the tool with ProvinceSetUpper.py. Once opened, simply load the .csv file and adjust the settings as needed:
- Start ID: The ID of the first province in the list.
- Religion, Culture, Terrain: The religion/culture/terrain all provinces will share.
- Is Tribal: If unchecked, will create Castle/City/Temple. If checked, will only create a Tribal holding and leave the rest empty.
- Temple Dist.: If Is Tribal is checked, this is the percentage chance that a temple holding will be added (e.g. 20% roughly one in five counties will have temples).
-
RGB Base: The base colour all titles should share. Every title will slightly deviate from this base colour. So, if the RGB Base is set to something like
(255, 60, 0)all titles will have some slightly different shade of red.
Hint: The settings are not case sensitive and will always create lower case outputs since that's what CK2 uses. And just for the record, yes you can and are intended to write in your custom culture/religion. Spaces will turn into underlines.
Hint: The settings are saved between sessions in the 'config.ini'
Simply drop the appropriate .tga image files into the Databases\Flags folder. They can have any name, it only matters that they're the proper format (CK2 wants .tga and 128x128). The tool will randomly pick flags from the folder and distribute them across the counties. It will only use each flag once, unless there are more provinces than flags, in which case it will re-shuffle them and start again.
If 'Flag Removal' is checked, the used flags will be put moved into the 'Databases\Flags\Removed' folder, if you want to make sure no flags are re-used between sessions or for keeping track.
Hint: Even without checking 'Flag Removal', you can see the flags that were assigned to which county by checking the 'setupper.log'.
Once everything is set, just click on Write, and all the appropriate files will populated the Output folder (will be created if it doesn't exist already).
Hint: This will overwrite already existing files of the same name. However, some files (like localisation, province set-up etc.) are numbered based on the Run ID of the current run. The current Run ID can be found in 'config.ini' or the 'setupper.log'
Now that all the files exist, simply move them over into your mod.
- The
history/andgfxfiles can be moved over as-is. - The contents of the
localisation,landed_titlesandprovince_setupshould be copied into their relative files.
While you can play with all the created files, they should be seen as a foundation and further refinement should be done by hand where wanted or needed.
Best is you check out the Map modding entry on the wiki. This tool basically takes care of most of the Adding a province step, which is the most time-consuming and annoying step.
Apart from those files, keep in mind you obviously still need to make the actual map(s) and don't forget to take care of definition.csv and to update default.map.