Chalsean
commented
4 months ago This will be difficult to work around, SendAddonMessage is the backbone for communications and XFaction is chatty in large confederates. Possible things to target:
- [ ] Merge as many messages as you can
- [ ] Track if someone has logged in since last heartbeat, if not, no need to send data
- [ ] Track message ids as soon as packet is seen, not after message is stitched together
- [ ] Randomize a short pause on forwarding messages to recognize duplications
- [ ] Develop a deterministic algorithm to generate multiple unique message prefixes to get around the constraint
Addon messaging changes The C_ChatInfo.SendAddonMessage API and its logged variant now aggressively throttle traffic on all chat types, including whispers. The details of this restriction appear to match previously implemented changes for party and raid communications.
Each registered prefix is given an allowance of 10 addon messages that can be sent. Each message sent on a prefix reduces this allowance by 1. If the allowance reaches zero, further attempts to send messages on the same prefix will fail, returning Enum.SendAddonMessageResult.AddonMessageThrottle to the caller. Each prefix regains its allowance at a rate of 1 message per second, up to the original maximum of 10 messages. This restriction does not apply to whispers outside of instanced content.