It is visible at the changelog, one should always read thatFluffyBird wrote: »I see no problem when an addon adds new ways of interaction that are limited to the users of that addon. I'm concerned, though, that such thing can be added silently. If an addon uses such intrusive (even if allowed) functionality it should have some kind of well visible warning. Just my opinion, ofc.
It was not added silently, he described it and the purpose.
Just because something is possible doesn't mean it's intended or technically allowed. ZOS have changed things in the past e.g. Miat's PVP Alerts alerting NBs in stealth using abilities on you.Again, its not an addon authors fault, what possibilities developer (ZOS) opens in their API. Its devs responsibility to block such things.
Again, its not an addon authors fault, what possibilities developer (ZOS) opens in their API. Its devs responsibility to block such things.
WolfStar07 wrote: »It is visible at the changelog, one should always read thatFluffyBird wrote: »I see no problem when an addon adds new ways of interaction that are limited to the users of that addon. I'm concerned, though, that such thing can be added silently. If an addon uses such intrusive (even if allowed) functionality it should have some kind of well visible warning. Just my opinion, ofc.
It was not added silently, he described it and the purpose.
I'm not sure, but I think the concern was if the author chose not to include it in the changelog, users would not have known. I've seen other authors write "I've done A, B, and a bunch of other things that I don't feel like writing out." It doesn't happen often, and it sometimes isn't just coding stuff the average user wouldn't understand anyway. However, an author could theoretically include intrusive behaviors that very few people would be aware of if they chose not to post it.