It is when they'll go so far as leave the group altogether when the healer won't give in to them and they don't get their way. At that point it's clearly not just innocently "asking".
Right he asked and the healer stomped his feet, so the tank stomped back. They're both guilty here. But he starts out by merely asking a question, which could have gotten an equally simple response.
Easy response "Sorry I don't have it slotted since at this level my dps can make much more of a difference than protect, however if you want to wait 1 minute for cooldowns I can cross class it then cross class it back, if not then just trust me, you will be fine."
Saying that you don't have Protect slotted is not "stomping your feet".
It seems like you're trying to create some equivalence here where none exists. Everyone could have just zoned in and ran the instance and things would have been fine. The tank could have simply said "Oh, ok" and ran the instance and things would have been fine. Instead, he chose to make an issue of it and quit. The healer in this equation is not at fault for anything whatsoever.
I use the same order as Gideon. Sometimes I consider swapping Protect and Cleric Stance just because not having Protect (even at low levels were the fairy can solo heal no problem) really seems to unnerve people.
Agreed, something as simple as this would alleviate anyone's concerns. If the tank wanted it, then right there you've just offered it to him and the healer can go back to slotting whatever else he wants after that.
Easy solution slot it, cast it, switch it out. Is it completely necessary? No but why not? Also how many of you have had some bad brayflox NM runs? Getting that with some fresh players can be rough. Protect can be very helpful if your tank is under geared and under experienced.
Everything you said here is wrong.Protect should be in the first slot, always. Cleric Stance should never be the first. Blizzard II is only useful for FATE's and is general worthless in all content.
It is somewhat reasonable, but if you're stopping the run to ask a non-WHM for Protect before maybe... level 30, it does demonstrate your lack of knowledge of how the cross class skills work, and how much you overestimate Protect's contribution in early dungeons.. Not everyone will put it in their first slot, nor should they necessarily.Asking if they can have Protect is not being a jerk. It's a perfectly reasonable request.
This is not what I'd call an "easy solution". For one, I guarantee I would forget to do this before every low level dungeon because *it just doesn't matter*, and two, having to do it twice after entering the dungeon is a lot of ability downtime.Easy solution slot it, cast it, switch it out.
/shrug I wouldn't leave because of it but I'd always have level appropriate gear and I'm not learning a role. It is easy though... If someone told me to put up protect I'd damn well switch it out and make them wait as a matter of course. :-p I'd also be laughing on my end b/c yes in most cases it isn't necessary. (At brayflox level I have it slotted though. I don't trust new tanks in there and I already have cleric stance and swiftcast)
You're funny if you think groups nowadays will wait.If someone told me to put up protect I'd damn well switch it out and make them wait as a matter of course.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.