Then they would just make the addon use the same layers as DBM and damage meters… They just use hidden chat channels to communicate…
Oh really? You obviously don’t know anything about coding and how APIs work… Luckily, I do. Here’s what’s needed to make a basic LFG addon:
Autoinvite
*This can be killed off, but would disrupt some “whitelisted” addons that use similar functionality. The alternative, if killed off, would be to just manually send the invites out with a click.
Alternative to autoinvite: Click to send invite
*Breaking this would require a straight ban on /invite XXXX from macros even, to where it could only be executed if manually typed in chat, which could be done I suppose.
Class/Level/Talents
*To break these, then you’d be breaking dozens upon dozens of other popular addons.
Basic attached keyword information for which zone
*Simple text, what will they do, ban certain words like DM or UBRS?
A method of parsing chat text
*Would kill off dozens and dozens of other addons. Could kill off a lot of weak auras that rely on text in chat as triggers, and or DBM if it has any scripting that looks for boss text.
A method of communicating using public or hidden channels
*Breaking it’s access to public channels, would obviously break dozens of other addons. Breaking it’s access to hidden channels would kill off portions of DBM and damage meters that need to communicate for synchronization purposes.
So tell me exactly how they are going to completely break this again addon again? Like I said earlier, with the example of one button dps macros, where they tried multiple times to break the API for them, yet it’s 2019 and they are still going strong… Why can’t they break them? Because to do so would mean modifying the API to the point that it would break a bunch of other things.