thats even worse!
If it were firesday you hit ONE of 3 possible elements.
So, to quote my previous statement:
notice I took out the "I'm sorry", because you didnt warrant it this time.AHAHAHAHAHAHHAHAHHAHAHAHAAHHAHAHAHAHAHAHAHAHAHAHAH AAHAHHAHA
AAAAAAAAAHAHAHAHAHAHAHAHAHAHAHAHAHAHHAHAHAHAHA
AAAAAAAAAAAAAAAAAHHHHHHHAHAHAHAHAHAHAHHAHA HAHAHA
Sorry but these "OMG WEAKNESSES CHANGED, we did everyyyyyyyyyyything and it didnt proc" posts are stupid. After spending 7 hours last night in Uleguerand bringing Anemic Aloysius and Awahondo to 100% as well as dropping Resheph 2 or 3 times without failing any red or grellow's (other than one which very well may have been 1k needles), They have NOT changed.
If this guy cant even probably transcribe what day it was, he probably fucked up one of the viable 18 spells, presuming he got the days/elements correct.
Guess its my fault for not spending 7 hours in a game Sorry =/ But w/e. let him be.... And i dont care if he or other ppl says... If someone really thinks there's a change or something they did .. they can just post it.. seriously.. but well not talking anything more about that or about those "little kids"
Is it possible to stagger while a mob is under a special job ability effect? Ie mighty strikes, invincible, etc.? My group has always waited for these to wear just to be safe. Given that the actual meikyo effect lasts 30 seconds, it would still be up for a little while after the 3rd weaponskill.
Apologies if this has been answered before.
In that case I have no idea. Good to know that about job abilities though.
My group had a similar issue with the tier 2 corse in attowha. We covered every spell for the three elements at least three or four times without any luck on the stagger. I have also felt like our luck with a whm nin blm set up to be much worse than it should be (since the Heroes update). I just attributed it to the RNG working against us, but I can't say I would be completely blown away to learn that something has changed.
Edit: Nvm, wasn't 100% on this but seems to be have been cleared up somewhat in the Tahrongi thread.
http://www.bluegartr.com/threads/955...cussion/page74
Having done a bit more testing on this, it seems you can proc during 2 hours as long as they don't interfer with the AI (I.E. Glavoid not WSing during BW & Chloris not WSing during Hundred Fists.)
Have personally seen procs on the T2 Diremite in Uleguerand during Hundred Fists (it still WSs) and during Tunga's Chainspell, among a few others. This is still somewhat a theory, but it seems the most likely explanation to me.
That seems to be true~ Chloris def didn't proc !! during 2HR, re-proc'd w/o 2HR. And earlier had scorp NM use Mighty Strikes but still managed to land red !!.
In addition to that, my group claimed Turul at 22:10 yet exploited blue with Full Break. This is the only experience I have had with the hours being off for anything other than 6-7 blunt.
Failure may have been on to something when he suggested that the first hour of each day is a toss up between the two types of weapons.
Should be easier to figure out now w/ abyssites of discernment on so many people, I'll post what I find out when I go trollin' for procs later.
The abyssite of discernment is nice. Whenever you get off a spell or weaponskill it may show a message in your log related to that weakness trigger. "The fiend appears vulnerable to polearm weaponskills!" - "The fiend appears vulnerable to lightning elemental magic." - "The fiend appears vulnerable to darkness elemental based weaponskills!" It helps narrow down the list extremely fast.
Sorry if it has been already said, but I'm not finding this answer anywere(Search button isn't helping).
Should people wait a certain amount of time before trying to do a !! trigger, when a previous different colour !! weakness has already been triggered?
IE: You proc blue !!, then, do you have to wait a certain amount of time before you have a chance to get a grellow !! trigger?
Yesterday we were fighting Dvalinn, and we were trying to proc both red !! and grellow !!.
Grellow !! procced, I waited the silence effect to wear off on Dvalinn(because our leader tells us to wait for the previous !! effect to wear off), then I tried Tachi: Koki, and nothing happened(and no, it wasn't casting anything, it wasn't TP moving, nor it was stunned). Few minutes later, I retried Tachi: Koki, and we got the red !!.
Chat logs:
[23:14:33]Leth starts casting Drain on Dvalinn.
[23:14:36]Leth's dark magic skill rises 0.3 points.
[23:14:36]Leth's dark magic skill reaches level 323.
[23:14:36]Your attack staggers the fiend!
[23:14:36]The fiend is unable to cast magic.
[...]
[23:15:10]Dvalinn starts casting Stonega III.
[23:15:13]Leth casts Stun.
[23:15:13]Dvalinn is stunned.
[23:15:17]Dvalinn is no longer stunned.
[23:15:21]Sakamoto readies Tachi: Koki.
[23:15:22]Auston readies Ascetic's Fury.
[23:15:23]Dvalinn is paralyzed.
[23:15:27](Sakamoto) koki X
[...]
[23:23:57]Sakamoto readies Tachi: Koki.
[23:23:57]Your attack staggers the fiend!
[23:23:57]The fiend is frozen in its tracks.
No chance of having messed up anything with the 1° Koki, the only thing I can think about is that I tried to proc red !! just after 45ish seconds grellow !! procced.
We already experienced a similar event when we tried to trigger grellow !!, while red !! were just procced(and the mob was still terrorized), but once the terror effect went off, we just procced with the same spell we tried to when the NM was terrorized.
You can't proc a !! while one is already on (amnesia from blue, silence from yellow or terror from red), but since it clearly casted before the Koki, silence wasn't on.
The Koki was used at a wrong time, which is why it didn't proc. I wasn't there, so I can't tell you what, and since you cut a lot of the log out (maybe things that you found to be irrelevant, but actually isn't), there's not much help there either.
You can't proc a !!! on top of another, but in your case, Dvalinn was able to cast Stonega which means its weakness has already wore off.
My bet based on your log is that he still was in the animation of the spell (stonega III), even after the stun. The 1st koki landed during casting then.
Edit : beaten
Yes, I've cut the irrelevant lines, the full logs would have been:
[23:15:10]Dvalinn starts casting Stonega III.
[23:15:11]Alleitaliano casts Cure III.
[23:15:11]Auston recovers 215 HP.
[23:15:11]Kogenta casts Haste.
[23:15:11]Auston gains the effect of Haste.
[23:15:12]Kogenta starts casting Erase on Kogenta.
[23:15:12]Leth starts casting Stun on Dvalinn.
[23:15:13]Leth casts Stun.
[23:15:13]Dvalinn is stunned.
[23:15:15]Dvalinn's casting is interrupted.
[23:15:17]Dvalinn is no longer stunned.
[23:15:18]BastionPrefect : The southeastern enemy force is 400 yalms away from the outpost and closing!
[23:15:18]We had best step up our preparations.
[23:15:19]Daeron starts casting Erase on Auston.
[23:15:19]Kogenta casts Erase.
[23:15:19]Kogenta's slow effect disappears!
[23:15:20]Alleitaliano starts casting Cure IV on Zello.
[23:15:21]Auston uses Boost.
[23:15:21]Auston's attacks are enhanced.
[23:15:21]Sakamoto readies Tachi: Koki.
[23:15:22]Auston readies Ascetic's Fury.
[23:15:23]Dvalinn is paralyzed.
[23:15:25]Kogenta starts casting Cure IV on Auston.
[23:15:25]Alleitaliano starts casting Silena on Zello.
[23:15:26]Daeron casts Erase.
[23:15:26]Auston's weight effect disappears!
[23:15:26]Dvalinn is paralyzed.
[23:15:26]Daeron starts casting Slow II on Dvalinn.
[23:15:27](Sakamoto) koki X
Understood, so most likely it has been stuck on his Stonega animation for 4ish seconds(that is still a reasonable amount of time) after the stun effect wore off.My bet based on your log is that he still was in the animation of the spell (stonega III), even after the stun. The 1st koki landed during casting then.
Thank you for the answers.