Abyssea - Misareaux Discussion

[Francisco]

wrong thread

[Salmijr]

Kutharie is the only one we havent killed either, since it's never up. Time to start killing Ramuh and see if it has any relation I guess. Most people avoid the avatars cause they can rape with their 2 hr.

[Bladefury]

Kutharie is the only one we havent killed either, since it's never up. Time to start killing Ramuh and see if it has any relation I guess. Most people avoid the avatars cause they can rape with their 2 hr.

Jala - Leviathan @ Mis =P

But the group I have to kill something like this is at most 8 people deep on 2 nights a week... hoping it is something that can be anticipated/planned, or I'll be waiting a while to pay for the damn boomerang drop from an LS that has bodies more readily available...

[Bladefury]

For what it's worth, after another night of watching, the bastard popped yesterday, only to depop 5 minutes later... it was approximately 10:00 on Lightsday. I did not check the Ironclad to see if it had anything to do with the pop. Really hoping that the 5 minute window can be tied to some form of forcing the pop, else it's going to be hard to get this thing, short of just happening to be in the zone and doing nothing when it's up.

[Plow]

For what it's worth, after another night of watching, the bastard popped yesterday, only to depop 5 minutes later... it was approximately 10:00 on Lightsday. I did not check the Ironclad to see if it had anything to do with the pop. Really hoping that the 5 minute window can be tied to some form of forcing the pop, else it's going to be hard to get this thing, short of just happening to be in the zone and doing nothing when it's up.

Seems to me like that's kind of the idea with these mobs... completely uncampable/farmable, you just gotta catch em through luck.

[Linsivi]

For what it's worth, after another night of watching, the bastard popped yesterday, only to depop 5 minutes later... it was approximately 10:00 on Lightsday. I did not check the Ironclad to see if it had anything to do with the pop. Really hoping that the 5 minute window can be tied to some form of forcing the pop, else it's going to be hard to get this thing, short of just happening to be in the zone and doing nothing when it's up.

First time we killed, it popped while the Ironclad was being fought, so doubt it has any relation.

[Bladefury]

First time we killed, it popped while the Ironclad was being fought, so doubt it has any relation.

So you guys selling then Lins!?! (Already know how that would work w/ all the proclaimed THF's in your LS...)

Guess I know where my mule's stones are going >.>

[ronin sparthos]

The only Caturae that ive seen pop exactly after an Ironclad has died is Sippoy.

Yaanei seems to be up rather frequently from the number of people in Ls that have died to it climbing for the seal quest in that zone.

Still never seen Kutharei up even after spending ~5hours in zone stopping by his pop point often enough.

[Bladefury]

Mule sat there, and got raped by him today... good thing tho, cuz we got claim and I have my shiny new Boomerang =P sadly, no idea what triggered it... was trying to kill the Jala's (Leviathan) and that didn't seem to do much. Good luck to any others, as I know I won't be burning more stones on this for the time being

[Eldelphia]

Pulverizer driving me nuts.... got it to 3% before it raged. Yes, it took that long. We tried proccing the !! and am beginning to think that's a mistake. Zerging him to 13%, cs stun and go nuts work?

[Alistrianna]

Pulverizer is squishy so zerg would be overkill on it. If you want to trigger red easier, just pull the NM to the cliff by the Amhuluk ??? spot and have the tanks drop down the side while Pulverizer sits up top. It's melee attacks will not hit anyone on the lower level and they can hold it without being constantly stunned and amnesia'd. Arm Cannon was the only TP move that I remember hitting the people holding it in place. I'm unsure if Eradicator was affected by the height difference. This also lets your DD walk up behind Pulverizer to attempt to trigger atma while allowing them a lil breathing room to time their WS between attacks and TP moves.

[Hanyoko]

Have a good stunner to stun it after it does a swing to increase the window for the melee to run in and try and proc !!
Pulverizer's (and normal ironclads) regular melee swings are unnamed TP moves.

[Eldelphia]

Pulverizer is squishy so zerg would be overkill on it. If you want to trigger red easier, just pull the NM to the cliff by the Amhuluk ??? spot and have the tanks drop down the side while Pulverizer sits up top. It's melee attacks will not hit anyone on the lower level and they can hold it without being constantly stunned and amnesia'd. Arm Cannon was the only TP move that I remember hitting the people holding it in place. I'm unsure if Eradicator was affected by the height difference. This also lets your DD walk up behind Pulverizer to attempt to trigger atma while allowing them a lil breathing room to time their WS between attacks and TP moves.

Yeah, damaging him isn't the issue, it's trying to proc the freaking !! and so we draw the whole thing out. Thanks.

[ejiboo]

Have a good stunner to stun it after it does a swing to increase the window for the melee to run in and try and proc !!
Pulverizer's (and normal ironclads) regular melee swings are unnamed TP moves.

you can proc !! in the middle of a normal swing. pretty sure we've done it multiple times.

[Byrthnoth]

you can proc !! in the middle of a normal swing. pretty sure we've done it multiple times.

Pretty sure people have a lot of trouble triggering !!s because they don't account for client-server lag when they time their weaponskills between swings. You're able to proc during swings because you also don't account for client-server lag.

Have someone use /follow on you (same movement speed) and watch how far behind you they are when you run. The amount of time between when you stop and when they come and stand on you is approximately the client server lag. Every action you do to the monster has about that much lag built into it.

[Hanyoko]

Pretty sure people have a lot of trouble triggering !!s because they don't account for client-server lag when they time their weaponskills between swings. You're able to proc during swings because you also don't account for client-server lag.

Have someone use /follow on you (same movement speed) and watch how far behind you they are when you run. The amount of time between when you stop and when they come and stand on you is approximately the client server lag. Every action you do to the monster has about that much lag built into it.

Until you dualbox (or run side by side pcs) people never realize how bad this really is. The sheer quantity of messages dropped during the zoning process is also staggering.

[Alistrianna]

I thought you can't proc a weakness when the mob is stunned or terrorized.

[Byrthnoth]

You can proc Red !! while it's stunned, as long as you stunned it while it wasn't readying a TP move (also swinging in the case of the giants) or casting. Basically, if it's OK to proc when you land stun, it's OK to proc while it's stunned.

[Kirschy]

You can proc Red !! while it's stunned, as long as you stunned it while it wasn't readying a TP move (also swinging in the case of the giants) or casting. Basically, if it's OK to proc when you land stun, it's OK to proc while it's stunned.

Had a person in my ls say they tested this and found it was untrue. During stun animation !! cannot proc. Also tested using a correct WS "too far away" which can't proc. And the number of times red !! can proc on a particular mob is capped at 5. Sounded like fairly good testing to me, so I won't be trying to proc !! during a stun~

[Byrthnoth]

I don't know, perhaps they were stunning during TP moves or casting? I know that we procced !! on Hadal Satiator at low HP by having people WS after my Stun.