KissAssist Release KissAssist 5.6 Updated 11/13/2012

[Maskoi]

Re: KissAssist 5.3 Updated 10/25/2012

KissAssist 5.3 Updated 10/25/2012
~Fixed some MQ2Exchange issues when pulling with ranged items

 

[wbb007]

Re: KissAssist 5.3 Updated 10/25/2012

Is it possible to have my mage pull AND have his pet tank? I have him set to PullerTank now and pulling works great. The problem is that he doesn't send the pet in to attack before the mobs get on him and start the beatdown. I'm trying to have him pull with a cast but then have him send the pet in before they reach him.

 

[Maskoi]

Re: KissAssist 5.3 Updated 10/25/2012

PullerPet tanking is not yet supported but I am working on it. It won't be ready next release but the one after that. Look for for in a couple of weeks.

 

[Maskoi]

Re: KissAssist 5.4 Updated 10/28/2012

KissAssist 5.4 Updated 10/28/2012

~Canni and other mana gathering abilities now work during combat. There is nothing to change in your ini files.

~Gift of Mana section added
GoM Settings
GoM allows you assign a spell to cast during combat if Gift of Mana goes off. Allows you to target mob, main assist or yourself

• Syntax : Your Spell|Target = MA/Me/Mob - Mage example below would try to cast Ruthless Servant on the current Mob, MA's Target, if GoM goes off

[GoM]
GoMSHelp=Format - Spell|Target, MA Me or Mob, i.e. Rampaging Servant Rk. II|Mob
GoMSpell=Ruthless Servant|Mob

~Fixed constantly targeting your own pet if pet is Main Assist and using pet heals.
~Fixed aliases writing when creating ini file for the first time. Previously was not writing them until you changed the KissAssist version in the ini file.

 

[Joman]

Re: KissAssist 5.4 Updated 10/28/2012

Awesome, I have been doing this manually now I can leave my shammy alone

Will Test it out tonight

Thanks Maskoi.

 

[wbb007]

Re: KissAssist 5.4 Updated 10/28/2012

This site is awesome. This macro is awesome. I've got it running on 3 different classes now and it's working great. Your work on shambot got me to follow you to this site and I'm very glad I did. Thank you and all the devs for the killer work.

Not sure if you guys see this type feedback as helpful or annoying but I thougth I'd mention a couple of things I noticed last night. On my mage the DPS|DPSInterval setting isn't working for me. I set it to 18 seconds and he keeps blasing away every few seconds. The interval didn't seem to be the default 5 seconds. Looked like there was some variance. Also, I'm noticing some pause behavior on the puller that looks mechanical. With a merc tank and a bard puller, there is a pause of 2-3 seconds before he moves from the "stop at camp post pull" spot to the "behind mob" spot when the MA takes over. When the mob dies he also pauses at the "stop at camp" spot before taking off to get another mob. I only mention these small issues because they look scripted. I expect the code is very involved and relies on multiple components. Thanks again for making this so easy to do and fun.

 

[Maskoi]

Re: KissAssist 5.4 Updated 10/28/2012

Thanks for the feedback. I haven't tested pulling with a merc tanking in a very long time.

The puller won't move until the mob is at the AssistAt= mark. That is why he is delaying before attacking. Try setting it to AssistAt=98

I will look at the pulling from where he is if within the camp radius. so he just pulls instead of moving to his anchor spot then pulling.

The default interval doesn't kick in until the second pass of spells. you can control it by spacing the spells out further in health to cast at ie 95 80 70 55 etc. I will look at reinstalling the delay in the 1st pass of casting.

 

[wbb007]

Re: KissAssist 5.4 Updated 10/28/2012

Try setting it to AssistAt=98

It works better with it set to 98.

Forget to mention I tried to setup a level 8 SK to pull via melee to a merc tank and I'm getting this ....
Aborting Pull! Target invalid now! PCNear
This is in a zone where I'm the only player. The SK runs out to the target, pops the message then runs back to the anchor spot. Any idea what's going on?

 

[neophys]

Re: KissAssist 5.4 Updated 10/28/2012

Hi Maskoi,

Been using your macro for a while now, and really enjoy it. Most of my group is PET based, and due to this I wanted to suggest a small addition to your macro, or perhaps there is already a way of solving this.

Would it be possible to add an extra parameter to the pet part of the macro, which states when to make the pet attack. The overall assist % will work in alot of cases, but it would be alot more flexible to be able to specify a second parameter under PET in the ini file for when pet's should attack.

