View Single Post
07/16/17, 09:10 AM   #29
jpdouble69
Join Date: May 2015
Posts: 13
An early summary

All authors that posted here in this thread are arguing pretty much the same way.
They say that it is their right to implement any function into their addons and hide them to the user who is installing the addon. They do not document these function(s) nor do they give the user any option in the settings - the user has to execute them in the client - that's all.

The authors that are posting here all have these kinds of invisible/hidden functions implemented.

They argue that they put in a lot of work into it and it it their addon(s). So they have the right to do whatever they want.
There is not a single author in this thread having doubts about the way these functions are handled and distributed nor that they might change it in the future.

You can call it coincidence, bias or whatever you want. The issue stays the same: The user has to execute this stuff not knowing about it. No declaration, no option, no control, no choice, nothing. That is the way these authors want it. It was not done that way by accident, it was meant to be exactly that way.


I hope more and more people will become aware. Then there is a good chance that users concerns and rights are not taken lightly anymore and changes are being made by the authors – not ZoS.
  Reply With Quote