Well the plugins were meant to act as group members without player intervention. They were given the ability to be "manual" in the sense that you would control the movement of the character, choose what to engage directly, and leave ability selection and use up to the plugin, with more complicated classes having some options to have a preference for one thing over another when abilities conflicted. It was honestly never intended to be a direct replacement for things like KA/MA where you choose what abilities to use, and under what conditions to use them, or to easily omit the usage of oddball abilities at a whim.
When someone request (or even demands in some cases) a toggle for an ability, it means the code must be adjusted to allow the toggle. Which sounds relatively easy. Make bool, give user option to flip it.
When in reality it's create bool, initialize bool, create INI option, make something that gets the INI option, make something that sets the INI option, make command parameter, add command parameter to the help output, make help output for the options of the bool, determine if we've already created enough button elements, if not alter the XML, add enums for the class specific toggle, create the checkbox, tell the checkbox what it's called, tell the checkbox what to do when toggled, tell the checkbox what the tooltip is, now that the toggle is in place, should we use something else in it's place, or does that defeat the purpose of the toggle. If it doesn't defeat the toggle, figure out what we should replace it with, determine where in the flow to add it, determine the conditions under which to use the new thing, and finally Add a TLO for the toggle. This in pretty much requires 5 separate files are edited to accommodate each toggle. Not to mention the time it takes to reflect on considering the changes, and any other work as mentioned in the "should I replace it with something else" thought process.
Which has to be done for every button we create. It's a fairly decent sized addition to the code in general to add a single toggle. Which is why we ask for justification for such things. It's not a completely trivial task to add a single button, and adding button on button on button for toggle on toggle on toggle gets quite redundant and takes away from development for all those other plugins people keep asking about.
Just pointing out that there comes a point where people want a toggle for every possible situation and it's going to end up that the entire plugin is one big toggle which detracts from the simplistic approach intended for the plugins. We saturate with too many options as Sic mentioned and people aren't going to have as easy a time getting setup and going because they are going to question if they should have things on, in what situations they would want to use one option over the other etc. A large portion of the users for the plugins just want to be able to load it, glance at a couple of things to consider and fullsend their group member into the jaws of death and expect the plugins to do it's job.
I want to stick to the "expect the plugins to do it's job" portion of things and not keep adding all the toggles. Because going down that road we'll end up with people also wanting conditions for every single option we add to the plugins for toggles. Which is pretty much how we ended up with TLO's so people could write macros that micro manage the plugins. Which, yall can thank Sic for that because I don't do any of the work on the TLO's at all. I'm not opposed to the idea I just don't want to put any effort into it as I feel it starts to get out of scope for the plugins.
This isn't meant to point the finger at any one user, or any group of users that might make a request for options. Just saying that we should keep in mind the original intent of the plugin and try to maintain that. There comes a point where one of the alternative resources might be a better fit for a user if they feel the need to decide each and every ability that's used.
