This is a known issue that appeared in the 10/7 update. We’re working on it.
As noted earlier, if you have a character who was jumped forward in their story (a while ago), you were reset back to the L26 step where you choose an order, so you won’t miss any content.
This has been covered a couple of times, though I can’t find one of the other threads now. Anyway, the “survivor” achievement (which didn’t quite work reliably) was replaced with a to-be-announced achievement that’s tied to the upcoming October holiday content.
My apologies, yes you’re right, it got bumped to the 10/22 update.
There’s a 6 page thread entitled “End Story Loot.”
https://forum-en.gw2archive.eu/forum/game/story/End-Story-Loot-spoilers/76517
TL;DR summary is: the 10/1 update changed the end game rewards to include 3 random green/yellow items, and a token that can be given to the Pact supply officer in Fort Trinity for a unique item. As of right now, there IS a bug, where the Pact officer is only available during the celebration story step, he’s intended to be available at all times once you’ve finished the story.
It was added in the 10/1 update I believe.
The marker is probably trying to display the shortest route from your current location, which would be through the asura gate at Vigil Keep. (It doesn’t know whether or not you can actually use the gate.)
I just tried it right now and it worked correctly. Note that the wind must blow at least once for the safety checkpoint to be enabled—you can’t just leap into the chasm to bypass the puzzle. Also, note that I’ve done this step dozens of times with no speed boosts/leaps/skills at all. You do need to stop about halfway across (behind the wall), there isn’t time (7 seconds between gusts) to run the entire way in one go.
What map are you in? The story start point is just outside Fort Triniry in the Straits of Devastation.
If you get knocked off during the jumping puzzle, you’ll be downed and teleported to the start. You can either bandage up and try again, or allow yourself to die and “Retry from checkpoint” which will set you past the jumping puzzle.
I’m trying to offer a possible workaround for a bug that I cannot reproduce after playing through the story step a dozen times. Since I can only test solo myself, it might be an issue with multiplayer.
It’s intended to be available for anyone who’s completed the story. I don’t know why, but the change didn’t make it to the live servers. We’re looking into it.
I’ve asked programming to look at it, since it seems to be isolated to the engineer, so it’s something out of my hands.
We’re looking into it, but we haven’t been able to reproduce after a dozen run throughs of the story step, so it’s a bit tricky.
1 – Try the story step solo. This appears to only happen if you play co-op (since more creatures are spawned.)
2 – Look around the from entrance of the fort, there’s occasionally a Risen who will hide out under/around the ramp leading into the fort.
As posted above:
1 – Try the story solo. This seems to only pop up when doing it with multiple players.
2 – Look around the gate, it seems to be a nefarious zombie that’s hiding out under/around the ramp leaing into the fort.
I’ve asked a programmer to look at this, sounds like the 10/8 update broke something.
Try running it solo, it might be a scaling issue.
EDIT: It looks like it’s set up correctly, so the only thing I can figure is that one of the undead is either spawning in a bad spot, or being pulled to a bad spot by combat. Check around all the routes they attack from, and check around the fortress gate, to see if any are “stuck”.
(edited by Jeffrey Vaughn.1793)
“We”? How many players were in the group?
We’ve now played through this about a dozen times with no blocking issues, so I’m having a hard time trying to identify the problem.
I’ve asked a programmer to look at it, what’s baffling is that it was fine about 2 weeks ago, and there’s nothing on the content end that appears to be incorrect.
If you’re stalled at the front gate, look around. There’s almost certainly a zombie hiding out somewhere. Once it dies, the next wave will spawn.
Every hostile (red) creature in Dredgehaunt has a very small chance to drop a key.
Failing the jumping puzzle will down you and out you back at the start so you can bandage up or try again, or die and skip the puzzle. (If you choose “Retry from checkpoint” after being knocked off the ledge, it will put you past the puzzle.)
What’s the paticular story step name? There are many steps that involve disguises, so I’m trying to narrow down the issue.
It’s been covered in other threads, but it’s a to-be-announced achievement related to the special October holiday content.
Neither of those are bugs, the first time you weren’t on the story step yet, and the second time, you were disconnected when the group completed the dungeon.
Would appreciate more information on this and how to best avoid running into problems.
Short answer: if you’re playing a Sylvari, don’t group with someone when they choose their order. The issue I’m aware of happens to secondary players who choose to advance their story past the “choose your order” story step, but never actually chose an order. (The player who “owned” the story step will be fine.)
[BUG] Party members getting sent to wrong faction when sharing their Personal Story
Posted by: Jeffrey Vaughn
The problem is that there is literally no difference between a character who intentionally picked the Vigil and one who got sent there by the bug, so there’s simply no way to automatically fix affected characters. Our CS team does not have the ability to change your current quest or order, either, so it’s not something that we can manually fix on a case by case basis, either.
[BUG] Party members getting sent to wrong faction when sharing their Personal Story
Posted by: Jeffrey Vaughn
What race were you playing? From what we’ve seen, only sylvari are running into this issue, so we’re testing a change to prevent this in the future. Unfortunately, we have no way of knowing if a given character chose their order, or was inadvertently sent to the wrong one, so I don’t anticipate a retroactive fix being made.
I don’t think it’s unreasonable to expect players to change up their weapons/traits if they’re finding that their current setup isn’t working for them. Trying to make all story steps the same difficulty for every single possible build is nigh-impossible.
As far as I know, any character who has completed the story will receive mail with the new reward(s). We’re not transmuting the old rewards or searching the character’s inventory for them, etc. so it doesn’t matter if you sold/salvaged/deleted them.
What is your current objective?
This is a different stall than was reported initially, and though I’ve never seen it I’m going to see if I can recreate it.
This is covered in the original “end story loot” thread.
https://forum-en.gw2archive.eu/forum/game/story/End-Story-Loot-spoilers/346959
TL;DR: 10/28 update will have both the retroactive reward, and an upgraded (GW1 token style) reward
There is a retroactive fix planned, and I’ve also been told that we’ll be using a GW1-style token system so you can choose a better reward item when you complete the story. (We agree that three green items isn’t cool enough.) I wouldn’t expect to see the new rewards and retro fix until the 10/28 update, though, because the upcoming holiday content is eating up our precious testing time.
(edited by Jeffrey Vaughn.1793)
Can you try rescuing the skritt in a seperate order? I suspect that rescuing the skritt in a different order than expected (the 2 downed skritt, then the one at the back of the cave) might be causing an issue.
EDIT: It might also be an issue with the last skritt being in combat or otherwise interrupted when he’s trying to play a scene, which then kicks off the final objective.
(edited by Jeffrey Vaughn.1793)
Update 2:
Sounds like the fixes passed stage 1 of testing, so they’re moving it into the 10/8 update for further testing. Specifically, this should fix the block for some folks when they talk to Trahearne at the start, and reduces a lot of the spawns across the story step. There’s still some funkiness with the enemies at the end displaying as white/yellow instead of red, but that’s a seperate issue we’re looking into for a later update.
This was covered in the bugs forum, but characters who were jumped ahead in their story were reset back to the step where you choose your order. A lot of players were upset about missing a significent chunk of content, and this was the most reliable way to address the issue. (An “opt-in” solution would have opened its own can of worms.)
You have to plug the leaks to stop them from spawning.
What’s your current objective? Can you talk to the Pale Tree if you manually select it before interacting? (If Trahearne and the Tree are the same distance away, it will randomly pick one to talk to if you don’t have one selected.)
Still not fixed, South gate bugged out 5 times in a row today.
What exactly does that mean? What’s your current objective? Did you lead Trahearne to the gate? Did he comment on it? Did you get the step to talk to him? Did you talk to him? Did he summon any help?
Update:
I just found and fixed (for reals) the problem with the story stalling when you tried to talk to Trahearne. Turned out to be some corrupt data, so it looked ok in some cases, but was failing on the Live server. While I was at it, I also thinned out a lot of the spawns. I’m still seeing weird name color issues at the end, and I’ve asked our programmers to look into it. (They’re showing up on the correct hostile team, but displaying the wrong color for some players.) It’s currently in the queue for our testing department to run through it, I’ve asked that this be expedited and added to the 10/8 update since this story step has been such a huge problem.
Since it’s 4:30pm local time, it won’t hit testing until tomorrow, but I’ll post another update once I get approval to add this to the 10/8 update.
Her appearance is based on the country of origin you chose for her. (Elona, Kryta, Ascalon, if I remember correctly.)
We’re tracking a general bug with joining other players in instances. There’s a long thread here:
I don’t know if you saw the thread in the Bugs forum about players who were skipped ahead as part of a workaround a few weeks ago. On Monday a code fix went in that reset those characters back to the chapter 2 step right before they pick an order. Many players expressed concern over the missed content and rewards, and this was the cleanest way to handle it.