Resolved Existing 1.1.4 save loaded into 1.2 kingdoms with zero towns/castles do not get destroyed

[Kaihuligan]

Summary:
Loading an existing 1.1.4 save where I've got an enemy kingdom with zero castle or town fiefs left doesn't trigger the kingdom destroyed event that a save started in 1.2 would upon taking a kingdom's last fief

Played through for another 100 days or so of in-game time under 1.2, and they still remain as a kingdom without triggering it, suggesting they'll remain as an annoyance permanently (as per 1.1.4 and previous versions) unless you allow them to capture a fief and then take it off them?

How to Reproduce:
Load a save from 1.1.4 with an enemy kingdom without any fiefs.

Have you used cheats and if so which:
No.

 

[MArdA TaleWorlds]

Could you send us your save file where you are experiencing this issue?

Do you have a save file of the session that you experienced this issue? With your save file, we can reproduce the issue much easier and faster. You can find your save file here: "C:\Users\username\Documents\Mount and Blade II Bannerlord\Game Saves"
To send us a ticket, please visit the www.taleworlds.com site and login to your forum account from the top right. Click on "My Account" and then click on "My Open Tickets". You can create a ticket there and include the save file as well as the forum link of this thread. You can find more info about how to upload files to us with the new ticketing system here. Thanks for reporting and sorry for any inconvenience!

 

[Gadheras]

When there is a timer involved to trigger this, maybe the old save isn't compatible with this. If the trigger fire when their last fief is lost, while you load in save where they already have no fiefs left.

 

[Kaihuligan]

Hi MArdA, created a ticket with save game as requested. Cheers.

 

[uçanbiblo]

Hey, i have forwarded the issue to the QA team for further inspection. Thank you for your time and sorry for the inconvenience.

 

[GeorgeD]

Hey, i have forwarded the issue to the QA team for further inspection. Thank you for your time and sorry for the inconvenience.

This has been fixed in a recent patch

 

[uçanbiblo]

Hey, i am glad the problem is solved. Please let us know if you encounter any other issues.

 

[uçanbiblo]

Hey, i would like to inform you that our team have fixed this issue and the fix should be implemented. Please let us know if you encounter any other issues.