[config] change disable to toggle

[flaree]

closes #415

[ltzmax]

Maybe we can remove it from being optional to use enabled: ? Right now based on the wording, it says to redo the command to re enable, which might be confusing for our user base?

[userandaname]

Maybe we can remove it from being optional to use enabled: ? Right now based on the wording, it says to redo the command to re enable, which might be confusing for our user base?

i'm not the one to really say here, but i'd say that it'd make more sense to make it optional in the case that users are already used to /config enable, and so bot-hosters forking BallsDex may want to change that option based on their user-base?

[laggron42]

i'm not the one to really say here, but i'd say that it'd make more sense to make it optional in the case that users are already used to /config enable, and so bot-hosters forking BallsDex may want to change that option based on their user-base?

It's going to be super hard to have two conditional blocks of code, if self hosters don't like the way we're going they're free to fork/stop updating, we focus on our own user base. I try to consider the selfhosters when adding or changing stuff, but having this sort of switch is really overcomplicated for nothing.