Question - Pulling by Con/Level?? (1 Viewer)

[theGreatGizm0]

Searched for a bit and I only found a few references of people saying "I had my toon set up to pull by con" or "i was pulling by level in such and such" but I can't figure out how to set up what levels to pull by in kiss assist?

Is there a way to assign what to pull by con color or level?

 

[wowfool]

This is how I did it, added to Sub ValidateTarget (Line 850 or so)
/declare PullValid int local 0
/declare min int local 5
/declare max int local 12

/if (${DebugCombat}) /echo DEBUGCOMBAT ValidateTarge Validate 2
| Pullers check your con
/if (${Select[${Role},PullerPetTank,PullerTank,Hunter,Puller]}) {
/if (${Target.Level} > ${max}) /return BadLevel
/if (${Target.Level} < ${min}) /return BadLevel
}

The bold parts are what I added. Set the min and max level to pull and it seems to work.

 

[cosyg]

So are the 5 and 12 the actual level of the mobs or variables based on your current lev?

 

[riot]

Wow he over complicated the fuck out of that, lol.

/target range 5 12

Would target the closest mob between between 5 and 12.

 

[ctaylor22]

Wow he over complicated the fuck out of that, lol.

/target range 5 12

Would target the closest mob between between 5 and 12.

He is validating the mob for pulling. you don't want to /target a mob until you are sure it is validated. /target range 5 12 will target the closest mob between 5 and 12, that includes mobs you may want to ignore that are of the same level range.

 

[riot]

I see none of that in his post. I see him going through a targeting loop and canceling the mob if they're higher than x or lower than y. There's no check in there to ignore mobs you don't want to pull either, which would be easily added with noalert #.

Given that he uses ${Target.Level} all of his "validations" take place after the mob is targeted which can result in a constant stream of target -> cancel targets instead of just validating the target BEFORE it's even targeted by using spawnsearch filters.

- - - Updated - - -

Oh I see now he put it in the "validate" sub. But regardless he still uses ${Target} which, last I checked, doesn't work unless the mob is actually targeted.

A better spot to put that is the actual spot where KA searches for spawns before theyre targrted as opposed to after they're targeted.

 

[ctaylor22]

He just needs to change his reference from ${Target.Level} to ${Spawn[${MobID}].Level} and it should still work in the validatetarget routine.

/if (${Select[${Role},PullerPetTank,PullerTank,Hunter,Puller]}) { 
   /if (${Spawn[${MobID}].Level} > ${max}) /return BadLevel
   /if (${Spawn[${MobID}].Level} < ${min}) /return BadLevel
}

 

[riot]

Touche my friend, touche!

 

[ctaylor22]

Not Touche at all, You partially touched on a big change made to the validatetarget routine.

Oh I see now he put it in the "validate" sub. But regardless he still uses ${Target} which, last I checked, doesn't work unless the mob is actually targeted

This change was made due to an announcement made by EQMule. The change had to do with not being able to target mobs greater than a certain distance. The ValidateTarget routine was changed to reference the Spawn TLO and not the Target TLO so distance was not an issue.