Custom Commands

Creating Commands

Create custom commands tailored to your server with flexible triggers and responses.

Overview

SYNTHET allows you to create custom commands that execute specific actions when triggered. Whether you want to automate responses, create fun commands, or build complex workflows, custom commands give you complete control over your bot's behavior.

Commands can have single or multiple triggers, optional arguments, cooldowns, and permission restrictions. You can also chain commands together to create more sophisticated automations.

Core Concepts

Understanding these fundamentals will help you build powerful custom commands:

Trigger

The word or phrase that activates your command. Must start with a prefix (default: /). Triggers are case-insensitive.

Response

The message or action that executes when the trigger is used. Can include text, variables, and embeds.

Arguments

Optional parameters passed to the command. Useful for dynamic commands that need user input.

Cooldown

Time delay between uses (per user or global). Prevents spam and abuse of automated commands.

Permissions

Restrict who can use the command based on roles, channel, or user ID. Essential for moderator tools.

Creating Your First Command

Use the command creation interface to build a new custom command:

/command createOpen the command creation interface
/command create <name>Create a command with a specific name
/command listView all custom commands on your server
/command edit <name>Modify an existing command
/command delete <name>Remove a custom command
/command test <name>Test a command without triggering cooldowns

Command Properties

Configure these properties when creating or editing a command:

Name

Text

Unique identifier for your command. Used internally for management.

Example: welcome, rules, info

Trigger

Text

The prefix + word users type to activate the command. Can have multiple triggers.

Example: /hello, /hi, /greetings

Response

Message

The text message sent when command is triggered. Can include variables and formatting.

Example: Hello {user}! Welcome to {server}.

Embed

Optional

Rich formatted message with colors, fields, and images. More visually appealing than plain text.

Example: Embed with title, description, fields, footer, etc.

Cooldown

Time (seconds)

Prevents the same user from using the command too frequently.

Example: 5, 30, 300 (for 5 minutes)

Permission Level

Dropdown

Restrict usage to specific roles or permission levels.

Example: Everyone, Moderator, Admin, Owner

Channel Restriction

Optional

Limit command to specific channels. Useful for keeping spam in designated areas.

Example: general, announcements, #commands

Delete Trigger

Toggle

Delete the user's command message after execution.

Example: Useful for keeping chat clean

Mention Response

Toggle

Tag the user who triggered the command in the response.

Example: Shows who requested the action

Simple Command Examples

These examples show basic commands you can create:

Welcome Message

Trigger: /welcome
Response: Welcome to our server, {user}! Read {channel_rules} before participating.
Use case: Greet new members with server information

Server Rules

Trigger: /rules
Response: 📋 **Server Rules**\n1. Be respectful\n2. No spam\n3. Follow Discord ToS
Use case: Quick reference to community guidelines

Support Links

Trigger: /help
Response: Need help? Check our FAQ: https://example.com/faq or DM a moderator.
Use case: Direct users to support resources

Fun Fact

Trigger: /fact
Response: 🎓 Did you know? Honey never spoils and can last forever!
Use case: Share interesting trivia regularly

Multiple Triggers

A single command can have multiple trigger words. This lets users invoke the command in different ways:

/hello
/hi
/greetings
/hey

All four triggers will execute the same command response. Useful for common variations of the same command.

Add multiple triggers separated by commas when creating your command.

Using Arguments

Commands can accept arguments to make them more dynamic and flexible:

Single Argument

Command: /remind [message]
User types: /remind Study for exam
Response: 📌 Reminder set: Study for exam

Multiple Arguments

Command: /calc [num1] [operator] [num2]
User types: /calc 10 + 5
Response: 10 + 5 = 15

Optional Arguments

Command: /poll [question] [option1] [option2]
User types: /poll "Cats or dogs?" Cats Dogs
Response: Poll message with reaction options

Cooldown Configuration

Cooldowns prevent spam and control command usage:

Per-User Cooldown

Each user has their own cooldown timer. Perfect for economy or leveling commands.

Example: 30 second cooldown

User A waits 30s between uses, User B has their own 30s timer

Global Cooldown

All users share the same cooldown timer. Good for bot-wide announcements.

Example: 5 minute cooldown

After any user triggers it, all users must wait before using again

No Cooldown

Command has no cooldown restrictions. Use only for safe, informational commands.

Example: /rules, /help, /info

Users can spam these, but they should be read-only informational commands

Permission Settings

Restrict command access based on user roles and permissions:

Everyone

Anyone on the server can use this command. Default for public, informational commands.

Members Only

Only users with a specific member role can use the command. Good for verified users.

Moderator

Restrict to users with moderator role. Use for moderation tools like kick, mute, or warnings.

Administrator

Only server admins can use this command. Essential for dangerous operations.

Owner Only

Only the server owner can execute this command. Maximum security for critical features.

Channel Restrictions

Limit where commands can be executed:

Whitelist Specific Channels

Command only works in designated channels. Perfect for keeping spam in specific areas.

Example: /fun command only in #off-topic or #games

Blacklist Specific Channels

Command works everywhere except designated channels. Useful for important channels.

Example: Disable /dice in #announcements

Advanced Options

Fine-tune command behavior with these options:

Delete Trigger Message

Automatically delete the user's command message after execution. Keeps chat clean and prevents clutter from command calls.

Mention User in Response

Tag the user who triggered the command in the bot's response. Shows who requested the action and notifies them.

Ephemeral Response

Only the command user can see the response. Useful for private information or personal commands.

Case Sensitive Trigger

Require exact case matching for triggers. By default, triggers are case-insensitive.

Tips & Best Practices

  • • Use descriptive command names that clearly indicate what the command does
  • • Add appropriate cooldowns to prevent spam and abuse
  • • Use permission levels to restrict dangerous commands to moderators and admins
  • • Include variables like {user} and {server} to make responses more personal
  • • Test commands before deploying them with the /command test feature
  • • Use multiple triggers for the same command to accommodate user preferences
  • • Delete trigger messages for cleaner-looking chat (when appropriate)
  • • Document your custom commands so users know they exist
  • • Keep response messages concise and clear
  • • Use embeds for complex information instead of plain text
OverviewVariables