Question - Why does this particular paladin DPS section constantly spam?

[RoboClaptrap4]

Here is my paladin's DPS section. Why does he constantly spam every stun in this list, instead of respecting the DPSInterval=4 line? Any ideas? Every other character seems to behave normally, but for some reason my paladin has no patience for that and just goes full ham with every stun, wasting them by repeatedly stunning an already stunned mob

[DPS]
DPSOn=1
DPSSize=20
DPSSkip=20
DPSInterval=4
DPS1=Cease|100|cond1
!DPS2=Divine Stun|100|cond2
DPS3=Force of Piety|100|cond3
DPS4=Ancient: Force of Jeron|100|cond4
[KConditions]
ConOn=1
CondSize=4
Cond1=${Me.SpellReady[Cease]}
Cond2=${Me.AltAbilityReady[Divine Stun]}
Cond3=${Me.SpellReady[Force of Piety]}
Cond4=${Me.SpellReady[Ancient: Force of Jeron]}

 

[RoboClaptrap4]

I did find a solution to my issue (adding a !${Target.Stunned} condition), but I'm still curious what the rules of DPSInterval are and why they didn't seem to apply here. Is it because stuns technically have a duration?

 

[Many_Whelps]

DPSinterval affects nukes that do instant damage so that you can pace out your DD spells. Because those stuns have a duration and, I'm assuming, put a debuff on the mob, KISS doesn't know that they are, in effect, redundant. Until you tell it. That's why adding the condition works. DPSinterval isn't meant to be a blanket "wait X seconds before moving to the next DPS#".

 

[kaen01]

@SA_krycek is right, DPS interval is wierd, but i dont agree with him that it shouldnt be a blanket "wait x seconds" because thats how its specified as in the instructions for kiss:

DPSInterval 2 Any # Attaches a timer in seconds to DPS spells with 0 duration after they are cast. If you are nuking too fast you can slow down by increasing the interval.

zero duration to me, means dots, not nukes and stuns, and personally on my mage i have tried to set it to both 1 and 100 and it never worked slowing down his nukes, i mentioned this to @ctaylor22 and @Maskoi, that it might be broken.