Make your own slash commands for your server, like a rules command that posts your
rules or an ip command that answers with your game server's address. (Configure → Custom commands.)
Each command has a name (lowercase letters, numbers, - and _, up to 32 characters)
and a short description members see in Discord's command list. It answers with your
text, a rich embed, or both. Tick Reply privately and only the member who asked
sees the answer. Limit who can use it to some roles, and where it answers to some
channels: leave either blank for every member and every channel. A command can also
hold subcommands, so one name covers several answers, such as team join and
team leave. Saving writes the command down, and it reaches Discord when you apply.
Make it do something. A command can run up to five steps before it answers:
Give a role, Take a role or Toggle a role on the member who ran it, or
Pick at random from a list of texts, which the answer shows as {pick}. At most
three steps change roles. Packet checks every step before it runs any, so a command
whose role is gone or sits above Packet's own role is refused rather than half done.
Steps never touch coins or XP.
Ask the member something. Add up to five options for the member to fill in: text,
a whole number, a member, a role, a channel, or a pick from a list. The answer shows in
the reply where you write {option. and the option's name, then }. Add up to ten
buttons under the reply: a link, or a button Packet answers when it is pressed, with
its own steps and a private reply.
Waits and triggers. Set how long each member waits between uses, or how long the
whole server waits, up to an hour. Commands that change roles always wait at least 3
seconds per member. Turn on Answer a message and a message that says your phrase runs
the command too, as a public reply: match it as a whole word, the whole message, at the
start, or anywhere. Packet answers a trigger at most once every 5 seconds in a channel,
and up to 50 commands can have one. The reply can use {channel}, the {user.*} group,
{server} and the standing variables (see Message variables below).