Advertisement

ChatThrottler

(5.1 KB) Download the Curse Client

Last Update: Nov. 4, 2007 (8 months ago)
Category: Chat & Communication
Tags: chat, limit, message, and spam
Project Manager: galmok
Current Version: ChatThrottler 0.12
(for World of Warcraft 2.2.3)
Downloads Today: 1
Downloads Total: 2,921
Favorites: 8
Comments: 23
  • About ChatThrottler
  •  

THIS ADDON IS OBSOLETE AS OF PATCH 2.3.

ChatThrottler hooks SendChatMessage and listens for the THROTTLED notice. As long as you don't get the THROTTLED notice, ChatThrottler simply passes on the messages to the original SendChatMessage function and you shouldn't notice any change.

If you do get the THROTTLED notice, you have hit the server message rate limit and the server has thrown away messages. ChatThrottler will, when the THROTTLED notice occurs, resend messages and at the same time queue incoming messages. It will send 1 message and wait for the server to echo it (or receive another THROTTLED notice). It will do this until the queue is empty, ater which ChatThrottler will again pass messages directly to the original SendChatMessage function.

ChatThrottler has this slash-command:

/chatthrottler unhook

Using it, will disable ChatThrottler and restore the original SendChatMessage. The setting is not save so ChatThrottler will be enabled upon next login again.

  • Downloads (5)
  •  
Advertisement

You need to login or register to post comments.

