Guild Wars 2

Pedra.4381:

So ArenaNet devoted programming and resources to ensure that a “determined” potentially abusive player could not receive this achievement and in doing so inconvenienced thousands of players who just want to play the game?

Just the opposite, really. I didn’t implement this particular achievement, so I can’t really go into detail on the the specifics, or speculate on future plans, but the current system is a simple brute force solution to keep people from trying to cheat death by zoning/disconnecting/etc.

Did you check inside the Kraal? The Branded bombard the village itself, so you won’t see them running in from outside like in the first 2 waves.

That looks to be an issue with players loading it at vastly different times, so “late” players don’t get the message to start the scene. I’ll fix it up after the holidays. For now, running it solo will work correctly.

What’s your current objective?

“Fighting the Nightmare” is the tutorial that all sylavari do. The full storyline is “Awakening”, “Holding Back the Darkness”, “A Sly Trick”, “Deeply Tangled Roots”, and a final step based on what you choose to do at the end.

What did you do for levels 1-10? “Fighting the Nightmare” and “Awakening” are the first 2 steps in the shield storyline.

Chapter 1 (levels 1-10) revolve around the white stag, the shield, or the green knight, depending on your character creation choices. What’s your current story step objective?

Known bug, will be fixed in the Wintersday content update.

The original post is about crashing, the trebs are another matter. If you have “Fast cast ground targeting” turned on in options, it will try to fire the trabuchet at your mouse cursor, which you might have in a bad spot. Also, many siege weapons require you to hold down the fire button to “charge” the shot, or it might try to fire too close.

Several updates ago, yes.

Yes, one sitting. (Again, to keep players from trying to cheat by disconnecting right before death.)

In theory you could sit on a story step entrance for a quick teleport. They tend to be in safe areas, but close enough to enemies a determined player could abuse them. There might be other cases I can’t think of right now.

Did you change maps at any point? That will reset your progress. (So players can’t abuse it by switching to another map when they’re about to die.)

Yes, the bug only happens if the story owner is a sylvari who completed the “mirror” storyline. Other players are unaffected.

That’s a known bug, that will be fixed when the Wintersday content update is rolled out shortly.

That’s a known issue that will be fixed in the Wintersday content update.

Are you sure you’re at the highest point? The “highest point” requires you to climb several sets of stairs in the ark, I’ve had other bug reports from players who were still on the main deck and didn’t realize the the marked location was ABOVE them.

You have to keep searching the area until you find the scabbard—it’s randomly mixed in with the others, and if you find a certain number of relics but no scabbard, it will mark the scabbard on the minimap so you don’t get lost. But it’s entirely possible to find the scabbard right away, or not until you’ve searched multiple relics.

Stuck how? The game freezes when you try to interact with it? The story objective remains active?

It vanishes when you pick it up, but it counts for the rest of the story step. It’s a “virtual item”. We had too many issues with players losing the bundle.

https://forum-en.gw2archive.eu/forum/game/story/Battle-of-Claw-Island-bugged/973056

It’s a timing issue, there are some occasional cases where players will load at slightly different times, and it can throw off the story script. In this case, for example, it kicks off a cutscene when the story owner enters the map, but they might enter BEFORE other players have finished loading, so they won’t see it. I can fix this up, but right now I don’t have an ETA for when it will hit live—we’re past the deadling for the Wintersday content update, so it probably won’t be before the end of the year.

Any crash logs are sent off to the server/programming team, so hopefully it’s something they can address soon. I’ve run through this story step multiple times myself in the past couple of days with no crashes/disconnects, so there doesn’t appear to be anything I can do on the content end, sorry!

You can complete the story version of the dungeon before it’s your active story step, which doesn’t just finish your story. I’m not entirely sure how it works in co-op, but AFAIK you don’t get the reward until you get the “end of story step” splash screen, which might not trigger until you finish the celebration.

Ok sorry now I’m totally confused. “Story mode” is usually used to referred to the dungeon, so I’ll ask again—did you complete “Victory or Death”? Do you have a current story step in the upper right corner?

Ah, ok, I asked the forum mods to move this to the dungeon forum then, since it’s not strictly a “story” issue. (Confusing, I know, but the story step and story mode of the dungeon are totally unrelated.)

I’m sorry, but I don’t understand what you mean by “last quest on camp”. Did you complete the Arah dungeon story mode, or did you complete “Victory or Death” (the last story step)?

Is the final story step complete? Note that the Zhaitan dungeon “story mode” and the actual story step are different, so it’s possible you completed the dungeoun but not the story step.

So, using the video as a guide, were you able to get past it? Occasionally (as in the video) the first step isn’t firing off, but I’ve never seen any others fail.

The gadget bugs are known issues, not sure when a fix will go in since it’s not something I can personally fix. CS has no ability to roll back/change your story step. Normally, logging out while in a story instance will cause you to appear in the open world zone on relogging, so that part sounds correct, but I’ve never heard of any story step just completing itself arbitrarily.

There are also NPCs from all the other 4 races that show up later, though unless you did their story branch, you won’t recognize them.

No worries.

Have fun, I love that step. (“I hate you guys.”)

Pressing 1 does nothing?

What happens when you take a drink? Going by the screenshot, it’s all working correctly.

I just looked at this story step and didn’t see any issues. If I’m reading your post correctly, you can’t see any of the effects when the consoles fire. What do you mean by “I see one, but never two”? Do some of the effects appear? What happens if you use the center console first?

Workaround: No player should move until the story owner has loaded in, let them move forward to trigger the cutscene with Romke. The issue is that a secondary player can trigger the cutscene before the story owner is present, so they never get the signal that the story should proceed.

Should be fixed in the next content update.

I haven’t had an issue with this story step, so without seeing exactly what you’re doing I can’t offer any advice. I’m 99% certain it’s not bugged, though.

That’s a known bug, I’m not sure where the original thread is. It will be fixed in the next major content update (Wintersday.)

What’s your current objective and story step name?

Conversations are a different matter, those vary from conversation to conversation. In general, conversations where the story owner makes a choice will be broadcast, other conversations are not. (To prevent the story owner from trying to spam all the other players.)

I’ve put in a bug for that issue (the turret on the tank) but it’s a programming issue, not something I can fix on the script side, so I don’t have an ETA for a fix. Sorry!

Cutscenes inside a story instance will play for everyone. Cutscenes in the “real” world will only play for the player that triggered them. Some story steps have to you talk to NPCs in the open world, and any cutscenes they fire off will only appear for the player doing the story step.

If it’s not giving you an option to get an orb, there’s still an enemy in the area.

The tower not displaying its undamaged state is a known bug, and hopefully it will get fixed soon.

As always, make sure they have enough room in their mailbox. There’s a limit on how many letters you can have, and it will queue up mail past the limit. Have him clear out his mailbox to make room.

As I posted above, this will be fixed in the next large content update (the Wintersday update.) I fixed both the stall, and the missing audio during the cutscene.

The personality traits have no mechanical effect, they’re their for roleplaying purposes. In some cases, they might open up new conversation options or reactions, but we intentionally de-couple them from mechanics so you don’t feel compelled to “maximize” your character by picking a specific personality.

Yes, as mentioned above it sould be in the next content patch. (The Wintersday update.)

When is “recently”? Which story step was it?

When did this happen? That bug was fixed about a month ago.