Add into config a block of friendly command names, that are essentially a middle ground between internal keys and trigger phrases - These should be less verbose than trigger phrases (as they don't need to uniquely mark a message as invoking CadenceBot), but they should be configurable and should match the trigger phrases well enough that a user recognizes one for the other. Of course in default config these will be mostly the same as the internal keys:
play => play
stop => stop
help => help
helpTopic => help
search => search
request => request
library => library
nowplaying => now playing
But this provides a layer we shall use to abstract our userspace away from our implementation details.
Then expose this to detailed helptext similar to how we expose the trigger phrase - Perhaps something like %friendly play?
Add into config a block of friendly command names, that are essentially a middle ground between internal keys and trigger phrases - These should be less verbose than trigger phrases (as they don't need to uniquely mark a message as invoking CadenceBot), but they should be configurable and should match the trigger phrases well enough that a user recognizes one for the other. Of course in default config these will be mostly the same as the internal keys:
play => play stop => stop help => help helpTopic => help search => search request => request library => library nowplaying => now playing
But this provides a layer we shall use to abstract our userspace away from our implementation details.
Then expose this to detailed helptext similar to how we expose the trigger phrase - Perhaps something like
%friendly play?