Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
On the positive side, I now tested carefully vanilla vs. Unop, and it seems our fix is working exactly as intended. After the new Unop version is released, the issue will be gone.
BTW, with just vanilla, the entire Sahara is locked, not just the corridors - but it's difficult for you to see the difference, because it's not easy to say what is "Sahara" and what are "corridors" without looking at the game code.
I deleted the file "00_building_requirement_triggers.txt" and now I could build holdings, while the crossings in Sahara (such as those from Kanem to Lybia) were still locked from new holdings, as intended.
Regarding the skill points, their bases are updated, so unless you are checking them right before and after the visit you might not notice the difference. Which skill point exactly is determined by the "court type" if the capital (if the ruler has a royal court), or random otherwise.
Basically, in 1.13.2, Paradox prevented holding construction in the entire Sahara region if the terrain is Desert or Desert Mountains.
In 8.0.32 (latest version), @Kazarion fixed this, except for provinces that are "corridors", since this was the original intention of the Paradox fix.
So just for these 19 provinces, it is not possible, and this is intended. Anywhere else it should be possible.
I tried with a ruler who doesn't hold a holy site with the same result.
I also examined the old fix mod. The code is indeed quite old and I don't have the CK3 base files of that version to compare, but from what I could guess by comparing to newer version files, the fix seems to have been meanwhile adopted in CK3.
If you are able to reproduce the issue in vanilla without any mods, please open an issue with us with the exact steps to reproduce it.