There are a few reasons for having pet attack later, but mainly for me, it's because my Mage and enchanter is set to assist at 99%, which will cause slow's and debuffs to land while mob is running into camp. But if pet - especially Mage pet - does more dmg than the puller did with arrow/dagger, it will force the mob to stop and attack the pet, and not run all the way to the camp.

Perhaps It's an easy fix that i could implement myself in the macro if you don't like adding a second assist parameter to the pet section, but in that case perhaps you could direct me to where in the Macro to do this?

EDIT
I changed the macro abit on my own, perhaps it's not the best way, but it's a suggestion atleast

At line 124 add the following

	/call LoadIni Pet PetAssistAt			int	    	95

At line 734, overwrite with the following line

        /if (${Target.PctHPs}<=${Math.Calc[${PetAssistAt}-${AttackDelay}]}) {

In the Kissassist_Name.ini file add the following under PetOn=1

PetAssistAt=98

 

[Dragonfire]

Re: KissAssist 5.4 Updated 10/28/2012

Thank you very much Maskoi! This macro is incredible.

I have found one issue and have one suggestion (at this point :-) )

When range pulling with a ranger (PullerTank), the ranger makes a headshot and drops the mob on the pull shot. The ranger then just sits there not knowing what to do. It does not change target nor does it move back to camp. It would be nice if it looted and returned to camp.

A suggestion with the new tradeskill bags. If the loot.ini was specific to a PC, two PC's could loot with one only picking up tradeskills and the other picking up vendor trash. This would create a much better farming situation.

 

[Maskoi]

Re: KissAssist 5.4 Updated 10/28/2012

Hi Maskoi,

Been using your macro for a while now, and really enjoy it. Most of my group is PET based, and due to this I wanted to suggest a small addition to your macro, or perhaps there is already a way of solving this.

Would it be possible to add an extra parameter to the pet part of the macro, which states when to make the pet attack. The overall assist % will work in alot of cases, but it would be alot more flexible to be able to specify a second parameter under PET in the ini file for when pet's should attack.

There are a few reasons for having pet attack later, but mainly for me, it's because my Mage and enchanter is set to assist at 99%, which will cause slow's and debuffs to land while mob is running into camp. But if pet - especially Mage pet - does more dmg than the puller did with arrow/dagger, it will force the mob to stop and attack the pet, and not run all the way to the camp.

Perhaps It's an easy fix that i could implement myself in the macro if you don't like adding a second assist parameter to the pet section, but in that case perhaps you could direct me to where in the Macro to do this?

EDIT
I changed the macro abit on my own, perhaps it's not the best way, but it's a suggestion atleast

At line 124 add the following

	/call LoadIni Pet PetAssistAt			int	    	95

At line 734, overwrite with the following line

        /if (${Target.PctHPs}<=${Math.Calc[${PetAssistAt}-${AttackDelay}]}) {

In the Kissassist_Name.ini file add the following under PetOn=1

PetAssistAt=98

What you did is exactly how to add petassistat.

 

[neophys]

Re: KissAssist 5.4 Updated 10/28/2012

Great Maskoi, thanks for feedback.

Any chance that this would be something you can see a benefit in, and would consider adding to the script?

 

[Maskoi]

Re: KissAssist 5.4 Updated 10/28/2012

Thank you very much Maskoi! This macro is incredible.

I have found one issue and have one suggestion (at this point :-) )

When range pulling with a ranger (PullerTank), the ranger makes a headshot and drops the mob on the pull shot. The ranger then just sits there not knowing what to do. It does not change target nor does it move back to camp. It would be nice if it looted and returned to camp.

A suggestion with the new tradeskill bags. If the loot.ini was specific to a PC, two PC's could loot with one only picking up tradeskills and the other picking up vendor trash. This would create a much better farming situation.

Does have Headshot have an emote that I could write an event for? I don't have a high level ranger so I have no way to explore and test this.

I will be working on ninjadvloot which handles all the looting in a few weeks. Assigning separate lootini files can get messy but I will look at it.

 

[Maskoi]

Re: KissAssist 5.4 Updated 10/28/2012

It works better with it set to 98.

Forget to mention I tried to setup a level 8 SK to pull via melee to a merc tank and I'm getting this ....
Aborting Pull! Target invalid now! PCNear
This is in a zone where I'm the only player. The SK runs out to the target, pops the message then runs back to the anchor spot. Any idea what's going on?

I know what this weirdness is and its something I have to fix next version.

The quick fix is find the line below around line 537

 /if (${SpawnCount[loc ${Target.X} ${Target.Y} radius 25 pc]}>=1 && ${Pulling}) /return PCNear

