Combat Assist KissAssist 12.002.038

The issue was that both ReturnToCamp and ChaseAssist were turned off and the distance from camp was greater than MeleeDistance. So made a change to use MA's Location, in place of camp location, when ChaseAssist is on or ReturnToCamp is off.

Who would of thunk?

Special Thanks goes out to @ShadowPanda for all the help.

My bad. I forgot to remark out the kissmycmds.inc line at the end of the macro.

This should fix the issue with Writebuffs using the Buffs Window and kicking out errors. Not thoroughly tested, so be careful out there.

Added additional Event filter entry, to trap for Spell interrupted message.

Updates to fix the PetAttackDistance for non pet classes.

This is a quick summary of some changes and additions added to KissAssist this Update:

1. Added a check for when a character joins your group. The check is used to force the CheckecBuffs routine to re-check buffs on everyone, and reset all buff timers.
2. Added a check to try and target the highest level mob in camp when there is no named in camp. This is dependent on the mob being in range of the MA when selecting from multiple targets.
3. Fixed an issue when using a wild card search for MobsToPull. "MobsToPull=a shak dratha*,a gor taku*" will now find and pull the correct mobs.
4. Consolidated the Pet attack code. Moved the /pet swarm command into the PetCombat routine.
5. Fixed an issue with not triggering queued events properly.
6. Added a check for Non-Melee characters, to break invis when in the combat routine. Had to make a few changes to keep from breaking the Aggro routine where characters would FD or Fade to loose aggro.
7. In the CombatCast routine, the MA and MAOnce tag will now target your pet if "pettank" is found as part of your Role.
8. When in Chase mode. The MA's location is used to determine if mobs are in range to engage in combat, and not the camp location.
9. Fixed an issue with !class and !class using the dual tag. Some classes were getting buffed.
10. Added a check to turn /pet taunt off if your character is in an assist type role.(Why in the hell does my pet keep dying?)
11. OpenInvSlot routine now uses ${Me.NumBagSlots} to figure the number of top level inventory slots you have available.
12. Fix an issue when trying to set the MA with like named characters. The AssignMainAssist routine now uses exact name matching.
13. /zoneinfo command now shows the PullLoc's in the Kissassist_info file for the current zone. When PullLocsOn is set on.
14. Macro now checks and loads the MQ2Rez plugin, when it is not loaded, and you have RezAcceptOn set.

Hunter Role Changes:
FindMobsToPull will now search for mobs using the characters current location and if no mobs are found,
then will try and find mobs using the characters camp location.
Pet will now be sent to aggro mob when the mob is close, and not bother using PullWith.
Pet is now summoned to you if the pet is to far away and you need the pet to attack your target.
Uses the "Summon Companion" AA, if you have the AA.

Mez logic Changes:
Found an issue where if the MA breaks mez, on a mob that is NOT the MA's target. The mob was not getting re-mezed.
This can happen when the MA pulls with a DOT spell and the initial mob selected by the MA, to tank in camp. Is not the mob he pulled.
Added a message for when the MA breaks mez on a mob.(Tell the MA to stop pulling with a DOT spell)
Fixed an issue when AE mezzing. If one of the mobs resisted the AE mez, the caster could/would get stuck in a loop re-casting the AE Mez.

This update will affect those using the !class tag in the [Buffs] section only. So if you don't use the !class tag for buffs. Then you can ignore this update.

Sorry for the double updates today.

Fixed an issue where Melee characters would take off running after targets outside of MeleeRange.

Added a new flag to the [General] section LOSBeforeCombat=0/1 The default is 0(off) so your combat(Melee and Casters) won't try and get Line Of Sight on mobs before they start combat. This function, when turned on, checks for MeleeDistance before it engages. This function was added mainly for Melee, when fighting in locations where there are obstacles(Walls, rocks, stumps, etc...) keeps the character from engaging because the mob is not in LOS, but is in MeleeDistance range. This function is executed before the combat routine is entered. Movement is then controlled from within the combat routine.

For non-melee DPS(Casters) this will move them towards the mob until they obtain Line Of Sight, and then stop them there before dropping them into the combat routine. It is strongly recommended that you only use this functionality with MQ2Navigation as your primary movement utility. Only in very specialized situations would you be able to use this functionality without MQ2Navigation, but it is not recommended.

If all your casters are running closer, to a mob than you think they should be, it most likely has to do with framerate(s). The routine will try to obtain LOS for a max of 5 seconds. While your character is moving towards the Mob. LOS is being checked every 1-10th of a second, or basically 10 times a second. When LOS is obtained the character is stopped(/nav stop, /moveto off) at that location. If the 5 seconds expires and your character has still not obtained LOS, then the character is stopped at their current location and the routine exits.

OK Guy's this worked for my group using the /pettoysplz group command. Give it a try and let me know.