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!

New Report Usability conflict with Knockout Framework

Messages
35
I have Knockout Framework installed (I primarily use it for a different character), and discovered a conflict when I went to claim Abernathy Farm as a vassal.
Basically, KF has a thing where the settlers dropped by the raiders are rendered unconscious during the attack. They aren't in the wounded state, though, so the quest doesn't count them as defeated.
The solution was to wake each settler one by one and beat them with Big Jim, but it's a weird chore to complete. Is it possible to work with KF, or should I just remove it?

Anyway -
 
Is it possible to work with KF, or should I just remove it?
I would suggest to disable/remove it, at least for now. It will probably require special handling in the Conqueror scripts &/or possibly even for Knockout Framework to do a patch or update for this. I would say that issues that affect many players are probably likely to take precedence over highly specific cases like this. Generally speaking, things that affect everybody or a very high percentage of players using Conqueror/Sim Settlements, are likely to be higher priority. Just my 2 cents, given that I suspect resolving this isn't going to be simple, scripts in Knockout Framework are complex I imagine & Conqueror has extremely complex scripts.

If you like you could try to ask the Knockout Framework author about it, to see if it might be resolvable from Knockout Framework's side of things. With the expansion having just launched, things are pretty busy at the moment.
 
That is a perfectly reasonable answer - to be honest, one I expected, too. If possible, can Knockout Framework be added to the potential conflicts list? That way, anyone else with the same perverse load order as me is aware?
 
That is a perfectly reasonable answer - to be honest, one I expected, too. If possible, can Knockout Framework be added to the potential conflicts list? That way, anyone else with the same perverse load order as me is aware?
I completely agree, though I don't have access to edit the wiki. If I see one of them online I might message them.
 
Confirming the problem. Solution: Disable humans from being able to be knocked out in Knockout Framework MCM before attacking the settlment. Then reenable them after the attack is over.

Should be documented somewhere (or more prominently if it already is), took me quite a while to figure out why the quest did not end even though all settlers were down.
 
Confirming the problem. Solution: Disable humans from being able to be knocked out in Knockout Framework MCM before attacking the settlment. Then reenable them after the attack is over.

Should be documented somewhere (or more prominently if it already is), took me quite a while to figure out why the quest did not end even though all settlers were down.
A great find! I would have assumed that Knockout Framework needed to be uninstalled, so this is cool that MCM can spot solve it when needed!

I believe @WetRats might be involved with the Wiki. I think this could be helpful to include somewhere on there.
 
A great find! I would have assumed that Knockout Framework needed to be uninstalled, so this is cool that MCM can spot solve it when needed!

I believe @WetRats might be involved with the Wiki. I think this could be helpful to include somewhere on there.

I could add a Known Mod Conflicts section.
 
No apology necessary.

I do think a Mod Conflict Sub-forum with big red flashing arrows pointing to it might save a bunch of people some headaches.
 
No apology necessary.

I do think a Mod Conflict Sub-forum with big red flashing arrows pointing to it might save a bunch of people some headaches.
I really think so as well. That way support & others who help can point to the relevant thread. I think it would streamline the process & save a lot of time in the long run.
 
Top