Welcome to the AFK Mods bug tracker. In order to report an issue, you need to have a VALIDATED account to post one. Once you have followed the link the registration email sent you, please select a project from the drop down menu below. Select “Open New Issue” and fill out the form with as many details as possible.

Please also consider sending your bug report to Bethesda if you are reporting on an issue with Skyrim Special Edition, Fallout 4, or Starfield. Doing so will help everyone on all platforms.

Issue Data
Status: Closed
Issue Type: Bug Report
Project: Unofficial Skyrim Special Edition Patch
Component: Skyrim SE: Vanilla
Category: Quests & Dialogue
Assigned To: Nobody
Platform: Windows PC
Severity: Medium
Votes: 0
Watching: N/A
Opened By iJM on Feb 2, 2021 5:10 pm
Closed By Arthmoor on Mar 13, 2023 11:58 pm
Resolution: Not A Bug

Issue #29565: Some problems with WIAssault01 and WIAssault02

 
Aren't WIAssault01 and WIAssault02 should have aliases allowing reserved?

Also, I think that something is wrong with condition "GetEventData, GetValue, Crime, NONE" == 1 in quests in WIAssaultNodeA.

In order to test efficiently I've set WIEventChance to 100, then removed that condition from WIAssault01 and left it untouched in WIAssault02.
(And I've set those aliases to Allow Reserved: Attacker, Relative, Victim).
You can see log here: https://pastebin.com/GKDbiNdJ

It seems that WIAssault02 never starts because of failed condition.

Maybe it should be using "Crime Status" instead of "Crime", just like WIKill06? I don't know.

Comments

1 comment(s) [Closed]
Arthmoor said:
 
There isn't anything wrong with these quests - for starters, the whole node has only a 30% chance of running at all. Then you have to have run out the timer between instances.

All in all, it's not supposed to be a super common thing and appears to be behaving properly.

Comment #1 Mar 13, 2023 11:58 pm
Showing Comments 1 - 1 of 1