Forsaken High Plains Blues Bug

[ZTK211]

So I finally decided to get the 2 DLCs for forsaken and shadowkeep at the start of season 10, and i'm finally getting around to playing the forsaken DLC quest line now that finals are over. Everything was fine until I was asked to hack a terminal in High Plains Blues. I held E to hack the terminal, my ghost went out and did it's hacking/scanning animation, but (now 15 mins of waiting, and a attempt at abandoning and restarting the quest later) my quest isn't progressing, and i have no idea what's wrong. plz help

[gzilladude]

I've never encountered a bug like this before. Are you sure you are hacking the right terminal? There are scannable objects in the game. could it be you are accidentially scanning one of those lore objects?

[Handoiron]

I remember high plains blues being a bit ambiguous with it's progress markers at one point.

Basically your only prompt of what to do is ghost mentioning something about meeting some allies and not freaking out when you see them.

At that point, you're cut loose with no real direction of where to go. You are supposed to go towards the main part of tangled shore.

Basically you want to start moving from where you are towards meeting with spider in his hideout and you'll pick up the quest progress prompts as you travel there.

[ZTK211]

it's the terminal in the slaughtered camp that the game prompts and shows you exactly the terminal you need to scan. it's supposed to open a door to a smuggler's tunnel from what the tutorials i looked up said. like i cant even get past the first part of the map for this quest.

here's a video of the terminal i'm talkin about https://youtu.be/y4xAaW3Nbow?t=202
where the timestamp starts (3:21 if time specific link doesnt work, and just starts the video normally) is exactly the terminal i'm stuck at. it does the hacking animation but the passage doesnt get revealed

like it's pretty hard to scan the wrong object when the game is prompting you to scan this exact terminal

[ZTK211]

well i dont know what's changed, or when it changed, but it's finally working and i can move on with the quest line. i still got no clue as to what the cause of the issue was, but i'm just glad it's fixed now.