The guys answer, how they're based on macc ergo "shouldnt miss"
It's not that bad of a reply. Sure, he could have said "It behaves like a nuke, so it can ve resisted multiple times but never outright miss", but the correlation of macc based -> doesn't miss is not too bad. There's enfeebles, and those do miss, but anything that does damage, and is magic based, can't outright miss, so it's an okay reply.
Hows this for fun:
8 pm: People shout for Tchakka. I join in since I need the KI. 20ish in the zone at this point. 30% colo rate.
1:30 am: Tchakka is now at 51%. By this point most of the NAs that were in there (including ALL of the CORs and PLDs) have left. Couple JPs start showing up. I say fuck it and log out near the entrance to the reive, just in case.
8:20 am: I decide to check to see if it was over before I went to work. Tchakka is now at 21%. The same solo JP PLD has now been tanking this thing for roughly 7 hours.
So to everyone whos been bitching about 5 hour Zapdos fights, come on down to Carby. We've got a shark fight that, at this rate, is looking to last at least FIFTEEN FUCKING HOURS.
How is that possible... every time I've done these they haven't lasted over 2 hours. Do people even try to coordinate jobs instead of letting people come as whatever when they send tells? COR!
Except nukes don't miss (resist message) unless they are immune or have something like magic shield up.
Ele WS can obviously can have damage resisted but the weaponskill can't miss, even if the reply wasn't 100% accurate it certainly wasn't some wild stupid assertion a million miles from the truth. You could probably scan through yells from any NA prime time period on any server on any given day and find something far more worthy of this thread than that.
The only reason that one is lasting so long is the fact that there is a shark/bee shout every single day. More and more people are getting the wins and less people need to show up, given the fact that there was a shark shout literally the day before this one, it's not surprising that no one went.
I've been camping GW shouts for the past 3 days hoping for an Achuka shout for my mules...NOPE
All I've seen are Bee (I think I saw 2 or 3 different bee shouts yesterday at varied times) and Shark.
speaking of, anyone know why the shout filter doesnt work? Or is it a known broken thing.
I joined hurkan shouts two days in a row and got the bullet both times. Decided to quit while I was behind and not join the shout last night. Got all 5 KI, done with wildskeepers till they add the next set. This system is stupid.
Yeah, I got 4 bullets from that thing before I finally finally got something else (axe) fuck that bird. Proceeded to get the hat from the quest and forget that bird even exists
At least you got the killshot on Zapdos >_>
This is from a month ago or more. Everything has come full circle.
And for good measure:
Just had this princess leave a PUG for Orobon clear (helping a friend who missed KI) because they wouldn't switch to the appropriate /WAR sub for the fight.
Also because you apparently need a pt of BLUs stun locking NMs.
I agree that they should have changed their subjob, but otherwise, I'm not seeing the problem here. The gloves may be only Rank 1, but they still provide benefits on-par with other Haste glove options for MNK (e.g., Brego Gloves). They look to be capped on Haste in a PDT set (HQ head and body, too) with some ACC pieces. Unless that's what they full-timed without exception, I don't think there is anything wrong with their gear.
You realise /run is about on par with /war if you are capping attack/accuracy. This person's refusing to change SJ is silly (because its not likely grounded by logic), but making a big deal over someone changing to a SJ which will have no impact on the jobs performance is equally silly.
As already said there is nothing majorly wrong with that hybrid tp setup, most of the upgrades could quite easily be gear that person doesn't possess.
I think the picture took away from the random fail I was trying to illustrate, which itself is a random fail.
They were worried about stuns (as was everyone in the alliance from their shell) because we did not have a group of BLUs devoted to keeping him stun locked. I regret not posting the entirety of my thoughts on that.