Question - Firing off too soon.

[Adahman]

Hi all,
I have a mage with the following DPS section:
DPSOn=1
DPSSize=5
DPSSkip=20
DPSInterval=2
DPS1=Bolt of Flame|65|Once
DPS2=NULL
DPS3=NULL
DPS4=NULL
DPS5=NULL

He fires off that Bolt of Flames as soon as the MOB is in camp. I thought the DPS1 statement says not until 65? Or am I missing something?

 

[reedreddington]

I do not use those values that way. I have not seen it work properly, per the wiki, myself. I use the AssistAt [Melee] values to control when my casters are nuking. If your mage seems to die on every pull adjust the AssistAt value much lower while keeping the PetAssistAt values high

 

[nitramneb]

You could also add a condition like Cond1 = ${Target.PctHPs} < 65 (in KConditions section of ini), which would make sure it doesn't fire before that. just |Cond1 after your current DPS entry.

 

[pascualito]

Use DPSOn=2
Should work

KissAssist - Read?Guides

www.redguides.com

 

[nitramneb]

With condition, DPSOn=2 will work - DPSOn=2 doesn't use the number as a health level, it just orders the DPS entries in descending order. So if 65 is the first number, it's going to fire as soon as the engage % in Melee is hit.

 

[kaen01]

i am wondering if the |once tag overwriter the hp number in this case..

 

[Sic]

i am wondering if the |once tag overwriter the hp number in this case..

That's my thought

 

[Adahman]

So, so far I've taken the |once tag off and changed the DPSOn=1 to 2. He still fires off as soon as his pet attacks. Does it matter that the pet is party tank?

 

[Adahman]

Nevermind! Nitramneb was right. the conditions were the fix. Thanks all.

 

[exocet]

DPS1=Bolt of Flame|65|Once

should be the fix to this issue...

When your mob enters camp, it’s often already Below 100% (pulled, dotted, or hit on the way in). Sometimes even < 65% by the time your mage evaluates DPS, meaning the mob is already under 65% → OK to cast immediately

Goodluck