• 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

KissAssist Release KissAssist 7 Updated 09/22/2014 v7.6.1

Maskoi

old and salty
Joined
Sep 28, 2005
RedCents
82,796¢
attachment.php


KissAssist 7 Updated 09/22/2014 v7.6.1

Instructions/Settings Info Click Here

Current Features


  • Supports all classes for DPS Melee, Caster and Bards
  • Supports any level character
  • Set up characters to Pull, Tank or Assist others.
  • Select Player, Mercenary or Pet as Main Assist
  • Toons can follow Main Assist, remain stationary or return to anchor spot after mob dies.
  • Pets supported
  • Keep all buffs up Auras, Group, Self, Pet and Clickys
  • Creates an ini file for each toon
  • Separate Melee and Casting DPS settings.
  • Single Buff section for ease of use supports Spells/AA's/Items
  • Single DPS section for ease of use Spells/AA's/Items/Discs
  • Auto Mana/Endurance med detection depending on class.
  • Med settings to turn ON/Off and percentages to Start/Stop
  • Separate Bard twist setting for combat and non combat
  • Single Heal section for ease of use. Heal with any class or your pet
  • Loot mobs and set up what items to keep. sell, or destroy via ninjadvloot and separate loot.ini file
  • Auto accept rez if turned on via MQ2Rez
  • Auto accept party Invites
  • Auto accept trades from other players/toons
  • Mount support AA or Item.
  • Mez mobs feature
  • Auto detect progression servers and set variables accordingly for features not yet available. i.e. Extended Target Window.
  • Commands to turn on/off major features i.e. healing, mezzing, melee etc.
  • Basic mercenary control - Define when merc attacks.
  • Supports Attack Buffs
  • Supports Autofire
  • Rez players
  • Auto revive Mercs
  • AFK Tools - Inspired by AHTools
  • Burn Section
  • Pull mobs ini file support
  • Ignore mobs ini file support
  • Mez Immune ini file support
  • Recognition for players on Zek server
  • EQBC message support.

K.I.S.S. Assist is our macro for all classes/levels for exclusive use of our subscribers at RedGuides.com

Requires plugins* MQ2Cast, MQ2Exchange, MQ2Melee, MQ2MoveUtils, Mq2Rez, & MQ2Twist (Bards) ,Extended Target Window and ninjadvloot.inc file.

* All plugins are included in our compile.




If you like KissAssist and would like to help keep up my enthusiasm
for adding/updating features, Please consider donating. Thanks


Ninjadvloot.ini is included with the Official Compile or get it here
 

Attachments

Last edited:
AT LONG LAST PULLERPETTANK ROLE

pullpet.jpg

This is an official relaese. TreeHuginDruid and I has been working on PullerPetTank for the last 2 month. TreeHuginDruid doing all the heavy coding for PullerPetTank Role

TreeHuginDruid said:
I am pleased to announce that KissAssist 7.6.1 IS ready for distribution to the community.

As Maskoi has been busy with the Kiss Task system coding / bug fixes .. I have taken a more active role in fixing minor issues with KissAssit.mac as well as developing new functions based upon user requests.

When referring to INI file, I am referring to (KissAssist_[ToonName].ini)

My involvement as a dev for KissAssist has been the following:
~ Added functions and bug fixes for PullerPetTank role.
~ Added function to break mez on a mob when ready to engage it when in PullerPetTank role (BreakMez). Default value =null. New Variable in ini:
Syntax: PetBreakMezSpell=SpellName
Rich (BB code):
[Pet]
PetBreakMezSpell=NULL
~Added function to automatically move away from mob if hit in PullerPetTank and Assist roles (Event_GotHit).
~Added feature to pull with pets. Simply have PullWith value set to Pet. HOT!
Rich (BB code):
[Pull]
PullWith=Pet
~Added function/ability to wait for rampage pets to despawn before next pull cycle (CheckRampPets). New Variable in ini:
Rich (BB code):
[Pet]
PetRampPullWait=1
Added function to enable puller role toggling on pulls (TogglePullerMode). New Variable in ini:
Rich (BB code):
[Pet]
PetRampPullWait=0
--- Option is turned off during initial creation in your ini.
~Added function (and variable(s) to KissAssist_[ToonName].ini) to autoload a predefined spellset for KissAssist at program load. New Variables in ini:
Rich (BB code):
[SpellSet]
SpellSetName=KissAssist
LoadSpellSet=0
--- Option is turned off during initial creation in your ini.

