Well SE stated before 2.0 launched that an addon API would be made available. So it's coming, even if some people don't like it.
Some specific points:
A damage meter or combat parser is a tool. Like any other tool it can be misused. I would submit though that a person who's going to be a jerk about damage meters, is probably going to find a way to be a jerk without damage meters. So given that jerks are impossible to avoid entirely, I'd like the easy information. Also as I'm sure you're aware, this is a technology we already have, albeit in an unsanctioned form.DAMAGE METERS!!!!!
I, for one, don't enjoy memorizing long boss attack patterns. All a boss mod is in the entire world is an on-screen stopwatch.BOSS MODS!!!!!
Did encounters in WoW have to be designed around the assumption that people would have them? Sure. Did it make more complex and interesting encounters? Absolutely yes.
I'd rather SE's development time was spent on game systems and content. Not spent on letting me turn my hotbars into 3x4 squares (or 4x3, or 2x6...) or letting me re-skin the UI windows so they look like they came from the set of Star Trek the Next Generation.SE creating them
An addon API allows users to make their UI do what they want it to do. Oftentimes these adjustments would be in such tiny demand that spending dev time and resources on them would be a grievous misuse of their time and effort.
So the way this one works, if you were unaware, is that it checks to see when a particular target is loaded in by your client. So at best this lets you know if something spawned within 100 meters of your character. And actually the most recent addon API for WoW denies this information to the client. Now it only barks if you happen to mouse over a rare NPC.NPCScan
It doesn't really matter though, since FFXIV doesn't have rare NPC spawns outside of hunts (which are already tracked by third-party software), an addon like NPCScan would be pretty worthless.



Reply With Quote



