BigWigs Bossmods

611 - Disable "this zone requires the ____ plugin" warnings

I'd love to see an option to permanently disable the "Please note that this zone requires the _____ plugin for timers to be displayed." messages. I'm fully aware that I need LittleWigs if I want to see timers for Mogu'shan Palace, etc. and seeing this message for every dungeon I run on every character every day is a little much. Similarly, I run all the classic, TBC, and sometimes Wrath instances every week on multiple characters for achievements or transmog, and don't need to be warned over and over that I'm not going to get timers for Ragnaros 1.0 if I don't install BigWigs_Classic.

Since BigWigs original mission was to reduce boss mod spam, I think an option to reduce this particular spam would fit right in. If not, can you at least make the list of which zones I was warned about save between sessions on a per-account basis?

Thanks!

User When Change
funkydude Jul 31, 2013 at 13:10 UTC
funkydude May 29, 2013 at 00:53 UTC
funkydude May 28, 2013 at 11:31 UTC
Phanx May 28, 2013 at 10:41 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of Phanx Phanx Aug 06, 2013 at 02:35 UTC - 0 likes

    Also, you're entirely correct that my code was "poorly researched" -- I threw it together for myself in about 30 seconds, and published it in case anyone else happened to find it useful, too. My hope was that it would encourage other people to drop by this ticket and express their interest in an option to hide the messages, who wouldn't have otherwise gone out of their way to post about it. It was no way intended as an insult toward you, or an attack on your addon, which has been an invaluable part of my many years of WoW raiding.

  • Avatar of Phanx Phanx Aug 06, 2013 at 01:30 UTC - 0 likes

    The desirability of my addon -- or any addon -- is purely subjective. I'm sure you personally use plenty of addons I would deem pointless or counterproductive. That doesn't mean I'm going to add code into my addons to break those addons, or try to prevent everyone else from using them.

    As a matter of basic courtesy, if I find that an addon I'm using is having an undesirable effect on another addon or the default UI, I don't just add code into one of my addons to break it. I contact its author to make them aware of the problem, and give them a chance to fix it, and then -- if they can't or won't fix it -- I uninstall the addon. If you don't like what my addon does, you don't have to use it.

    What my plugin does is no different than what hundreds of other addons do in modifying the behavior of other addons, or of the default UI. For example, I personally find it undesirable to have mana bars added to Grid -- but I recognize that people choose to use the GridManaBars plugin to hook into Grid's internal functions and add mana bars because they want mana bars. I don't add code in Grid to break GridManaBars, and I don't make baseless accusations of copyright infringement to try to have it removed from the Internet or force Julith to remove the word "Grid" from its name and description. I just don't install it on my computer.

    And if I started getting bug reports from GridManaBars users about problems caused by GridManaBars, guess what -- I still wouldn't add code to Grid to break GridManaBars, and I still wouldn't attack its author, publicly or privately. If I became aware of an ongoing incompatibility between GridManaBars and Grid, yes, I would send its author a PM -- or post a bug report on its download page -- to make sure they were aware of the problem.

    I'm sorry if you feel that blocking a few chat messages from your addon is some kind of personal attack against you, but it really isn't.

  • Avatar of funkydude funkydude Aug 06, 2013 at 00:23 UTC - 0 likes
    Quote from Phanx:

    No, you didn't. You only mentioned a problem at all after I came here and asked why you deliberately broke my plugin. Would it really have killed you to send me a PM saying "hey, what you're doing is messing up the options if people use LittleWigs and your plugin at the same time, can you please fix this" ?

    What. I should have to send you a PM to point out an obvious poorly researched change by you? You think I exposed the table just for the sake of it?

    Quote from Phanx:

    No, you didn't. You only mentioned a problem at all after I came here and asked why you deliberately broke my plugin. Would it really have killed you to send me a PM saying "hey, what you're doing is messing up the options if people use LittleWigs and your plugin at the same time, can you please fix this" ?

    Your entire addon is undesirable, especially since you didn't ask permission to release an addon changing my code, and you think you're justified a PM notification?

    Quote from Phanx:

    I really don't understand why you're blowing up about this, especially when I already updated my plugin to resolve the issue you alluded to.

    Not from what I see, you're still nilling entries in MY table.

  • Avatar of Phanx Phanx Aug 06, 2013 at 00:12 UTC - 0 likes

    I did tell you about it in this ticket...

    No, you didn't. You only mentioned a problem at all after I came here and asked why you deliberately broke my plugin. Would it really have killed you to send me a PM saying "hey, what you're doing is messing up the options if people use LittleWigs and your plugin at the same time, can you please fix this" ?

    It's not like I released the plugin maliciously for the express purpose of causing the options for (eg.) Lucifron to show up in the Pandaria category -- which is obviously undesirable, but hardly catastrophic. The fact that my plugin was causing that issue was an unintended side effect, but rather than just contacting me about the problem and asking me to fix it, your chose to escalate immediately to outright aggression and hostile actions.

    I really don't understand why you're blowing up about this, especially when I already updated my plugin to resolve the issue you alluded to. If there is some other issue still outstanding, I'm not aware of it, so please just tell me what it is so I can fix it.

  • Avatar of funkydude funkydude Aug 05, 2013 at 05:06 UTC - 0 likes
    Quote from Phanx:

    Why would I respond to the ticket when your last response said you would think about it?

    That's clearly not what I last said.

    Quote from Phanx:

    "I didn't suddenly complain about the issue because you added a RW print.

    So you did acknowledge what I last said then...

    Quote from Phanx:

    I can see where wiping the zonesList table could conceivably "break" anything is not actually applicable to users of my plugin

    Clearly people using your plugin have 0 chance of even having 1 external addon installed, right? ...

    Quote from Phanx:

    In the future, if you think my addon is causing a problem, please just be an adult and tell me about the problem so I can fix it, instead of passive-aggressively breaking an addon people are choosing to use.

    I did tell you about it in this ticket...

    So where do we go from here, I can make the table local, grab unhooked copies of AddMessage, force-disable the name of your addon, etc, etc. You cannot win this but you seem to want to push it.

    Last edited Aug 06, 2013 by funkydude: quotes
  • Avatar of Phanx Phanx Aug 05, 2013 at 00:15 UTC - 0 likes

    Why would I respond to the ticket when your last response said you would think about it? What else is there for me to say at that point? I didn't suddenly complain about the issue because you added a RW print. I complained about the issue when I started using BigWigs again for the first time since Wrath, and my chat frame was getting spammed every time I entered an old raid or LFD 5-man.

    As for breaking the configuration layout, the only place I can see where wiping the zonesList table could conceivably "break" anything is not actually applicable to users of my plugin, since they are using my plugin instead of using LittleWigs, BigWigs_Classic, etc. -- so options panels for those 5-mans and ancient raid zones listed in zonesList will never be created in the first place.

    However, since you clearly think it's The End Of The World for the ~100 people who are using my plugin, I've updated it to only remove the zones whose plugins aren't currently enabled. In the future, if you think my addon is causing a problem, please just be an adult and tell me about the problem so I can fix it, instead of passive-aggressively breaking an addon people are choosing to use.

    Last edited Aug 05, 2013 by Phanx
  • Avatar of funkydude funkydude Aug 04, 2013 at 10:46 UTC - 0 likes

    You never responded to the ticket, I considered it fixed since the chat message has been in for months without complaint until I changed it to print in RW. So yes I broke it and will continue to do so, especially since your plugin will break the configuration layout.

    If you keep pushing this I will be forced to make 2 tables and stop exposing it to you.

    Last edited Aug 04, 2013 by funkydude
  • Avatar of Phanx Phanx Aug 04, 2013 at 02:11 UTC - 0 likes

    In r11013 you renamed the "zoneList" table to "zonesList". If you made this change to break the plugin I released to block the warning spam, please consider that people choose to use my plugin because they don't want to see those messages. Nobody is forcing them to use my plugin -- why go out of your way to force them to be spammed with warnings they clearly don't want?

    If you weren't aware of my plugin, and just changed the table name on a whim, please avoid changing it again in the future unless the existing name is actually causing some problem.

    Or, you know, just add the option in BigWigs to not spam users with "warnings" about missing boss mods for AQ20. ;)

    Last edited Aug 04, 2013 by Phanx
  • Avatar of funkydude funkydude Jul 11, 2013 at 19:37 UTC - 0 likes

    I've removed the RW message now so it's just a chat print again like before.

  • Avatar of tonyleila tonyleila Jul 09, 2013 at 23:57 UTC - 0 likes

    I love BigWigs but I think we know had this feature long enoth that everyone who ever used bigwigs now knows about its small brother. Please make an option to disable it or at least disable the raid warning part of it - a note at the download page woud have been enoth.

    What happened too cool futures like blocking boss videos like back in cata?

Facts

Last updated
Jul 31, 2013
Reported
May 28, 2013
Status
Fixed - Developer made requested changes. QA should verify.
Type
Enhancement - A change which is intended to better the project in some way
Priority
Medium - Normal priority.
Votes
1

Reported by

Possible assignees