Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
All messages are in Trade or General unless otherwise noted. Will continue editing this post to add messages until your edit.
BadBoy r1122
<>
^ I'm assuming this is spam based on its inclusion of a QQ number.
Also, the Unicode fullwidth characters cause all subsequent characters on the same line to be invisible. The forum appears to be eating them, but that's a fullwidth left parenthesis between NM and MSV, a fullwidth right parenthesis between TOES and ,getting, and a fullwidth colon between QQ and the number. Everything in that entire Unicode block -- \239\188\129 through \239\191\174 -- causes this problem, at least in my client. I've added the entire range to the heavyList table my local copy of BadBoy, as I can't see that there's any legitimate use of these characters in WoW chat messages, but that may be outside the addon's scope for you.
Due to Blizzard's continued nerfing of the reporting system we now implement our own mini blacklist. Currently, we use the calendar date API to create a 1 day table that expires every day. This table prevents showing the "click to report" message for people you've already reported, it doesn't however prevent seeing chat from that person, that's up to the current filters.
As if it wasn't bad enough that they made the internal blacklist clear itself when you log to a different character in 5.0/5.1 it seems they've broke it further this patch. After reporting a certain amount of people the internal blacklist clears itself. The reporting functionality then breaks altogether and no longer adds the people you're reporting to the internal Blizzard blacklist.
Unfortunately Blizzard has been on a mission to make their spam blocking functionality worse and worse as time goes by, so this new system should help out not only with this new issue but also with character swapping. It's sad that the best version of the spam reporting system was the one the originally implemented in TBC.
I'm pretty sure the reporting system just sends everything into a black hole, and no Blizzard employee ever looks at it. Also, they seem to be severely understaffed in general; my last ticket took 7 days to get a response. :(
Also (last post is getting really long and I don't want this to get lost) since you're now keeping a manual blacklist, can you hook the regular chat-based reporting function and add the people I'm manually reporting to it? I doubt it helps for me to report the same player every 15 minutes, and I'd rather just not see their spam.
Also (last post is getting really long and I don't want this to get lost) since you're now keeping a manual blacklist, can you hook the regular chat-based reporting function and add the people I'm manually reporting to it? I doubt it helps for me to report the same player every 15 minutes, and I'd rather just not see their spam.
No. I'm not really interested in hooking and the function doesn't provide player GUID anyway.
You can stop reporting non-whisper guilds ads, my goal isn't to block every single one and I don't have the patience for it right now.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorThe 1 was part of the Skype ID, "QQ" is a very popular Chinese IM client.
<>
<>
BadBoy r1122
<>
^ I'm assuming this is spam based on its inclusion of a QQ number.
Also, the Unicode fullwidth characters cause all subsequent characters on the same line to be invisible. The forum appears to be eating them, but that's a fullwidth left parenthesis between NM and MSV, a fullwidth right parenthesis between TOES and ,getting, and a fullwidth colon between QQ and the number. Everything in that entire Unicode block -- \239\188\129 through \239\191\174 -- causes this problem, at least in my client. I've added the entire range to the heavyList table my local copy of BadBoy, as I can't see that there's any legitimate use of these characters in WoW chat messages, but that may be outside the addon's scope for you.
BadBoy_Guilded r178
<>
<>
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorIs the guild spam a whisper?
<>
BadBoy_Guilded r178 missed spam in Trade:
<>
BadBoy_Guilded r178 missed spam in whispers:
<>
Also, can you please fix BadBoy_Levels printing "BadBoy_Levels == 1" every time I show or hide the BadBoy options panel?
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorI can't remember my reason for this but I won't be removing it.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium<>
<>
BadBoy_Guilded v2.9, trade chat:
<>
BadBoy_Guilded v2.9, whisper:
<>
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorAs if it wasn't bad enough that they made the internal blacklist clear itself when you log to a different character in 5.0/5.1 it seems they've broke it further this patch. After reporting a certain amount of people the internal blacklist clears itself. The reporting functionality then breaks altogether and no longer adds the people you're reporting to the internal Blizzard blacklist.
Unfortunately Blizzard has been on a mission to make their spam blocking functionality worse and worse as time goes by, so this new system should help out not only with this new issue but also with character swapping. It's sad that the best version of the spam reporting system was the one the originally implemented in TBC.
Anyway...
BadBoy r1137
<>
BadBoy_Guilded r183
Spam in trade chat:
<>
Spam in whispers:
<>
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorNo. I'm not really interested in hooking and the function doesn't provide player GUID anyway.
You can stop reporting non-whisper guilds ads, my goal isn't to block every single one and I don't have the patience for it right now.
Fixed the rest.
<>
<>