File Details
SpamThrottle5.0.zip
- R
- Aug 29, 2012
- 5.96 KB
- 8.5K
- 5.0.4
- Retail
File Name
SpamThrottle.zip
Supported Versions
- 5.0.4
12/05/2009 - Initial Release
12/07/2009 - Update to handle a potential problem with the way that LUA handles comparisons with uninitialized table elements on different WoW clients, thus potentially creating an "always filter" condition on some clients.
12/08/2009 - Updated to game version 3.3.0
01/03/2010 - Patched a bug whereby the filter was firing for each chat window opening, thus every window other than General was getting marked as a duplicate. For some people's setup this caused a problem. Simple fix was to filter messages after they have been seen 7 times, which is the number of times this filter is called for each message. This may require a more elegant solution in the future.
01/07/2010 - Implemented the more elegant solution to resolve above problem, using an event handler. Added gapping capability to allow repeated messages to be shown at a user-specifiable frequency (called the gapping value). Default gap is 600 seconds between repeated messages. Added a variable updating code to automatically roll saved variables forward from previous versions.
02/03/2010 - Implemented the fuzzy match filter to catch very similar messages, usually as a result of trying to defeat SpamThrottle. Made this an option so that users can require an exact match. Also added the /y channel for filtering, since some players were trying to defeat SpamThrottle by using the /y channel in Dalaran.
16/10/2010 - Updated for patch 4.0.1. Note that this is a working version, but point updates may be required to fix little things here and there if any issues are uncovered.
16/10/2010 - Re-upload to fix file naming problem.
04/03/2011 - Updated the game version applicability (no changes needed)
04/26/2011 - Updated to game version 4.1.
04/30/2011 - Fixed a minor error in the TOC file on the version
11/30/2011 - Updated to game version 4.3
08/28/2012 - Updated to game client version 5.0.4
The /y filter has a minor interaction with Prat 3.0 with message gapping. It is not a significant issue and may be addressed in future releases.