So about Enochian

I've been 60 for like 4 or 5 days now and I have two things to bring up about Enochian.
First is that Blizzard4 and Fire4 can be frustrating to cast.
They can be cut off with .2-.1seconds left on the cast if either Enochian or umbral ice time out. It also happens if I Swiftcast it, the animation will go off as if I cast it but the spell won't come out. I think it would be cool if the cast could still go through if we have over 3/4 of the cast done, and not just cut us off, leaving us standing there thinking, " oh, nothing happened".
Second is recasting of Enochian. Make it so that the buff as a whole is renewed, and not just the next tier, as if I cast Blizzard 4. If I want to keep busting out spells I sometimes preemptively recast enochian right when it times out, and it may give me 5 seconds instead of 30 seconds, now I have a long cooldown for 5 seconds of up time.

Fight mechanics don't annoy me a much anymore more now that I know the fights, its just the above issues that make Enochian weird and klunky.

You cannot recast Enochian while it's active. You're basically using Blizzard IV without even casting it except doing so will shorten the remaining time. Best to just let Enochian run out when it is off cooldown.

Quote:

---

Originally Posted by Twilite

You cannot recast Enochian while it's active. You're basically using Blizzard IV without even casting it except doing so will shorten the remaining time. Best to just let Enochian run out when it is off cooldown.

---

I think OP knows that...

I feel like enochian and astral fire should have their duration increased by like 5 seconds. Reduce potency or something if you have to make up for that extra 5% damage increase but these two timers are so tight that rotation fluidity is just absolute trash. The forced cancels are awkward and interrupt/punish gameplay

I also agree that I feel like recasting enochian itself should completely reset the duration. It would just make everything a lot smoother. The way that our class is with the GCD starting at the beginning of a cast makes all this artificial "waiting" a detractor from gameplay. The addition of all these off GCDs into a class just doesn't mesh well with these extremely tight timers, sharpcast is obviously an ability that would benefit from actually being weaved in between GCDs but of course you have to awkwardly mash buttons to get the sharpcast F1 in between your two F4s.

Just want to clarify that the my opinion is that the current rotation is certainly doable but it just feels messy and needs some adjustments.

Basically make it work like the current version of Huton for Ninja's.

Cast Enochian itself to activate it, and fully refresh it using B4. As long as you stay in combat, and keep an eye on your timers, you could maintain Enochian indefinitely.
With this kind of change, we could feasibly build a rotation which would refresh Enochian in a reliable way, while maintaining high dps (movement mechanics permitting).

Doesn't sound like a bad idea.

Yes I actually like the sound of that. I don't think Blizzard 4 should reduce the max duration, it should be a complete refresh.

when enochian is about to drop of and your at bliazard stage just cast thunder let it drop off then reapply and continue back into fire chain.

the thing I don't like is the slight delay going from fire 3 to fire 4, it waits just a second for the astral fire buff to apply before we can go into fire 4 slowing us down, this of course happens twice in the fire chain. and weirdly it doesn't seem to happen in the blizzard 4 cast.

I agree that bliz 4 should just renew enochian instead of giving us a reduced timer, but maybe just limit its ability to be refreshed to a set number of times.

personally I would like to see the astral fire buff increased by a couple of seconds thus freeing us just slightly to move alittle and still maybe finish our rotation. but not enough to allow another cast before having to refresh astral fire.

a big benefit to this would be that he potential for our recast of fire 3 could still be under astral fire assuming we didn't have to move.

I havnt done the math or intend to but it seems that if theres a good chance we will get interrupted on our fire chain and thus cant complete a full chain then we may aswell be doing our old rotation as its more reliable and flexible with less chance for a dps loss.

Funnily enough the Astral Fire not clicking fast enough for Fire 4 was actually a "bug fix" in 2.1 where people were able to get their first fire spell out after Fire 3 with the reduced cast time. IIRC there was some flare bug with that too.

honeslty I think enochain refreshing is fine with ice 4 and the move itself, dont really think we need the move to reset it, just need to pay attention. However with other things......

1. Make sharpcast be off of the GCD and allow us to use it while we are casting to save us that fill up in our rotation (if they do, make Surecast also off GDC so WE COULD USE THE DAM THING! WE HAVE A FREAKING TRAIT FOR IT BUT NO WHERE IN ROTATION).

2. When enochain or Astral/umbral fall off as OP said we instantly have those moves cut off, no recovery like with any other fire or ice spell after their astral/umbral fall off before move is done, we get like .5-1 extra sec to recover from those to keep us as max astral/umbral. Ice4/fire4 should allow us the same benefit of finishing the move to reapply buff/deal damage before 1 of them falls off, we just seemed to get punished if we try to squeeze one more move in after all the moving we have to do in expansion.

yeah, that 2.1 "fix". the Reason that happened was because you could keep the half cast fire spell with max umbral for 2 moves. I would use fire 3 at launch and be able to use a fire 1 with half cast due to buff not falling off fast enough xD, oh those were the days.

Quote:

---

Originally Posted by HaroldSaxon

Funnily enough the Astral Fire not clicking fast enough for Fire 4 was actually a "bug fix" in 2.1 where people were able to get their first fire spell out after Fire 3 with the reduced cast time. IIRC there was some flare bug with that too.

---

The main reason was people were able to get off two Flares off in a row without any cooldowns. Timing it right, you would still get your mana back after the first Flare and be able to cast the second one with UI3 speed and AF3 damage. Squenix fixed that by putting an aritifical 0.5 second neutral stance window between the switch from UI to AF. The side effect of that was our single target rotation got a lot more awkward with the mana ticks as well.

I may have even been the first one to make the suggestion to use double Flare as AoE rotation on the forums, and it got quickly fixed after. I'm sorry everyone.