the Sim Settlements forums!

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Bug Cannot revassalize a lost settlement?

Gron the Barbariab

New Member
Messages
6
Playing with latest version of Sim Settlements Conqueror as a warlord in Survival mode. Note that I already had 3 functioning outposts and several vassals when this occurred.
  1. Captured Abernathy Farm with a small warrior force (who all died), then vassalized that settlement as a zero guard location (received warning that it was vulnerable, but did nothing).
  2. Some time later I received the message that Abernathy Farm had been lost to hostile forces.
  3. Returned to main HQ and saw in my war desk that assaulting Abernathy to vassalize was not an option.
  4. Traveled to Abernathy, thinking I needed to re-scout it - encountered Raiders who attacked me from inside the farm. Killed them all and swept the town. Civilians were all friendly to me, with no remaining hostiles. No status change in Abernathy (still independent).
  5. Returned to HQ, checked the war desk. Abernathy is still not listed as a valid vassal assault target, but it is on the list of valid targets for Outpost conversion.
Am I doing something wrong? Am I supposed to take it as an outpost, then change it into vassal?
I should note that I also have two 'outside the warlord network' settlements that I'm independently developing.

Thanks.
 

kinggath

Well-Known Member
Staff member
Administrator
Moderator
Verified Builder
Messages
3,663
I believe I have this figured out. Apologies no one responded to you @Gron the Barbariab - you had posted this in a category section that shouldn't have been possible so no one was able to respond - was just pointed out to me.
 

kinggath

Well-Known Member
Staff member
Administrator
Moderator
Verified Builder
Messages
3,663
Oh and I will have it fixed for next version (4.2.9a) but it likely won't fix saves retro-actively as there's no way to detect when this occurred currently. So I can at least prevent it from happening in the future.
 
Top