Benefits of Registration

  • Interact with hundreds of thousands of other gamers on an open social network.
  • Post your stories, news, images, videos, and other content to share.
  • Create a network with your fellow gamers or join an existing one.
  • Gain reputation for everything you do.
 
  • Nov. 15, 2007, 06:08PM (7 months, 3 weeks ago)

    Just an update:

    ChatThrottler is not necessary anymore. In fact, it can make your situation worse in that it throttles messages for all custom channels combined whereas the the client throttles messages per channel. The client does not throw away messages anymore.

    I can REALLY recommend removing it. I did and I wrote it. ;-)

  • Nov. 4, 2007, 11:38PM (8 months ago)

    Thanks for the work in any case, appreciated.

  • Nov. 4, 2007, 11:24AM (8 months ago)

    Starting from patch 2.3, it seems as ChatThrottler can be removed:

    "In 2.3 chat channels are rate limited on the client in the same way whispers are now.
    Each chat channel is limited separately, at a rate of 10 messages in 10 seconds. This means that you can send one message every second without ever seeing delays, or a burst of 10 messages every 10 seconds without seeing delays. Messages that exceed this rate are not dropped, but simply delayed in order until they can be sent.

    This does not affect SendAddonMessage() or party/raid/guild chat."

    http://forums.worldofwarcraft.com/thread.html?topicId=879058320&sid=1&pageNo=14#262

    Seeing as messages wont be lost and each channel (when SendChatMessage is used) will be throttled independently, the need for ChatThrottler will stop (from patch 2.3).

    Enjoy. :-)

  • Nov. 2, 2007, 01:11AM (8 months, 1 week ago)

    Just updated tonight, so I'll let you know if I run into the same situation again. Thanks for the work.

  • Oct. 31, 2007, 07:22PM (8 months, 1 week ago)

    Hmm we need to throw away messages if the queue for a particular channel becomes too long. A long queue for a channel will delay all messages. GEM 2.26 (a newer is available that may solve the problem) caused my queue to contain hundreds of messages in a short time. This will eventually eat all your memory and cause all sorts of side effects.

    I'd say if the queue length for a channel is over 30, then stop accepting any more messages for that channel (throw them away).

    But I am willing to listen for suggestions here.

  • Oct. 31, 2007, 05:22PM (8 months, 1 week ago)

    @scrumbus: I have been able to replicate your situation and know why it happens.

    ChatThrottler relies on messages being sent using SentChatMessage also get acknowledged by the server (either by the client receiving the message back or due to a throttled notice).

    There are situations it seems where a sent message ends up not getting a server acknowledgment. On of such situations are leaving a channel before a queued message has been sent. This make the internal state wait forever for the sent message.

    I'll add a timeout that makes ChatThrottler throw away such messages.

  • Oct. 31, 2007, 04:44PM (8 months, 1 week ago)

    v0.10: Forgot to hide the throttled event in v0.09. Fixed. (shouldn't occur much anyway).

  • Oct. 31, 2007, 04:36PM (8 months, 1 week ago)

    v0.09 uploaded:

    Changes since v0.07:

    Removed the Guild and Officer channels from the throttle monitor list (they are not rate limited anymore).

    Added a 13 messages/10 second send limit. Due to latencies, this is effectively a bit higher.

    If anyone managed to download 0.08 (was up for 1-2 minutes), then PLEASE do NOT use it. It will cause message corruption (adding a time value to each messages sent).

  • Oct. 31, 2007, 03:35PM (8 months, 1 week ago)

    @scrumbus: Your situation is apparently unique and I guess you must have had another addon interfering with ChatThrottler somehow. Maybe you had a run-away addon that pushed a lot of messages through SendChatMessage which could explain your situation. If that was the situation, then I either you must accept to lose messages or accept a delay in chat messages.

    But yes, starting today, Blizzard have taken the spam limitation of the guild and officer channels. I will release a new version so these channels will not be throttled anymore. This should prevent your situation from occurring again.

  • Oct. 31, 2007, 02:55PM (8 months, 1 week ago)

    I'm taking it to mean you'll no longer throttle the guild and general channels? That may resolve the problem I had last night where suddenly I was unable to chat to the guild channel or the general zone channel (/1). I waited for a good 10 minutes to see if my messages would come through and they didn't. It wasn't until I unhooked that I was able to talk again.

  • Oct. 30, 2007, 11:15PM (8 months, 1 week ago)

    According to this new information (blue posts), I will redo ChatThrottler soon to make it work close to these announced specifications:

    The throttling is set to15 messages in 10 seconds for all channels.

    Q u o t e:
    - does this affect raid?
    - does this affect guild/officer chat?
    - does this affect hidden, built-in addon communication channels?
    - does this affect private channels with fewer than 25 people?
    - does this affect whispers?

    It's not supposed to affect any of those. It was incorrectly doing so until today.

  • Oct. 30, 2007, 12:27PM (8 months, 1 week ago)

    @killerteddy78: I have tested that situation (spamming /8 (a test channel) and /g as well in the same macro without ChatThrottler installed. Result was that only the first message was sent.

    Try yourself with this macro (without ChatThrottler and create a channel 8 for testing purpose):

    /8 test1
    /g test2
    /8 test3
    /g test4

    You will find that only test1 is accepted by the server. The rest is lost.

    This means that once the THROTTLED notice is received, you are forced to throttle messages in these channels:

    /g
    /o
    /1-9

    ChatThrottler does exactly that. If we didn't throttle /g, you would lose messages either in /g, /o or /1-9, regardless of which message triggered the THROTTLED notice.

  • Oct. 30, 2007, 10:51AM (8 months, 1 week ago)

    With version 0.07 and GroupCalendar there were no error messages anymore, so synchronisations seems to work again now.
    But when throttling gets effective, alle messages seem to be throttled, also those in guildchannel arrived more than a few seconds late.
    Is it possible to have a parameter to make ChatThrottler active only on one channel (the one my guild uses for the calendar, would be it)? That would be great.

  • Oct. 29, 2007, 01:24PM (8 months, 1 week ago)

    Seems GEM is working now, need some more testing with rest of the Raidforce though.

  • Oct. 29, 2007, 10:56AM (8 months, 1 week ago)

    There is an AFK problem with ChatThrottler installed. The problem is with the autoClearAFK flag set (Interface option) and you send message that cause the THROTTLED event to fire. This can occasionally pull you out of afk. I have an idea for a solution but it is basically a compromise. I don't think it is possibly to fully solve this issue due to timing problems.

    And I will have to warn you about another problem that shows up rarely:

    When hiting the throttle limit, this macro (/8 being my test channel):

    /8 test1
    /8 test2
    /8 test3
    /8 test4
    /8 test5

    can rarely result in this being sent:

    /8 test1
    /8 test2
    /8 test3
    /8 test3
    /8 test5

    It is very difficult for me to reproduce (both good and bad: good = happens rarely, bad=difficult to provoke to be sure it is fixed) but it can only happens when you hit the throttle limit.

    Usually, ChatThrottler is much better than the alternative, though. :-)

  • Oct. 29, 2007, 08:46AM (8 months, 1 week ago)

    mouserecoil> Short answer : install ChatThrottler, and GroupCalendar should work again. Nothing more.
    If you test, can you confirm (or not) that GroupCalendar works again.

  • Oct. 29, 2007, 01:50PM (8 months, 1 week ago)

    have tested quickly with one person, creating a new event and having them request info and sending it back. appeared to work correctly, using latest groupcalendar. will test more thoroughly with rest of guild tomorrow. Thanks guys for your awesome plugin/fix :D

  • Oct. 29, 2007, 06:09AM (8 months, 1 week ago)

    hi, I have a question about this plugin. I noticed you guys have been talking about using this in conjunction with GuildEventManager to bypass blizzard's recent chat filtering change. A plugin similar to GEM, GroupCalendar, is currently broken as a result of the change. Could ChatThrottler be used in conjunction with GroupCalendar to avoid the chat limitation?

    If this is possible, how would we go about making these plugins work together to do this (assuming I don't just have to install ChatThrottler?

  • Oct. 29, 2007, 12:16AM (8 months, 1 week ago)

    Wonderful, working now. Will test tomorrow if rest of the GEM data is sent right also then. (Have to get some more online to test it!)

  • Oct. 28, 2007, 05:00PM (8 months, 1 week ago)

    I have just tested 0.05 with GEM and a multiline macro sending text to the GEM channel works fine now:

    This means, a macro like this (/SC being the GEM channel) will send all lines:

    /SC This macro should post 3 lines of wah if working
    /SC 1. Line: Wah
    /SC 2. Line: Wah Wah
    /SC 3. Line: Wah Wah Wah

 
  • Similar Addons
  •  
  1. 1,578 Carbonite Quest Chat & Communication, PvP, ...
  2. 685 WIM (WoW Instant ... Chat & Communication
  3. 599 Prat 2.0 Chat & Communication
  4. 521 ChatMOD Chat & Communication and Audio
  5. 194 TriviaBot Chat & Communication
Advertisement