DRG/SAM Seigan+Third Eye Performance

[Greylynx]

I recently dinged SAM35, and as I was leveling it for DRG sub I rushed out to test the performance of Seigan+Third Eye. I must say I am very disappointed so far. Out of 12 tests (meaning I used Seigan + Third Eye 12 times, against 5 different birds) fighting Lesser Colibri in Wajaom Woodlands as DRG75/SAM35 I had the following results:

1 anticipation: 2
2 anticipations: 8
3 anticipations: 1
4 anticipations: 1

Its true that this is a limited sample size. However, the result seems to clearly indicate that 2 anticipations is the norm. Have other people had the same experience? Will it improve when I get SAM37?

[raidenn]

Its completely random.

[Armando]

The longer Third Eye has been active, the more likely it is to not give you further anticipates. That's why the distribution turned out that way (it's not likely for it to die out immediately after used, but after the second attack round enough time has passed for it to be more likely to fail.)

[Greylynx]

Yeah I knew that was how it worked, I guess I just expected 3-4 anticipates to be the average not 2. Anyone have any personal experience with it? Is 2 the average for everyone else?

[Vyuru]

My average experience with it has been about 3 anticipations.

What normally happens is I WS, get hate, maybe get hit, maybe not, pop Seigan then Third Eye, anticipate a few attacks, about 3, then it goes down but Third Eye has about 5 or less seconds before it can be used again, so it's not down long at all.

Also, that is 3 or so attack rounds, double/triple attacks and multi hit WS are included in that, so sometimes I actually anticipate more attacks, sometimes not. I don't see the Counter effect activate that often though.

This is as both lvl 70 drg/sam testing and lvl 35-37 sam/war testing, I did a little tanking once I hit lvl 35+ on my sam to test it out.

[Lmnop]

I think most everyone around these boards have heard my complaints with Seigan. I have the poor luck to always end up in the scenario wherein I WS -> mob retaliates with WS -> I get Seigan/3E up but since the mob just hit me for 500 damage, he's content to turn back to the tank.

The few times it actually stuck with me, I've gotten 2 anticipates at best. I think I've yet to see more than 4 anticipates (and I believe that was on a Too Weak. Not that I think level has anything to do with it. It's purely dumb luck).

BTW, something I don't think would work but I don't think has ever been tried:

with Seigan up, activate Third Eye then pop Hasso. I wonder if that unique use of Third Eye would keep the benefits of Seigan. Would certainly be a nice (if time consuming) pre-WS procedure if it worked

[Vyuru]

with Seigan up, activate Third Eye then pop Hasso. I wonder if that unique use of Third Eye would keep the benefits of Seigan.

Just ran a partial test, didn't have time to get into a fight. If you do Seigan > Third Eye > Hasso, once you activate Hasso your Third Eye will still have a <30 second reuse timer, so it sounds possible. It is at least a way to shorten the Third Eye timer.

[Mouser]

It's really random. Sometimes it's one hit and gone. Though the best I've seen was 5 hits anticipated (a Heraldic Imp - I fired off Seigan/3rd Eye and waited for a nearby XP party to finish their Imp and pull it off me). It is very nice on Greater Colbri since multi-hit weapons skills (like Pecking Fury) are completely avoided as if they were a single attack.

[Sevv]

Yeah I knew that was how it worked, I guess I just expected 3-4 anticipates to be the average not 2. Anyone have any personal experience with it? Is 2 the average for everyone else?

I average 3-5 usually I'm just lucky like that =D


BTW, something I don't think would work but I don't think has ever been tried:
with Seigan up, activate Third Eye then pop Hasso. I wonder if that unique use of Third Eye would keep the benefits of Seigan. Would certainly be a nice (if time consuming) pre-WS procedure if it worked

It does keep the effect of seigan, I usually will seigan/third eye just before hasso -> penta thrust when I was using drg.