Guild Wars 2

DB said they farm us YB at SEA time, yea of course see how much they are and they still playing like that
Anet should fix this keep, they stack and killed our lord while half of them cata and treb our wall

Notice you have the Outnumbered buff there too. Clearly DB taking absolutely no chances with players they only outnumber 5 to 1.

Can you explain what’s going on there?

I’m guessing that they killed the lord while on outer…or they just all stacked in a corner to minimize damage while killing him? What’s the abuse?

Please, Yb did way worse than that while I was playing. Half the time there’s 7 people spawn camping while we’re outnumbered and 50 people going around taking everything we have. Just last night there were about 10 camping the entrance portal while the others were on keep lord. This shouldn’t be a complaint about how dab took adavantage of finally having a numbers upper hand but how there shouldn’t be two totally different times when teams dominate the map.

But this is on EB. Who even cares about EB? All the pros are on DBL.

Sviel.7493:

Can you explain what’s going on there?

I’m guessing that they killed the lord while on outer…or they just all stacked in a corner to minimize damage while killing him? What’s the abuse?

yes they actually spanking our lord while stay on outer wall. that was absurd since they get that big number of zerg they can easily take down lord without entering inner keep.

I won’t encourage this type of gameplay but got to admit, its humorous.

I see the exploit but how does it payoff? They cannot flip the keep without getting into inner either way.

looks to me like they are los’ing.

In the end, does it really matter? Part of the problem with this game mode is the total imbalance at various times in the day. On the surface this week shows DB and YB as pretty darn even. In reality DB rolls at certain times of the day and YB rolls at other times, both when the other is outnumbered…..

At game start it may have made sense to have battle groups that are assigned the common time slices SEA, EU, NA, OCX. The scoring could have adjusted based on the primary time zone assigned to the server. It’s just too late for that now so I care about when I play and not so much when I am asleep or at work. There are just some servers whose prime that doesn’t align with mine…….

I was there for this… essentially [RF] “Decent guild” stacked outside of inner on the northern supply hut and condi trashed the lord while the main zerg of 40-50 breached west inner.

By the time the main k-train breached the lord was dead and all they had to do was kill the 10 hopeless defenders.

If being able to kill the lord before you breach wasn’t bad enough, on top of that, if a poor soul got within epi range of that lord – INSTANT death, serious, no exaggeration INSTANT, LIKE RIGHT AWAY DEAD.

GG Anet..

Kilo.2539:

I was there for this… essentially [RF] “Decent guild” stacked outside of inner on the northern supply hut and condi trashed the lord while the main zerg of 40-50 breached west inner.

By the time the main k-train breached the lord was dead and all they had to do was kill the 10 hopeless defenders.

If being able to kill the lord before you breach wasn’t bad enough, on top of that, if a poor soul got within epi range of that lord – INSTANT death, serious, no exaggeration INSTANT, LIKE RIGHT AWAY DEAD.

GG Anet..

The really sad part of that is the fact that the Lord is supposed to be a benefit to your team, however, in this example he is a straight up liability that actually benefits the attacker.

I’m not sure why epi is so defended. Give it a strict limit on how many condis it can copy and move on.

or just make the lord not susceptible to epi. Solve your problem without nerfing it to the ground. gg ez pz my favorite color is clear

lol hilarious. A herd of catas on lord? Forget epi. Going anywhere near that would be death by cata.