Guild Wars 2

Hi! I’ve recently come back as well, and found myself in the same situation.
Here’s a Staff/GS power build I found in this forum : https://www.youtube.com/watch?v=gZOraV9CGdY (build link in the description). That’s how the pros do it. I think.

On the other hand here’s an atrocious build I’ve been playing with today (wvw zergling and small fights). I’m embarrassed to post, but perhaps people will suggest improvements. I made it because I was too cheap to replace my runes of hoelbrak (from a shattercat build from eons ago) : http://gw2skills.net/editor/?vhAQJARWl0nhC0YZawRNwtGL4G0ZLextLDwq/Fau3dvB-TVSBwA4UPgxhA4xDAwsSwrK/upiDv9H0cEAAcBACAgAwNv5Nv5NvZRAKTA-w

This isn’t a roaming build specifically, but this is what I’ve been tinkering with in WvW since yesterday :
http://intothemists.com/calc/?build=;00;3kHFJ0D4gJ-K0;9;49J9-T5;053-1;357A6-F05;9K-l51-o090;0VAVFWKXP2V3a_91-370B-7V-17V;9;9;9;7VVVVVV;9;0V6-6q
(edit: there seems to be a bug in the link, the grandmaster trait in soul reaping is supposed to be Foot in the Grave)

I definitely welcome any feedback or criticism. It’s very flavor of the month in that it leverages the changes of yesterday’s patch. I’m not too sure about Reaper’s Might/Unyielding blast, but the patch notes seem to invite us to sit in DS and auto attack.

One change I’d like to see in WvW is to remove the fade-in effect for character models coming out stealth. It lasts only about half a second, but it is distracting and gives a slight advantage to the person coming out of stealth. I assume it exists mostly for cosmetic purposes.

If a nerf to stealth was in order, my preference would be to add the reverse effect : a 0.5s fade-out to character models entering stealth.

However I think stealth should be left alone until the culling improves on all front. It could be months until we see improvements but in the meantime I shall deal with it :p

I recall a specific instance where I was disappointed with how the game encouraged mindlessness over tactical play.

We were defending a tower while severely outmanned. With those odds, there was no question that the tower was going to fall, eventually. At the first attempt, the enemy zerg built some flame rams that we quickly destroyed. Then, they resupplied and built some catapults. We countered again with our own siege.

At that point, I swear it was as if I could hear them say “we’re done with this silly game of siege, let’s just bash the door open”. They decided to hit the door with regular attacks and quickly burned it down.

It feels like, in specific ways (the ability for players to damage doors, the imperfect righteous indignation buff, the AoE limits, the culling), the rules of the game start breaking down the more people you have.

I don’t think anybody is saying that huge battles or large amounts of players are bad, but instead how some of the mechanics of the game make those encounters less interesting than they could be.

@Mishi

Thank you for the quick response. Good to see both the SoR community and ArenaNet not tolerating any foul play.

@Miasmic
I do not wish to slander SoR as a server, or contribute to the flames on this forum, but since you offered to take action we have some evidence of exploiting by a SoR guild here on our forums :
http://isleofjanthir.net/forum/showthread.php?tid=452

I know that most of us in IoJ, Blackgate and SoR want nothing but a fair fight. See you on the battlefield !

During the BWEs, head start, and the few first days after release, everything was fine.

But for last few days, I’ve been experiencing the same issue others have described in this thread.

I’m getting frequent lag spikes that last for a few seconds. It seems particularly severe in WvW. My connection is otherwise fine and I can communicate with my guild mates over ventrilo during the lag spike (which they are not experiencing).

Today for the first time it lasted long enough that I got disconnected and was sent back to character selection. At first I thought my ISP was to blame, but looking at this thread I see a lot of people have exactly the same issue.