It doesn’t do that. It reads the combat log.
2 Likes
Your Combat Log is the “radar”, the addon just scans it. You can watch your Combat Log and see the same things Spy tells you.
You get a radar by default. It is called the Combat Log.
Wrong there is no combat in bootybay! Its scanning the area for players another way!
Again its not scanning combat log, there is no combat in Bootybay bro!
That’s exactly what it scans and the Combat Log doesn’t require you to be in combat…
Exactly, it needs to be banned. I could see maybe, maybe scanning combat logs of people in combat near you.
But reading combat logs of people out of combat thats to much! This addon is bad!
Uhhh…
No. The Combat Log tracks any actions by yourself, surrounding NPCs, and surrounding players. Buff yourself and it’ll show on your Combat Log and anyone within range of you. That’s default UI.
2 Likes
Some don’t get how the game works…even after 15 years. xD
2 Likes
Its a bad addon, and should not be allowed in game.
1 Like
It literally functions by using the ‘onEvent’ API call in the LUA code to retrieve information from the event API’s, specifically “COMBAT_LOG_EVENT_UNFILTERED”.
This API can be called at any time and it does not matter that you are in Booty Bay or not, it is always running and it contains a lot more data than just ‘combat’, which is why it will track people there.
In order to ban this addon you would need to disable LUA from being able to call events from the API “COMBAT_LOG_EVENT_UNFILTERED”. This will never happen because it breaks so many addons it would be chaos, imagine a good portion of all existing addons now broken.
It’s not going away, tough luck.
5 Likes
… lol
Do you know anything about the combat log?
1 Like
Sorry, no changes!
No, you weren’t in the previous post. But at least in this post you do.
It does, as this addon gives players information they wouldn’t have read before/highlights it to make it even easier [for those who would have/attempted to actually read it], which manifests as them playing differently in a given situation. Particularly in PVP scenarios, and especially with stealth this benefits players facing off against stealthers, much to the detriment of those utilizing stealth. Furthermore, it also gives information about the level and class and can automatically alert others. This undeniably changes how/how effectively PVP is approached in the game.
This is a non argument.
I know that this existed during Vanilla. However, it was not nearly as prevalent, hence the shift. It shouldn’t have been allowed then either though, as it undermines how WPVP was designed.
So, “no.”
Yet, as pointed out, this addon has created a change. What to do when there are multiple contradictory changes on the table? Leaving it changes the game. Removing it/addons entirely changes the game. This brings us to the crossroads of that concept again, subjectivity in, “what should be prioritized?”
You say keep it [and make the experience different than it actually was in general].
I say toss it [changing the game, but making it closer to the original experience overall].
Though, my reasoning isn’t necessarily tied to strict, blind adherence to the original, so that #nochanges bit doesn’t really have all that much weight with me to begin with. I maintain that this add on is bad for the game, as it automates something that I feel should have to be done manually by the player.
Maintaining the same API access we’ve had for 15yrs. The end.
The player still has to read, process, and react to the signals presented on their own, no different than reacting to (or ignoring) the sound of a stealth NPC/player occurring, or noticing a read-out on the Combat Log. Simply put, this isn’t automation, anymore than Scrolling Combat Text, Prat, or any host of visual timers for buffs/debuffs.
The status quo is against your position, and your position is that of purely aesthetic preference. Status quo wins.
Eh, I wouldn’t say 100% maintaining. The original API allowed for addons to check target health and cast the appropriate ranked heal. …bit too much ez-mode (like healing is Retail).
I do not see that. I see threads like this pop up all the time, and the same people defending the add on. I think its a small minority of cheaters that want to keep it, because they cannot play without crutches.
2 Likes
Well that was automation which is why it was cut off before Vanilla even came close to finishing. I’m fine with the 1.12 API access.
It is largely the same folks bleating on about “cheating” and “crutches” without substantiation, but you miss my point entirely.
Blizzard sets the status quo, not the players. The status quo provides support for and active knowledge of addons like Spy, DBM, Prat, etc. So if you’re going to convince Blizzard to alter the status quo, you’ll need more than “I don’t like this.” You could start by more clearly defining why you want to call reading a combat log as “cheating” but eh… I’m not holding my breath.
At the cost of ruining aspects of the game? No.
Perceiving this and processing this information has been made much, much easier. Stealthing is supposed to be subtle and the player isn’t supposed to know all of this information without having spotted them themselves.
So, your defense is literally a logical fallacy. Okay.
I don’t think it’s so much defending as trying to correct misinformation.
Also…are you in favor of banning DBM and BigWigs? What about things like Vuhdo, Decursive, and Grid?
As has been explained, no, it has not.
The add-on existed in vanilla. The add-on does not actually change how the game is played, as people were already capable of detecting stealth via their combat log, and banning it would be the change.