Guild Wars 2

This has been going on so long that I have a very hard time believing it hasn’t been reported here before, but the search function didn’t find anything for “temple” or “Dwayna”. Sorry if this has already been submitted.

The Temple of Dwayna meta-event frequently bugs – at least on Dragonbrand. After defeating the Priestess of Dwayna, Historian Vermoth normally approaches the statue, and the ghost of Malchor appears. This frequently fails to happen. When this bug occurs, the Temple of Dwayna meta-event does not restart and is impossible to complete until after a server reset or a new patch is released.

This bug is currently in effect on Dragonbrand. According to gw2stuff.com, the event has been in “Beat up Malchor” phase for the last 61 hours.

It’s getting bugged on serveral servers already due to this issue.

Basically, if you have people luring Risen mobs to Historian Vermoth, the event chain has an opportunity to stall.

It is happening again. Event stopped progressing on Blackgate.

Probably better to start a new thread for this. Yes it’s bugging, but they’d fixed the original cause. This is nothing but speculation, but more likely that new content is creating a different failure to similar effect. New content would include the latest living story content that throws a new effect onto champions, complete with new abilities and such. Could be the historian is getting hit by one of the attacks and is still suffering from it after losing invulnerability. Could be Malchor himself is coming under the effect and doing something unexpected. Could be any of a million things, but the original bug was fixed.
//Portable Corpse

Historian Vermoth disappeared, so the best guess was that he got affected by Toxic Corruption and disappeared after taking down Risen Priestess of Dwayna.

The other question is “Was the original bug fixed?” Considering that Historian Vermoth can still disappear after taking down Statue of Dwayna, thus denying everyone from accessing the karma merchant, I’d say no.

That I’d not seen it fail for a good long while suggests to me that it was fixed. That you had to dig up a 4 month old thread to say ‘still happening’ suggests it was fixed. That id seen it break repeatedly on my sever in the last week, and server hopping found me other broken instances…that tells me this is new. Perhaps it’s a repeat of the old bug. Perhaps it’s something completely different. Assumptions in getting the developers what they need to troubleshoot it can waste dev time and delay fixes.

Please, work from the facts of the now, not the ghosts of an old bug,
//Portable Corpse

Came to make a thread about this. It’s been stuck for 41 hours on my server, according to gw2stuff.com