Quote Originally Posted by Katryn View Post
It is possible your tank was playing with a controller--that can make communicating harder. Also, was the conversation during or in between fights? I am too busy healing to even think of looking at a chat box for anything more than pre-determined shorthand (eg. one RM group decided to macro DD if shiva cast diamond dust since i was having trouble spotting it--i'm legally blind.) when a fight is going on. Further, if the tank did jump it's entirely possible they didn't / don't even know what Shield Oath is. That's annoying, but it's the truth.

Talking about someone like they aren't there is rude, though. If their performance did not seem satisfactory to the group, they should have been kicked. There was no need for drama.
Yea sadly he never actually waited. He just ran with his pace and didnt care for others. I mean with <se.1> you can notify someone to check the chat atleast. But yet not response. He stayed in the sword oath stance for the whole fight, while we had to deal with little casualties (we as dps tanking trash mobs, the healer had to heal everyone). He didnt lose aggro on bosses, but I guess thats cause the dungeon was easy.

And again, this is just a callout for the harder dungeons and endgame content. People complain about getting kicked in chats and whine about why they get booted. Underperformance is a reason which many dont assume.

Quote Originally Posted by Shadow_Novus View Post
I'll hazard a guess and say it was because it was a tank and they wanted to just finish the duty. Waiting for a replacement tank to queue in progress can really, really suck. Most times it ends up like waiting in a DPS queue except you're already in the dungeon.
You got it right friend. It was a low level roulette, getting replacement for that one during peak hours... is insane wait time.