Guild Wars 2

Wow there’s an interesting implication to this. There is a hard maximum of achievement points, and if you failed to get any of the historicals, you will never be able to reach that maximum.

I don’t know if this is a bug, or if it’s deliberate, but on my computer, I can’t look straight down with the action camera mode.

For some reason when I try to use an AoE affect directly on my feet, or shoot an enemy directly below me in Bloodstone Fen, or even just look straight down for any reason, it doesn’t work. It can point about 90% of the way downward, then it just doesn’t move any further downward.

It’s still playable, but it’s really annoying.

Tarasicodissa.7084:

I can’t see any glitch at all, everything is working as intended.
Since there is 2 of you in the instance, Mordy’s breakbar is scaled to TWO people, not one.

This appears to be a bug which is known, at least on the wiki. Here’s a quote from the Hearts and Minds wiki page under the bugs section:

In the final phase of the fight, sometimes Mordremoth’s defiance bar wont be broken after activating the rift and a new rift will not appear. If that happens he is immune to all attacks, but the bar can now be broken using crowd control skills such as Knockback or Chill.

I don’t doubt what you’re saying, about how the bar is harder because there are more people in the instance, but I don’t think that’s the intended way to take the boss down.

There are also other reasons to believe that this is not the game working as intended. For example, the only solution to this problem, if you find your party doesn’t have enough CC to knock down the bar, short of logging out, is to commit suicide intentionally to get the restart mote to appear. However, Canach will try to rez you. So you have to struggle against him in the hopes of finally managing to kill yourself.

There’s no way this state of affairs is deliberate.

Admittedly, that would be kinda cool, because it would fit with the theme of a battle of minds. If Mordremoth just tried to wait you out, and see if you get bored enough to kill yourself.

Anyway, perhaps I can try to contribute my two cents to this issue for the benefit of the game staff. When I played and experienced this problem, I found that I was trying to close rifts at the exact same time as another player in my party. We both just dove on the rift the instant it became appropriate to do so.

I think, perhaps, there may be a race condition where signals to create and destroy the rifts (and execute their associated effects) were happening in an unexpected order because of multiple players interacting with it at the exact same time.

It’s just a theory. If anyone has ever experienced this issue with only one player, then please speak up, because it would rule out my theory.