You want Blizzard to remove chat parsing? Have fun with that request…
2 Likes
Seems like to remove an addon like this, addons would need to be forbidden from working with combat and chat stream i/o. Which I would have zero issues with.
1 Like
If it is not a big deal then you wouldn’t mind them removing it.
Non-sequitur. Removing the addon means breaking the Combat Log or breaking chat parsing API or both, and neither of these things should be broken. Spy Classic simply isn’t a big enough deal to warrant such changes.
2 Likes
So if it isn’t a big of a deal Blizzard can prohibt its use or make a way to disrupt the addon no problem.
1 Like
Assuming Blizzard can actually break this without breaking literally every single other addon that posts messages, talks to other addons (like DPS meters and Boss mods), reads chat, color codes chat, customizes personal only alerts and messages, etc… sure.
And by sure I mean LOL no because Blizzard isn’t going to break it because it’ll break 90% of all other addons that involve text and chat parsing.
The other option is breaking the Combat Log which won’t be happening either.
You understand that this add-on is literally just a combat log parser right? Like many of other add-ons the PvE inclined rely on?
How do you remove something like this without breaking everything else? It existed in Vanilla too, if not by the same name. So. You know. #nochanges
The best part of this is that by whining about it, you’ve just drawn attention to it in the most public way possible, and now it will get thousands of more downloads, and even more people will use it contrary to your intent.
This is AAA+++ premium Streisand effect in action boys and girls
7 Likes
Ragefist gets a cookie!
Since you like to point out fallacies yours this time is a Slippery Slope.
You are just pilling a lot of hypotetical catastrophic outcomes to defend your point which makes you look silly.
I’m pretty sure they can do stuff to prevent the apocalypse happening if they decide to do something to break the addon and you said it yourself:
“Assuming Blizzard can actually break this… sure.”
Then that’s the end of it, since it is not a big of a deal after all.
1 Like
Gonna blow your mind when i say this but… this addon has been a thing since WoTLK…
queue dramatic music
The plot thickens…
1 Like
The difference between your non-sequitur (a formal fallacy) and my alleged “Slippery Slope” (an informal fallacy) is that you have to prove the matter, you can’t just look at the form, hence informal. Falling face first off a 1,000ft drop onto cement is going to lead to your bones crushing and your death… these are a series of events that lead one to the next.
So let’s see if you proved your allegation shall we?
Ooo and it looks like you failed. You admit you’re not even sure Blizzard could somehow accomplish the feat, but you are still self-assured to know that no amount of breaking Spy Classic would lead to any other issues.
The thing is, addons work by accessing the API. To break an addon, Blizzard changes/restricts/breaks the API functions the addon relies upon. Since every addon relies upon multiple API functions, the goal then becomes break access to the API function(s) that create the unwanted behavior.
In the case of Spy Classic, as Ragefist already pointed out very succinctly, all the addon does is parse the Combat Log. To break this function, you’d have to either make chat log parsing a protected function, thereby breaking every single other addon that accesses chat, or make significant changes to the Combat Log itself, thereby breaking every single other addon that reads and relies upon that Combat Log data. The other function is Spy Classic communicating with other addon users, which was a function ADDED in Vanilla to give addons this specific functionality without needing to spam the visible chat logs to send information, so this too is unlikely to be broken.
So if you want this addon broken you either have to want chat addons killed, combat log addons killed, or addon to addon communication killed, or some combination. This isn’t happening unless Blizzard really wants the playerbase pissed off because they can’t customize chat, use RP mods, see damage meters, post logs, or have any sort of sync between addons.
You lose. Good day.
4 Likes
I know we are a small bunch, but Aion players used to do that all the time.
That sound like Carbonite did back in the day. I think? I know I had addon that did exactly same thing back in TBC. Gathered the flagged Horde and report them to everyone with addon.
2 Likes
You keep with your fallacies, they are the creators of the code, they know how to handle things I’m sure of it, on the other hand your argument is that they are so stupid and incompetent that they will not figure out a way to break the addon withouth destroying everything else, either that or your claim is that it is impossible to do it just because…
Either of those are incorrect and are also assumptions.
In the end since it is not a big of a deal if they can actually do this without bringing the WOWpocalipse then it is fine as you just said in your previous post.
I do always love this response when Blizzard themselves have explained how and why they break addons for the last 15 years…
Hahaha
Yeah but they have the means to do something if they believe some addon is breaking the game or doing stuff that disrupts the intended flow of the game or mechanics.
If they come and say: “It’s ok to use the addon” then as much as i hate it i will have to just accept it and use it, but if they think the addon is not ok im sure they will do something about it.
They may have to think really careful to see if they can do it without breaking anything else and if they do break something if it is worth breaking just to prevent the use of this addon, that is on them to decide and to consider, we will just have to accept their desicion.
Right now we are just being vocal about something we don’t like, just like with the layering problem, people complained and people defended it, in the end they decided to take action against it and we just have to accept it.
So the only purpose of posts like this is to bring it to the attention to Blizzard, they will decide and we will just have to accept their desicion, or maybe they won’t even say a thing about this and in their silence their answer would be implicit.
Yeah, its called restricting or altering the API, the thing addons rely upon to pull info directly from the game.
This is more or less implied given the rules and restrictions of the API. Things are good until they are not, not the reverse.
Kind of like how you’re NOT doing right now by demanding its removal despite it using common and acceptable API functions that have existed since Vanilla in largely unchanged states?
That’s a funny way to spell “whining”
Well you can stay mad just because i won you the prior argument, doesn’t matter to me, I just tried to be more neutral this time.
If I am against something I will voice my opinion on it no matter how much I hurt the feelings of the opposite “faction” or the other side of the argument.
But I am mature enough to accept a desicion from Blizzard if their resolution is against my personal opinion on the matter no matter how much I am against it, I will just have to use the stupid addon and move on.
Unlike you that you are still mad at me.
Hopefully at some point this forum will stop overreacting to non issues.
2 Likes
Explain why Spy breaks the game, because by your logic and others’ its been doing so for a very long time and Blizzard is clearly blind to it. Spy has been around since at least Wrath. I would know, I’ve been using it since then. Addons with similar functionality likely also existed in vanilla and TBC. Are you aware of how the addon functions? It does not scan for nearby players at all times, it only reads mouseovers and combat logs within proximity. Do you have a solution that doesn’t involve breaking the rest of the most popular addons or are you just mega butthurt because your stealth gank attempt failed on somebody who was ready with it installed?
2 Likes