King Decisions can be delayed by Waiting past the deadline
Summary: As King, I can conquer a city, and use my Parade perk, Festivals, and a matching-culture Governor to farm Loyalty in a very hostile city. This is intended. What is probably not intended is that if I do the above set-up, then "Wait here for some time", the Kingdom Decision for owner of the city ignores the 48-hour timer until I leave the city/perform a game tick. I have repeated the trick, waiting in the city for 20~ days to get up to Loyalty 100.
However, the thing which I just saw caused a freeze-crash. I had a decision for Peace with the kingdom of the city I was attacking, but while I was sieging, the 48-hour timer wasn't ticking, so once I finished the loot screen, the game would freeze. My guess is that it didn't like the Towns Conquered data being messed with!
How to Reproduce: Be a kingdom ruler. Have a pending kingdom decision. Wait in a city or in a siege. Count the days. The decision will trigger once you exit the city, or conquer the siege.
Summary: As King, I can conquer a city, and use my Parade perk, Festivals, and a matching-culture Governor to farm Loyalty in a very hostile city. This is intended. What is probably not intended is that if I do the above set-up, then "Wait here for some time", the Kingdom Decision for owner of the city ignores the 48-hour timer until I leave the city/perform a game tick. I have repeated the trick, waiting in the city for 20~ days to get up to Loyalty 100.
However, the thing which I just saw caused a freeze-crash. I had a decision for Peace with the kingdom of the city I was attacking, but while I was sieging, the 48-hour timer wasn't ticking, so once I finished the loot screen, the game would freeze. My guess is that it didn't like the Towns Conquered data being messed with!
How to Reproduce: Be a kingdom ruler. Have a pending kingdom decision. Wait in a city or in a siege. Count the days. The decision will trigger once you exit the city, or conquer the siege.
