• Hail, we're RedGuides. We want you to play six (yes, 6!) EverQuest characters at once. We have scripts and a friendly community to help, please join our playstyle and say hello! 👋
KissAssist

KissAssist Release KissAssist (5 Viewers) 12.002.40

Join Level 2 to download
Overview Commands Instructions Updates (71) Reviews (5) History Discussion
Any try using the new PULLPAUSE COND option? I'm using it to call if one of two buffs are off and it works to stop pulling. However the puller (Chanter) doesn't cast the buffs on herself and then resume pulling. It just keeps messagein MQ2 that holding pulling due to pull hold condition. Any ideas please, tried using 0 time to wait and 1.

Cond:
Cond13=!${Me.Buff[Eldritch Rune XXXVIII].ID} || !${Me.Buff[Ward of the Beguiler].ID}

Buff Settings.
BuffsOn=1
BuffsSize=14
Buffs1=Voice of Perception
Buffs2=Hastening of Jharin
Buffs3=Shield of Inevitability
Buffs4=Ward of the Beguiler
Buffs5=Marvel's Unity
Buffs6=Staff of Eternal Eloquence|cond5
Buffs7=Eldritch Rune
Buffs8=Veil of Mindshadow
Buffs9=Night's Perpetual Terror|ma
Buffs10=Gather Mana|Mana|50|cond1
Buffs11=Glyph Spray
Buffs12=Summoned: Dazzling Modulation Shard|Mana|75|80
Buffs13=Twincast Aura|Aura
Buffs14=Mana Radix Aura|Aura
RebuffOn=1
CheckBuffsTimer=1
PowerSource=NULL

;pull with AA slow
PullWith=Slowing Helix
PullMeleeStick=0
MaxRadius=800
MaxZRange=200
UseWayPointZ=0
PullWait=5
PullRadiusToUse=90
PullRoleToggle=0
ChainPull=1
ChainPullHP=40
PullPause=30|1|Cond13
PullLevel=0|0
PullArcWidth=0
PullOnReturn=0
[PullAdvanced]
PullLocsOn=0
 
Hello all,

New problems with Melee for my group running Kiss. It seems sometimes the toons will assist the main and start casting spell but they will not run the engage the mob. Happens on RNG, BST, BRD after each pull with bard pulling. Camp radius is all set to 60 on each . Tank is set to 50 to make sure there isnt camp creep. However, Is there just a way to make the MT issue a command at the start of each new mob to bring melee to him only. Kinda like a Docommand?

I also have chase set to ON but this does not fix the problem.
 
In your KissAssist ini's are you setting them to Role assist

I use this hot key for the ones that use KissAssist:

/mac kissassist assist ${Group.MainTank} 98

Also in the KA ini check the Melee section.

[Melee]
AssistAt=98
MeleeOn=1
FaceMobOn=1
MeleeDistance=75
StickHow=snaproll
AutoFireOn=0
UseMQ2Melee=0
TargetSwitchingOn=1

Zeb
 
Zebadiah said:
In your KissAssist ini's are you setting them to Role assist

I use this hot key for the ones that use KissAssist:

/mac kissassist assist ${Group.MainTank} 98

Also in the KA ini check the Melee section.

[Melee]
AssistAt=98
MeleeOn=1
FaceMobOn=1
MeleeDistance=75
StickHow=snaproll
AutoFireOn=0
UseMQ2Melee=0
TargetSwitchingOn=1

Zeb
Click to expand...

Yep role is assist

i use just /mac kissassist with MT targeted. Default for assist i have assigned is at 99. Then set DPS stuff at 97 to give them time to move over to mob.

[Melee]
AssistAt=99
MeleeOn=1
FaceMobOn=1
MeleeDistance=40
StickHow=snaproll rear
AutoFireOn=0
UseMQ2Melee=0
TargetSwitchingOn=1

This is mine above.

MT will engage and they will stay at camp sometimes and not move.

Also changed below to see if it would help with chase and nope:

[General]
KissAssistVer=12.002
Role=Assist
CampRadius=90
CampRadiusExceed=100
ReturnToCamp=0
ChaseAssist=1
ChaseDistance=15
 
Can anyone please help me out? I have plenty of Balanced Axe Components and it actually summons the axes but after summoning it I am seeing this:

