Muting

Staff++ adds the ability to mute players. Next to the permanent mute command it also adds the tempmute command. With every mute a reason must be given why this player is getting muted.
Configuration
1
mute-module:
2
  # Whether or not the plugin will use "/mute player" features.
3
  enabled: true
4
  # Will the player know he is muted.
5
  default-soft-mutes: false
6
  # Commands that get blocked when a player is muted
7
  blocked-commands:
8
      - msg
9
      - whisper
10
      - tell
Copied!
Permissions
Permission
Description
staff.staffplus.mute
Permission for muting a player
staff.staffplus.tempmute
Permission for temporarily muting a player
staff.staffplus.unmute
Permission for unmuting a player
staff.staffplus.mute-bypass
Permission for bypassing being muted
staff.staffplus.mute-notifications
Permission to receive notifications when someone is muted/unmuted
staff.staffplus.mute-override-softhard
Permission to use the -soft/-hard option when muting players. See soft/hard mutes 
Commands
Command
Description
/mute [player] [reason] [-soft?] [-hard?]
Permanently mute a player 
/tempmute [player] [amount] [unit] [reason] [-soft?] [-hard?]
Temporarily mute a player
/unmute [player] [reason]
Unmute a player
Soft/Hard Mutes
Staff++ provides two ways of muting. Mutes where the player will be notified he is muted, we call this hard mutes. And mutes where the player has no idea he has been muted, we call this soft mutes.
By default all mutes are hard mutes but this can be changed with the default-soft-mutes configuration property.
1
mute-module:
2
  # Will the player know he is muted.
3
  default-soft-mutes: false
Copied!
You can override the default mute type by specifying a -soft or -hard option when muting players.
1
/mute playername To much spamming -soft
Copied!
Even though a soft mute will not notify the player that he has been muted. There is no easy way to fake the blocked-commands of the mute configuration. If a player executes one of the blocked commands nothing will happen so he might figure out something is going on.
Restricting tempmute duration
The tempmute command can also be configured to restrict the duration a staff member can use for a mute.
Give the staff member and extra permission with a duration limit as suffix. Example: staff.staffplus.tempmute.limit.2w , with this permission a staff member can only issue a mute for a maximum duration of 2 weeks.
A staff member must have both permissions to use the command. So for a 2 week duration limit the permissions needed are:
staff.staffplus.tempmute
staff.staffplus.tempmute.limit.2w
Possible time values:
s = second
m = minute
h = hour
d = day
w = week
M = month
y = year
Time values cannot be combined. For example this is invalid: ".1m30s" instead type ".90s"
Extending/reducing mute duration
A mute duration can be extended or reduced by the following commands: 
/mute-reduce [player] [amount] [unit]
/mute-extend [player] [amount] [unit]

This command can also be limited in duration the same way a tempmute is limited.
Giving the player the following 2 permissions will limit the extension duration for example:
staff.staffplus.extendmute
staff.staffplus.extendmute.limit.2w
When extending a mute, the staff member cannot extend the mute further than his tempmute limit will allow. This is to prevent a staff member spamming an extend command.
This means that if a player is muted for 2 months. His mute cannot be extended by a staff member whose tempmute limit is 3 weeks for example.
Examples
Permanent muting
/mute [player] [reason]
1
/mute playername He was bothering me
Copied!
Temporary muting
/tempmute [player] [amount] [unit] [reason]
1
/tempmute playername 15 MINUTE He was bothering me
Copied!
The duration of the tempmute is specified by [amount] [unit]
Amount must be a positive number > 0 and unit must be one of the following:
SECOND
MINUTE
HOUR
DAY
WEEK
MONTH
YEAR
The tempmute command can be delayed by adding a -D option to it. This will delay the command until the player muted will come online
Unmuting
/unmute [player] [reason]
1
/unmute playername We are friends now
Copied!
Another plugin is overriding the /mute, /tempmute, /unmute
It is possible that another plugin like 'essentialsx' might get priority over the mute, tempmute and unmute command. To prevent this we suggest the same solution as is proposed by EssentialsX.
Configure your server aliases in such a way that the mute commands from Staff++ will always be used. This can be done by editing the commands.yml file and specifying your aliases there.
To enable Staff++ mute commands this would be done in this way:
1
aliases:
2
    mute:
3
    - "staffplus:mute $1-"
4
    tempmute:
5
    - "staffplus:tempmute $1-"
6
    unmute:
7
    - "staffplus:unmute $1-"
Copied!
More info on the bukkit wiki​
Integration
The discord integration plugin supports notifying to a discord channel whenever a player gets mute/unmuted.

Features - Previous

Kicking

Next - Features

Protection

Last modified 28d ago

Copy link

Contents

Restricting tempmute duration

Extending/reducing mute duration

Another plugin is overriding the /mute, /tempmute, /unmute

Integration