• 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

Problem - "mage" issues from recent patch (6 Viewers)

Joined
May 21, 2020
RedCents
34¢
Version of KissAssist.mac?
12
When did your problem start?
6/18
Character Role?
  1. Tank
  2. Hunter
What class is having this issue?
  1. Warrior
How often does this issue occur?
Always
Can you reproduce the issue?
yes
The recent patch changed the SClassInfo / ClassInfo tags for mage/magician, and now when I run KA and a mob has the word "mage" in the name, it throws a warning. I searched the macro for "mage" and "spawnsearch" with no results. I am assuming it is due to ${SpawnCount[${vstStr1} radius ${MaxRadius} zradius ${MaxZRange} targetable ${SearchType}]}>${PullMaxCount} or something simlar, but I cannot figure out how to get around this warning. KA still functions but just throws warnings.

1781792588358.png
 
The recent patch changed the SClassInfo / ClassInfo tags for mage/magician, and now when I run KA and a mob has the word "mage" in the name, it throws a warning. I searched the macro for "mage" and "spawnsearch" with no results. I am assuming it is due to ${SpawnCount[${vstStr1} radius ${MaxRadius} zradius ${MaxZRange} targetable ${SearchType}]}>${PullMaxCount} or something simlar, but I cannot figure out how to get around this warning. KA still functions but just throws warnings.

View attachment 77630
well kiss would need to be updated. the warning says it is a deprecation - so it is still going to function as it did before - but warn that there was a deprecation.

there's nothing for you to fix (unless you edited your kiss, which would get overwritten next time you patched)
 
well kiss would need to be updated. the warning says it is a deprecation - so it is still going to function as it did before - but warn that there was a deprecation.

there's nothing for you to fix (unless you edited your kiss, which would get overwritten next time you patched)
I would gladly edit my kiss if i could figure out what to edit even if its just commenting out a line. I dont overwrite my macros from patch so while i appreciate the warning, its not a concern for me.

any help with what to edit out until a real fix is appreciated.
 
1781797410025.png
Best place I could find without actually testing everything was the spawn count for 'eye of' checking in validate target.

Set up the above test just to prove the second part of the If isn't short circuited and still triggering the issue.

Short answer: comment out line ~983 of kiss assist. Looks like this:
/if (${MobName.Find[eye of]} && ${SpawnCount[pc ${MobName.Right[${Math.Calc[${MobName.Length}-7]}]}]}) /return Spell-Eye-PC

This just reminded me of how lucky we are to have Lua now.
 
View attachment 77633
Best place I could find without actually testing everything was the spawn count for 'eye of' checking in validate target.

Set up the above test just to prove the second part of the If isn't short circuited and still triggering the issue.

Short answer: comment out line ~983 of kiss assist. Looks like this:
/if (${MobName.Find[eye of]} && ${SpawnCount[pc ${MobName.Right[${Math.Calc[${MobName.Length}-7]}]}]}) /return Spell-Eye-PC

This just reminded me of how lucky we are to have Lua now.
tyvm for the reply, I will test this!
 
why the heck is spawn search even checking for mage when there is never been a mage class in eq, its always been Magician and or MAG

its not a kissassist issue, its a spawn search issue, it treats mage like a class and not a name like it should, so they probably fixed it, and having a gnome mage on target gets you into that bit
 
It's checking for "Does my targets name start with 'eye of' and do the right most characters starting from the 7th index contain a PC name?

So it is asking, is my target "eye of PCNAME". But the target is "a gnome mage" so it turns into SpawnCount[pc mage]

I just looked over kiss and looked for mobname being used in a spawn search. Didn't actually test this.
 
yes but spawn search should not treat mage as a class tag, it should only treat it as a name, but yes with a gnome mage you gonna hit that check, but i thought eye of zomm was just that and not eye of bytebite
 
1781800883871.png To add to this discussion, I confirmed that it is indeed the target name thats causing this, and not the class because this target did not cause any warnings. I still have not gotten around to testing the fix.
 
1781801748110.png

spawn search needs this tag to even search by class, anything other than is treated as name

1781801796220.png

so technically

${SpawnCount[PC Magician]} should only count players with the name magician


so something changed in spawn search.
 
Problem - "mage" issues from recent patch

Users who are viewing this thread

  • snoojis
  • D
  • S
  • Redfrog
Back
Top
Cart