Guild Wars 2

Did guild treks tonight and Friday, and I have one grumble and a suggestion …

Quirk/bug/difficulty: Interacting with the trek location is buggy. We actually failed one mission tonight because the location would not activate. We had 3-4 people standing inside it, and it took (literally) 2-3 minutes without the interaction registering. Other locations often take 1-2 minutes to register.

I do not know if this is due to multiple people spamming, and the game trying to register an interaction, or if there is some other issue.

Suggestion: Before the trek mission is activated, the UI mentions <number> of <total> (like “17 of 30”). Once the trek is activated, this designation is lost, and it makes it rather difficult to find your assigned target.

I find it “normal” that a guild will assign people to specific targets based upon <number> of <total> due to time limits. So could we please have the <number> of <total> text remain after the trek mission is activated, and have it next to the location’s name?

Thanks for considering both the quirk and the suggestion.

Adzekul of Seafarer’s Rest

Bump.

Long live Scant/

We just failed a trek because on 6 separate treks it too over 4 minutes each to register an interact. One of them I was siting on spamming interact for over 9 minutes before it registered. For the love of Grenth please fix this bug, it has taken one of my favorite activities and turned it into a keyboard smashing rage-fest.

I have figured out that spamming “interact” is a mistake. The way to do it is to Click “interact” and wait 5 seconds for it to register, otherwise you seem to reset the “register algorithm” every time you re-interact.

Adzekul.3104:

I have figured out that spamming “interact” is a mistake. The way to do it is to Click “interact” and wait 5 seconds for it to register, otherwise you seem to reset the “register algorithm” every time you re-interact.

That’s not my experience. Sometimes it triggers right away, sometimes there’s a delay. Yes, spamming might reset it, but then there’s (apparently) a chance that the subsequent trigger time is lower.

Regardless, it’s quirky; we shouldn’t have to guess when/whether we’ll get credit.