![]() |
|
|
|
#1
|
|||
|
Not sure what you’re talking about #1 slot, it doesn’t have some special exemption. The number slot has nothing to do with GCD reset. That’s something that applies to any slot that isn’t currently on cool down.
Read Loraen’s guide here that specifically talks about spell line ups. You will get a general feel for what you should be using. He even has a few YouTube videos linked of some solo battles I recommend you watch them you’ll get a feel for how switching it done at the highest level. https://wiki.project1999.com/Loraen%27s_Enchanter_Guide | ||
|
|
|||
|
#2
|
||||
|
Quote:
| |||
|
|
||||
|
#3
|
||||
|
Quote:
OP, I'd probably use mez for this little trick/bug/exploit. Being able to get one off quicker is nice. Seems most are using Root/Mez for this slot. | |||
|
Last edited by Crede; 12-15-2018 at 11:44 AM..
|
|
|||
|
#4
|
||||
|
Quote:
You are correct that if you absolutely spam you can sometimes get a 2.25 recast spell to fail with the spell timer error. You have to wait a slight pause. I don't think the OP was talking about the top slot over-riding the recast time (other than the GCD) of longer recast spells. | |||
|
|
||||
|
#5
|
||||
|
Quote:
| |||
|
|
||||
|
#6
|
||||
|
Quote:
I think you are just under-estimating the time. Dazzle loaded in first slot: 1) cast dazzle >>> hit instant item >>> cast dazzle = spell error 2) cast dazzle >>> hit instant item >>> **wait 1 sec** cast dazzle = spell error 3) cast dazzle >>> hit instant item >>> **wait 2-3 sec** cast dazzle = success The result is how I described it in a previous post, but I tested it this morning after I saw you post to see if I could recreate what you describe. | |||
|
|
||||
![]() |
|
|