My thoughts are going towards having more subcommands ($group join ) to make it more sensible. $myprefs, as an example I feel is very awkward and certainly isn't intuitive.
Following that, at the moment, toggling the Offline Ping preference is a bit cumbersome, and that's for just the one property. If there are going to be more properties added down the road, I feel like there needs to be a nicer system in place. Is it more sensible to have individual commands for each preference ($group [pref-name] [setting]) or should we look into using something a little more reactive.
It is possible to wait for responses, so perhaps having a more interactive type system, where the bot explicitly asks for certain settings, possibly using the reaction system as a selector.
Any thoughts or input on the matter would be greatly appreciated.
I need some better command names/structure.
My thoughts are going towards having more subcommands ($group join) to make it more sensible. $myprefs, as an example I feel is very awkward and certainly isn't intuitive.
Following that, at the moment, toggling the Offline Ping preference is a bit cumbersome, and that's for just the one property. If there are going to be more properties added down the road, I feel like there needs to be a nicer system in place. Is it more sensible to have individual commands for each preference ($group [pref-name] [setting]) or should we look into using something a little more reactive.
It is possible to wait for responses, so perhaps having a more interactive type system, where the bot explicitly asks for certain settings, possibly using the reaction system as a selector.
Any thoughts or input on the matter would be greatly appreciated.