jsr09
Member
- Joined
- Jan 24, 2019
- RedCents
- 150¢
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.

do you have anything else setup - like boxhud, or an mq2hud, or using something that might be trying to create dannet queries?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

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
i'm wrong plenty, however, the issue as explained by knightly > here < is that an unused variable can get "locked out"@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.
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.i'm wrong plenty, however, the issue as explained by knightly > here < is that an unused variable can get "locked out"
aye for sure don't think this kiss's fault (despite other things someone said above to say it was)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)

