-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
I tried adding Holdings and that has not changed anything. I also tried using V9 of the tool (which is the most recent old version I have) and that one appears to work perfectly.
I think some ill advised design has snuck into the map filler tool.
I've added some config settings to disable certain things. But apparently for one of those I didn't make the logic: setting not there -> do what you always did
Basically you'd have to add this to make it bahave like before:
writeTitleHistory=true
Normally for all titles that do not yet exist in history/titles a title file is created with the header as set in the config file and with the de jure liege set as liege. With that setting you can disable that (for whatever reason).
Or wait for a fix. But that'll probably take some time as that would be the only content of that bugfix release.
v9 shouldn't really work anymore.
Make sure that you have added the climate (winter!) column. Without that column it shouldn't really work anymore.
I've added some config settings to disable certain things. But apparently for one of those I didn't make the logic: setting not there -> do what you always did
Basically you'd have to add this to make it bahave like before:
writeTitleHistory=true
Normally for all titles that do not yet exist in history/titles a title file is created with the header as set in the config file and with the de jure liege set as liege. With that setting you can disable that (for whatever reason).
Or wait for a fix. But that'll probably take some time as that would be the only content of that bugfix release.
v9 shouldn't really work anymore.
Make sure that you have added the climate (winter!) column. Without that column it shouldn't really work anymore.
Last edited:
Thanks for the reply! When I said v9 worked I meant it was able to create the history files. Anyway, thanks to your help I've been able to get my mod working. Could not have done any of this without your tools and guides!
I need help how to fill positions.txt :unsure: I try to creating map manual without any software. My project successfully, but I see no province and character holder. I'm pretty sure that cause positions.txt :unsure:
Edit: Here is my question, How to get the position numbers?
Edit: Here is my question, How to get the position numbers?
Hard to really understand what you are trying to say.
If you are using the latest version you need to make sure that you have "writeTitleHistory=true" in your config file. This is a fix for a little screw-up from my side.
If you have this history/titles will be generated. If not you'll have a count-only world.
positions are something completely different: To have correct positions you'd need to load up with the nudge tool (there's a flag in CK2's settings.txt). Then set all positions accordingly.
You also said that you see "no province and character holder". You will only see county holders if you assign characters to titles (in the history folder).
The game seems to not load special charactered counties still, all the counties in my Norway and Iceland with Thorn or Eth aren't being loaded.
You said that before, I know. But I can't quite figure out why Thorns would be a problem. Do you have some example lines from the spreadsheet that do not work?
In the beta, there was some minor change in the way the game handles province names with special characters. For most purposes, the names have been converted to not use those characters. Using Osnabrück as an example:
The real name with special characters goes in localisation/text1.csv:
Code:
PROV87;Osnabrück;Osnabrück;Osnabrück;;Osnabrück;;;;;;;;;xThe sanitized version appears everywhere else:
File name: 'history/provinces/87 - Osnabruck.txt'
In map/definition.csv:
Code:
87;84;48;171;Osnabruck;xThe devs went to considerable effort to sanitize the names in definition.csv, and to insure every used province in that file had some name. I have to assume they did so for a reason. I saw a comment that the definition.cv name is used to connect to the province history file name, but I haven't verified that.
Yeah, I know that jursamaj. I even released a version before that was supposed to address this issue. The umlauts are working now afaik. Only the Thorns and Eths seem to not work. Maybe the devs are normalizing those letters in a different way than I do. I am replacing thorn with th and Eth with dh. I'll need to do some digging to track this down.
Edit:
I just realized that þ and Þ are two different characters ^^
Am I still missing a letter?
put('œ', "oe");
put('þ', "th");
put('Þ', "Th");
put('ð', "dh");
put('Ø', "O");
put('ø', "o");
put('À', "A");
put('Á', "A");
put('Â', "A");
put('Ã', "A");
put('Ä', "A");
put('Å', "A");
put('Æ', "Ae");
put('Ç', "C");
put('È', "E");
put('É', "E");
put('Ê', "E");
put('Ë', "E");
put('Ì', "I");
put('Í', "I");
put('Î', "I");
put('Ï', "I");
put('Ð', "Dh");
put('Ñ', "N");
put('Ò', "O");
put('Ó', "O");
put('Ô', "O");
put('Õ', "O");
put('Ö', "Oe");
put('Ø', "O");
put('Ù', "U");
put('Ú', "U");
put('Û', "U");
put('Ü', "U");
put('Ý', "Y");
put('Þ', "Th");
put('ß', "ss");
put('à', "a");
put('á', "a");
put('â', "a");
put('ã', "a");
put('ä', "ae");
put('å', "a");
put('æ', "ae");
put('ç', "c");
put('è', "e");
put('é', "e");
put('ê', "e");
put('ë', "e");
put('ì', "i");
put('í', "i");
put('î', "i");
put('ï', "i");
put('ð', "dh");
put('ñ', "n");
put('ò', "o");
put('ó', "o");
put('ô', "o");
put('õ', "o");
put('ö', "o");
put('ø', "oe");
put('ù', "u");
put('ú', "u");
put('û', "u");
put('ü', "u");
put('ý', "y");
put('þ', "th");
put('ÿ', "y");
put('š', "s");
put('Š', "s");
put('œ', "oe");
put('ž', "z");
put('Ÿ', "Y");
Edit:
I just realized that þ and Þ are two different characters ^^
Am I still missing a letter?
put('œ', "oe");
put('þ', "th");
put('Þ', "Th");
put('ð', "dh");
put('Ø', "O");
put('ø', "o");
put('À', "A");
put('Á', "A");
put('Â', "A");
put('Ã', "A");
put('Ä', "A");
put('Å', "A");
put('Æ', "Ae");
put('Ç', "C");
put('È', "E");
put('É', "E");
put('Ê', "E");
put('Ë', "E");
put('Ì', "I");
put('Í', "I");
put('Î', "I");
put('Ï', "I");
put('Ð', "Dh");
put('Ñ', "N");
put('Ò', "O");
put('Ó', "O");
put('Ô', "O");
put('Õ', "O");
put('Ö', "Oe");
put('Ø', "O");
put('Ù', "U");
put('Ú', "U");
put('Û', "U");
put('Ü', "U");
put('Ý', "Y");
put('Þ', "Th");
put('ß', "ss");
put('à', "a");
put('á', "a");
put('â', "a");
put('ã', "a");
put('ä', "ae");
put('å', "a");
put('æ', "ae");
put('ç', "c");
put('è', "e");
put('é', "e");
put('ê', "e");
put('ë', "e");
put('ì', "i");
put('í', "i");
put('î', "i");
put('ï', "i");
put('ð', "dh");
put('ñ', "n");
put('ò', "o");
put('ó', "o");
put('ô', "o");
put('õ', "o");
put('ö', "o");
put('ø', "oe");
put('ù', "u");
put('ú', "u");
put('û', "u");
put('ü', "u");
put('ý', "y");
put('þ', "th");
put('ÿ', "y");
put('š', "s");
put('Š', "s");
put('œ', "oe");
put('ž', "z");
put('Ÿ', "Y");
Last edited:
Well, there don't appear to be any province/county names vanilla with thorn or eth in them. But it doesn't look like it would matter how you normalize it, as long as you make it the same everywhere but localization.
jursamaj you are absolutely right. As long as they match we should be fine.
I wonder why Biskupsruð did not work. ð should've been normalized to dh. Is the title named correctly in landed_titles, Keanon?
I wonder why Biskupsruð did not work. ð should've been normalized to dh. Is the title named correctly in landed_titles, Keanon?
Landed titles were fine, but some some reason the program didn't update Biskupsrud to Biskupsrudh when I reran it after the update.
Edit: Inside Title History that is. Important detail right there.
Edit: Inside Title History that is. Important detail right there.
I need to release a new version with all the updated normalisation values soonish. But there is a minor bug that I caused in that last version: As stated earlier on this page you'd need to have writeTitleHistory=true in your config.properties to get history/titles created (fixed in that sooni-ish next version).
Some additions that could be awesome are:
-a way to specify a date for title history other than 1066.1.1
-two new coumns, one to define succession law and another for gender law. Empty means agnatic primogeniture per depault.
-a third column that function as a switch. If set to 1 the mapfiller would create a character of appropriate culture and religion. That would make the scenario editor more funcional too, since you could quickly change ownership of titles between characters, specially in areas where you don't have interest in creating specific characters.
-a way to specify a date for title history other than 1066.1.1
-two new coumns, one to define succession law and another for gender law. Empty means agnatic primogeniture per depault.
-a third column that function as a switch. If set to 1 the mapfiller would create a character of appropriate culture and religion. That would make the scenario editor more funcional too, since you could quickly change ownership of titles between characters, specially in areas where you don't have interest in creating specific characters.
Thanks for your suggestions!
Have you taken a look at config.properties? Some dates are specified right there and can be changed to your preferred year!
Currently only a title file is generated (with the laws as stated in the config file) if none is present. Would that gender law be enforced onto those titles or only written on initial creation?
Generating characters for titles is an iffy thing: You probably want to generate a character, a dynasty (in common/dynasties) for that character. For that you would need a dynasty name. Then a bunch of relatives would make sense, too. You know, so that the liege doesn't inherit a bunch of counties if that guys from syphilis.
But yeah, if you come up with a re-run friendly way to do this I might integrate functionality of my character editor into the map filler. Would be helpful in a number of cases.
Have you taken a look at config.properties? Some dates are specified right there and can be changed to your preferred year!
Currently only a title file is generated (with the laws as stated in the config file) if none is present. Would that gender law be enforced onto those titles or only written on initial creation?
Generating characters for titles is an iffy thing: You probably want to generate a character, a dynasty (in common/dynasties) for that character. For that you would need a dynasty name. Then a bunch of relatives would make sense, too. You know, so that the liege doesn't inherit a bunch of counties if that guys from syphilis.
But yeah, if you come up with a re-run friendly way to do this I might integrate functionality of my character editor into the map filler. Would be helpful in a number of cases.
Thank for the pointer to the configuration file!
As for laws, I'd say rewritten with every rerun: If you use the mapfiller for that, then either it is your first run or you are making so masdive a change that it compensates the potential lose of other information.
As for characters. I would be fine with a dummy character per province, with "of <province>" and perhaps spose and couple children, though I would be fine with just the ruler.
Also, if landed titles files would be written in different files, sorted by empire, that would help when doing msnual modifications i some are and the reworing the map in another
As for laws, I'd say rewritten with every rerun: If you use the mapfiller for that, then either it is your first run or you are making so masdive a change that it compensates the potential lose of other information.
As for characters. I would be fine with a dummy character per province, with "of <province>" and perhaps spose and couple children, though I would be fine with just the ruler.
Also, if landed titles files would be written in different files, sorted by empire, that would help when doing msnual modifications i some are and the reworing the map in another
I was pondering myself if a file per empire + 1 for all left-over kingdoms would be a better solution.
But why would you manually change it? It is not really necessary at all and takes away the possibility to do mapfiller re-runs :huh:
But why would you manually change it? It is not really necessary at all and takes away the possibility to do mapfiller re-runs :huh: