Announcement problem when routed to 'say' or 'yell' #466

Open
  • View malyeen's Profile
    malyeen created this issue Feb 27, 2021

    If you're reporting a problem, please ALWAYS include the following information or I won't be able to help you!  (Suggestions or feature requests need not use this template)

    • Addon version (Example: r664-alpha)
    • Did you RESTART the game after updating the addon? (Make sure to exit and close fully the client, and not just reload your UI, to detect newly-added files)
    • Steps to reproduce the error or unwanted behaviour (If the addon won't load, make sure to enable script errors!)
    • Any other information you consider relevant or helpful in solving the problem (Screenshots, expected behaviour, things you already tried to fix the issue...)

     Thank you for understanding! It's not always easy to troubleshoot problems. Please don't make it more difficult by disregarding these suggestions.

    When I set announcement(example: Son of Galleon's Saddle: 1700 attempts) routed to certain channel(say, yell and general) I keep getting the message 'Interface action failed because of an AddOn'.

     

    I've been using Rarity since Legion and it was working properly until early BfA. It no longer works since then.

     

    Something to note:

    - I get this error message only when I'm at outdoor field of any expansion. It still works fine in every instances(dungeon and raid).

    - Only three channels(say, yell and general) suffer from this error message, other channels(guild chat, party, raid etc) have no problem.

    - Disabling every other addon except Rarity did not solve anything.

    - Rarity version: r704

    - taint log when I got this error message:

    2/28 09:16:22.309 An action was blocked because of taint from Rarity -
    2/28 09:16:22.309 SendChatMessage()
    2/28 09:16:22.309 Interface\AddOns\Rarity\Libs\LibSink-2.0\LibSink-2.0\LibSink-2.0.lua:446 func()
    2/28 09:16:22.309 Interface\AddOns\Rarity\Libs\LibSink-2.0\LibSink-2.0\LibSink-2.0.lua:519 pour()
    2/28 09:16:22.309 Interface\AddOns\Rarity\Libs\LibSink-2.0\LibSink-2.0\LibSink-2.0.lua:525 Pour()
    2/28 09:16:22.309 Interface\AddOns\Rarity\Core\GUI.lua:2559 OutputAttempts()
    2/28 09:16:22.309 Interface\AddOns\Rarity\Core.lua:730 CheckNpcInterest()
    2/28 09:16:22.309 Interface\AddOns\Rarity\Core\EventHandlers.lua:1533 ?()
    2/28 09:16:22.309 Interface\AddOns\Armory\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:119
    2/28 09:16:22.309 xpcall()
    2/28 09:16:22.309 Interface\AddOns\Armory\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:29 Dispatch()
    2/28 09:16:22.309 Interface\AddOns\Armory\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:64 Fire()
    2/28 09:16:22.309 Interface\AddOns\TomTom\libs\AceEvent-3.0\AceEvent-3.0.lua:120

  • View malyeen's Profile
    malyeen     edited description Feb 27, 2021
  • View Cakechart's Profile
    Cakechart posted a comment Mar 1, 2021

     

    There've been some API limitations put into place by Blizzard since this was first implemented. I'd wager that is the most likely cause, though I'd have to investigate to say for sure.

     

    Status: https://github.com/SacredDuckwhale/Rarity/issues/275

To post a comment, please login or register a new account.