Custom commands
Typed commands and tags without arbitrary code.
Start here
Make a slash command that replies with a saved message
PulseOne → Dashboard → select your server → Modules → Custom commands
Choose Modules → Message builder and publish the message you want the command to send.
Go to Modules → Custom commands. Under Commands create or edit a command.
Under Message choose the published template. In Arguments enter the required typed inputs (up to 10).
In Cooldown and access, decide who may use the command and how frequently.
Save the command configuration, then run it in a test channel as an eligible and an ineligible member.
Practical example
Create a rules-response command and set a cooldown so it cannot be spammed.
Before you begin
- Enable first: messages.
- Discord bot permissions for the operational slice: ViewChannel, SendMessages, EmbedLinks.
- Review staff roles and channel access in your server before using the feature.
Overview of the setup
Before you begin
Publish a Message Builder template containing the response body and its typed variable placeholders.
Configure
Define a slash-first command, its inputs, role/channel scope and cooldown; map approved inputs to template variables.
Test and verify
Invoke it from a permitted role and channel, then inspect execution history and try a blocked user to verify restrictions.
Features explained
What each feature does and what to check before publishing or installing the result.
Slash-first custom commands
Prefer a named slash command over free-text parsing; command definitions do not execute uploaded code.
Typed arguments and variables
Define only needed arguments and verify sample values render into the correct template fields.
Cooldown and run history
Cooldowns constrain repeated use; history helps investigate failed or denied invocations.
If it still does not work
- Command not appearing? Check command registration, bot installation scope and whether the module is running.
- Reply shows missing variables? Match Arguments with the published Message builder template.
Troubleshooting and safety checks
- Command missing or denied? Check registration, enabled state, scope, template publication and required inputs.
- If a capability is unavailable in the UI, check the module's current rollout/availability instead of assuming every roadmap item is live.