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

Stirrup quest is incorrectly requiring The Extortionist #311

Open
tarkovplayer opened this issue Jan 11, 2023 · 5 comments · May be fixed by #312
Open

Stirrup quest is incorrectly requiring The Extortionist #311

tarkovplayer opened this issue Jan 11, 2023 · 5 comments · May be fixed by #312

Comments

@tarkovplayer
Copy link

I don't know if it has other unlock requirements but I had Stirrup available in the game before completing The Extortionist.

@ambassador86
Copy link
Contributor

I also had it available before.

@tarkovplayer
Copy link
Author

tarkovplayer commented Jan 11, 2023

completing Acquaintance also unlocked The Tarkov Shooter - Part 1 for me without completing The survivalist path - Unprotected, but dangerous (which is also unlocked by Acquaintance)

@RussMcGill
Copy link

@tarkovplayer According to the wiki, Acquaintance unlocks both The Tarkov Shooter - Part 1 and The survivalist path - Unprotected, but dangerous simultaneously, is that not correct?

RussMcGill added a commit to RussMcGill/tarkovdata that referenced this issue Feb 9, 2023
@RussMcGill RussMcGill linked a pull request Feb 9, 2023 that will close this issue
@tarkovplayer
Copy link
Author

I don't remember now why I was commenting that; I thought I didn't see both quests active on tarkovtracker at the same time, looking at the data that should already have been the case though (and I can reproduce that it works as expected now).

@RussMcGill
Copy link

Ok cool. Well the original issue should be fixed once the pull request is reviewed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants