Delve

[Fake]

If Daku is actually resisting after 5mins then your GEO isn't doing languor or focus, or your stunners have terrible gear/uncapped skill.

You likely saw resist because it put its shield up and didn't notice, since it can do it at any time below 25%

[Ramzii]

Yeah, you're doing something wrong. Even on kills where we had some DD die extending the fight to >10min, we still just barely missed the stun wall. Languor/focus wasn't up or it was aura'd.

[Sukian]

A big thing that can go wrong is if you are tossing out random stuns or potentially stunning all spells. You'll definitely hit the cap faster that way.

[NynJa]

no

And we only really get lag in Ceizak, slight ones in Foret and none in Morimar at all

Theyre all in the same area >.>

[Helel]

Don't need to stun any of his spells other than dispelga. Can stun him with 1 SCH like all the other NMs, though you should use COR to reset strategms since he takes slightly longer. This allows you to have warlock's roll as well (though certainly not necessary).

Regardless, stun walls won't be an issue for anyone after tomorrow.

[Dazusu]

Theyre all in the same area >.>

You say that like its relevant to experiencing latency in those zones. Sometimes the excessive latency can be caused by mob positioning due to the layout of the specific area of the zone you're in. If you're being sent mob updates for 50 mobs in a room parallel to the tunnel you're in, while trying to stun - you're gonna lag like a bitch (experience high received data rate, pauses in action for a second, etc)

[Dazusu]

I really do feel blessed being on a low pop server; we rarely get lag spikes that bad anymore.

Until they merge us with Cerberus, or other random low pop server.

[Rhiannon2]

no

And we only really get lag in Ceizak, slight ones in Foret and none in Morimar at all

To be fair, you can no longer tell who stunbots and who doesn't. Even people in the same linkshell don't know whether other people in that same shell have DL'd the program. Something like Calcifying Mist can foul up even the best stunner unless they use the program.

[Ophannus]

If you did say a 250 damage Helix upon pulling Matamata, would it do 250 damage every 10 seconds regardless of how many TP moves it used since it's a DoT?

[dasva]

If you did say a 250 damage Helix upon pulling Matamata, would it do 250 damage every 10 seconds regardless of how many TP moves it used since it's a DoT?

I seem to remember someone saying it didn't do much. Not sure if it's been tested but it may do dot equal to the dmg dealt before accounting for mdt maybe? Would be a funny way of doing matamata though

[Norto]

It's pretty subtle, but one way you might be able to tell is if your stunners bite on moves that shouldn't be stunned but have similar sounding names (Bubble Shower and Bubble Curtain), since I assume these programs wouldn't mess up on that stuff. For me, I'll throw my stun away on the wrong move occasionally, and consider myself an above average stunner overall, but I do think a lot of legitimately good stunners will probably be suspected of botting now. And not to say that there aren't plenty of good stunners who just can't perform in Delve due to the lag/packet issues, as that's beyond frustrating, I'm sure.

[Yugl]

Packets and spikes affect programs too. The main issue with mist, in my experience, has been an issue where XI delays/ignores inputs. The other issue is that stunners don't use BM. If you use BM, you see TP moves faster because BM doesn't save messages until animation happens.

[Sukian]

The alternative is to animation stun. For peiste it should die quick enough before you lose all your charges.

I've stunned a ton and can safely say that if you are still struggling to stun megs boss tp moves by chat with or without battlemon, try and animation stun. Seems quicker/less miss stuns

[Bored]

Shark-

we did our 1st foret run yesterday, did pretty well 1-5 and shark to 64%, timed out. Had 5mins to mess with him, and 2 DD dead at the 1st tp move.
But today we had 15mins on him, and timed out at 47%. All DD's on him.
74-50 took forever.
The pt setup was changed some though wondering if that was the reason timing out.
Dmg just seemed very meh tonight.
PT tonight we had 4x mnk/run, mura sam, drg.
The PT where we had 2 less DD on it and killing faster was
2x mnk/war, 1 mnk/run, mura sam, drk, drg.

Basically 33%atk+DA loss with all the mnk/runs. Do you guys bring only 1 mnk/run on shark wins? Aura was dropping so fast that, i see not one reason to bring 4xmnk/run, 1 seems well enough. Maybe 2 if a mnk happens to get killed and cant get thunder spells back up.

Also, after every 25% dmg was ok, but remember reading, ppl would spam dispels? Does it gain a boost on a certain tp move that needs dispelled?

[Diomer]

Shark-

we did our 1st foret run yesterday, did pretty well 1-5 and shark to 64%, timed out. Had 5mins to mess with him, and 2 DD dead at the 1st tp move.
But today we had 15mins on him, and timed out at 47%. All DD's on him.
74-50 took forever.
The pt setup was changed some though wondering if that was the reason timing out.
Dmg just seemed very meh tonight.
PT tonight we had 4x mnk/run, mura sam, drg.
The PT where we had 2 less DD on it and killing faster was
2x mnk/war, 1 mnk/run, mura sam, drk, drg.

