Question - what can i change to make surly KA casters obey their ini

[timmy]

Version of KissAssist.mac?

12.02

When did your problem start?

long term problem

Character Role?

1. Assist

What class is having this issue?

1. Beastlord
2. Enchanter
3. Magician
4. Shaman
5. Wizard

How often does this issue occur?

Sometimes

Can you reproduce the issue?

yes, but not on demand.

sometimes, but not always, my ka casters, including hybrids, ignore their ka settings for when to engage a mob. they will ignore some/all of the settings in the CampRadius, AssistAt, MeleeDistance, or the MobHealth% in their DPS section.

example settings i use:

CampRadius=35

AssistAt=99

MeleeDistance=50

DPS14=Barrage of Many|98

i've watched a naughty mage break all these settings by casting on mob at 100 percent health outside the camp and meleedistance numbers. should that even be possible? are the CampRadius and MeleeDistance combined to determine the range at which a caster or hybrid will engage with spells?

i used KA to pull on my tank so i could watch the mage and can confirm that the tank didn't call for attack. and even if he did, would that change the behavior of my ini settings? i've also seen this behavior when i play my tank manually, which is 95 pecent of the time.

i've watched, actually watched, this scandalous mage follow his settings on a mob pulled from spawnpoint x only to ignore those settings on the repop of the same mom from spawnpoint x. no, he doesn't worship bristlebane.

the problem is i can't predict this behavior. it will always happen eventually, but it doesn't seem to follow any rules. i've posted randomly about this before and followed some others who've had similiar issues. i don't believe this is a LOSBeforeCombat issue, because i've witnessed the behavior w/ and w/o this setting being enabled.

this problem seems limited to casters and hybrids. my pure melee don't engage early. ever. my bl is by far the worst offender, to the point where i've benched him. even putting his AssistAt, PetAssistAt, and DPS values to 90 percent doesn't keep him from flying out of camp to engage a pulled mob at 100 percent in the middle of nowhere.

anyone have any insight? i'm considering trying a hard range check condition for each DPS entry but that seems excessive.

 

[Amarth]

dpson=2

 

[stvski]

Mage stuff
check pet attack distance in your ini
also make sure pet hold is on - without pet hold on - any spell that hits the pet will cause him to attack -

 

[timmy]

dps=2 is the only way I roll. pet hold is on and pet attack distance is at 50. tank is marked assist. toons are started with proper tank. meshes are updated. toons have food and water.

 

[stvski]

random thought
I have noticed when i used kiss - when my lag-0-meter got above 300ms - crazy shit would happen when boxing all my 6 toons on one computer

something else to check is your frame limiter settings

 

[ctaylor22]

if your mage is in group with your MA, the Call from the MA is not needed. The Call from the MA is for out of group characters assisting the MA.

When you start kiss check the message the echos your assistat value "/echo KissAssisting >> ${MainAssist} << at ${AssistAt}%"

Your DPS and/or Melee characters have to enter the combat routine to start combat. Once in the combat routine there are 2 checks that are done that will start combat.

Here is the logic that will start DPS/Combat or dump you out of the routine.

Main Melee/DPS Start check:

/if (${Spawn[${MyTargetID}].Type.NotEqual[Corpse]} && ${Spawn[${MyTargetID}].PctHPs}<=${AssistAt} && (${Spawn[${MyTargetID}].Distance}<${CombatRadius} || (${Math.Distance[${CampYLoc},${CampXLoc}:${Spawn[=${MainAssist}].Y},${Spawn[=${MainAssist}].X}]}<=${CombatRadius} && ${Math.Distance[${Target.Y},${Target.X}:${Spawn[=${MainAssist}].Y},${Spawn[=${MainAssist}].X}]}<=${CampRadius}))) {

Here is the break down:
if attack target is not a corpse "AND" attack targets percent of HP is less than or equal to AssistAt "AND" 1 of the following checks has to be true.

attack target distance has to less than CombatRadius "OR" Mainassist distance has to be in CombatRadius of your camp location "AND" your current target has to be within CampRadius of the Main Assist.

There is a secondary check that is done if the above logic fails. This check is mainly for pet class characters that send in their pets before they start DPS/Melee and for support characters that mez and debuff before they start attacking(AssistAt)

/if (${Spawn[${MyTargetID}].Distance}<${CombatRadius} || (${Math.Distance[${CampYLoc},${CampXLoc}:${Spawn[=${MainAssist}].Y},${Spawn[=${MainAssist}].X}]}<=${CombatRadius} && ${Math.Distance[${Target.Y},${Target.X}:${Spawn[=${MainAssist}].Y},${Spawn[=${MainAssist}].X}]}<=${CampRadius})) {

here is the break down:
if attack target distance id less than CombatRadius "OR" the following:
Mainassist distance has to be in CombatRadius of your camp location "AND" your current target has to be within CampRadius of the Main Assist.


Not sure if this helps any, but getting a debug log of the mage from before the MA goes to pull the mob, till after the mage starts to attack, could be of use. Just PM me the log and I will take a look.