Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RI Executive Level Quest Start Fix #618

Closed
Constellation-VASCO opened this issue Nov 14, 2023 · 3 comments
Closed

RI Executive Level Quest Start Fix #618

Constellation-VASCO opened this issue Nov 14, 2023 · 3 comments
Labels
Fix Ready A fix for this issue is ready for merging and testing Platform: PC (Steam) This issue is being reported from the PC release of Starfield on Steam Type: Missions & Dialogue Relates to missions (quests), NPC dialogue or player dialogue options

Comments

@Constellation-VASCO
Copy link
Collaborator

Determined that Ryujin Industries quest RI08 "Executive Level" 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 "Sabotage".


Details

Interesting in rolling this into the community patch and joining for the long term so long as I become a contributor.

Determined that Ryujin Industries quest RI08 "Executive Level" fails to start if you have previously killed Ularu's door guard (17CF0E). Corrected quest alias conditions to allow for this actor to be dead. Quest now starts as expected after the quest "Sabotage".

If you've already failed to start the Executive Level quest, some console commands will be needed to get you back on track:

startquest 18B717
setstage 18B717 100

Game Version

1.7.36.0

Language

English (EN)

New Game

Yes

Reproduction Steps

Kill Ularu's door guard on executive floor in Ryujin Tower before starting RI08 "Executive Level".

@Constellation-VASCO Constellation-VASCO added Platform: PC (Steam) This issue is being reported from the PC release of Starfield on Steam Type: Missions & Dialogue Relates to missions (quests), NPC dialogue or player dialogue options labels Nov 14, 2023
@Constellation-VASCO
Copy link
Collaborator Author

Link to mod on nexus: https://www.nexusmods.com/starfield/mods/6819

@Pickysaurus Pickysaurus added the Fix Ready A fix for this issue is ready for merging and testing label Nov 14, 2023
@Constellation-VASCO
Copy link
Collaborator Author

Constellation-VASCO commented Nov 14, 2023

I've just looked at the quest script. From what I can tell, making the actor optional is fine.

If we use "Allow dead" it does mean that the dead guard will be teleported to Alias_SecurityPostFurniture or Alias_SecurityGuardMasakoFurniture which may not be desirable, especially if the actor has been cleaned up. It may be safer to just mark the guard as optional - but if the Alias fails to fill stages 1000 and 1100 will throw errors

@Constellation-VASCO
Copy link
Collaborator Author

I've added a variation of this fix, Alias_RyujinIndustriesSecurity is now marked optional (the other flags are not required). The quest script qf_ri08_0018b717 has been updated where it was using

Alias_RyujinIndustriesSecurity.GetRef().MoveTo(Alias_SecurityPostFurniture.GetRef(), 0.0, 0.0, 0.0, True, False)
Alias_RyujinIndustriesSecurity.GetRef().MoveTo(Alias_SecurityGuardMasakoFurniture.GetRef(), 0.0, 0.0, 0.0, True, False)

these have been replaced with

Alias_RyujinIndustriesSecurity.TryToMoveTo(Alias_SecurityPostFurniture.GetRef())
Alias_RyujinIndustriesSecurity.TryToMoveTo(Alias_SecurityGuardMasakoFurniture.GetRef())

this will avoid papyrus errors as GetReference() will return nothing on an empty alias.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fix Ready A fix for this issue is ready for merging and testing Platform: PC (Steam) This issue is being reported from the PC release of Starfield on Steam Type: Missions & Dialogue Relates to missions (quests), NPC dialogue or player dialogue options
Projects
Status: Closed
Development

No branches or pull requests

2 participants