- Joined
- Jun 12, 2015
- RedCents
- 58,244¢
-
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! 👋
KissAssist Release KissAssist v10.2.3 Released 1/06/2018 - Return of Dawn of the Bard
- Thread starter Maskoi
- Start date
Re: KissAssist v10.1.3 Released 11/12/2017
OK, just letting everyone know that if you are using the OLD if, notif, ifme, notifme tags. Start converting them over to the conditions, that are now available in Kiss. I will be removing the code that uses the if, notif, ifme, notifme tags in stages. The first stage will remove the core code that uses the tags, but not the logic for making sure shifting the tags around in the correct order. The final stage will be removing the remaining logic that shifts the tags around.
You have been notified.
OK, just letting everyone know that if you are using the OLD if, notif, ifme, notifme tags. Start converting them over to the conditions, that are now available in Kiss. I will be removing the code that uses the if, notif, ifme, notifme tags in stages. The first stage will remove the core code that uses the tags, but not the logic for making sure shifting the tags around in the correct order. The final stage will be removing the remaining logic that shifts the tags around.
You have been notified.
aspire2008
Well-known member
- Joined
- Nov 10, 2012
- RedCents
- 2,583¢
Re: KissAssist v10.1.3 Released 11/12/2017
I understand that was for people that didn't know much about macros or writing if conditions, but i'm glad its getting removed if it speeds up the macro.
Also, there wasn't much you could do with those tags but super simple 1 part statements I think? I never used them so not sure on that part.
I understand that was for people that didn't know much about macros or writing if conditions, but i'm glad its getting removed if it speeds up the macro.
Also, there wasn't much you could do with those tags but super simple 1 part statements I think? I never used them so not sure on that part.
- Joined
- Dec 1, 2014
- RedCents
- 340¢
Re: KissAssist v10.1.3 Released 11/12/2017
What's the command to have your assists check their target against MA and change if it doesn't match? I can't remember if it's a KA or melee cmd
What's the command to have your assists check their target against MA and change if it doesn't match? I can't remember if it's a KA or melee cmd
- Joined
- Jun 12, 2015
- RedCents
- 58,244¢
Re: KissAssist v10.1.3 Released 11/12/2017
i probably asked before, but i seen in some inis, among them some from maskoi, and they been using like:
i was wondering why, and also wondering what the single does, because if its to fire when there is one mob, why not have it in dps?
i probably asked before, but i seen in some inis, among them some from maskoi, and they been using like:
Rich (BB code):
[AE]
AEOn=0
AECOn=0
AESize=3
AERadius=50
AE1=Vilify|1|single
AE2=NULL
AE3=NULLi was wondering why, and also wondering what the single does, because if its to fire when there is one mob, why not have it in dps?
Re: KissAssist v10.1.3 Released 11/12/2017
i have been having an odd occurrence that i have noticed in the last week or so, even though all my toons have the misc gem set as MiscGem=11 several have randomly been using gem 5 for buffs instead, so far the affected toons all have ini files that have not been changed in months and none of them have holy/down's that go anywhere near spell gems. anyone have any ideas what may be causing this?
i have been having an odd occurrence that i have noticed in the last week or so, even though all my toons have the misc gem set as MiscGem=11 several have randomly been using gem 5 for buffs instead, so far the affected toons all have ini files that have not been changed in months and none of them have holy/down's that go anywhere near spell gems. anyone have any ideas what may be causing this?
Re: KissAssist v10.1.3 Released 11/12/2017
Most likely has something to do with MQ2Casts defaulting to gem5, if the spell needs to be memed. Not sure why the spell is not getting memed into the MiscGem slot before trying to cast the spell.
Most likely has something to do with MQ2Casts defaulting to gem5, if the spell needs to be memed. Not sure why the spell is not getting memed into the MiscGem slot before trying to cast the spell.
Re: KissAssist v10.1.3 Released 11/12/2017
I figured it had something to do with something to do with mq2cast reverting to defaults and frankly wouldn't mind too much. however once it casts it then unmem's and leaves the gem blank, odd behavior considering the fact that kissassist is rather good at rememing even to the point of interrupting mid cast to remem, to the point that any time my porters have to cast i have to pause the macro just to port us somewhere. a behavior i would love to see addressed if possible, though hardly a priority
I figured it had something to do with something to do with mq2cast reverting to defaults and frankly wouldn't mind too much. however once it casts it then unmem's and leaves the gem blank, odd behavior considering the fact that kissassist is rather good at rememing even to the point of interrupting mid cast to remem, to the point that any time my porters have to cast i have to pause the macro just to port us somewhere. a behavior i would love to see addressed if possible, though hardly a priority
- Joined
- Nov 17, 2017
- RedCents
- 1,094¢
Re: KissAssist v10.1.3 Released 11/12/2017
I updated to the latest version 10.1.3 and now I am getting the following error on my mage.
This only comes up if I have pullerpettank as the mode, pettank works and puller works.
- - - Updated - - -
Ok seems I have another issue, my mage and sham are casting and sending pets at the edge of casting range even when I set the camp radius small.
This was my previous default and seemed to work but now even at 5 and 10 they attack at spell range.
I updated to the latest version 10.1.3 and now I am getting the following error on my mage.
This only comes up if I have pullerpettank as the mode, pettank works and puller works.
Rich (BB code):
[2017/12/01 19:24:27] [MQ2] Pulling with PET now !
[2017/12/01 19:24:27] Subroutine TogglePullMode wasn't found
[2017/12/01 19:24:27] kissassist.mac@6539 (Pull): /if (${Select[${Role},pullerpettank]} && ${PullRoleToggle} && ${Group.Puller.ID}==${Me.ID}) /call TogglePullMode TurnOff
[2017/12/01 19:24:27] kissassist.mac@6157 (PullCheck): /call Pull
[2017/12/01 19:24:27] kissassist.mac@1069 (Main): /if (${PullMob}) /call PullCheck
[2017/12/01 19:24:27] The current macro has ended.- - - Updated - - -
Ok seems I have another issue, my mage and sham are casting and sending pets at the edge of casting range even when I set the camp radius small.
This was my previous default and seemed to work but now even at 5 and 10 they attack at spell range.
Rich (BB code):
CampRadius=20
CampRadiusExceed=100- Joined
- Nov 17, 2017
- RedCents
- 1,094¢
Re: KissAssist v10.1.3 Released 11/12/2017
Once I cranked down the meleedistance to 50 they started to behave better and actually let mobs get into camp.
Something else I just watched though, a roamer walked into camp and attacked and killed my sk, then the rogue, then the shaman, then the mage but none of them attacked back, they just stood there.
Once I cranked down the meleedistance to 50 they started to behave better and actually let mobs get into camp.
Something else I just watched though, a roamer walked into camp and attacked and killed my sk, then the rogue, then the shaman, then the mage but none of them attacked back, they just stood there.
Re: KissAssist v10.1.3 Released 11/12/2017
The whole letting the mobs kill the group members has to do with the MA/Mainassist not picking up the mob that was in camp. need to make sure the MA/Mainassist has Return To Camp turned on and him MeleeDistance is set appropriately. It just sounds like you need to do some fine tuning.
The whole letting the mobs kill the group members has to do with the MA/Mainassist not picking up the mob that was in camp. need to make sure the MA/Mainassist has Return To Camp turned on and him MeleeDistance is set appropriately. It just sounds like you need to do some fine tuning.
Funzilla32
New member
- Joined
- Oct 21, 2017
- RedCents
- 22¢
Re: KissAssist v10.1.3 Released 11/12/2017
Has any thought been given to the following:
1. Not casting while invis || moving || chaseon (as a default not via conds)
2. Ability to set MA || SA || TA /if !${MainAssist.ID}
Sorry to hijack the discussion.
Has any thought been given to the following:
1. Not casting while invis || moving || chaseon (as a default not via conds)
2. Ability to set MA || SA || TA /if !${MainAssist.ID}
Sorry to hijack the discussion.
Re: KissAssist v10.1.3 Released 11/12/2017
The check not to cast if invis should already be built in to KA. We are currently working on adding a new command /switchma witch will switch the MA to the character that issues the command. That way you can setup any group member to switch to being ma, and take the MA role at will, by just issuing the command. I still have more testing to do before I release the code..
The check not to cast if invis should already be built in to KA. We are currently working on adding a new command /switchma witch will switch the MA to the character that issues the command. That way you can setup any group member to switch to being ma, and take the MA role at will, by just issuing the command. I still have more testing to do before I release the code..
Re: KissAssist v10.1.3 Released 11/12/2017
still hate fact if you are attacked while running they will stop running effectively screwing whole group up. they should chase till you are at spot then if ma attacks them they assist not just stop and get beat on.
still hate fact if you are attacked while running they will stop running effectively screwing whole group up. they should chase till you are at spot then if ma attacks them they assist not just stop and get beat on.
Funzilla32
New member
- Joined
- Oct 21, 2017
- RedCents
- 22¢
Re: KissAssist v10.1.3 Released 11/12/2017
Thanks for the quick reply!
I can confirm they are buffing and casting when a /chase is called. This is a bit of a pain, but I can work around it until it's looked into further.
/switch MA.
I've played around with that functionality and removed the comment out in the current version. What I'm driving at is the ability to add some fluidity to the mix. Like the old Rogue Helper mac, one could assign one or more MA's, two, whatever the situation called for without having to add more buttons to a crowded hot-bar.
When the shit hits the fan, you want the machine to handle it fast - I don't afk at all but when the MT drops, having to hit a key (as I play the MT manually) losing precious seconds is the difference between a wipe and clawing back for a win. i.e Alt Tab, push button, wait a few seconds, toons respond.
Also, another issue I've picked up is the follow and stay type commands, /chase on and /chase off. KA doesn't seem to switch off /campradius when a move is called, I've had instances with a /chase off via EQBC sees the mobs "ping pong" back to the original camp loc.
I'll scrub the INI's and start with a fresh Vanilla folder and see if I can reproduce.
Otherwise, very much enjoying the macro and keen to see the ongoing evolution!
- - - Updated - - -
Yes, this is annoying. +1 (above post about toons stopping when aggro happens while OTM) for this being an issue here as well.
Sounds like it's a known issue (?) and thought is occurring on how best to handle this.
Thanks for the quick reply!
I can confirm they are buffing and casting when a /chase is called. This is a bit of a pain, but I can work around it until it's looked into further.
/switch MA.
I've played around with that functionality and removed the comment out in the current version. What I'm driving at is the ability to add some fluidity to the mix. Like the old Rogue Helper mac, one could assign one or more MA's, two, whatever the situation called for without having to add more buttons to a crowded hot-bar.
When the shit hits the fan, you want the machine to handle it fast - I don't afk at all but when the MT drops, having to hit a key (as I play the MT manually) losing precious seconds is the difference between a wipe and clawing back for a win. i.e Alt Tab, push button, wait a few seconds, toons respond.
Also, another issue I've picked up is the follow and stay type commands, /chase on and /chase off. KA doesn't seem to switch off /campradius when a move is called, I've had instances with a /chase off via EQBC sees the mobs "ping pong" back to the original camp loc.
I'll scrub the INI's and start with a fresh Vanilla folder and see if I can reproduce.
Otherwise, very much enjoying the macro and keen to see the ongoing evolution!
- - - Updated - - -
Yes, this is annoying. +1 (above post about toons stopping when aggro happens while OTM) for this being an issue here as well.
Sounds like it's a known issue (?) and thought is occurring on how best to handle this.
Last edited:
Re: KissAssist v10.1.3 Released 11/12/2017
Most likely we will need to do 2 things. 1 - add a flag that allows you to ignore agro when in chase mode, and 2 - what to do when you get agro when in chase mode. I think there is some room for improvement when it comes to chase mode, and everyone has their own opinion, but I don't want to make it so complicated it is no longer KISS.
Most likely we will need to do 2 things. 1 - add a flag that allows you to ignore agro when in chase mode, and 2 - what to do when you get agro when in chase mode. I think there is some room for improvement when it comes to chase mode, and everyone has their own opinion, but I don't want to make it so complicated it is no longer KISS.
Funzilla32
New member
- Joined
- Oct 21, 2017
- RedCents
- 22¢
Re: KissAssist v10.1.3 Released 11/12/2017
Agreed on the KISS principals being applied, is that via the lens of the user or the maintainer? =p
I'd be happy to donate for the purpose of exploring this further. If this is outside of the overall vision and purpose of the project I'll wrangle something custom for myself. To be terse, I'm looking to avoid having to maintain my own little private fork of the great works taking place here anytime a new version is pushed.
Coder I am not, but I have something like this in mind, been playing around with macros for a bit and find it almost as much fun as playing EQ.
Another issue that may have a simple solution from a bright spark was the implementation of the /chase function and not being able to assign a "ChaseToon" instead of the bots chasing after the main assist as defined by KA.
E.g - Playing at the keys in a group with a merc tank, the cleric or other toons if assisting off a caster or me as a puller, when a /chase is called they seem to default to grab onto the defined KA main assist and chase after them or "it" instead of the "Sender" or a designated follow toon.
I'll maybe cobble together something to handle chat requests from EQBC, saying that I know enough to be dangerous with TLO's and scripting in general.
Just some feedback on an excellent macro, and by no means do I want to come across as critical. Just a few small things that I think would make this just that much better, without weaving in a high degree of complexity from a development perspective, and KISS for the rest of us!
Thanks again!
Agreed on the KISS principals being applied, is that via the lens of the user or the maintainer? =p
I'd be happy to donate for the purpose of exploring this further. If this is outside of the overall vision and purpose of the project I'll wrangle something custom for myself. To be terse, I'm looking to avoid having to maintain my own little private fork of the great works taking place here anytime a new version is pushed.
Coder I am not, but I have something like this in mind, been playing around with macros for a bit and find it almost as much fun as playing EQ.
Rich (BB code):
/if !${ChaseOnVarCheck} && !${Me.Invis} || !${Stick.Active}) /call CombatStuffAnother issue that may have a simple solution from a bright spark was the implementation of the /chase function and not being able to assign a "ChaseToon" instead of the bots chasing after the main assist as defined by KA.
E.g - Playing at the keys in a group with a merc tank, the cleric or other toons if assisting off a caster or me as a puller, when a /chase is called they seem to default to grab onto the defined KA main assist and chase after them or "it" instead of the "Sender" or a designated follow toon.
I'll maybe cobble together something to handle chat requests from EQBC, saying that I know enough to be dangerous with TLO's and scripting in general.
Just some feedback on an excellent macro, and by no means do I want to come across as critical. Just a few small things that I think would make this just that much better, without weaving in a high degree of complexity from a development perspective, and KISS for the rest of us!
Thanks again!
- Joined
- Jun 12, 2015
- RedCents
- 58,244¢
Re: KissAssist v10.1.3 Released 11/12/2017
my short idea, have toons auto chase main assist, have main assist pick a target and stay on it, unless called by main tank to switch target, if main tank calls target switch, ma switches to his and everyone else assist of ma.
if in chase mode, and being attacked everyone run to main tank and let him sort it out, and ma can pick a target when he within 25 range of main tank.
my short idea, have toons auto chase main assist, have main assist pick a target and stay on it, unless called by main tank to switch target, if main tank calls target switch, ma switches to his and everyone else assist of ma.
if in chase mode, and being attacked everyone run to main tank and let him sort it out, and ma can pick a target when he within 25 range of main tank.
aspire2008
Well-known member
- Joined
- Nov 10, 2012
- RedCents
- 2,583¢
Re: KissAssist v10.1.3 Released 11/12/2017
I know its been like a month since I asked, but curious what all the changes were in the past 3 releases.
I know its been like a month since I asked, but curious what all the changes were in the past 3 releases.
LurkMcGurk
BANNED
- Joined
- Jul 1, 2015
- RedCents
- 9,632¢
Re: KissAssist v10.1.3 Released 11/12/2017
Just to let you know we added a new command /chaseme. It lets any character in your group become the chasee.
This was done when we added the /chaseme command. The new variable is called WhoToChase. It defaults to the mainassist, so when you use /chase KISS still functions the same. The /chaseme command sets the WhoToChase to the character issuing the command. The command basically issues the /bcg //chase on ${Me.CleanName} command, so by using /chase on CharacterNameHere you can have any character /chase any other character not just the Main Assist.
^ kaen gets it
- - - Updated - - -
my ma is my main tank so if he don't have it they should be catching up to him.
Just to let you know we added a new command /chaseme. It lets any character in your group become the chasee.
This was done when we added the /chaseme command. The new variable is called WhoToChase. It defaults to the mainassist, so when you use /chase KISS still functions the same. The /chaseme command sets the WhoToChase to the character issuing the command. The command basically issues the /bcg //chase on ${Me.CleanName} command, so by using /chase on CharacterNameHere you can have any character /chase any other character not just the Main Assist.
Funzilla32
New member
- Joined
- Oct 21, 2017
- RedCents
- 22¢
Re: KissAssist v10.1.3 Released 11/12/2017
Bravo! Excellent and prompt implementation on community requests that just make this great tool that much better.
Now, I wasn't aware of the syntax with /chase more or less already existed, is the current config / setup documentation current and correct?
Will test this out in the morning =p
Glad I'm a member here, thanks again, great work!
Bravo! Excellent and prompt implementation on community requests that just make this great tool that much better.
Now, I wasn't aware of the syntax with /chase more or less already existed, is the current config / setup documentation current and correct?
Will test this out in the morning =p
Glad I'm a member here, thanks again, great work!
Re: KissAssist v10.1.3 Released 11/12/2017
ahh i see, i just use my tank as my ma and always chase him but when one drops invis and gets aggro they just wanna stand there instead of catching up with group then group stands where they are i run back and now the group is split up usually causing a wipe .
ahh i see, i just use my tank as my ma and always chase him but when one drops invis and gets aggro they just wanna stand there instead of catching up with group then group stands where they are i run back and now the group is split up usually causing a wipe .
Fennil
Member
- Joined
- Oct 26, 2016
- RedCents
- 42¢
Re: KissAssist v10.1.3 Released 11/12/2017
Undefined Variable WhatItem used on line [email protected] /call CastBard "${WhatItem}" ${WhatID} CastItem macro paused..... wtf???
Undefined Variable WhatItem used on line [email protected] /call CastBard "${WhatItem}" ${WhatID} CastItem macro paused..... wtf???
Re: KissAssist v10.1.3 Released 11/12/2017
Try re-downloading KA. you may have gotten an older version in the download. That error was fixed in the last revision.
Try re-downloading KA. you may have gotten an older version in the download. That error was fixed in the last revision.
Fennil
Member
- Joined
- Oct 26, 2016
- RedCents
- 42¢
Re: KissAssist v10.1.3 Released 11/12/2017
bug .
bard not keep twist when buff done
when start melee twist again
bug .
bard not keep twist when buff done
when start melee twist again
Rich (BB code):
TwistOn=1
TwistMed=21
TwistWhat=21 8 1 21 4 2 21
Buffs1=Songblade of the Eternal|me
MeleeTwistOn=1
MeleeTwistWhat=21 6 1 21 4 2 21aspire2008
Well-known member
- Joined
- Nov 10, 2012
- RedCents
- 2,583¢
Re: KissAssist v10.1.3 Released 11/12/2017
Sounds like /twist off needs to happen between pulsing a gem song and casting an item somewhere in the code. Because this isn't an issue with the macro per se, its an issue with EQ that has existed since 1999, this happens without mq2 if you cast a item while casting a gem song.
So :
Gem song cast -Gem song cast finishes - /twist off - cast item - back to casting song order
So essentially, there should be /twist off line before any item cast check.
Sounds like /twist off needs to happen between pulsing a gem song and casting an item somewhere in the code. Because this isn't an issue with the macro per se, its an issue with EQ that has existed since 1999, this happens without mq2 if you cast a item while casting a gem song.
So :
Gem song cast -Gem song cast finishes - /twist off - cast item - back to casting song order
So essentially, there should be /twist off line before any item cast check.
Re: KissAssist v10.1.3 Released 11/12/2017
Try replacing your whole CastBard routine with this and let me know if this helps?
I think the issue was the WasTwisting Variable was never getting set to False so it thought it was always twisting.
Try replacing your whole CastBard routine with this and let me know if this helps?
Rich (BB code):
Sub CastBard(string WhatSpell,int WhatID,string sentFrom)
/if (${Debug}) /echo CastBard Enter Line#: ${WhatSpell} ${WhatID} ${sentFrom}
/varset WasTwisting ${Twist}
/if (${WasTwisting}) {
/squelch /twist off
/delay 30 !${Twist}
}
/if (${Target.ID}!=${WhatID} && ${Spawn[id ${WhatID}].ID}) /call CastTarget ${WhatID}
/if (${FindItem[=${WhatSpell}].ID}) {
/if (${Debug}) /echo I am a bard CastBard ${WhatSpell}
/delay 10
/casting "${WhatSpell}|item" -targetid|${WhatID}
/delay 300 !${Me.Casting.ID}
/varset CastResult ${Cast.Result}
} else /if (${Me.GemTimer[${WhatSpell}]}==0) {
/delay 2
|/if (${Me.GemTimer[${WhatSpell}]}!=0) /return
/squelch /twist once ${Me.Gem[${WhatSpell}]}
/delay 30
/varset CastResult CAST_SUCCESS
}
/if (${WasTwisting} && !${Twist}) /squelch /twist
/return ${CastResult}I think the issue was the WasTwisting Variable was never getting set to False so it thought it was always twisting.
Re: KissAssist v10.1.3 Released 11/12/2017
bard cast item buff problem can try this
bard cast item buff problem can try this
Rich (BB code):
|--------------------------------------------------------------------------------------------------------------|
Sub CastBard(string WhatSpell,int WhatID,string sentFrom)
/if (${Debug}) /echo CastBard Enter Line#: ${WhatSpell} ${WhatID} ${sentFrom}
/if (${FindItem[=${WhatSpell}].TimerReady}!=0 && ${Me.GemTimer[${WhatSpell}]}!=0) /return
/varset WasTwisting ${Twist}
/if (${Twist}) /squelch /twist off
/if (${Target.ID}!=${WhatID} && ${Spawn[id ${WhatID}].ID}) /call CastTarget ${WhatID}
/if (${FindItem[=${WhatSpell}].ID}) {
/if (${Debug}) /echo I am a bard CastBard item ${WhatSpell}
/casting "${WhatSpell}|item" -targetid|${WhatID}
/delay 20
/delay 300 !${Me.Casting.ID}
/varset CastResult ${Cast.Result}
} else {
/if (${Debug}) /echo I am a bard CastBard song ${WhatSpell}
/delay 2
/squelch /twist once ${Me.Gem[${WhatSpell}]}
/delay 33
/varset CastResult CAST_SUCCESS
}
/if (${WasTwisting}) {
/squelch /twist
} else {
/squelch /twist off
}
/return ${CastResult}
|--------------------------------------------------------------------------------------------------------------|
Last edited:
Maskoi
old and salty
- Joined
- Sep 28, 2005
- RedCents
- 82,796¢
Re: KissAssist v10.1.4 Released 12/23/2017
KissAssist v10.1.4 Released 12/23/2017
Changes since 10.1 - 10.1.4
Turbo changed from 80 to 120
Missing bites, gores,rampages,smashes added to Got Hit event
Replaced most /goto with /break or /continue to update and stream line Kiss for latest MQ2 updates
Tweaked mob distance checks to be more aware of character xyz in and out of camp
Added some labels for better Debugging
Mash AA fix
Toons not returning to camp fixed
Check ini will not show missing items due to summoned items not being in inventory on startup
New command added /chaseme
/chaseme will make all toons running Kiss follow who ever issuses the /chaseme command Requires MQ2EQBC to be loaded.
/switch has been changed /switchnow. So check all of your hotkeys if you use this command
Drag added to Gmail Events
The puller now will drag their corpse back to camp from out in the field if they died for a rez if he comes within 80' of it while pulling
Kiss no longer saves settings to mq2moveutils ini file. - From EQmules version
Conditions have been added to AE section.
Kiss will now add a _I to instanced zone names in KissAssist_Info.ini file to indicate the zone is an instance
Cast Section revamped
Pull section revamped
Bard not twisting randomly Fixed
Updated to include 13th spell gem. Please re-download.
KissAssist v10.1.4 Released 12/23/2017
Changes since 10.1 - 10.1.4
Turbo changed from 80 to 120
Missing bites, gores,rampages,smashes added to Got Hit event
Replaced most /goto with /break or /continue to update and stream line Kiss for latest MQ2 updates
Tweaked mob distance checks to be more aware of character xyz in and out of camp
Added some labels for better Debugging
Mash AA fix
Toons not returning to camp fixed
Check ini will not show missing items due to summoned items not being in inventory on startup
New command added /chaseme
/chaseme will make all toons running Kiss follow who ever issuses the /chaseme command Requires MQ2EQBC to be loaded.
/switch has been changed /switchnow. So check all of your hotkeys if you use this command
Drag added to Gmail Events
The puller now will drag their corpse back to camp from out in the field if they died for a rez if he comes within 80' of it while pulling
Kiss no longer saves settings to mq2moveutils ini file. - From EQmules version
Conditions have been added to AE section.
Kiss will now add a _I to instanced zone names in KissAssist_Info.ini file to indicate the zone is an instance
Cast Section revamped
Pull section revamped
Bard not twisting randomly Fixed
Updated to include 13th spell gem. Please re-download.
Last edited by a moderator:
- Joined
- Jun 12, 2015
- RedCents
- 58,244¢
Re: KissAssist v10.1.4 Released 12/23/2017
causes an error the sub is named:PullModeToggle
Rich (BB code):
LINE 6563: /if (${Select[${Role},pullerpettank]} && ${PullRoleToggle} && ${Group.Puller.ID}==${Me.ID}) /call TogglePullMode TurnOff