and comment it out by putting a | in front of it or just delete that one line.

 

[Maskoi]

Re: KissAssist 5.4 Updated 10/28/2012

Great Maskoi, thanks for feedback.

Any chance that this would be something you can see a benefit in, and would consider adding to the script?

I am working on new roles PetTank and PullerPetTank so something very similar will be included in a near future version.

 

[dencelle]

Re: KissAssist 5.4 Updated 10/28/2012

any chance in adding in necro to be able to mezz... theres a high level spell that necro's get (think its called dread but not sure) that is a 25ish second mezz... when i'm not using kissassist i use this spell on a fairly reg basis when the group i'm in gets in trouble and has a add under level 92 (mostly groups in grounds or VoA vally)... its not too important but it would be a little nice to be able to do that...

i also noticed if your shrouded (as a ench or a clr or some spell caster) it doesn't reconize your trying to cast aas... any clue on this?

also to make it easyer on everyone trying to debug when something goes wrong IE spell not firing off for unknown reason would you be able to add a easy debug mode (ie /if (${Debugmode}) /mlog on) idk.. would seem easyer... just imo... other than that.. been working great... other than it doesn't scratch my back when it itches... lol

 

[AnonymousHero]

Re: KissAssist 5.4 Updated 10/28/2012

Should already be able to... Just put a 1 for mez section and the spell that the necro uses to mez. It'll only start mezzing if theres 2 or more mobs in the camp I believe.

 

[Maskoi]

Re: KissAssist 5.4 Updated 10/28/2012

The mez section only recognizes bards and chanters. The necro is a weird mez thing that I have no clue how it works. No one has ever mentioned it before. I will have to explore the spell line more.

Never even occurred to me to try kiss with a shrouded toon. Will look into this month. If it is an easy fix I will add it but not making any promises.

As far as debug
/debug - Turn On/Off Debug Spam Generic Stuff
/debugmez - Turn On/Off Debug Spam Mez Section
/debugbuffs - Turn On/Off Debug Spam BuffsSection
/debugcombat - Turn On/Off Debug Spam Combat Section
/debugheal - Turn On/Off Debug Spam Heals Section
/debugpull - Turn On/Off Debug Spam Pull Section

 

[deaths]

Re: KissAssist 5.4 Updated 10/28/2012

I'm haveing a few problems with pulling manly my puller is randoml picking mobs to pull witch cause problems when she pickes one that is behind 1-2 other mobs is there any way to get her to aways target the closest one or is this some thing to do with them wandering and she thinks she know what one is closest

 

[Maskoi]

Re: KissAssist 5.4 Updated 10/28/2012

I am testing some new pull code. I will post it later if it works.

 

[Teichou]

Re: KissAssist 5.4 Updated 10/28/2012

I'm haveing a few problems with pulling manly my puller is randoml picking mobs to pull witch cause problems when she pickes one that is behind 1-2 other mobs is there any way to get her to aways target the closest one or is this some thing to do with them wandering and she thinks she know what one is closest

happens to me all the time...lots of it has to do with crazy LoS in EQ...EQ sucks for LoS

 

[Dragonfire]

Re: KissAssist 5.4 Updated 10/28/2012

Hi Maskoi,

Emote:

Sam performs a FATAL BOW SHOT!!
You hit an orc for 159426 points of damage.

Does have Headshot have an emote that I could write an event for? I don't have a high level ranger so I have no way to explore and test this.

I will be working on ninjadvloot which handles all the looting in a few weeks. Assigning separate lootini files can get messy but I will look at it.

 

[Dragonfire]

Re: KissAssist 5.4 Updated 10/28/2012

In the Hunter mode, with AFKToolsOn=0 I am getting Aborting Pull! Target invalid now! PCNear. The closest PC is 4,219 away.

[AFKTools]
AFKToolsOn=0
AFKGMAction=/quit
AFKPCRadius=150

 

[Dragonfire]

Re: KissAssist 5.4 Updated 10/28/2012

LOS really has issues. I'll have it target something on the other side of a big rock and it will just sit there trying to hit the mob through the rock.

 

[Maskoi]

Re: KissAssist 5.4 Updated 10/28/2012

Something in the last patch borked my the PCNear code. It thinks PCs are everywhere. I am reworking some of the pull code and hope to have a new version in a few days.

Its not afk tools. It is a check to see if PCs are the near the mob you are pulling so you don't try and pull another partys mob.

 

[Maskoi]

