tunnel vision

[lxChrisxl]

i realize it's a problem for some of you but please for the love of god work on it. it can make some runs really annoying.

example: in a levi ex run you have a ninja that has the wrong venom on and keeps stunning. you tell them to switch and you tell them again and again....and again. it takes nearly four or five wipes for them to finally switch and stop messing things up because they can't multitask.

actually i probably could have said ramuh and left it at that

[RaineAmorie]

I can't say I'm immune to tunnel vision, (ask the 1st boss in AK HM) but it can really wreck a run. Levi EX is a great example, if people are throwing out stuns all willy-nilly you're most likely fish food. My healer buddy has problems with tunnel vision, but a few strategic changes to the HUD has been a huge help.

[NyarukoW]

Be more patient with them. 4 or 5 wipes is no reason to get upset and QQ about it. You are actually fortunate you got someone who learned it in 4 or 5 wipes and is trying adapt. You'll probably need more than 500 wipes to clear T9 with random people you find on the DF.

[lxChrisxl]

Be more patient with them. 4 or 5 wipes is no reason to get upset and QQ about it. You are actually fortunate you got someone who learned it in 4 or 5 wipes and is trying adapt. You'll probably need more than 500 wipes to clear T9 with random people you find on the DF.

i used to try and helped people with things like t5/9 in duty but i stopped for another reason other than tunnel vision but that's a different subject. it's just one example from one run though. multiply that and it gets really annoying. also QQ needs to die as a thing, so silly.

Why would you engage again until you've discussed what the issue was last time?
It shouldn't take another run for the ninja to notice you were speaking to him. But if you just jump right into the fight again it's not his fault for following suit.

me and the tank told them to change multiple times before the tank would start the fight and during the fight. even explained why we were telling them to switch venom's and when they finally changed they said sorry and said they focus too hard and don't look at chat. which is a problem in mmo's

[Niwashi]

... and when they finally changed they said sorry and said they focus too hard and don't look at chat. which is a problem in mmo's

Which is why it was pointed out that these discussions should take place between attempts, when there is nothing else going on except chat. That's the only time you can really expect anything you say in chat to be seen.

If, after the first wipe, everyone had stopped while you pointed it out, the NIN involved saw your message, replied to it, and acted on it, then you could have succeeded on the second try. The extra minute or two to actually stop everything else while discussing strategy can save far more time in repeated wipes. (Of course, this advice is mostly for tanks. If you weren't tanking at the time, you wouldn't have had control over this.)

[Canadane]

Why would you engage again until you've discussed what the issue was last time?
It shouldn't take another run for the ninja to notice you were speaking to him. But if you just jump right into the fight again it's not his fault for following suit.

[Mishini_Dracoto]

[QUOTE=Canadane;2740683]Why would you engage again until . . . .QUOTE]

As a tank, runs take too long if you let players argue in between each pull. Especially since people rage at each other in the same way that the OP originally phrased his post. I don't want people to start a fight and rage quit, so I would rather just pull again.

I haven't levelled NIN, but I fail to see how running the wrong buff on 1 DPS class would wipe even Levi Ex. One DPS isn't that important.

[aisustrong]

[QUOTE=Mishini_Dracoto;2740754]

Why would you engage again until . . . .QUOTE]

As a tank, runs take too long if you let players argue in between each pull. Especially since people rage at each other in the same way that the OP originally phrased his post. I don't want people to start a fight and rage quit, so I would rather just pull again.

I haven't levelled NIN, but I fail to see how running the wrong buff on 1 DPS class would wipe even Levi Ex. One DPS isn't that important.

stuns on Levi ex
have you done Levi ex?
not getting the stuns basically perfect is almost garunteed wipe

[Ashkendor]

Be more patient with them. 4 or 5 wipes is no reason to get upset and QQ about it. You are actually fortunate you got someone who learned it in 4 or 5 wipes and is trying adapt. You'll probably need more than 500 wipes to clear T9 with random people you find on the DF.

4 or 5 wipes to something this easily fixed are definitely cause for being upset. They have less to do with the mechanics of the encounter and more to do with the person knowing what their own skills do. Would you be mad if your tank went in without Shield Oath/Defiance 4 or 5 times in a row? Hell, I'd probably kick them after 2.

I haven't levelled NIN, but I fail to see how running the wrong buff on 1 DPS class would wipe even Levi Ex. One DPS isn't that important.

They are if they're stunning the crap out of the caster add, which only serves to build up its stun resistance and prevents the Paladin from locking it. Hysteria on the entire party isn't exactly conducive to clearing Levi EX.

@ OP - Honestly, if someone doesn't answer me after several attempts in chat, I throw a few <se.1> in there. Since that's the sound that tells use, people will usually look at the chat box out of reflex at that point.

[Niwashi]

if someone doesn't answer me after several attempts in chat, I throw a few <se.1> in there. Since that's the sound that tells use, people will usually look at the chat box out of reflex at that point.

I don't get sounds playing based on commands like <se.1>. I'm not certain, but I think it's because I already have another sound configured for party chat (as well as another for FC/LS chat, plus the default one for tells). Even if you use "<se.1>" in party chat, I'll just hear the party chat sound, which overrides the sound you specified. (Ok, I guess that's not entirely relevant, since I'm still getting a notification of some kind telling me to check chat, but your mention of using <se.1> made me think of it.)