Test whether a LiteBans mute covers a private-message command

Applies to: LiteBans; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

A mute may stop public chat while another plugin still accepts private messages. Test the exact command route your players use instead of treating every chat-like feature as equivalent.

Follow the procedure

List the public and private message commands available on this server, including namespaced aliases and proxy commands. Identify which plugin handles each route.
Prepare two consenting test accounts without mute bypass permissions. Check the sender’s existing mute status and save the relevant LiteBans configuration before editing its command controls.
Apply a short /tempmute PLAYER 2m Message-route trial to the sender. Record the punishment ID, scope and expiry; keep the recipient account unrestricted.
Try ordinary public chat, then the actual private-message command and its documented aliases. Record whether the server rejects the command or the recipient receives the text.
If an unintended route remains open, use the installed release’s documented muted-command configuration to cover that specific route. Check proxy-owned commands in the proxy configuration too.
Repeat the same messages after applying the supported configuration change and after the mute expires. Confirm normal private messaging returns without additional staff intervention.

Check the result

During the mute, each command covered by your moderation policy should be rejected and the recipient should receive no message through those routes. After expiry, both public chat and the approved private-message command should work. A blocked public message alone is insufficient evidence.

If the result is wrong

If the test still leaks messages, inspect command ownership and aliases before adding broader restrictions. A backend cannot necessarily block a command intercepted by the proxy first. Remove only the trial mute when finished and restore the specific configuration edit if it blocks unrelated player commands.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report