Verify the server scope of a LiteBans network punishment

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

A local punishment and a network-wide punishment can produce different results when players change backends. Confirm the scope explicitly so staff do not overreach or leave an unintended bypass.

Follow the procedure

List the backend names shown by /litebans servers and identify the public connection path. Use the names LiteBans recognizes rather than a hosting-panel label that may differ.
Choose a test account and inspect existing bans or mutes before starting. Record which backends should enforce this trial and which should remain usable.
Read the Server Scopes documentation linked from the commands reference. Confirm the installed configuration’s default scope and the permission required to choose a different scope.
Issue an approved short trial with an explicit server:NAME argument using a recognized backend name. Record the resulting punishment ID and reported scope.
Test through the proxy on the selected backend and a second backend. Repeat the relevant action, such as joining or sending chat, rather than relying only on a server-switch message.
Reverse the specific trial and verify normal access returns on both backends. Document when staff should choose local scope and when a separately authorized global action is appropriate.

Check the result

Only the intended backend scope should enforce the local trial, and the punishment record should display the expected scope. A global trial requires its own approval and check. Shared database connectivity by itself does not prove all punishments are network-wide.

If the result is wrong

If scope results differ from policy, inspect server names, plugin placement and shared database configuration. Avoid broad global bans as a diagnostic shortcut. End the trial by its exact record and keep the observed backend results before adjusting default scopes.

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