Duplicate CK III - Weird Duchy setup in 1066 Abyssinia

[Pepper13900]

Short summary of your issue
Weird Duchy setup in 1066 Abyssinia

Game Version
1.5.1

What OS are you playing on?
Windows

What platform are you using?
Steam

What DLC do you have installed?
Royal Court,

Do you have mods enabled?
No

Have you tried verifying your game files (Steam only)?
No

How much "pain" is this causing you?
3

Please explain the issue you experienced in the most condensed way possible
I don't know if it is intended, but I find strange that the mesfin/duke of Aksum starts with a duchy title (Petty Kingdom of Aksum) that doesn't correspond to his starting duchy territory (Petty Kingdom of Gondar), and that belongs to the neighbouring negus/king of Abyssinia.

For its part, the negus/king of Abyssinia holds the duchy title of the mesfin/duke of Aksum's territory (Petty Kingdom of Gondar), and none of its own starting territory.

They therefore hate each other's guts out - making for a rough start for the "Beta Israel" achievement with the mesfin of Aksum, as you can't even swear fealty to try to eat up the Abyssinia kingdom from the inside.

Please explain how to reproduce the issue
Launch a game at the 1066 start date. This setup is visible from the start.

Is there anything else you think could help us identify/replicate the issue?


I have attached a save game
No

Upload Attachment
File(s) attached

 

[Pepper13900]

Hi,

Sorry to bump up this thread, but the situation is the same in 1.7.0 "Bastion".

It sounds like it would only need a database tweak to fix this setup.

Thanks a lot for this new update, anyway !

 

[Pepper13900]

Hello,

Just checked : the situation is the same in 1.8.0 "Robe".

Thanks !

 

[Pepper13900]

* waves frantically at the QA team *

Still this weird setup in 1.9.0.4 "Lance".

Thanks !

 

[Chaotic Raven]

After all this time, your waving worked, hello there! We've already confirmed this issue, but thank you for your report, help and of course determination!

Also if you want to let us know about an issue we could potentially miss or wasn't just fixed in newer versions, you should check if this old report is not in our archive, as there is new way to report issues - in situations like that for better visibility just create new report using new reporting system!

And again, thank you for your patience!

 

[Pepper13900]

Thank you for your kind reply !

It's duly noted for future bug reports : I will do that.