While trying to create Ryujin Industries Background Checks Quest Start Fix I actually broke the next quest too by accident. Now I've fixed a potential failure to start for Ryujin Industries Guilty Parties Quest. Hoo ray!
Permissions and credits
Credits and distribution permission
Other user's assetsThis author has not specified whether they have used assets from other authors or not
Upload permissionYou are not allowed to upload this file to other sites under any circumstances
Modification permissionYou must get permission from me before you are allowed to modify my files to improve it
Conversion permissionYou are not allowed to convert this file to work on other games under any circumstances
Asset use permissionYou must get permission from me before you are allowed to use any of the assets in this file
Asset use permission in mods/files that are being soldYou are not allowed to use assets from this file in any mods/files that are being sold, for money, on Steam Workshop or other platforms
Asset use permission in mods/files that earn donation pointsYou are allowed to earn Donation Points for your mods if they use my assets
Author notes
This author has not provided any additional notes regarding file permissions
File credits
This author has not credited anyone else in this file
Donation Points system
This mod is opted-in to receive Donation Points
Changelogs
Version 1.1
Added additional flags that should prevent another quest blocking scenario where you may have prematurely entered syndicate HQ and killed guards prior to this mission preventing the quest from starting.
Determined that Ryujin Industries quest RI05 "Guilty Parties" fails to start if you have previously killed Ularu's door guard. Corrected quest alias conditions to allow for this actor to be dead. Quest now starts as expected after the quest "Background Checks".
If you've already failed to start the Guilty Parties quest, some console commands will be needed to get you back on track:
startquest 1EE0C8 setstage 1EE0C8 100
Idk when Bethesda will release official fix. This should be a simple temporary workaround.
