Comments (13)
from imperatortock3.
We can also autogenerate the titles like I did for tag->title conversion.
from imperatortock3.
Yes, but I would suggest adding a regionMap.txt for some cases.
Syntax: link = { imp = lusitania_region ck3 = k_portugal rank = e }
Rank refers to the rank of the overlord. A governor will always be one rank lower (except for generated independent duchies, in which case governors would not be converted)
from imperatortock3.
Coats of arms of governors could be generated like this:
k_GOVERNOR_[ABC]_[XYZ] = {
sub = {
parent = "e_IMPTOCK3_[ABC]"
instance = { offset = { 0.0 0.0 } scale = { 0.5 0.5 } } # top left
instance = { offset = { 0.5 0.5 } scale = { 0.5 0.5 } } # bottom right
}
sub = {
parent = "[XYZ]" # defined elsewhere
instance = { offset = { 0.5 0.0 } scale = { 0.5 0.5 } } # top right
instance = { offset = { 0.0 0.5 } scale = { 0.5 0.5 } } # bottom left
}
}
Where ABC is the country in I:R and XYZ the region. All regions will be defined.
from imperatortock3.
Localisation for governors could be generated as "[ABC_adj] [XYZ]", where ABC is the I:R country, XYZ the region; e.g. a governorate in Cisalpine Gaul by the Romans would be generated as the Kingdom of "Roman Cisalpine Gaul".
Titles for governors would be generated as "k_GOVERNOR_[ABC]_[XYZ]". Governors for countries that are lower tier than Empires should be discarded. The governor of the capital region of the country will also be discarded. In all other instances, a governor will gain the generated governorate title and all counties that are found to be within it.
The governorate title will always have de_jure_drift_disabled = yes, can_be_named_after_dynasty = no, can_create = { always = no }
The governorate title will be defined as de jure part of the country it is part of.
E.g.:
e_IMPTOCK3_PRY = {
...
k_GOVERNOR_PRY_central_italy_region = {
...
}
}
The governorate title's history should look like this (recycling example from above):
k_GOVERNOR_PRY_central_italy_region = {
769.1.1 = {
holder = imperator123
liege = "e_IMPTOCK3_PRY"
government = feudal_government
succession_laws = { high_partition_succession_law }
}
}
high_partition_succession_law will mean that the successors of the governor will never hold two governorates at the same time.
from imperatortock3.
Governors for countries that are lower tier than Empires should be discarded.
Don't you mean kingdoms instead of empires?
from imperatortock3.
from imperatortock3.
Stuff left to do:
- Generate governorship colors with country color serving as base https://discord.com/channels/612683871112396800/692883287336681592/889701266035453984
- Convert governors under duchies to county holders
- The generated (not mapped to vanilla title) governorate title will always have
de_jure_drift_disabled = yes
,can_be_named_after_dynasty = no
,can_create = { always = no }
- If region has only 1 governorship:
- Don't add country adjective to name (example: Persis instead of Persian Persis)
- If region has multiple governorships:
- If any area in the region is at least 75% owned, use the area name for governorship name
- Fallback to name of most developed controlled territory
from imperatortock3.
The governorate title will always have de_jure_drift_disabled = yes, can_be_named_after_dynasty = no, can_create = { always = no }
@IohannesIohannium Should this also apply to vanilla titles from your mappings?
from imperatortock3.
No
from imperatortock3.
The "can't be created etc." part should be pasted only on regions that generate multiple governorates
Persian Persis would get it, Arachosia wouldn't, Ireland wouldn't, Carthaginian Portugal would
from imperatortock3.
The "can't be created etc." part should be pasted only on regions that generate multiple governorates
Persian Persis would get it, Arachosia wouldn't, Ireland wouldn't, Carthaginian Portugal would
Governorships being named <country adjective> <region name>
like "Carthaginian Portugal" should be extremely rare now (they're supposed to use area and province names instead), so I think the limitations to title creation and de jure drift are no longer needed.
from imperatortock3.
Coats of arms of governors could be generated like this:
k_GOVERNOR_[ABC]_[XYZ] = { sub = { parent = "e_IMPTOCK3_[ABC]" instance = { offset = { 0.0 0.0 } scale = { 0.5 0.5 } } # top left instance = { offset = { 0.5 0.5 } scale = { 0.5 0.5 } } # bottom right } sub = { parent = "[XYZ]" # defined elsewhere instance = { offset = { 0.5 0.0 } scale = { 0.5 0.5 } } # top right instance = { offset = { 0.0 0.5 } scale = { 0.5 0.5 } } # bottom left } }
Where ABC is the country in I:R and XYZ the region. All regions will be defined.
@IohannesIohannium if you want to proceed with this, please create a file with CoA definitions for regions. But I think it should be limited to only the regions that we know what should be used as flag for. I imagine it's a few at most. For the remaining governorships CK3 can just generate CoAs like it does now.
from imperatortock3.
Related Issues (20)
- Umbrian and Samnite name lists
- Convert defensive leagues
- Convert male pattern baldness when CK3 1.12 is released
- Broken carthage_pagan localization HOT 1
- Parallelize the conversion of colored emblems
- Convert character fertility
- Compatch for CK3 1.12
- Remove anachronistic legend seeds HOT 1
- Update the integration tests to optionally fail on converter warnings
- Add CB mapping for `maurya_decline_wargoal`
- Add vanilla CK3 setup option to the de jure setting
- Character converted to unexpected religion HOT 1
- Compatch for CK3 1.12.5 if needed HOT 1
- Crisis of the Third Century: convert major landowners as direct vassals HOT 1
- Crash on loading saved CK3 game with static de jure option + TFE
- TFE: characters can convert from Chalcedonian to Nicene HOT 1
- Unrecognized keywords in landed title definitions: `destroy_on_succession`, `can_destroy`, `ignore_titularity_for_title_weighting`
- Update province, religion and culture mappings for Invictus 1.8
- Chalcedonian is missing the Hof for AD 453
- Add invention mappings for TFE
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from imperatortock3.