soloing: running behind a mob after landing a stun

[dindaur]

[Kneesmasher]

[Luminarius]

[Zorbee]

[dindaur]

[Peaky]

[Blabberpuss Stryyker]

[Zyba]

[Peaky]

[Blabberpuss Stryyker]

[Peaky]

[Zyba]

[Blabberpuss Stryyker]

[Abazzagorath]

[Saeel]

[Zorbee]

[Peaky]

Before Knight's Return Strike, if a mob's dps was sufficiently high to warrant it, I started to stun-lock mobs at around 12% if they enraged (so as to prevent enrage from even happening). Clearly that doesn't work on stun immune mobs, but that used to be such a small percentage of the population

[Wyvernwill]

[Zanador]

I generally don't stun lock because I like to see crap dead before they bring the last server down when soloing so I rely heavily on damage shields for more dps and that don't work if you lock a mob and it doesn't hit you.

[Zorbee]

For my own benefit:

Sacred Force 75/4.00s Cast Time 1.0, Recast 12.0
Force of Timorous 80/4.00s Cast Time 1.0, Recast 12.0
Lesson of Contrition 80/5.25s Cast Time 2.0, Recast 24.0


Theoretically, here is the best you could do.

01: Cast SF 1.0
02: SF Lands (recast at 14), Stunned 1
03: Stunned 2
04: Stunned 3
05: Stunned 4, Cast FoT 1.0
06: FoT Lands (recast at 18), Stunned 1
07: Stunned 2
08: Stunned 3
09: Stunned 4, Cast LoC 2.0
10: Unstunned Round of Combat
11: LoC Lands (recast 35), Stunned 1
12: Stunned 2
13: Stunned 3
14: Stunned 4, First available recast: Cast SF 1.0
15:Stunned 5, SF Lands (recast at 27) Stunned 1
15.25 LoC End
16: Stunned 2
17: Stunned 3
18: Stunned 4. Cast FoT 1.0
19: FoT Lands (recast at 31) , Stunned 1
20: Stunned 2
21: Stunned 3
22: Stunned 4
23: No here's where you have a break down. You'll have at least one, possibly two rounds of combat before your next stun can be cast.
SF can't land for another 5, LoC for 14.

But there are many problems with this table.

#1. Fizzles. A fizzle will stop a recast for 2.25, while you could switch to the next available stun, that won't be possible since you are at absolute max timers.

#2. Mob interrupts. Same as fizzles in problem although you can usually recast faster.

#3. This cast and recast demands that you cast at the exact time. However, for the first durations, your spell will already be ready and if you have a spam hot key (like /cast 6, /cast 7, /cast you'll actually cast FoT one second earlier and LoC two seconds earlier. This will allow you to miss the first round of combat in the guide, but it means you'll have longer and longer recast waits.

So taken in consideration that the only realistic way to have multiple stuns set up is a stun spam key, I'm going to have to do some testing with the same spell recasts (i have the lower versions since only 70, but same cast times, recast times, just lower levels). However, I think that this result will be in the same results ballpark as previous testing. That stun lock with 3 stuns is not possible. Even 4 seconds out of 24 is a very gracious and optimistic declaration.

[dindaur]

[Wyvernwill]