Skip to content
Fork Docs
Guide v1

/mod mute

Apply a Discord communication timeout to a member.

Availability

Section titled “Availability”

Public source-edition command; execution remains conditional on installation, server policy and the running service. This reference is built from the repository, not a live Discord registration probe. Explicit registration contexts: server.

Syntax

Section titled “Syntax”
/mod mute <user:User> [duration:String] [reason:String]

Angle brackets indicate required input; square brackets indicate optional input. In Discord, choose the command and fill its named options, rather than typing the brackets.

Parameters

Section titled “Parameters”
Name Type Required Allowed values / bounds Default when omitted Description
user User Yes No registration choices declared; handler validation applies. Required input Target member to mute/timeout
duration String No No registration choices declared; handler validation applies. 10m Mute duration (e.g. 10m, 1h, 1d, 7d). Default: 10m
reason String No No registration choices declared; handler validation applies. Rule violation / Moderator decision. Reason for the mute/timeout

Permissions

Section titled “Permissions”

Required native member permission(s): ModerateMembers (Administrator normally satisfies native permission checks).

Fork role access is evaluated using the underlying mute policy key, even when the slash name is grouped. Native Discord permission checks remain separate from Fork role grants. Sensitive commands fail closed before valid setup; native Administrator bypasses Fork’s role matrix, not Discord’s bot permissions or target hierarchy. See Permission model.

Where a member-targeting mutation calls the hierarchy guard, the server owner, the caller and Fork are protected. Targets must be below the acting moderator (except the owner) and Fork. Read-only history/list paths do not necessarily apply the same target guard. The bot needs the native permission required by the actual Discord action.

Examples

Section titled “Examples”
Slash options
/mod mute user:@Alex duration:10m reason:Repeated disruption
Prefix equivalent and aliases
Default prefix
f!mute @Alex 10m Repeated disruption

Default prefix: f!; installations can configure another. Handler aliases: timeout, tempmute. Aliases are prefix names, not additional slash commands.

Grouped prefix routes also delegate to the original handlers, but aliases retain that handler’s argument parsing. Conflicting aliases are rejected as ambiguous. Prefix replies are generally visible in the channel; prefer slash privacy controls for sensitive personal data.

Expected result

Section titled “Expected result”

Sets a timeout and records its reason/duration. This is not a voice-only mute or a custom mute role.

Failure cases

Section titled “Failure cases”

Malformed duration, protected role hierarchy, missing Moderate Members or Discord rejection can prevent the timeout. Check the returned error, current bot status and the relevant server permissions. A timeout or uncertain receipt is not proof that nothing happened; inspect state before repeating a mutation.

Usage limits

Section titled “Usage limits”

Parsed duration is capped at Discord’s 28-day timeout maximum.

Section titled “Related commands”
Section titled “Related guides”

Source edition v1 · Registration, direct handler and shared authorization review are hash-bound in the local documentation validation. This is not a production feature-availability certification.