Also encountering this bug. I fall short of Guardian Leap targets consistently in Huttball, which traps me in the pit. Happens several times in a row.

Oh grow up:rolleyes:. If you removed the constant availability of Guard, you might be able to mitigate one DPS switch but then the next and all the rest after that while you're on cooldown would be free kills. TTK would be retardedly short. We'd go from having to pick targets to just hard focus trains. Highest DPS wins. And we'd have threads about that next. Speaking of the smallest percentile though, something you can add to that list is the actual number of reg wzs you have where the tank does something more than guard someone he thinks is a healer, then run out of guard range and pretend to be a DPS all game. Or he dies quickly at the start of the match and never uses guard or taunt after that. Guarded targets only become unkillable when your team is unorganized or your (completely random) composition is bad.... Which are not game balance issues.

So they should balance the game around completely random groups of eight people who don't pay attention to anything and mostly run around being stupid? No thanks. There's no reason to change anything when no one has proven there's anything wrong with the Guard mechanic.

I must be missing something. Would someone please explain to me how a close game between two hypothetically even ranked teams is an issue that needs some kind of solution? Why do we need to "fix" people playing well together and against eachother?

Can I join your club? I know it's only 49k and not 50, but I'm working on it. http://i44.tinypic.com/2v1m9dx.jpg http://i41.tinypic.com/6iy790.jpg

Bolster probably pushes us beyond Partisan gear levels, thus making the upgrade from Partisan to Conqueror even less perceptible than it would be under pre-2.0 conditions. The price we're paying for "equality" is any sort of sense of achievement (or simply character advancement, to suit my fellow gear-isn't-hard-to-get advocates) for getting new gear. I think it's going to have kind of an ironic (and detrimental) effect on the community.

Only one screenshot.

Why would you want to guard/intercede a dead person?

It's been around well before 2.0

What does guard have to do with intercede? I've never run into any of the problems you've described.

/signed. Just allow tanks to override each other's guards. Right now there are a surplus of really bad tanks that queue up, guard someone, and then run off and hump a wall somewhere, making it impossible for me to bounce to their target when they get focused.

Not sure if trolling.

What needs fixing with the resolve bar?

Vanguard doesn't have killing power anymore. It just doesn't. If you don't get a string of extremely lucky crits, you're going to have a ***** of a time killing any healer who knows what he's doing.

If your whole team is standing in a 5m radius and allows themselves to be smashed to death, they kind of deserve it. Smash/Focus may be "loleasy" to play, but to insinuate that there's nothing you can do about it (which is the argument of most of the people in this thread) would indicate to me that the problem isn't with smash. They can be focused, taunted, stunned, rooted, knocked back, knocked down, and mezzed just like every other class in the game. If your "smash is OP" scenarios center around the victim group doing nothing, well, there you go.

Whooooops.

II totally disbelieve any claim that force scream hits for 10k. Show me proof of it happening CONSISTENTLY against comparably geared targets (vs situationally with Inspiration + Red buff + power procs ), and maybe I'll agree with you. As it is, we have some very good smashers in our guild, and they "only" seem to hit particularly squishy targets for 9k, which single-target-wise, is about on par with every other dps class but vanguard. AOE wise I think it's "fine", considering they don't do much else. Show me someone who smashes comparably geared targets for 12-14k (without exploiting bolster) and I'll agree it's probably OP. As it stands, it just doesn't happen, or I haven't seen it happen, and I PvP a lot. Is it simple, cheesy, boring? Personally, yeah, I'd agree with that.

I rather think the point is "look at these guys being bad", not "look at me being awesome". Not that, of course, Cilas isn't awesome.

Hmm. I've never seen a smash monkey three shot someone. Yeaaah, one of us is trolling here. That's for sure.

Someone who gets the jump on you should have the advantage. That's why they call it "getting the jump". In any case, I do a lot of taunting and peeling so I generally figure out who the smashers are pretty quick. After that, their names/appearance don't USUALLY change. And I have their number for the rest of the match. If you're a dps, you should figure the above out just as quickly. If you're a healer, don't worry about it. I got this. (Same goes for DPS. I'm an equal opportunity guard bouncer.)

What you're suggesting would break the spec, and anyway I rarely see smashers hit harder than 9k. The ones that do are usually exploiting bolster. I don't think they ever hit my tank harder than 6k. I'm sorry, it's just not that hard to react to. The spec does ONE thing. One smasher is not a problem. Two are annoying if they work together, but I'd rather see two coordinated smashers on a team than two snipers.

Sorry, one team playing very badly is not indicative of a balance issue.

Depends on whether or not they have singularity up. If they don't, I lol because I now have EXTRA (on top of the already ample amount) time to react. If they do, I choke or stun them and spam freezing force and lol all the way to the bank, because they can't reach me anymore. And if they're not in Shii-Cho form, I just ignore them.

I must be some kind of PvP prodigy-Jesus, because I don't have that problem. Or smash spec is the easiest class in the game to anticipate and a lot of people just don't pay any attention to what's going on. I'm not sure at this point which is more likely.

Approximately how much time does it take to find the Shii-Cho form icon? (Hint: It's the blue one!)