Question:

When I manually right click on a spammer and report them, it is added to a list instead of being reported at once - is there a way to avoid it being added to the list but forced to be reported NOW ?

Here is a request:

When you are told to click on a link to bring up the report window, I'd like a feature to see the "clear" button disabled.

So many times I end up clicking on that instead of reporting the spammers and then its too late..

For now, the quick and dirty way is to do a search in your addons directory for the file "LibDBIcon-1.0.lua"

Replace all versions of this file with the one included with SpamSentry.

I'm sure there's a better fix, but this works for me.

So is there a straightforward resolution to turning OFF the minimap icon and getting it to stay off?

Further testing with the icon duplication problem shows that any addon using the updated ldbicon library will cause spamsentry to have 2 icons. Looks like there was a change in version 7 or 8 that broke spam sentry's ldb code. I tried changing the version in spam sentry's libraries, but that didn't help, so for now I'm downgrading ldbicon library in all of my other addons to version 6.

I've installed the newest bigwigs bossmods and for some reason it causes SpamSentry to duplicate its icon. This is with broker2fubar installed, so I get an icon on the fubar and on the minimap. Not sure which mod is the culprit here.

*note: I rolled back the ldbicon library included with bigwigs (rev: 8) to the one that spamsentry uses (rev: 6) and that made the problem go away.

Good for you. But as I said, I find that with as much as addons are coded, recoded, and often conflict with one another, I see that assertion as highly impractical and unrealistic.

Add in that I use a number of fairly unique addons that have fallen into disuse and disrepair but are at present irreplaceable, and there you have it.

In any case, few of these errors make any part of my interface unusable, so I don't generally care much about them.

And on the odd occasion where one of them does matter, I want an error catcher there recording it, but not shoving it in my face along with the 5-10 other inconsequential errors I receive regularly.

I have 143 folders (embeded libraries) in my addon directory (without the blizzard ones) and usually have 0 errors when playing :P Might be addon conflicts that are causing them but usually you don't have that many errors when everything is working right.

The setting's there, but if I recall the last time I tried that, the problem was it just didn't report or record anything either. It's like turning it off.

I don't want it off, I just don't want it in my face every five seconds. I want to be able to read it when I choose. So far the only error catcher that I've seen that does this reliably is ImprovedErrorFrame- which the understandable concession that it's reports aren't too verbose.

I presented that thought to the Swatter team, and I recall the response I got was something along the lines of "you shouldn't have errors popping up that often".

And my retort was something along the line of "you try having 200+ addons installed and see if you don't get at least five errors a session."

But anyway, to make a long story short, they ignored me.

There *is* a way to disable the swatter pop-up but I can't remember how exactly. But I know the setting is there. I have mine set up that way. It then simply sends the error notification to my chat tab where upon I can click it's link to open Swatter. There have been rare occasions where Swatter has popped up before my add-ons have fully loaded but that seldom interferes with my gaming session. "/swatter show" is the command to force it to pop-up, I believe, if it's hidden. Perhaps "/swatter hide" is the opposite. Try "/swatter help" to see if it lists some commands. Gotta love old-school text interfaces.

Incidentally, SpamSentry appears to be compatible with Cellular (the add-on) as well.

Edited the quote to cut down a bit on the wall of text effect, leaving the relevant parts to my reply.

Not a problem. I'm grateful in turn that you listen to feedback. You'd be shocked how many authors I've encountered who seem to be deaf, dumb and blind when it comes to things like this.

That and I realize it takes interaction like this to keep an Addon in healthy shape. And to me, this has alwasy been a quality Addon, well worth the effort. You do a great job, and I appreciate it, that's enough for me.

I'm not sure if the ChatThrottleLib thing is incidental or not. It doesn't always occur in conjunction with a false positive in SpamSentry.

As for a full stacktrace, that came out of ImprovedErrorFrame. I actually have !Swatter available to me if that will produce the desired specifics, but I don't normally keep it enabled.

I have about 200+ addons installed, and frankly some throw regular errors at me that, even if I could figure out why they occur, I often find authors are much more interested in playing the blame game than helping me to get down to the problem and fix it.

So, Improved Error Frame allows me to queue error messages without having them forced into my face every session- which would make the game with my current UI frankly unplayable. I've asked the team that authors Swatter to make queueing an option- because, like you, I think !Swatter produces much more explicit error reporting- I just can't have an Addon enabled that's going to be blocking my screen up every ten seconds.

Sadly the !Swatter team doesn't seem too interested in including a rather simple feature like that, so I'm stuck with Improved Error Frame.

When I'm not doing anything important I'll have to let !Swatter have a go at it and see if I can capture a more detailed error for you, but sadly I can't promise much. Just getting those four false positives was somehting of a rigmarole. This will be moreso, I suspect.

Finally, I have a few false positives, occurred literally within seconds of one another:

1 and 3 and 4 all come from the same individual, though it isn't like he's a level 1 or anything. It's consistent at least. The first of those two got caught in the filter twice- three times if you count the second variation.

Actually each time it happens it seems like there's an error from a version of ChatThrottleLib used by another addon- CallToArms. Lemme see if I can get a copy of that error...