USSEP breaks Forsworn Conspiracy and nobody's talking about it

[DragonbornVet]

I just hit the part where you confront Madanach in Cidhna Mine and the whole thing felt completely neutered compared to my last playthrough. Turns out USSEP "fixed" a bunch of the quest logic and now the guards don't actually turn hostile when they're supposed to, the dialogue branches feel broken, and honestly the whole moral weight of the quest just... evaporates.

I get that USSEP patches bugs, but this feels like it's patching the quest's teeth out. The Forsworn Conspiracy is supposed to be this claustrophobic betrayal where everything falls apart and you're genuinely unsure who to trust. Now it's just kind of a thing that happens and then you're done.

Has anyone else noticed this? I'm trying to figure out if I should just disable USSEP for this specific quest or if there's a patch for the patch or something. I don't want to uninstall it entirely because I rely on it for other stuff, but I'm genuinely considering rolling back to see if the "broken" version was actually better designed.

 

[WhiterunModder]

I haven't noticed the guard hostility thing specifically, but I'd be curious what exact behavior you're seeing. The Forsworn Conspiracy is one of those quests where the vanilla logic is genuinely messy - there's a lot of conditional flags that can get stuck depending on what order you do things in, so USSEP might've "fixed" it in a way that actually breaks the intended flow rather than restores it.

That said, I'd be skeptical about disabling USSEP wholesale for one quest. The dependency chain is brutal - you've got stuff relying on USSEP fixes downstream in your load order, and pulling it mid-playthrough can corrupt saves in weird ways. If you really want to test the vanilla behavior, honestly you'd need to start a fresh save without it from the beginning.

What I'd actually suggest is checking the USSEP changelog for that specific quest and seeing what they claim to have fixed. Sometimes the patch notes are vague, but if you can identify the exact change they made, you might find a user-made patch that reverts just that one thing, or at least understand whether it's actually a regression or just a different design choice. There's also a chance someone's already made a compatibility patch for this exact issue - the modding community's pretty thorough about catching when USSEP overshoots.

What dialogue branches felt broken to you? That might help narrow down whether it's actually a USSEP problem or something else in your load order interfering.