Issue Data
|
|
||||||||||||||||||||||
Forgot to mention: the version of USSEP I got the bug on was 4.3.6c, not the most recent 4.3.7.
Here's a patch with a simple but not perfect fix for the issue. It just adds a "Player accepted CR04" condition to the CR04 line in DGIntimidateVictoryYes topic. The condition was inspired by a similar one in the dialog lines that start CR04 brawls.
The setup of DGIntimidateVictoryYes topic is: the CR04 line is at the top of the order, the other 19 options could be spoken only by 19 different and unique actors, so one option per one actor (kinda, one of the 19 actors is "orc chieftain" job faction, but whatever). So the fix will work fine if the player hasn't accepted the CR04 job from Farkas yet. But when the player has both the Farkas job and some other way to start a brawl with one the 19 NPCs, it becomes murky again, and I guess it couldn't be fixed without a major rework of the whole brawl system.
The setup of DGIntimidateVictoryYes topic is: the CR04 line is at the top of the order, the other 19 options could be spoken only by 19 different and unique actors, so one option per one actor (kinda, one of the 19 actors is "orc chieftain" job faction, but whatever). So the fix will work fine if the player hasn't accepted the CR04 job from Farkas yet. But when the player has both the Farkas job and some other way to start a brawl with one the 19 NPCs, it becomes murky again, and I guess it couldn't be fixed without a major rework of the whole brawl system.
Comment #2 Feb 26, 2026 6:12 pm
Edited by gavrant on Feb 26, 2026 6:15 pm
Apparently, the site's anti-spam or something does not like my attachments? So here's a text version of the patch:
In dialog info 00047AD6 add this condition: Subject.GetVMQuestVariable(CR04 [QUST:00025231], ::IsAccepted_var) = 1
and just in case change Previous INFO field of that info to NULL in xEdit.
In dialog info 00047AD6 add this condition: Subject.GetVMQuestVariable(CR04 [QUST:00025231], ::IsAccepted_var) = 1
and just in case change Previous INFO field of that info to NULL in xEdit.
Comment #3 Feb 26, 2026 6:26 pm
Edited by gavrant on Feb 26, 2026 6:32 pm
I don't think this bug is specific to Favor013. I had pretty much the exact same thing happen to me with Favor017 once. I forget who I did it with, but CR04 was pointing to one of Favor017's givers, and I opted to do Favor017 first, but after I beat them, I got the CR04 dialogue instead of the Favor017 dialogue. I wouldn't be surprised if this could also happen with TG01 and FreeformRiften19, and any other quest that involves initiating a brawl.
Comment #4 Mar 2, 2026 5:13 pm
Edited by SkyLover on Mar 2, 2026 5:14 pm
SkyLover, you're right, that post-brawl dialogue topic deals with a bunch of quests indeed. But the thing is: almost all of them are attached to very specific unique NPCs (Mikael, Rolff, etc.) and those NPCs have only one single post-brawl line, so these lines can't conflict with each other. The 2 exceptions that target multiple NPCs are the CR04 line and one for orc chieftains (0006FAB8, Favor017-related, and it does not appear to collide with anything else there, even with CR04). So it's enough to fix the CR04 one for the problem to go away, I think.
I've been unable to get Farkas to offer CR04 at all ever since I was still doing the Companions questline. If there are conflicts like these that mess up quests, it makes me wonder if that's why CR04 won't come up as a radiant.
Showing Comments 1 - 6 of 6

Issue Data