Custom commands cleanup

[TheOriginalSoni]

All issues and bugs with customcommands

[TheOriginalSoni]

~addccommand should not give entire embed, but split it into "Print the embed reply" and the actual embed itself.

~addccommand should probably limit size to 994 when adding commands

[TheOriginalSoni]

~addccommand and ~editccommand can be merged (See ~tether for how)

Moving here from #64

[TheOriginalSoni]

Random idea. What if custom commands were allowed to have parameters, like $1

So

~addcustomcommand issues "https://github.com/kevslinger/bot-be-named/issues/$1" on setup

~issues 29 returns https://github.com/kevslinger/bot-be-named/issues/29

Will this be easy or feasible

Splitting from #29

[TheOriginalSoni]

Feature request : Allowing global custom commands

Custom commands that can be used from any server, and not just the server storing it. Would be limited to only bot owners, but would be very handy.

Probably simplest done by doing an optional parameter

~addcustomcommand commandname global "Command reply"

[petecao]

~addccommand and ~editccommand can be merged (See ~tether for how)

Moving here from #64

Do you think a "this custom command already exists, do you want to overwrite" confirmation would work for this? I would want to keep ~editcommand and get rid of ~addcommand in this case

[TheOriginalSoni]

Feature request : Allowing global custom commands

Custom commands that can be used from any server, and not just the server storing it. Would be limited to only bot owners, but would be very handy.

Probably simplest done by doing an optional parameter

~addcustomcommand commandname global "Command reply"

Partially started in 34e53e3.

@kevslinger I don't understand what database[....] vs Session(...) things do, so stalled until I understand cache/how to implement it

[TheOriginalSoni]

~ Custom reponses, where instead of custom command, you're adding 10 possible answers

[TheOriginalSoni]

• Finish global custom commands transformation (See TODO in code)