Re: KissAssist 5.4 Updated 10/28/2012

Find this line and comment | it out or delete to solve that issue for now.

 /if (${SpawnCount[loc ${Target.X} ${Target.Y} radius 10 pc]}>=1 && ${Pulling}) /return PCNear

 

[dencelle]

Re: KissAssist 5.2 Updated 10/04/2012

KissAssist.mac@Line 120

Change

    /if (${Select[${Me.Class.ShortName},BRD,ENC]}) {

to

    /if (${Select[${Me.Class.ShortName},BRD,ENC,NEC]}) {

|Necro mez code
            /if (${Me.Class.Name.Equal[Necromancer]}) { 
                /delay 3s ${Cast.Ready[${MezSpell}]}
                /call CastWhat "${MezSpell}" ${MobID}
                /delay 5s ${Cast.Status.Equal}
                /varcalc MezFail ${MezFail}+1
                /if (${Macro.Return.Equal[CAST_SUCCESS]}) { 
                    /varcalc MezCount[${TimerNum}] ${MezCount[${TimerNum}]}+1
                    /varcalc MezTimer${TimerNum} ((${Spell[${MezSpell}].Duration.TotalSeconds}+${MezMod})*10)*.85
                    /if (${DebugMez}) /echo MezTimer${TimerNum} ${MezTimer${TimerNum}}
                }
                /if (${Macro.Return.Equal[CAST_RESIST]} && ${MezFail}<2) {
                    /echo MEZ Resisted -> ${Spawn[${MobID}].CleanName} <- ID:${MobID}
                    /docommand /bc [+g+]MEZ Resisted -> ${Spawn[${MobID}].CleanName} <- ID:${MobID}[+x+]
                    /goto :retrymez
                }
            }

and it adds necros to mezzing class and does pretty good CC control... necros still can't use the AE mezz since thats auto blocked by the macro anyways...

 

[dencelle]

Re: KissAssist 5.4 Updated 10/28/2012

KissAssist@Line 389
++

/if (!${Spawn[${Target}].ID}&&${Role.Equal[PullerTank]}) /Target ${Me}

if we have no target at all we target our selfs but only if role is set to PullerTank... otherwise it runs like normal and doesn't target self...

 

[dencelle]

Re: KissAssist 5.4 Updated 10/28/2012

            /if (${Me.Pet.Height}<1) /varset PetShrunk 1
            /if (${Debug}) /echo Pet Height: ${Me.Pet.Height} PetShrunk: ${PetShrunk}
            /if (!${PetShrunk} && ${PetShrinkOn}) {
                /call CastWhat "${PetShrinkSpell}" ${Me.Pet.ID}
                /varset PetShrunk 1
                /delay 20
                /squelch /target clear
            }

to

            /if (${Debug}) /echo Pet Height: ${Me.Pet.Height} PetShrunk: ${PetShrunk}
            /if (${Me.Pet.Height}>1 && ${PetShrinkOn}) {
                /call CastWhat "${PetShrinkSpell}" ${Me.Pet.ID}
                /delay 20
                /squelch /target clear
            }

pet height 2 should be good enough right? anywho this seems like a little cleaner code... + it will shrink pet all the way to the smallest size (maybe)...

 

[dencelle]

Re: KissAssist 5.4 Updated 10/28/2012

/if (${SpawnCount[loc ${Target.X} ${Target.Y} radius 10 pc]}>=1 && ${Pulling}) /return PCNear

/if (${SpawnCount[loc ${Target.X} ${Target.Y} radius 25 pc]}>=${Math.Calc[${SpawnCount[loc ${Target.X} ${Target.Y} radius 25 Group]}+1]} && ${Pulling}) /return PCNear

untested but might work to fix that pc near issue

 

[dencelle]

Re: KissAssist 5.4 Updated 10/28/2012

        /call GroupWatch
        /echo Looking for Close Range Mobs
        /squelch /alert clear 1

to

        /call GroupWatch
        /if (${Debug}) /echo Looking for Close Range Mobs
        /squelch /alert clear 1

no need to flood the chat wnd with a echo over and over maybe use a popup instead... for this one... chat wnd is busy enough... till then i'd change it to debug mode only...

 

[Maskoi]

Re: KissAssist 5.2 Updated 10/04/2012

KissAssist.mac@Line 120

Change

    /if (${Select[${Me.Class.ShortName},BRD,ENC]}) {

to

    /if (${Select[${Me.Class.ShortName},BRD,ENC,NEC]}) {

|Necro mez code
            /if (${Me.Class.Name.Equal[Necromancer]}) { 
                /delay 3s ${Cast.Ready[${MezSpell}]}
                /call CastWhat "${MezSpell}" ${MobID}
                /delay 5s ${Cast.Status.Equal}
                /varcalc MezFail ${MezFail}+1
                /if (${Macro.Return.Equal[CAST_SUCCESS]}) { 
                    /varcalc MezCount[${TimerNum}] ${MezCount[${TimerNum}]}+1
                    /varcalc MezTimer${TimerNum} ((${Spell[${MezSpell}].Duration.TotalSeconds}+${MezMod})*10)*.85
                    /if (${DebugMez}) /echo MezTimer${TimerNum} ${MezTimer${TimerNum}}
                }
                /if (${Macro.Return.Equal[CAST_RESIST]} && ${MezFail}<2) {
                    /echo MEZ Resisted -> ${Spawn[${MobID}].CleanName} <- ID:${MobID}
                    /docommand /bc [+g+]MEZ Resisted -> ${Spawn[${MobID}].CleanName} <- ID:${MobID}[+x+]
                    /goto :retrymez
                }
            }

and it adds necros to mezzing class and does pretty good CC control... necros still can't use the AE mezz since thats auto blocked by the macro anyways...

Looks like the mez is spotty lv 55 to 72 only undead versions but will test test this out.

 

[Maskoi]

Re: KissAssist 5.4 Updated 10/28/2012

KissAssist@Line 389
++

/if (!${Spawn[${Target}].ID}&&${Role.Equal[PullerTank]}) /Target ${Me}

if we have no target at all we target our selfs but only if role is set to PullerTank... otherwise it runs like normal and doesn't target self...

Why would you target yourself?

 

[Maskoi]

Re: KissAssist 5.4 Updated 10/28/2012

/if (${SpawnCount[loc ${Target.X} ${Target.Y} radius 10 pc]}>=1 && ${Pulling}) /return PCNear

/if (${SpawnCount[loc ${Target.X} ${Target.Y} radius 25 pc]}>=${Math.Calc[${SpawnCount[loc ${Target.X} ${Target.Y} radius 25 Group]}+1]} && ${Pulling}) /return PCNear

untested but might work to fix that pc near issue

I changed this code in 5.5 to add the group to an ignore list so it no longer sees them as pcs.

 

[Maskoi]

Re: KissAssist 5.4 Updated 10/28/2012

        /call GroupWatch
        /echo Looking for Close Range Mobs
        /squelch /alert clear 1

to

        /call GroupWatch
        /if (${Debug}) /echo Looking for Close Range Mobs
        /squelch /alert clear 1

no need to flood the chat wnd with a echo over and over maybe use a popup instead... for this one... chat wnd is busy enough... till then i'd change it to debug mode only...

This is the message to let you know you are pulling. If you are in a camp that's has long respawns times change PullWait=0 to a higher value to increase the time between searches. ie 30 would look every 30 secs when no spawns are up.

 

[dencelle]

Re: KissAssist 5.4 Updated 10/28/2012

Why would you target yourself?

just makes it so if your dont have a target when your pullertank it will set you ass the MA... it was frustrating me because i kept getting a error saying that i need to target my MA -.- highly annoying when trying to set up 6 bots and you forget 1 little thing...

 

[dencelle]

Re: KissAssist 5.4 Updated 10/28/2012

This is the message to let you know you are pulling. If you are in a camp that's has long respawns times change PullWait=0 to a higher value to increase the time between searches. ie 30 would look every 30 secs when no spawns are up.

ah kk will change..

 

[Maskoi]

Re: KissAssist 5.4 Updated 10/28/2012

it was frustrating me because i kept getting a error saying that i need to target my MA

What error? I still don't understand this.

 

[dencelle]

Re: KissAssist 5.2 Updated 10/04/2012

Looks like the mez is spotty lv 55 to 72 only undead versions but will test test this out.

wouldn't the necro using this know that and would only activate it if they were fighting undead?

as for a coding solution

/if (${Target.Race}==${ZombieRaceID}) /return

ect for all the undead races... i think theres only a few... zombie and skelly... you could set a list just like your ignore/pull list for each zone and let players choose what they want the mezz code to go for... <--- that all made sense in my head but probably no one elses...

 

[dencelle]

Re: KissAssist 5.4 Updated 10/28/2012

What error? I still don't understand this.

"You do not have a Mercenary, PC or Pet targeted. Please target Main Tank and restart macro."
if your mode is pullertank and you have no target you get that annoying message...