Rooster
Well-known member
- Joined
- Jan 2, 2014
- RedCents
- 1,611¢
- Version of KissAssist.mac?
- 11.001
- When did your problem start?
- Since i started using it
- Character Role?
- PullerTank
- What class is having this issue?
- Warrior
- How often does this issue occur?
- Always
- Can you reproduce the issue?
- yes
I have noted that if a mob has wandered into camp and either been messed by my enc, or aggros a group member/pet and remains far enough away to be outside of the MeleeDistance range the tank never engaged or adds it to an add list
After turning on /debug i see it enter and leave the MobRadar and other stuff as if it's just waiting for mobs to spawn to pull
If i manually /varset MeleeDistance to a number in which the add is within the radius it will engage it
But this doesn't make sense, why is MeleeDistance (the distance which you engage at? ) vs CampRadius (radius which to consider mobs within your camp ?) If an add is within a CampRadius AND aggro (on xtarget/beating up a player or pet) should it not engage anyhow?
Maybe im missing something, i have only in the past couple weeks started to really use this
After turning on /debug i see it enter and leave the MobRadar and other stuff as if it's just waiting for mobs to spawn to pull
If i manually /varset MeleeDistance to a number in which the add is within the radius it will engage it
But this doesn't make sense, why is MeleeDistance (the distance which you engage at? ) vs CampRadius (radius which to consider mobs within your camp ?) If an add is within a CampRadius AND aggro (on xtarget/beating up a player or pet) should it not engage anyhow?
Maybe im missing something, i have only in the past couple weeks started to really use this

