What real life governments is the Japanese Monastic Feudal government supposed to represent?
What real life governments is the Japanese Monastic Feudal government supposed to represent?
How can I raise my Mandate?
On the Japanese Wiki Corpus, I saw names frequently being written as (Clan) no (Name). Is that a valid way to do it?
As far as I know, the only way to get male concubines in the game is to be Bön (uneligible for Chinese Imperial), African (uneligible for Chinese Imperial) or a reformed faith with Equality/Enatic Clans (both uneligible for Chinese Imperial). As such, the Chinese Imperial government has no special provisions to modify concubinage for a female ruler, who would not have access to concubines. Technically, a reformed Shenist/Thanist/Muist faith with Equality/Enatic Clans is eligible for Eastern Imperial and such an Eastern Imperial EoC will benefit from the small additional number of consorts, however the Grace system is disabled for non-Chinese Imperial EoCs (due to it being based on the assumption that China is functioning roughly historically) so you'll have to use non-Grace methods to get male concubines anyways.Can female EoCs accept male concubines?
Can female EoCs accept male concubines?
Thank you to everyone who has made this amazing mod.
I am playing as the Liao Khagan at the 936 start. I have already discovered the helpful event to give me the Sixteen Prefectures. Great idea!
Is there any explanation of the decision(s?) to allow the Liao Khagan to claim the Mandate of Heaven and/or settle down as Chinese Imperial? I have JD (though not Rajas if that's relevant).
I've had a little look at the kom_khitan_decisions.txt file and it seems like I either need to settle (as feudal??)or acquire an Imperial bloodline by marriage (since none of the Liao characters seem to have one), [EDIT: on further digging through the files it seems that the Abaoji bloodline counts for this purpose? It's not clear in-game] but it's an understandably complex bit of script.
Please feel free to point me to a dev diary if it's already explained somewhere. I searched through this thread for such phrases and I got four pages of snippets for Liao, never mind the actual text of the posts, and it seems that many of the earlier dev diaries have long been superseded.
Thank you for the explanation! It makes sense given that's the interface for nomadic settlement too.Right click on the CoA of a county located in de jure e_china or the "China" region that's held by you, one of your vassals or below, one of your non-Chinese Imperial tributaries, or a vassal of one of your vassals or below, one of your non-Chinese Imperial tributaries and you should see the decision,
assuming you'd currently be eligible for the government based on culture and religion.
e_china = {
holder_scope = {
NOR = {
current_heir = {
character = FROM
}
}
# The AI should not do this if it shares the dynasty of the EoC
OR = {
FROM = {
ai = no
}
NOT = {
dynasty = FROM
}
}
}
}
e_china
is the de jure Empire of China. I am neither the holder nor the heir to the de jure Empire of China, nor am I the AI. If it's de jure, I should not be blocked. But I am. So I wonder whether there is some other bit of script that is relevant?Thank for the warning. I have now got Rajas via the Subscription Service to avoid this.However, the decision currently doesn't check for a potential game over due to an unplayable (after settling) religion, so you'd probably have some issues there if you're still Buddhist.
I took a quick look at the code and I think the issue is that you started in 936. In this start date e_china does not exist (due to the Five Dynasties and Ten Kingdoms not really having a "legitimate" Emperor of China as conceived of in Chinese histriography). As a result, when the game tries to make sure you're not already the heir to the EoC, there is no EoC to check against and it returns false by default. I'm pretty sure this is a bug, but I'm not sure whether it is fixed in the current dev build. It should be fixable by just adding an OR condition that checks whether e_china exists like this:But there is a mystery criterion "Empire of China" which is not explained in the tooltip. Looking at the script, it says:
e_china = {
OR = {
holder_scope = { # either you satisfy the condition relative to the current Emperor
NOR = {
current_heir = {
character = FROM
}
}
# The AI should not do this if it shares the dynasty of the EoC
OR = {
FROM = {
ai = no
}
NOT = {
dynasty = FROM
}
}
}
has_holder = no # or there is no current Emperor
}
}
That's very strange. My game (with all DLCs enabled) crashes immediately upon loading the "just after I replaced the Jin" save, and I can't open the file to check because my laptop is stubbornly insisting to me that the file is somehow corrupted. Exactly what combination of DLCs were active when you created this save? The only possible reason I can think of for the instant Game Over is that something weird happened with DLCs and it decided that you couldn't actually play as a Taoist on loading, since if you were able to create the save I assume you successfully took over the Jin Empire without getting a game over.When I try to load this save, I get an instant Game Over though.
[Snip]
I took a quick look at the code and I think the issue is that you started in 936. In this start date e_china does not exist (due to the Five Dynasties and Ten Kingdoms not really having a "legitimate" Emperor of China as conceived of in Chinese histriography). As a result, when the game tries to make sure you're not already the heir to the EoC, there is no EoC to check against and it returns false by default. I'm pretty sure this is a bug, but I'm not sure whether it is fixed in the current dev build. It should be fixable by just adding an OR condition that checks whether e_china exists like this:
<snip>
Thank you for this explanation and the bugfix. Yes, it works! The tooltip now lists an achievable condition. As the Liao of 936 (i.e. not subjugating the Jin), I can switch to Chinese Imperialism, save and reload (without Game Over).Regarding the decision not being available, I believe I did all of my testing in 1066, so a bug that only happens if China has no holder wouldn't have been caught. That should hopefully be fixable with @shenxy13's solution, so I suggest you try that. If it doesn't work, please let us know so we can troubleshoot that a bit further.
I think this mystery was cleared up by @Silversweeeper below, but for the record I had all DLC enabled except for the heavy metal music.That's very strange. My game (with all DLCs enabled) crashes immediately upon loading the "just after I replaced the Jin" save, and I can't open the file to check because my laptop is stubbornly insisting to me that the file is somehow corrupted. Exactly what combination of DLCs were active when you created this save? The only possible reason I can think of for the instant Game Over is that something weird happened with DLCs and it decided that you couldn't actually play as a Taoist on loading, since if you were able to create the save I assume you successfully took over the Jin Empire without getting a game over.
I could see it was a complicated bit of script but that must have taken quite a bit of effort to debug. Thank you so much for taking the time to investigate! I might investigate what happens if I switch to Chinese Imperialism after Subjugating the JIn at a later point, but in the circumstances it seems best just to forget about that approach and play from an earlier save now that I now how to use the Embrace Chinese Imperialism correctly. Or maybe I will try backporting the new Embrace Chinese Imperialism conditions checks from the GitHub into 13 if I am feeling ambitious during my Christmas holiday.As for the game over bug, I've discovered what's causing it, and it's a bunch of things coming together in a "fun" way. <snip>
In short, it's not something that I can provide a quick fix for, seeing as it's a lot of different things coming together and any quick fix that's not tested might result in new and exciting bugs. As the related events have been completely replaced in the dev version I'm instead going to focus on making sure that particular bug isn't in the next version when that releases.