Guild Wars 2

Mob Mentality – precision is decreased by 1% for every teammate over 10 in X radius… again this may cause conflict with the computations I guess. But would definitely be a quick solve.

Focusing in on the idea we want Zergs to spread out instead of stack up let’s pull a couple of classics out of the hat and reexamine them. Also note I bring this up primarily, because Anet promised new abilities are on the horizon to spice up current classes.

Skill Shots (skills that require aiming and a bit of finess to pull off – see burning speed or fire grab) and combos (skills that require you to have pulled off previous skills).

Now what if certain skill shot combos that are particularly hard to pull off made the end result ignore player cap and hit all 40 in that zerg ball.

Bad example using existing skills that’s too easy to pull off: burning speed into fire grab causes fire grab to hit all targets that could of been hit by burning speed (although burning speed itself only hit 5 or whatever..)

But why stop there? With new abilities in the works it’s possible to make these combos pro level, or even require more than one player to pull off (another bad example: I lay down burning speed in front of you (no not burning retreat or a fire circle, it only works with the correct combo) and you leap through it with 1000 blades smashing into the zerg ball.. I pity the ones who do not dodge).

Suddenly 10 masterful players can do a lot of hurt to a zerg ball, and players who [select target] and spam ¹¹¹¹ find themselves feeling a bit less pro.

Edit: Afterthought, this may a bit of good spice to add to some of the currently -more useless- weapons and utilites. Who uses flame axe? no one you say? We’ll what if I told you it was a Pandora’s box of skill shot combos suitable for striking fear into the heart of a zerg ball. (ya, your right, I probably still wouldn’t use it either…)

I cannot envision a strategy to prevent multi account users from circumventing this that do not punish multiplayer households. I am not a developer though.

Edit: This solution may be a little extreme, but what about a 5 day grace period after server transfer and new account creation where you are unable to deploy siege? This would solve 96% of the issues.

I see what your saying, but taking screen shots or reporting players based on action accomplishes little. Screen shots are a he said she said and reporting is based on chat logs, where it’s more likely you’ll get an ally banned for raging at them then any real resolution to a problem.

There should be a better solution, like limiting server transfer ability to matchup servers simultaneously with reset. I think most players could suffer through not being able to transfer to a WvW opponent server for 1 week, especially with guesting in place.

It’s bad enough we’ve had to do things like cut off users who aren’t in private teamspeak because map chat is not safe. Use decoy commander tags to draw attention away from capping squads (who don’t tag up). Borderhop the second trolls find the real capping squads. We’ve also had some of our commanders get insta reported/banned for raging at these guys when they are burning the supply of a keep under siege while typing positive comments like “we can do it guys!” and laughing all the way to the point tick with their guilds mates who are the ones with rams on the door. Tier 1 shouldn’t mean this. It’s one thing to be weary of spies in chat, but it’s totally gotten out of hand when you spend as much time on anti-troll tactics as you do playing the game.

I’m honestly surprised that other Vizunah guilds wouldn’t shame these ones for lack of integrity, but maybe they do, or maybe they don’t even know..

Playing on desolation and we have vizunah guild (part of our matchup) over here this week wasting supplies in garrison/keep on all maps and generally trolling in a fashion that’s just pc enough to not get kicked. Is there not a solution for this? Only thing I can do is log out for the week since I generally am here for WvW.

On a side note I realize this isn’t a reflection of vizunah in general, but reoccurring situations like this need to be addressed since they ruin the fun and just make people mad/quit.

This is not fixed. My guild just experienced this bug about 2 hours ago.