~Puller Roles will now auto target any toon flagged for medding in GroupWatch. This will update server on zoning to eliminate 0% mana bug after zoning or due to server lag.
~Hopefully the end of getting stalled on targeting corpses.
 
Last edited:
He spelled it as best he could while shaken in his boots about being sent to pull a dragon! lol
 
Finally getting around to testing this.

None of my bots assist anymore. I have to manually target each mob for them to attack.

Edit: I'm using PullerPetTank on mage and Assist on all the others.
 
Can you explain how that works?

If your in PullerPetTank role, checks that your leader .. then toggles yourself as puller when starting pull cycle, turns it back off once you reach back to within your camp radius.

Useful if your play-style is to ensure your cleric merc stays in camp on all pulls with you or pet.
 
Who are you assisting?

I'm assisting a pet. I checked ${MainAssist} and it return the pets name.

- - - Updated - - -

If your in PullerPetTank role, checks that your leader .. then toggles yourself as puller when starting pull cycle, turns it back off once you reach back to within your camp radius.

Useful if your play-style is to ensure your cleric merc stays in camp on all pulls with you or pet.

Ill give this a try and report back with details.
 
I've been testing this for a few hours and I have an issue. The pet pulls the mob, runs back to my mage, then turns and runs back to tank the mob. This is good, except on occasion he is too far away from the camp and none of my other toons assist. If he is too far, the healer won't heal him and he dies. Rarely, but happened one time.
 
Everything is working now. No idea why, lol. Just started going good.
 
not using the pet tank mode, just normal pullertank on my SK and my zerker just isnt working right, wont assist wont /chase etc

- - - Updated - - -

not using the pet tank mode, just normal pullertank on my SK and my zerker just isnt working right, wont assist wont /chase etc

gone back to 7.4 and it sems to work fine
 
Out of town for a few days but will check it out when I get back.
 
I've been testing this for a few hours and I have an issue. The pet pulls the mob, runs back to my mage, then turns and runs back to tank the mob. This is good, except on occasion he is too far away from the camp and none of my other toons assist. If he is too far, the healer won't heal him and he dies. Rarely, but happened one time.
Distance pet goes in to engage mob after pull is hard coded and will not be changed. Adjust your melee distance on assisting toons in their ini file, bump it up slightly.
 
Dident use the pet pull stuff, but regular assist- worked fine for me, but when the bots are getting hit they start running around- thats new to me on I cant see anywhere to turn it off?
 
Dident use the pet pull stuff, but regular assist- worked fine for me, but when the bots are getting hit they start running around- thats new to me on I cant see anywhere to turn it off?

Same thing happened here. The big problem was they took off running and trained us with a bunch of other mobs. Can we turn this off and also turn off pet hold? If the pet is tanking more than one, we need hold OFF.

- - - Updated - - -

Also, clicking back to camp is a little wonky. When my toon dies and gets rezzed right away, it will click back to a campfire that was placed earlier. I ended up having to run the toon all the way back to finish a quest.
 
This version is far too buggy to use right now. Looks like a down grade is in order :\

The bots just randomly stop assisting. They'll be going just fine then out of no where it stops. Restarting the macro does nothing to fix this either.
 
This version is far too buggy to use right now. Looks like a down grade is in order :\

The bots just randomly stop assisting. They'll be going just fine then out of no where it stops. Restarting the macro does nothing to fix this either.

Turns out the issue is in the other version too. The only way to get the macro to work is by restarting EQ.

Some things I've noticed:

Sometimes when loading and using a pet to tank it will say "Pet name is Pet" and other times it will say "Pet name is Pet Destructible Object". Usually when I get the "destructible object" output is when the macro stops working and I have to reboot EQ for it to work again.

Other times it happens upon death. After taking the rez the bot will just sit there and no longer assist however if I manually target the mob the bot will do its thing just fine until the mob is dead. Ending the macro and restarting it does nothing. I have to reboot EQ to get it to work.

Could it be an issue with a plug in storing some variables wrong? That's about all I can think of since the issue is persistent even when /endmac is used.
 
A thing u might want to consider for future upgrades, if a healer has to stop his casting for an emergency heal you dont have to dismount anymore, just ducking - even on a mount works
 
If the issue exists in this version it has always existed. . . so yes, it would be in 7.4.1 as well as 7.6.1 I have made absolutely NO changes to anything outside the scope of PulletPetTank role.

