v1.39
- Modified Patterns and Scrubs.

Verified that it blocks all the spammers in Daggerfall right now.

Not sure about other zones, PM me screenshots with normalized text and I'll get it fixed.

The latest release re-writes almost all of the patterns.

The list is getting a bit long so you will probably want to reset patterns to make sure you've eliminated anything old:

1. Navigate to Settings=>X4D AntiSpam
2. Click on "Spam Patterns" Edit Box.
3. Press Ctrl-A to select everything, then press Ctrl-X to Cut and Copy to the clipboard. This should consequently clear the list.
4. Paste your current patterns into notepad, unless you just don't care about them.
5. Click "[X] Defaults" Button to re-initialize patterns to latest.

If you had any custom patterns, you may want to test with just the defaults first.

Enjoy!

TLDR? PM Me a screenshot containing the normalized output and I can fix it even if I don't have access to the game.

This is the ultimate goal, as of yet I'm still seeing what these spammers come up with before trying to 'solidify' the normalization (and consequently, pattern generation.) As it stands, currently, I construct all patterns similarly. The only reason I haven't written a "how to" for creating patterns is that I don't know that I won't have to radically rethink normalization (I've had to do so twice already, for the better.)

99% of the time, PM me a screenshot that also shows the normalized output, I'll construct a pattern as soon as I see it. Today was an odd day, I had a double-shift at work and passed out after. Normally I would already have patterns in for these guys by now.

To "DIY":

Look at the normalized text and find the longest segment of "unique" text there, usually something real ugly like "wmvmwmvmlv.sdsv.ps.omvm" and just put that directly into the pattern list (at the very bottom, on a fresh line, I tell people to put two new lines at the bottom before inputting their patterns to reduce chance of errors.) This will, at least, serve as a temporary block until I can add a formal pattern. This "temporary pattern" will often come from the first half of the "normalized text", in more complex spam messages you will likely have to pull the "temp pattern" from the middle or end of the normalized text.

I do plan on implementing a heuristic analysis of chat looking for "would be" spam patterns, if you look at the list of existing patterns you an already see the same patterns across all spammers (harhar no pun intended.)

GL!

Best way to fix a problem like this is:

1. Navigate to Settings=>X4D AntiSpam
2. Click in the "Spam Patterns" Edit Box
3. Press Ctrl+A, then Delete. This should Clear all of the patterns.
4. Click "[X] DEFAULTS" Button, this should re-initialize patterns.

There is a mal-formed pattern is the problem. Possible has a line-break that shouldn't be present. Easiest fix is to do the above.

Alternatively, copy them to the clipboard and open in Notepad (or your favorite text editor, but not Word) and edit them there.

pChat would have to defer registration of ZO_ChatSystem event handler(s) for a second or two, and then use LibStub() to access LibAntiSpam as a library, then would need to implement a call to LibAntiSpam's Check() method, passing in the raw chat 'text' and 'fromName', receiving back a response indicating whether the check was considered spamming and/or flooding. It would then need to react accordingly (dropping the message, for example.)

The problem is that LibAntiSpam is initializing *after* pChat. But, conversely, if pChat were to initialize after LibAntiSpam then LibAntiSpam wouldn't be able to block anything.

Alternatively, you might find X4D Chat useful if all you're looking for is Timestamps, which is what you see in the default screenshot for the Add-On:

Thanks for the report, updated. Removing OP to minimize advertising.

No this sounds strange.

This might happen if you've entered more than 4K of patterns, which if you have I'm amazed, but then I don't believe you would be able to add empty new lines with Enter key either.

I would suspect another Add-On, unfortunately, for lack of a known reason for this to happen.