Skip to main content
Venon Security slash commands

What is the /challenges slash command for in Venon Security for Discord?

/challenges belongs to the member category and is part of the Wyzwania module. An administrator or a moderator reaches for it when the action has to be fast, fully traceable in the logs and in line with Discord's permissions.

Member

Category

Public

Permissions

1

Parameters

What it does

What is the /challenges command for?

Three tasks for today — claim XP for completed ones.

When to use it

Reach for /challenges when you need a repeatable administrative action without clicking through Discord's settings by hand. Venon Security watches the syntax, the permissions and the context, and the execution can later be tied to the moderation logs or the module's configuration.

Required permissions

The command requires the scope: Public. If Discord rejects the action, check the bot role's position in the hierarchy, the permissions on the channel and whether the module is enabled in the dashboard.

Syntax

Syntax of the /challenges command

Format

/challenges [private]

Angle brackets mark required parameters, square brackets optional ones. In slash commands Discord suggests the fields for you, so it is best to fill them straight from the suggestion list.

Example usage

/challenges private:yes

Treat the example as a template. Swap the member, channel, role, reason or duration for the real situation on your server.

Parameters

Command parameters

privateyes/nooptional

Show only to you

Problems

The most common problems

Missing permissions

Check whether the member and the bot both hold the required scope: Public.

Role hierarchy

For actions on members, the bot's role has to sit above the target's role.

Module disabled

If the command depends on a module, enable it in the dashboard and check the channel configuration.

Ready?

Add Venon Security and use /challenges with the full context

Slash commands work best alongside the dashboard, the logs and the protection modules. Add the bot to your server, read the documentation and set up your team's permissions.