Basically 33%atk+DA loss with all the mnk/runs. Do you guys bring only 1 mnk/run on shark wins? Aura was dropping so fast that, i see not one reason to bring 4xmnk/run, 1 seems well enough. Maybe 2 if a mnk happens to get killed and cant get thunder spells back up.

Also, after every 25% dmg was ok, but remember reading, ppl would spam dispels? Does it gain a boost on a certain tp move that needs dispelled?

Your DD is extremely slow and I don't think you did any better if we're comparing 5 min 64% timeout to 15 minutes 47% timeout. Somewhere there's quite obviously a huge problem; I just have no idea what it is with the information you gave us. We use MNK/RUN x4 DRG SAM as DDs for Foret and kill it in under 10 minutes including sleep.

[GeneyusTitan]

Verve needs a couple dispels. We have one person Hundred fist at the first verve, at 75, and at 50. We sleep it at 50 and do wildcards and redo troub songs that last the rest of the fight. If anyone gets HF back we have them do it at 25. The reason your dmg is bad is probably because your DDs have bad accuracy. While a lot of people can get away with other food, if you are struggling you should just use sushi. If your group is good you are killing it fast enough that missing out on the attack from other foods doesn't really matter. Sushi helps to make up for if buffs fall for a little bit too.

It won't matter after the update tomorrow, but you probably need to gearcheck your monks.

[Arthars]

dont stun magics, can extend charges before u need SP stun

after u stun verve, all schs can start thunder it, dont wait, so shield will be down much faster

he will always cast a spell after mayhem, do a normal attack move, before he readies another WS, so that is a shit load of time to bring the shield down.

also if your mnks r lazy/cheapass to use remedy after shield went down to remove the potent para, then get ur WHM to accession paralyna. If all 3 DDs are alive, curaga III and curaga IV will never cost any MP

just some ways to improve DDs..... but if they are pure flat badly geared, then yea.... nothing we can help here

670 acc + sushi for all DDs should not have any acc issue even if song sucked/non SV madrigals/non XI rolls. sulpor always up x2.. (common sense) and pflug/vallation everytime possible

fight him straight up where daku is pulled and dont even think of "pulling" him back. Chances r some people gotta die from first mayhem pondering somewhere in between deciding to fight or pull back
first 25% 100 fist + formless AFTER horn is down so no para'ed effects, should only take 2-3 mins
74% to 25% should be like 2-3 mins tops
24% to 0% should be another 2-3 mins depending on luck

rdms have nothing to do in this fight cept for curing/haste/refresh.... just spam dispels

[Norto]

rdms have nothing to do in this fight cept for curing/haste/refresh.... just spam dispels

I could be wrong, but can't RDM Silence it, also? Would probably also help with SCHs stunning his spells by mistake (not that it's something they'd want to be in the habit of doing). Pretty sure our RDM does, anyway, as well as the standard debuffs, while staying on top of dispels, at least prior to the shield spam phase.

EDIT: Actually, reading your post again, I see you mentioned that his casting a spell after Mayhem might buy more time to get the shield down, so I could understand opting not to silence it, if so.

[Sukian]

think of it this way, if you silence it (or any other boss) thats more tp moves you end up stunning. If it isn't casting it will do a tp move. You are better off miss stunning a spell on a couple then having to stun a lot more tp moves. Some may argue that its harder to follow up stun on a spell with a tp move but it's really only on the super quick ones like diaga/holy on tojil where if you actually stun after the spell gets off and it jumps right to a tp move once unstunned. This can be countered by having the other sch stop twiddling his thumbs and back up stun (if you solo stunning at the time)

[Bored]

Shark-

Well our Mnk's are geared properly. Wouldnt be anything different than what ppl would write on here, Oats, r15's, etc.
Personally think our DD are doing fine. 1st fight Sam was dead at start, so we started with 5/6 DD, then 1st tp move on pull dropped us to 3/6 DD. Then 1 DD fought adds. so 2 DD on it mostly for the fight.
Same ppl we do 5-6min tojils.
Geo's use Atk down and defdown with Maccup/mageva down, ACC is non issue with SV up, (but needed after)

Just seems confusing until i watched the video of why.
**We didnt start to fight until 2mins after SV had gone off, 100-75% took 2:47sec, Now the pain begins. Suppose to be BLunt time i thought but 4mnk took 7:15 to get 50% and heres why >.<. SV was off at 54% and Thats where problems started, ppl missing alot, 2DD died, and Not sure why but no songs were put back up for 2mins+, tried to sleep couldnt w/o N/T from bards, etc number off things going wrong. But pretty confident next fight.