That's why I kind of waited to get your feedback. Two problems "self resolved" apparently lol.
Any OTHER problem you have outside of this new 7.6.1 version has been there already since I changed nothing else.

I have come across 2 issues which I deem warrant a fix asap. One to signifigantly reduce the spam and improve the action of GotHit event function. An issue has been verified to exist when waiting rampage pets to despawn. Outside of those noted and verified fixes I have ready to push, all other issues will require a detailed explanation of the issue.

I'll talk with Maskoi and see if we can hash out an official question list we will require when submitting bug/error/problems for kissassist.

Turns out the issue is in the other version too. The only way to get the macro to work is by restarting EQ.

Some things I've noticed:

Sometimes when loading and using a pet to tank it will say "Pet name is Pet" and other times it will say "Pet name is Pet Destructible Object". Usually when I get the "destructible object" output is when the macro stops working and I have to reboot EQ for it to work again.

Other times it happens upon death. After taking the rez the bot will just sit there and no longer assist however if I manually target the mob the bot will do its thing just fine until the mob is dead. Ending the macro and restarting it does nothing. I have to reboot EQ to get it to work.

Could it be an issue with a plug in storing some variables wrong? That's about all I can think of since the issue is persistent even when /endmac is used.

- - - Updated - - -

minor thing, but I cant get it to cast wizzy pet at the mobs-

Mul's Pyroblade
http://everquest.allakhazam.com/db/spell.html?spell=35836

Assuming you using correct syntax, spell | mob health% to cast at. Lets assume 96% mob health.

For rank 3, your dps section should have a line that states:

DPS#=Mul's Pyroblade Rk. III|96


For rank 1, your dps section should have a line that states:

DPS#=Mul's Pyroblade|96

Make sure there are no trailing blank spaces at the end of the line.

- - - Updated - - -

Same thing happened here. The big problem was they took off running and trained us with a bunch of other mobs. Can we turn this off and also turn off pet hold? If the pet is tanking more than one, we need hold OFF.

- - - Updated - - -

Also, clicking back to camp is a little wonky. When my toon dies and gets rezzed right away, it will click back to a campfire that was placed earlier. I ended up having to run the toon all the way back to finish a quest.

1) Your toon is only moving 39 paces MAX away from mob's distance.... if you are running 39 paces away.. and agroing mobs... then only thing i can think of is that they spawned close you your camp WHILE you were in combat. If they are that close to you.. your camp spot/radius is off ....

2) Issue with returning to campfire .... perhaps you should reset your campfire where you want to camp???????????? I have not looked at campfire code... but i will discuss this with maskoi and see if we need to check where campfire location is / reset campfire location to current position on macro start if needed... TBD

GotHit is was picking up multiple got hits and interrupting the correct procedure to move away out of melee range from mob.

The issue with assist or pullerpettank running around like a nut when hit has been identified and resolved. It is an added function called GotHit ... it is a double checks to move out of mob's melee range if hit.

NORMALLY kissassist ALREADY moves you away then back to camp spot if you have returntocamp variable enabled in your ini. This was meant to be a secondary check for the PullerPetTank role to use while pulling, but added assist role to the logic as well.

This redundant check is there for a reason, it has been corrected to produce far far far less spam, and to run much more efficient / logically.

- - - Updated - - -

I'm posting my fixed version here until Maskoi is back and post it himself on top in thread.

Fixes: Minor logic fix to function to wait on rampage pets to despawn before next pull.
Fixes: Reduced spam and improved functionality to GotHit function when in assist or pullerpettanke roles.


Nothing outside the scope of PullerPetTank role was touched.
ANY other issues you are having.. will be looked into, but keep in mind... if they there now.. they have ALWAYS been there!

Use the problem discussion report thread please if having issues:
KissAssist-Problem-report-thread

Patch 4 fixes:
Fixes random wait loop on cycle pulls (could have gotten you stuck in an endless waiting loop)
Fixes syntax and logic issues with several functions (pull code, pet combat.. etc)


Test out KissAssist_v761_RC2_Patch4.zip posted below.
 

Attachments

Last edited:
I'd like it if my characters didn't run when they get hit. This happened in a DH mission when the enchanter naturally gets hit while mezzing, but then took off running and pulled more mobs. He could never get them mezzed because he would take off running before he cast mez. My healer let the tank die because he too took off running instead of letting the heal finish casting. Can you guys add an option for this? Moveonhit=0 maybe?