ABC - [2022/01/06 22:18:01] Summoned >> Deathfury Axe <<
ABC - [2022/01/06 22:18:10] Summoning >> Deathfury Axe << Failed - Check reagents, timer, etc
ABC - [2022/01/06 22:18:10] -- Turning off Deathfury Axe - Deathfury Axe|Summon|Deathfury Axe|0
ABC - [2022/01/06 22:18:10] I now have 60 of >> Deathfury Axe <<
ABC - [2022/01/06 22:18:10] You are missing components. Turning off Deathfury Axe.

Here is my config:

Buffs2=Deathfury Axe|Summon|Deathfury Axe|100|Cond1
Cond1=${FindItemCount[=Balanced Axe Components]}>4
 
Kar said:
Can anyone please help me out? I have plenty of Balanced Axe Components and it actually summons the axes but after summoning it I am seeing this:

ABC - [2022/01/06 22:18:01] Summoned >> Deathfury Axe <<
ABC - [2022/01/06 22:18:10] Summoning >> Deathfury Axe << Failed - Check reagents, timer, etc
ABC - [2022/01/06 22:18:10] -- Turning off Deathfury Axe - Deathfury Axe|Summon|Deathfury Axe|0
ABC - [2022/01/06 22:18:10] I now have 60 of >> Deathfury Axe <<
ABC - [2022/01/06 22:18:10] You are missing components. Turning off Deathfury Axe.

Here is my config:

Buffs2=Deathfury Axe|Summon|Deathfury Axe|100|Cond1
Cond1=${FindItemCount[=Balanced Axe Components]}>4
Click to expand...
${FindItemCount[=Balanced Axe Components]}
should be
${FindItemCount[Balanced Axe Components]}
maybe?
 
random question of the day. i am having a minor problem with my druid not breaking invis to cast anything. if i manually break his invis he works just fine, he just wont break invis.

any help would be great.
 
create a hotkey that uses /makemevisible or use it as a DPS entry with a condition. The condition is so one day when you want them NOT to break invis you can control it easier. Also you can use the ambush tag so they break invis before combat.
 
Does anyone know how to correct this minorly inconvenient issue? I am running 25 characters and the characters I use on KA tend to stop and wait until either the first mob on xtar is clear or all are clear when in chase mode and mobs are out of line of sight, i think it might be that the character doesnt start chasing my MA right away. they also seem to get stuck and not chase during events such as the mastery or hate trial, and any others where I am moving around a large area. and when i say stuck i mean that they just do not move, not that they are hung up on any objects / terrain.
 
Are the Characters that are being left behind sending a message like "Hey! I got left behind please run me to ChaseCharacterName"? Chasing characters will drop out of the chase routine when they have agro and are with in CampRadius of who they are chasing, or the character they are chasing get's to far away, either CampRadiusExceed, or Zdistance >100 away. There are times when a character will be casting a spell that takes a long time to cast, will be left behind.

For time when you have characters that don't make the trip with you. You can always use the /trackmedown command to get them to run to the chase character. From the chased character, I use /bca //trackmedown to send the command to everyone in the group.
 
ctaylor22 said:
Are the Characters that are being left behind sending a message like "Hey! I got left behind please run me to ChaseCharacterName"? Chasing characters will drop out of the chase routine when they have agro and are with in CampRadius of who they are chasing, or the character they are chasing get's to far away, either CampRadiusExceed, or Zdistance >100 away. There are times when a character will be casting a spell that takes a long time to cast, will be left behind.

For time when you have characters that don't make the trip with you. You can always use the /trackmedown command to get them to run to the chase character. From the chased character, I use /bca //trackmedown to send the command to everyone in the group.
Click to expand...
they are not saying anything, they just stay put. the trackmedown is working though so thanks for that :D would be nice if i could figure out something in the .ini file to make them do it on their own :/
 
I am having a weird issue. With no target selected, when I type /mac kissassist, no ini file is created for my necro or SK. Any idea why it will not create a kiss file for these 2? I think these are the only 2 I have never used in KISS.
 
Have you tried to do this.... /mac Kissassist 12

I do this when I start a new character and it generates the KA ini file.

NOTE: Might want to check and see if it is creating the file but puts it some place else.

