• 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

KissAssist Release KissAssist (2 Viewers) 12.002.039

No permission to download
Join us with Level 2 access RedCents
Overview Commands Instructions Updates (69) Reviews (5) History Discussion
necroforlife said:
Was on a mount, it's outdoor zone, but it's never done this before. I been using KISS for over a year and never seen this happen
Click to expand...

Here try this. Find the CastMem sub and make the following change:

From:
Code: 
        /if ((${Attacking} && ${MainAssist.Equal[${Me}]}) || (${HealsOn} && ${AggroTargetID} && ${sentFrom.NotEqual[Heal]} && !${Me.Mount.ID})) {
            /echo Cannot mem a spell durring combat or while you have aggro.
            /return notready
        }

TO:
Code: 
        /if ((${Attacking} && ${MainAssist.Equal[${Me}]}) || (${HealsOn} && ${AggroTargetID} && ${sentFrom.NotEqual[Heal]})) {
            /echo Cannot mem a spell durring combat or while you have aggro.
            /return notready
        }

See if that helps.
 
Relik said:
My bards seem to be getting stuck in the latest kiss in regards to casting items. Currently my bard is set to rebuff an item click which has a cast time and occasionally (pretty frequently) when it casts the item it will get ... stuck... The cast will finish but instead of actually finishing and ending the cast it will just get stuck and say it is casting the item still. Almost like it does if you play a single song and the song stays active, except its not a song its an item buff. I am assuming this has to do with twisting songs and clicking items but the code looks right to me to stop twisting before clicking the item so im not sure.

Either way as a result when it hits this part of CastBard the bard just hangs until I manually kill the spell cast.
Code: 
            /while (${Me.Casting.ID}==${FindItem[=${BardSpell}].Spell.ID}) {
                /delay 5
            }
Click to expand...


The next time this happens can I get you to use this command before killing the casting.

/echo ${Me.Casting.ID} ${FindItem[=${BardSpell}].Spell.ID} ${BardSpell}

please post your results.
 
ctaylor22 said:
The next time this happens can I get you to use this command before killing the casting.

/echo ${Me.Casting.ID} ${FindItem[=${BardSpell}].Spell.ID} ${BardSpell}

please post your results.
Click to expand...

[MQ2] 3628 3628 Songblade of the Eternal
 
I am assuming the casting window is NOT open, but why isn't ${Me.Casting.ID} being cleared if you are no longer casting. Well lets try this.

Here replace this line:

Code: 
    /while (${Me.Casting.ID}==${FindItem[=${BardSpell}].Spell.ID}) {

with this line:

Code: 
/while (${Me.Casting.ID}==${FindItem[=${BardSpell}].Spell.ID} && ${Window[CastingWindow].Open}) {

Let me know if that helps.
 
Having difficulties burning manually with /burn.

From macroquest ini file

Code: 
/burn=/echo set: WhenToBurn

All i get in MQ2 window is text saying set: WhenToburn

Is there something wrong with this line or am I looking at the wrong place?
 
this update completely breaks kiss, it wont assist anymore.
 
Is it normal for KA11 being a tank to switch between self and target back and forth really fast and very frequently?
 
XiroFS said:
Is it normal for KA11 being a tank to switch between self and target back and forth really fast and very frequently?
Click to expand...
I've seen this if you have a spell in your dps with |ME . i assume kiss is trying to check for said buff. like my cleric yaulp spell i have |ME so it would target myself then cast. no need for self target so i removed the |ME and it stopped
 
yeah, dont use |me on spells that have self as target, as that wont change anything for the spell, but only make kiss got nuts
 
It's an issue with having run ihc and ka I believe. Go into your macroquest2.ini file and delete the alias for /burn.

According MQ2 documentation you should also be able to type "/alias delete /burn" from in game as well.
 
kaen01 said:
yeah, dont use |me on spells that have self as target, as that wont change anything for the spell, but only make kiss got nuts
Click to expand...

so no me in the dps section. me is ok in buff section? and do you need a |mob in the dps section? isn't that the default? so basically the only thing you'd ever have in the dps section is |ma for say a combat proc buff or something of the sort. generally speaking? just trying to clean up my ini.
 
You'd need a |me in the dps section if the spell isn't self only. Like a shaman casting panther on themselves would need it. You don't need it for self only heals or self only buffs.
 
dreamflux said:
You'd need a |me in the dps section if the spell isn't self only. Like a shaman casting panther on themselves would need it. You don't need it for self only heals or self only buffs.
Click to expand...

yeah i am just trying to make my ini slow down a tiny bit with the target switching. and maybe squeeze a little more performance out of it. i think i sometimes get a little too OCD with tags. but again, if it's in the dps section, isn't the default target going to be a mob, so you would never need |mob either. or am i starting to think too much about it and it's not a big deal if |mob is in there.
 
I have noticed that on Kiss11 mages will not resummon their main pet if it dies and this is a problem. Mages should make it the number 2 priority to get a pet up asap right after running whatever they have setup to stop themselves from getting hit. This likely also applies for necro and bl but I do not play those classes with kiss.
 
I always run kissassist1004e15 on my cleric and currently KissAssistVer=10.0.4.1.99. Starting In the [General] Settings Section I will list and underline missing options or if more info is needed. I see some that and new and have a default of on and don't know what they do.
MoveCloserIfNoLOS=0 I have not idea what this is.
TheWinTitle=NULL I have not idea what this is.
GemStuckHelp=Sometimes the spellgems get stuck in a foreverloop, casting a altability that has a cast time will unstick it, this is a eq bug.
GemStuckAbility=NULL No info
RezAcceptOn=0|98 This should have been just 0. Has something changed or is it a typo?
LootOn=0 I read today that this turns on ninjadvloot. Could i get some clarification?
In this heals section.
AutoRez1=NULL
AutoRez2=NULL
AutoRez3=NULL First time seeing these and have no idea what they do.
Pull section
CheckForMemblurredMobsInCamp=0
PullNamedsFirst=0
ActNatural=1
UseCalm=0
CalmWith=Harmony
PullArcWidth=0 These items are missing and or not any information. I admit its pretty obvious how for UseCalm and CalmWith, but i don't know who, how many, is there a radius and what to expect.
Bandolier section
There is not Bandolier section and same for Ohshit.
I finally stopped bsing and hit 110 on my main three, so I have to make some changes to my ini files. I took a quick look at each Kissassist_Toonname.ini file. I noticed many new options and it looks like there are differences between kissassist1004e15.mac and Kissassist.mac ini. I ended up back here after looking at my copy that I have on one note. Having all the info in one places is great. Which was very handy when I was starting out. I can list some more stuff after I give my bard and mage a once over.
 
RezAcceptOn=0|98 This should have been just 0. Has something changed or is it a typo?

0 means you wont accept rezzes, 98 is the percent rez you would accept if the 0 was 1. so ideally should be set at 1|96 or at least 1|90 if your F2P, and using merc healers


the Autorez commands --- are for clerics shamans druids etc who have more than one means of Rezzing people, i.e
AutoRez1=Blessing of Resurrection
AutoRez2=Divine Ressurection
AutoRez3=Resurection Clicky and so on
 
You're running the eqmule mod of KA, so you need to check in on his thread. A lot of those are ini settings that only pertain to his mod and he has explanations of most.

PullArcWidth lets you set an angle range, directly in front of your puller, that you want them to pull mobs from. So PullArcWidth=180 will only pull mobs from in front of the puller. It is based on which direction you're facing when you start KA. =0 is the default and pulls from all around.
 
Ordell said:
So no posts in almost 2 months. What's going on with KA development?
Click to expand...
Maskoi has done a few >>> streams <<< lately and has mentioned some cool stuff coming here in the future, he's also stopped by Discord and chatted a bit. Last weekend he said he has some fixes for Kiss and a lot of little things that haven't got released yet, but will upload a new release in the next couple of days
 
ctaylor22 updated KissAssist with a new update entry:

Kissassist 11.002

This is the same copy that Maskoi posted in the General discord channel.
Click to expand...

Read the rest of this update entry...

Maskoi will be posting more details on this update. We made some changes to the burn section to try and make it bit more flexible. Each entry now has a third argument, but currently is NOT checked. The code is there, but the logic is not implemented. Also, I could use some input on how burns are actually used. My Main is a shaman not a huge DPS'r back in the day when I raided.

I added a new section [StartupCommands] that some of you may find useful. This is going to be an UN-DOCUMENTED feature for now. Format Example:

[StartupCommands]
CommandSize=5
Command1=/caption anon on
Command2=/memmyspells
Command3=/chase on
Command4=null
Command5=null

This is run just before the main loop is entered. If you don't know what I am referring to, then you may NOT want to use this feature.

There were more changes I am not going to cover. Maskoi has prepared a full write up of the new changes and will be posing them to the main thread.

Hope you all enjoy.
 
Last edited:
It looks like the GroupWatch function might be messed up? My only toons that had it on would sit and wait for the SK or Bst to get 100% endurance. As soon as I turned it off they both worked fine again. Both toons were at 100%
 
GroupWatch should only be turned on, on one toon and turned off for all others. If you have a puller or pullertank turn it on on that toon.
 
Same here.

I only have my pullertank set to groupwatchon=1 and hes sitting there waiting fpr my rogue to get 100% endurance for ages. All other toons are set to groupwatchon=0.

started to happen after latest patchday!
 
just noticed groupwatchon=2 works fine.

Guess its just the problem with melee endurance not being noticed correctly.
 
krause said:
just noticed groupwatchon=2 works fine.

Guess its just the problem with melee endurance not being noticed correctly.
Click to expand...
yup HERE is a thread talking about eqmule working on the issues with CurMana and CurEndurance as well as Mq2rez
 
You must log in or register to reply here.
KissAssist Release KissAssist
Next unread thread 🦁

Users who are viewing this thread

Total: 3 (members: 0, guests: 3)
Back
Top
Cart

Cart

Total -