The issues I have with pullerpettank are:

1. Sometimes the pet engages outside of camp radius therefore gets no assistance/heals from mercs or others set to assist the pet. Adjusted campradius but still has difficulty. It may work a little better if the pet were parked and the mage pulls with malo. Mage can run to the mob, malo, then run back behind the pet. Pet will engage when mob is in range.

2. The mage does not return to camp in a consistent manner - especially if on a mount. He will overrun the camp spot and park the mob on top of the group, or not run back to the group and ends up too far out of range. I changed /moveto dist to adjust and see if he will get closer but still doesn't work quite right.

3. Pet hold is stuck ON. So if my pet pulls two+, it kills the first but then runs back to the mage and has a delay before engaging the second. Meanwhile the mob is beating on the healer - who takes off running and trains us. Pet doesn't lock all mobs down so it's a vicious cycle. We really need a setting for this. The ONLY time I do hold is on a named mob. I think most mages agree with that.

I think you have done excellent work with this, Tree! It's really great for soloing, not quite there for working with a group. Where did you test this?
 
I'd like it if my characters didn't run when they get hit. This happened in a DH mission when the enchanter naturally gets hit while mezzing, but then took off running and pulled more mobs. He could never get them mezzed because he would take off running before he cast mez. My healer let the tank die because he too took off running instead of letting the heal finish casting. Can you guys add an option for this? Moveonhit=0 maybe?

The issues I have with pullerpettank are:

1. Sometimes the pet engages outside of camp radius therefore gets no assistance/heals from mercs or others set to assist the pet. Adjusted campradius but still has difficulty. It may work a little better if the pet were parked and the mage pulls with malo. Mage can run to the mob, malo, then run back behind the pet. Pet will engage when mob is in range.

2. The mage does not return to camp in a consistent manner - especially if on a mount. He will overrun the camp spot and park the mob on top of the group, or not run back to the group and ends up too far out of range. I changed /moveto dist to adjust and see if he will get closer but still doesn't work quite right.

3. Pet hold is stuck ON. So if my pet pulls two+, it kills the first but then runs back to the mage and has a delay before engaging the second. Meanwhile the mob is beating on the healer - who takes off running and trains us. Pet doesn't lock all mobs down so it's a vicious cycle. We really need a setting for this. The ONLY time I do hold is on a named mob. I think most mages agree with that.

I think you have done excellent work with this, Tree! It's really great for soloing, not quite there for working with a group. Where did you test this?

I've tested this in grelleths palace, the grounds, and several other zones.

Original - PET will enagage outside of camp radius if you are relatively close to camp OR you are pet pulling and YOU get hit on the pull with pet close by.
NOW - Pet will only engage mob if you are hit on pull and pet is within certain range of camp when you pull with spell. Get updated file on above post... has not been incorporated by Maskoi in original top thread yet.

Pet engages once mob breaks a specific boundary line from camp, regardless of pulling with pet or spell.

Pet hold is nothing new. It's been there since 7.4.1 and before. Just added line to force it to ghold if you have pet discipline rank 2, but it was always putting pet to hold.
Rich (BB code):
/if (${Me.AltAbility[Pet Discipline]}) /pet hold on
/if (${Me.AltAbility[Pet Discipline]}>5) /pet ghold on

Mage not eturning to camp consistently.... use my posted fix ... recheck.

- - - Updated - - -

If you are having issues....


Use the problem discussion report thread please if having issues:
KissAssist-Problem-report-thread

- - - Updated - - -

I'd like it if my characters didn't run when they get hit. This happened in a DH mission when the enchanter naturally gets hit while mezzing, but then took off running and pulled more mobs. He could never get them mezzed because he would take off running before he cast mez. My healer let the tank die because he too took off running instead of letting the heal finish casting. Can you guys add an option for this? Moveonhit=0 maybe?

The issues I have with pullerpettank are:

1. Sometimes the pet engages outside of camp radius therefore gets no assistance/heals from mercs or others set to assist the pet. Adjusted campradius but still has difficulty. It may work a little better if the pet were parked and the mage pulls with malo. Mage can run to the mob, malo, then run back behind the pet. Pet will engage when mob is in range.

2. The mage does not return to camp in a consistent manner - especially if on a mount. He will overrun the camp spot and park the mob on top of the group, or not run back to the group and ends up too far out of range. I changed /moveto dist to adjust and see if he will get closer but still doesn't work quite right.