Zeb
 
new trouble,,, when ill do /mac kissassist i didnt get new ini file for toon, do they going somewhere else these day instead of macro file?
 
eqjack said:
humm using legacy... do i need change for next?
Click to expand...
Legacy will soon be gone.

If you're not on emu, yup



It is OFFICIAL! MacroQuest is the version of MacroQuest that we offer here at RedGuides.

You will see this with "MacroQuest - Live" in the RG Launcher.

Please, check out this link: >>> Functions & Features Demo + Migration to the new MacroQuest<<<

There are a couple of small, yet important changes with MacroQuest:
1. mq2map click is Control+Shift+Click
2. new easyfind self travel is Control+Click (reminder in find window title bar)
3. new easyfind group travel is Control+Shift+Click
4. If you selected a destination in your zone guide and want to activate it you /travelto activate
5. /yes and /no are now aliases
6. your ini configuation files (like for kissassist) now reside in your "Config" folder and not your "Macro" folder
 
Szazor said:
View attachment 31375

If I have 2 groups camping in the same area and 2 pullers chain pulling.....Can I turn this PCNear setting off?

I have turned off afktools, and posse. cant seem to find where its coming from.
Click to expand...

Seems this issue never got resolved.

Using EQEmu, the RoF client, in a custom server... I am the only PC in the game so I can't imagine why it thinks otherwise.

Is there anything I can do to side step this check, in the mean time?

To further clarify the issue. It seems the PCNear issue is related to hunter role... Using pullertank, seems to have resolved it.
 
Last edited:
wymranar said:
Just switched over to next and /mac kissassist isn’t working. Did the nomenclature change?
Click to expand...
no it didn't, but make sure by "not working" you don't mean that your ini doesn't appear to be changing/created



There are a couple of small, yet important changes with MacroQuet vs the old MQ2 as explained > HERE <

Moving to MacroQuest mental notes:
1. mq2map click is Control+Shift+Click
2. new easyfind self travel is Control+Click (reminder in find window title bar)
3. new easyfind group travel is Control+Shift+Click
4. If you selected a destination in your zone guide and want to activate it you /travelto activate
5. /yes and /no are now aliases
6. your ini configuation files (like for kissassist) now reside in your "Config" folder and not your "Macro" folder
 
Are there any known issues with KA atm since the 64bit update? For some unknown reason my cleric went full dumb all day yesterday randomly, and just decided it would only heal the assist person and nothing else, not even himself. No changes on my end in terms of my .ini or version of MQ, was working fine pre-64. When I loaded the ini everything would be fine, but after a couple mobs it would go back to choosing not to heal anyone but the assist.
Thoughts?
 
Last edited:
ctaylor22 updated KissAssist with a new update entry:

KissAssist 12.002.009 Update

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...
Click to expand...

Read the rest of this update entry...
 
Getting an undefined variable warning on line 8203 for the variable ${PetAttackDistance}. Searched the code and could not find it declared anywhere unlike the other pet variables. Macro is paused but seems OK after an /mqp. Running on a bard, so hopefully won't see any issues.

This is related to a new INI setting?
 
Hmmm.. I can see where that could be an issue... But kissassist doesn't take into account that your MA is in a raid. Might take a bit of thought on how to handle something like that.
 
ctaylor22 said:
Hmmm.. I can see where that could be an issue... But kissassist doesn't take into account that your MA is in a raid. Might take a bit of thought on how to handle something like that.
Click to expand...
When the MA targets players or does things like switch to named mobs to get agro and switch back, the KA has a terrible time getting off that target (on our server in our guild). I have no sample size outside of our people. Seems everyone else just doesnt play anyone who requires a class plug or something anymore cause I never hear anyone have this issue, but we all have this issue, especially with bards that love to get stuck on the wrong mob when we're switching on raids. If you need any examples I would be happy to talk to you about it. Fixing it would keep our bards alive a lot more on raids.

Plus side is, I did the Basillica mission yesterday without having to reboot my shaman when i got adds on the final boss. Thats a new one.
 
Log in Join to reply
KissAssist Release KissAssist
Next unread thread 🦁

Users who are viewing this thread

  • T
Total: 6 (members: 1, guests: 5)
Join Level 2
Back
Top
Cart

Cart

Total -