Guild Wars 2

Are you leaving the area before the scene finishes? When it’s over, there’s a cutscene that triggers, but only if you’re in the area by Trahearne.

Throughout chapter 3 you will get to work for all 3 orders, then at the end you pick one of them to join (and to use their plan for the final step.)

For the 9/27 update, I reduced the number of banits in each wave, so you aren’t expected to fight 3 at once.

I’m also looking into Logan’s behavior, he’s attacking…very…slowly…if at all, and I can’t see why.

I hate to be a broken record, but the only way we can fix these is if you report them. Quest name, current objective, character class/level, description of the issue with as much detail as you can provide.

To report any bugs, please indicate the quest name, current objective, and character class/level. We can’t fix them if we don’t know what they are.

The changes I made to Mazdak’s health will apply to all story steps that he appears in, but I didn’t make any adjustments to the NPCs in this particular step.

As for defiant, note that Trahearne is NOT powering him up at all. All “champion” level creatures are defiant, which is a shield against crowd control effects. The number indicated how many effects the creature will ignore, then it becomes vulnerable to CC for a short time.

Ok, good news and bad news.

Good news: I discovered that Tonn had no underwater weapons, so he wasn’t able to help at all. I also reduced the difficulty of the shark, and no longer have it make a beeline for the player.

Bad news: To account for scaling in multiplayer, I increased the number of sharks. (From 1 to 2-6 depending on the player count.) Now that Tonn is armed, though, and the sharks won’t attack the player immediately, I found it to be challenging but doable.

Slated for the 9/24 update.

“Dead of Winter” will be adjusted in the 9/17 update, and I’ll be taking a look at “The Battle of Fort Trinity” later today (for the 9/24 update.) Again, thanks for the specific info.

At the moment we don’t have any way to “turn back time” so changing choices made at creation would require her to make a new character. Sorry!

I just looked at it and didn’t see any problems with the cannons/arrow carts. Do you have “Fast-cast ground targeting” enabled? If you do, it will try to fire the siege weapon at your mouse cursor.

For any difficulty issue (or bug, or any comment on a particular story step) please provide the name of the quest, your current objective, your class, and level. There are hundreds of different story steps, so I need specifics to know which one to look at. (Just remembering an NPC or moment in the step doesn’t help, either, since many appear in multiple branches.)

We haven’t found a way to get this to happen reliably, so it’s been very difficult to track down. We keep making minor improvements to try and fix the issue, but rest assured we’ll keep working on it until the problem appears to be fixed for good.

Khisanth.2948:

Can you be a bit more specific? Simply nerfing both of them doesn’t seem like the right answer.

I’d rather not get into specifics, since I don’t want to reveal everything behind the curtain. : ) But I reduced Mazdak’s health, reduced the health regen on the abomination, and removed a couple of the extra spawns.

Nope, I meant sword. Play the story step to the final encounter. : )

1) Wrong forum
2) It’s a 15gb game, so it’s going to take a while to download

Tanaquil.9314:

I watched most carefully and ran the minute the flag started to blow.

That’s exactly the WRONG time to run. The flags indicate when the wind is blowing, once they die down you can run to the next section. (Don’t try to do the whole run at once, you need to wait at the middle wall for the wind to rise and die again.)

I’ve reduced the difficulty of both the abomination and Mazdak; it’s still important to use the lightning attack on the sword to thin down his bodyguards (since it can chain to all of them) but it should be a lot easier now. We’re on a slower update schedule now, so it won’t hit the live servers until the Monday update. (9/17)

Again, thanks for the specific info, it really helps me to quickly look at and adjust these issues.

Aha, I finally got my GM tag added, so this should up as an official post. Anyway, we’re currently looking at the issue, it’s definitely not intentional. Thanks!

Thanks for the specific info, I’ll take a look at it tomorrow!

Checkpoints are very different from saving/restoring a quest that’s in progress. Checkpoints are really just resurrect points, but trying to restore a mission “in progress” means saving the state of all of the monters, enemies, quest steps, etc. There’s a lot of behind-the-scenes scripting that goes on quests, and trying to save/restore the state in a way that wouldn’t introduce new bugs is extremely difficult, at least in an MMO that isn’t set up to “save” stuff like a single player game might be.