3. Pet hold is stuck ON. So if my pet pulls two+, it kills the first but then runs back to the mage and has a delay before engaging the second. Meanwhile the mob is beating on the healer - who takes off running and trains us. Pet doesn't lock all mobs down so it's a vicious cycle. We really need a setting for this. The ONLY time I do hold is on a named mob. I think most mages agree with that.

I think you have done excellent work with this, Tree! It's really great for soloing, not quite there for working with a group. Where did you test this?

I have a fix ready to prevent assist toons from running off buggy when hit, waiting on Maskoi to post it to top thread.

- - - Updated - - -

Please keep in mind, all testing was done by myself or masdkoi. We don't have access to high level toons of every class, and we occasionally miss things. Our testers are gone, so working out any bugs as we hear about them.
 
Last edited:
Hello,
I tried a group with a monk, a bard , a warrior, a berserker , a necro and a Druid.
The monk, the berserkers and the bard are constantly returning to their initial camp position and reengaging the mob in the middle of the combat.
The Iamhit event does not behave well with casters like healers or mezzers.
Cheers
 
Doesent work in 7.4.1 and 7.6.1
Ok ... please continue this in the KissAssist Problem report thread.
I want to keep bugs and issues seperate from this thread, and leave it simply for distribution, discussion, requests for features etc.

In this manner I can just focus on that thread and address each issue as they are reported. In the mean time, my wizzy has some rank of that spell.. he using his highest level but i'll switch it to my rank of Mul's and see what happens.
 
noob question time again

how does the new spellset section work exactly?
[SpellSet]
SpellSetName=KissAssist
LoadSpellSet=0

do i save a spell set and put saved name after spellsetname=? and then obv loadspellset=1 ?


OK nvm above, gave it a try and all good so far, thanks
 
used with rogue today - rogue kept stealing aggro from the merc tank, and even though rogue was tanking, rogue would swing out, try and *get behind* the mob it was tanking, which would bring it further and further away from camp. Was very strange watching it happen.Rogue would back off, move back, mob would advance, rogue would engage, be tanking, back up to start to try and get behind, but mob would run up on rogue, etc etc...
 
used with rogue today - rogue kept stealing aggro from the merc tank, and even though rogue was tanking, rogue would swing out, try and *get behind* the mob it was tanking, which would bring it further and further away from camp. Was very strange watching it happen.Rogue would back off, move back, mob would advance, rogue would engage, be tanking, back up to start to try and get behind, but mob would run up on rogue, etc etc...

1) Wrong thread .... report it in the KissAssist Problem report thread and supply required information.
2) Your rogue is moving behind the mob because you have stick set to behind .... if the rogue is set as TANK role... you can not have stick command set to behind! Correct your stick on the rogue .....

For those having issues with Assist role ... ping ponging when under pullerpettank role ... gotHit event effecting your ASSIST toon......and ANY issue reported in the problem report thread ... (except bard twist/clicky item issue... ) please download the temporary fix I posted ( KissAssist_v761_RC2.zip ).

It is posted higher up in this thread for KissAssist 7.6.1

It has been updated as of today.....
 
Please check Sub DoWeMove. I replaced this
Rich (BB code):
/if (!${ReturnToCamp} && !${ChaseAssist}) /return
with
Rich (BB code):
/if ((!${ReturnToCamp} && !${ChaseAssist}) || (!${Select[${Role},puller,pullertank,pullerpettank]} && ${CombatStart})) /return
and fixed a lot of issues with tank and/or assists running back and forth from either the campspot or chasing the MA during battle. May not be best solution but my guys aren't running back all the time now. Tanks still does it some if he is also the puller but it is minimal in my use cases.
 
thanks for sharing. here is the fix.

Find text below in buffs sub
Rich (BB code):
        | Group Buffs
        /for i 1 to ${Buffs.Size}
            /doevents
            /call DoWeMove
            | If Buffs=NULL skip to next buff
and replace/call DoWeMove with the line in red
Rich (BB code):
        | Group Buffs
        /for i 1 to ${Buffs.Size}
            /doevents
            /if (${ChaseAssist} && !${CombatStart}) /call DoWeMove
            | If Buffs=NULL skip to next buff

this is the fix that will be in the next release.
 
KissAssist Release KissAssist 7 Updated 09/22/2014 v7.6.1

Users who are viewing this thread

Back
Top
Cart