StopAddonMessage
StopAddonMessage (SAM) is a firewall that lets you prevent addons from sending and receiving hidden messages.
- Don't want others knowing you're running a certain addon?
- Worried about what addons are broadcasting?
- Want to silence a spamming addon?
- Receiving You are not in a raid spam in battlegrounds/arenas?
- Receiving You are not in a guild spam?
SAM can help.
FAQ:
Q) How does SAM block outgoing messages?
A) SAM hooks SendAddonMessage() and blocks messages from being sent out.
Q) How does SAM block incoming messages?
A) SAM hooks frame's receiving CHAT_MSG_ADDON and blocks them from receiving the event.
Q) Can SAM block visible addon messages like Ding!, auto congratulations and Wintertime?
A) No. SAM deals only with the hidden messages.
Q) Can SAM stop addons from printing text to the chat box?
A) No.
Q) Can SAM stop You are not in a raid from spamming me in battlegrounds?
A) Yes. SAM will block the outgoing message and tell you which addon is causing it.
Q) Can SAM stop You are not in a guild from spamming me too?
A) Yes. And SAM will tell you which addon or prefix is causing that message to appear.
Q) Can I block messages from a specific person?
A) Yes. Enter their name into the names list and their incoming and outgoing messages will be blocked.
Q) Can SAM block other's addons from spamming me?
A) No. But SAM can block your addons from receiving/processing such spam.
Q) Can other's addons spamming me cause me to disconnect?
A) No. Incoming communications will not cause you to DC. If a poorly written addon keeps replying to spam then that could cause flood disconnection.
Q) Should I block inbound messages for addons that I'm not running?
A) No. Only block inbound messages for addons you are running. Otherwise you're not blocking the message from reaching anything.
Q) Why is Add incoming prefixes disabled by default?
A) There's no benefit in blocking messages if you're not also running the addon that receives them. But if you want them in the list, you have the option.
Q) Why is IgnoreMore a optional dependency?
A) IgnoreMore blocks regular chat, but not addon communications. SAM will block addon comm from people you're ignoring using IgnoreMore.
Donations welcome. There's a donate button here.
Bitcoin address: 1ERfbhT8B45GHeGUjequYisC9Q2sufxv5q
upgrade ~~~plz!^^
1x FuBar_HonorFu-2.0.70186\HonorFu.lua:416: attempt to call global 'GetDifficultyColor' (a nil value)
StopAddonMessage-1.4.1beta\core.lua:277: in function <StopAddonMessage\core.lua:210>
(tail call): ?:
---
Good idea.
There is also the "you arent in a GUILD "message, which you might want to add as well to the list of addons being reported by wrong commchannels ;)
In this case i wouldnt need yaiap any more
Either way I'll check it out tonight.. so far I love the mod, though I cannot say whether or not it's making any noticeable difference in overall system resources. (I'd hope that blocking them from addons which I don't want to communicate would speed them up and cause less of a drain on CPU.. but there's really no way to measure speed during raids other than to notice less lag, disconnects etc.. hehe)
If a message is blocked from reaching a addon, the hope is you'll save CPU cycles by not processing the data, potentially increasing FPS.
Try the 1.2.5beta. It has a change to how incoming prefixes are added to the list that may fix the spamming problem. I don't turn on Add incoming prefixes so I didn't notice the problem till you brought it up.
Hey, I have another prefix that says its being added, but isn't being added to my prefix list. Guild Greet, see attached image. Also, as you can see, it adds about 12-15 prefixes (the same one it claims), and does this everytime this guildie logs on. I added him to the ignored list, but he didn't log on again after that, so I'm not sure if it worked. This was last night, with the 1.2.4 version.
By the way, if I need to do additional troubleshooting for this, just let me know, I've just been distracted recently and its all I can do to remember to post things here! (version 1.2.4)
good to know.
in normal situations only 1-3 are used but according to nevcairiel 4-9 are also reserved for internal use.
Thanks yoshimo. I hadn't ran into ace's multipart comm msgs so I didn't see it before. Looks like ascii 1,2,3 is used. 1=start,2=middle,3=end
edit: typo
I noticed that SAM might have the same problem as my small prefix hunter.
I often noticed it adds prefixes with ?? in it.
this is caused by acecomm3 which uses \001 - \009 as suffixes for multipartmessages.
those are asciicontrolcharacters and are printed as "??" in chat.
I wondered why people using prefix hunter reportet prefixes i already have, only with a "??" appended. Now i know that those were ace3 addons ;)
the character after GLDR is asciicontrolcharacter \001 , called StartOfHeading.
Maybe it was broadcasting over guild chat.