Guild Wars 2

The guild mission timers need to freeze when your team is waiting in a que.

Once the mission is qued, the timer should not activate until the match is loaded. When the match ends, the timer count down needs to freeze until another match begins.

The way it stands now, guild missions can and often will fail due to que times soaking up the timer count down. This is unreasonable and needs to be fixed.

this week’s pvp guild mission is kitten.

4k rank points
8k rank points
16k rank points

done the 4k rank points.

not going to bother with the other 2.

We did 4k, 8k tonight but it is impossible to achieve 16k in 30 minutes with how much time is eaten up during ques.

It needs to be fixed.

Trevor Boyer.6524:

We did 4k, 8k tonight but it is impossible to achieve 16k in 30 minutes with how much time is eaten up during ques.

It needs to be fixed.

i did thought of wanna suggest in forum for the mission count down timer to be frozen while we wait for queue, but then again, all is vain!

the 16k rank points can be done if we have enough people around though.

unfortunately, i could only round up 4 others yesterday, making a 5 man team to try the 8k mission.

in the end, we settled for the 4k mission and called it a night. XD

It can be done by running multiple teams during the time frame? I did not know this.

Still, when it comes to spvp guild activity, running multiple spvp teams at once is something that rarely ever happens. Usually there is one favored team captain and everyone waits in line to run with that captain, rather than form a “Team (B)” so to say.

Even still, if no guild team is currently in a match, the timer should freeze or maybe do something like this:

• Guild Leader launches mission
• Mission becomes active for 2 hours
• Mission allows a maximum of 3 matches to achieve completion of the objective

This way, mission objectives remain difficult but are not arbitrated by the gamble of que wait times.