• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver

Problem - KA assisting

Twinkeltoes

Active member
Joined
Jan 8, 2022
RedCents
698¢
Version of KissAssist.mac?
v12.002
When did your problem start?
Off and on for a while. Noticed it mostly on my wiz and druid, But recently with bard
Character Role?
  1. Assist
What class is having this issue?
  1. Bard
How often does this issue occur?
Often
Searched and found similar issues but nothing that helped me resolve mine. First issue is KA doesn't always want to assist. I run KA on my 2 Bards, Wiz, and druid (also my ranger but I don't use him enough to track if this is an issue). Sometimes both when I'm playing them in group or outside in a 2nd group the KA toons seem to be lagging on assist or just simply not assisting and staying in one spot. All my KA are from the .ini library. I've never made adjustments to any conditions as frankly i'm just not comfortable in my experience to make them yet. I have added lines to buffs to account for which clickies I have.
I've tend to like to have my bard in the 2nd group to assist out of group with as most of my other toons are running CWTN and they can assist the bard while the tank/healer fight out of group. Sometimes I'll have a camp they assist from and sometimes I'll go hunter mode on tank and let the bard's group chase. The past couple of days I've noticed my bard would chase, but not always assist when the fight started. At first I thought it was because mobs were in a little cubby and there were LoS issues. I didn't think that should matter but I changed my ChaseDistance to be ontop of the tank as well as my MeleeDistance to be on the mob. To ensure there wasn't issues there.
I'm not sure why he's running around following the tank like he should, but randomly assisting or not assisting. Even when I try to set the assist at 100 or 99.
 

Attachments

One thing that I'm seeing is that your MeleeDistance is too small. I think it's a common misconception, but MeleeDistance=10 means that if the mob is more than 10 away from you, you won't engage the mob at all.

I'm not sure whether StickDistance actually does anything; someone else can perhaps chime in here, but you'd achieve the same result by changing "snaproll" to "snaproll 10" in your StickHow. I'd recommend setting your MeleeDistance to be a bit bigger than your ChaseDistance, or a little smaller than your Tank's CampRadius if you're using a camp. In your .ini I'd probably set it to 30 or 45? But setting it to 10 means you'll fail to engage a lot of mobs.
 
ooof, yea I downloaded and opened the ini file you posted...... It looks to me like it is two different files put into one. Maybe it was a copy and paste from one file into another? Either way, you have duplicate sections all over the place with different settings. I would start by either cleaning that up or by making a new ini file and copying 1 section at a time to it ensuring that each section has the settings you want. That or maybe delete the whole thing and go download a new one. When I get home from work tonight, I can share a 120 NOS bard ini file that works well for me.

I do agree with @manydills the most probable cause of the bard not engaging is the melee distance being set too low in the [melee] section. I typically set my melee distance to 5 more than whatever the distance is on my tank. My tank is usually 55 and all of my assist chars are at 60.
 
Here's my 120 bard, fair warning it blows through mana like crazy sometimes. So I also use mq2react for rallying solo to keep mana up to date. The reacts I use are:

[CODE title="MQ2React Bard Rally Pause"] BardRallyPause:
action: >-
/multiline ; /mqp on ; /twist off ; /alt act 1136 ; /sit ; /timed
400 /mqp off
condition: >-
${Me.CombatState.NotEqual[COMBAT]} && ${Me.AltAbilityReady[Rallying
Solo]} && ${Me.PctMana} < 30 || ${Me.CombatState.NotEqual[COMBAT]}
&& ${Me.AltAbilityReady[Rallying Solo]} && ${Me.PctEndurance} < 30[/CODE]
 

Attachments

One thing that I'm seeing is that your MeleeDistance is too small. I think it's a common misconception, but MeleeDistance=10 means that if the mob is more than 10 away from you, you won't engage the mob at all.

I'm not sure whether StickDistance actually does anything; someone else can perhaps chime in here, but you'd achieve the same result by changing "snaproll" to "snaproll 10" in your StickHow. I'd recommend setting your MeleeDistance to be a bit bigger than your ChaseDistance, or a little smaller than your Tank's CampRadius if you're using a camp. In your .ini I'd probably set it to 30 or 45? But setting it to 10 means you'll fail to engage a lot of mobs.
I didn't know that, I'll try playing around with that setting, but that is actually a new thing I experimented with trying to see if it'd work and it didn't. I'll try to set it to 60 and see what happens, but I believe that was the original setting.
 
ooof, yea I downloaded and opened the ini file you posted...... It looks to me like it is two different files put into one. Maybe it was a copy and paste from one file into another? Either way, you have duplicate sections all over the place with different settings. I would start by either cleaning that up or by making a new ini file and copying 1 section at a time to it ensuring that each section has the settings you want. That or maybe delete the whole thing and go download a new one. When I get home from work tonight, I can share a 120 NOS bard ini file that works well for me.

I do agree with @manydills the most probable cause of the bard not engaging is the melee distance being set too low in the [melee] section. I typically set my melee distance to 5 more than whatever the distance is on my tank. My tank is usually 55 and all of my assist chars are at 60.
Ya, that was an error I when I copied it to bring it here, I made a new file that I didn't clear properly. It wasn't the actual file as the original had the toons name on the .ini. I thought I was being cleaver submitting an bard.ini file and turned out I double pasted or something lol.
 
Here's my 120 bard, fair warning it blows through mana like crazy sometimes. So I also use mq2react for rallying solo to keep mana up to date. The reacts I use are:

[CODE title="MQ2React Bard Rally Pause"] BardRallyPause:
action: >-
/multiline ; /mqp on ; /twist off ; /alt act 1136 ; /sit ; /timed
400 /mqp off
condition: >-
${Me.CombatState.NotEqual[COMBAT]} && ${Me.AltAbilityReady[Rallying
Solo]} && ${Me.PctMana} < 30 || ${Me.CombatState.NotEqual[COMBAT]}
&& ${Me.AltAbilityReady[Rallying Solo]} && ${Me.PctEndurance} < 30[/CODE]
Thx, I'll give this a try later this week. I appreciate it.
 
Problem - KA assisting

Users who are viewing this thread

Back
Top
Cart