• 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 - Can't get KA to run

jsr09

Member
Joined
Jan 24, 2019
RedCents
150¢
Version of KissAssist.mac?
12
When did your problem start?
Beginning
Character Role?
  1. Assist
What class is having this issue?
  1. Bard
How often does this issue occur?
Always
Can you reproduce the issue?
Everytime i do /mac kissassit it comes up with the error
1639255976218.png
 
do you have any conditions or docommand entries in the ini for the toon that uses that variable? that would be my first check
 
we would need to know what the undefined variable is.

if it is something sensitive you could say something like "it is my maintank's name" instead of actually providing your main tank's name for example
 
It would not. Have you verified that dps name is not used in one of your ini's, and if it is, did you spell it correctly, and is the punctuation around it correct?
 
So, just to verify...If you go to your bard and type
Code:
/mac kissassist tank
for instance, it crashes with the error messages you've input above?
 
only if he's doing something different than every other KA user out there AN. I hear what you're saying, but I use KA every day, I never get that message. So he's got a different version, a bad setting, or he's executing different. I'm just trying to verify we're on the same page.
 
please forgive me guys, Im not very fluent in this. When i target my MA and type /mac kissassist is when i get the error
 
please forgive me guys, Im not very fluent in this. When i target my MA and type /mac kissassist is when i get the error
do you have anything else setup - like boxhud, or an mq2hud, or using something that might be trying to create dannet queries?
 
This sounds like a plugin issue. The error is getting thrown from kiss, but those 2 lines that are throwing errors have no reference to a variable. SO a plugin is crapping out on some thing and throwing the error from kiss.
 
so everytime i unload dannet it works just fine until i zone again then have to unload dannet again. Problem is cant use the boxhud without it
 
DanNet frequently traps errors thrown from other plugins. It would be interesting to see what plugins you have loaded. You can get a list from your session and either extract it from your server_character.log file (using /mlog on and /mlog off) in your Next\logs folder, or just expand the in-game MQ status window and grab a screen snip. Sometimes you have to /plugin bad_plugin unload and get MQ down to the bare minimum to clear up errors.

1639326263496.png
 
This sounds like a plugin issue. The error is getting thrown from kiss, but those 2 lines that are throwing errors have no reference to a variable. SO a plugin is crapping out on some thing and throwing the error from kiss.
so everytime i unload dannet it works just fine until i zone again then have to unload dannet again. Problem is cant use the boxhud without it

this is the issue
 
@Sic is rarely wrong. To me that means one of the various INI files in use by KissAssist must be corrupted in some fashion that results in the macro or a plugin trying to interpret it as a variable.

I'd start over with a pristine Kiss character INI file and see if the problem persists. If it does then Kiss is not part of the problem and MQNext probably needs a clean reinstallation.
 
@Sic is rarely wrong. To me that means one of the various INI files in use by KissAssist must be corrupted in some fashion that results in the macro or a plugin trying to interpret it as a variable.

I'd start over with a pristine Kiss character INI file and see if the problem persists. If it does then Kiss is not part of the problem and MQNext probably needs a clean reinstallation.
i'm wrong plenty, however, the issue as explained by knightly > here < is that an unused variable can get "locked out"
 
i'm wrong plenty, however, the issue as explained by knightly > here < is that an unused variable can get "locked out"
The lines that were being referenced with errors, don't have any variables in them, so the error is being caused outside of the macro, and in most cases that would be a plugin. Regardless of what is causing the error, it is not something that is wrong with the macro. I guess that was the point I was trying to make.
 
The lines that were being referenced with errors, don't have any variables in them, so the error is being caused outside of the macro, and in most cases that would be a plugin. Regardless of what is causing the error, it is not something that is wrong with the macro. I guess that was the point I was trying to make.
aye for sure don't think this kiss's fault (despite other things someone said above to say it was)
 
Problem - Can't get KA to run

Users who are viewing this thread

Back
Top
Cart