is knockback rude?

[Teryaani]

Did you end up with aggro on a mob because the tank isn't holding threat?
Did that tank, despite having marked that mob with a "1" not bother to pick the mob back up even after you dragged it through him/her twice?
Is the healer having to spam heal him/her because he won't bother to use cooldowns and thus leaving you unhealed and being eaten?
Then no, it's not rude. Otherwise it probably is.

[yexie]

you're fating, you pick your mob and start melee him, then out of nowhere he fly 20 yalms away right in the unsafe zone and you either have to wait for him to come back or chase him like an idiot.

Even worse if you're a caster, you pick a safe spot, you start casting your bombs then all you do is "spell interrupted" because of the knockbacks.

In neverreap today, i almost missed my bane because the whm knocked back the wamoura in the first pull.

Personally, when i leveled my brd, mch or whm i never used knockback attack unless i was alone because i know how frustrating it can be for others, but i'd like to know what you think about it, are you still using it because it's a great way to stun regardless of the others, or do you remove it from your hotbar because you know that whatever the situation is, someone will be pissed?

Yup, very rude. I do it to my bf to play around though <3.

[Eidolon]

I try to avoid it but if I use it once without thinking and you make a vile comment I'll use it exclusively to annoy you. <_< I've made tanks quit so many rouletts.

[Moonleg]

Only read the first page, but wanted to add my two cents.

In a lot of high-end content, knockback attacks do nothing. The mobs just resist the push and only the damage gets through. I can easily imagine people getting into a 'lazy' mindset of not remembering the knockback rules for every single mob in the game.

[Azper]

I use Fluid Aura almost exclusively on bosses these days as extra free DPS or if I specifically know the enemy is immune to the knockback portion of it.

[Aillith]

I only use it if I am soloing, if I know an enemy won't physically be knocked back, or in those rare occasions where a mob has broken and run over to beat on me and I'm poisitoned so that knocking him back into the melee scrum saves anyone running over to 'save' me.

[Shiki_Lockhart]

As WHM I use knockback in some circumstances only, like to stop a aoe cast from a mob that no one bothered to stun or is immune to stun but can get interrupted by knockback (like those dragons in stone vigil). If use I position myself to them not go too far, like if tank is facing them in the wall they will go to same exact place on the wall but with the spell canceled.

Now spam just because is on cooldown then nop.

[Ashkendor]

I use Blank on things that can't be knocked back either because they're immune to knockback or because they're against a wall, or to shove stray casters/ranged into a pile for AoE if for some reason the tank doesn't stack on them or there's more than one. I'll also use it as an interrupt for an annoying ability if my silence/stun is already on cooldown or as a killing blow. If I use it by hitting the wrong key or if something I thought would be immune is actually knocked back, I apologize cause I know it's annoying.

[NovaLevossida]

As a SMN, I'm usually in melee range attacking anyway, so I don't mind knockback unless you knock it in a direction that breaks casting. Please stop with that.

[Lemuria]

People really need to ask why knocking a mob out of AoE damage circles, out of melee range or out of line of sight is a bad thing? Are we really at the stage where we have to explain basic mechanics to players because they can't figure out the obvious issues for themselves?

...yes, it's annoying. Save your knockback skills for the few times they might actually come in handy, like knocking a mob TOWARDS your tank after stealing aggro or INTO a DoT field rather than irritating everyone else in the team for your paltry DPS.