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

Quest bug: "Scan the Keepers" doesn't re-activate during "Jahleed's Fears" #189

Open
henbagle opened this issue Dec 20, 2022 · 2 comments
Open
Labels
Milestone

Comments

@henbagle
Copy link
Owner

Describe the bug
I started "Scan the Keepers" from Chorban, did the paragon thing of declining to continue to scan, then went to Jahleed and discussed with him to turn legit (paragon blue dialog option). Jahleed then asked me to re-start scanning for him, which I accepted.

However, the "Scan the Keepers" quest did not reactivate and the keepers remained inert. 

I checked for example on this page to confirm that the functionality should actually be available: https://www.ign.com/wikis/mass-effect/Jahleed%27s_Fears (details in the last section)

@henbagle
Copy link
Owner Author

henbagle commented Dec 20, 2022

Jahleed asking to start re-scanning is dependent on you telling Chorban that you will not scan for him anymore. Agreeing will set a bool that indicates that you got the quest from Jahleed. I'm not sure exactly what the bug is here, whether the quest should be re-opened (not sure if that's possible), or if Jahleed should not ask you to scan if you've already told Chorban you won't scan.

@henbagle henbagle added this to the 1.6 milestone Oct 28, 2023
@henbagle
Copy link
Owner Author

Going to re-architect this quest so that if you tell Chorban that you won't scan for him anymore, the quest enters a "resting" state where you can't scan the keepers but it's still in your journal. Once you finish the conversation with Jahleed, you can either keep scanning and the quest reactivates or you tell him no and the quest completes itself for good. Going to require lotso testing.

@henbagle henbagle modified the milestones: 1.6, 1.7 Dec 19, 2023
@henbagle henbagle modified the milestones: 1.7, 2.0 Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant