Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
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)
My puller is an enchanter and it would be nice if there was an option like 'CheckBuffsWhenChainPulling=1'.
If my runes are not up, there is a chance I will die mid-pull and Kissassist will not check for buffs unless PullReset is called or it reaches the ChainPull threshold.
I currently modify...
Ah thank you CTaylor22, I was mistaken that using the ID of the AA ability was supported. I've been using it for years without issue until now.
I don't know if it was once supported in the past or I did it on a whim and it worked. I tend to use the ID of the AA when it fails to cast properly...
The main issue is that by specifying a number, Me.Book[#] and Me.CombatAbility[#] will return objects based on their slot/list number.
This is normally not an issue because the numbers are higher and those entries are empty and return NULL.
The problem you will encounter is you get different...
Using the name it never seems to fire (I usually start testing with a high number to test the spell can actually fire). I run into this issue a lot, so I started using AA # which has consistently worked for me.
The exact line is (under [Heals]):
"Heal8=180|40"
"Zealous Touch" is the 180th spell in my spellbook.
There is at least two different conditionals that can fail with this error, but I expect that there is more.
If you attempt to use a low numbered AA ability (for example: Hand of Piety #180) and you have at least that many spells in your spellbook, kissassist will fail with an error indicating the conditional is invalid.
Hand of Piety = AA #180
Complete Heal = spell in 180th position in spellbook...
on TLP servers reciving msg "You have no targets in your extended target window set to auto, Please set 1 target to auto and restart kissassist"
kiss worked fine b4 the patch.. we don't have an extended target window on TLP, what to do?
So I was running an older version of Kissassist that I got from a friend before I had a sub here, everything worked fine.. I have run into a weird issue after updating to the current Kissassist version. When I start the macro it works fine and operates fine for what I have it set to do.. My...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.