Ability to enable/disable features per server

[abrasmag3]

All features should probably start disabled?

Bonus points: Init the guild SQL automagically when you enable your first feature

[Coca162]

Does this mean that features that require lower permissions then MANAGE_GUILD would require an individual with MANAGE_GUILD to be enabled? And if so would we need to enable/disable features for ones which already require MANAGE_GUILD?

[abrasmag3]

1. Probably? You likely don't want a moderator to enable/disable features without an admin's permission
2. Probably not, although what features would fall into this category?

[Coca162]

For the 1st this would mean we would have to do checks on whether the permissions exist, though this can be done conveniently through poise checks, as long as they are able to be defined outside a module, poise examples do not clarify much.

The 2nd concern was more forward-looking and currently doesn't need to be thought about.