Verify PremiumVanish network vanish across Velocity backends

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

A vanished state on one backend does not establish network-wide visibility. PremiumVanish’s documented network feature requires compatible proxy and backend components with the intended shared storage.

Follow the procedure

Check the installed PremiumVanish release against the maintainer’s Velocity instructions. Confirm that the network-vanish command exists in that version rather than borrowing an older Bungee-only procedure.
List the proxy and participating backends, their plugin versions and the shared MySQL connection they are meant to use. Keep credentials out of screenshots and public logs.
Use read-only connection and startup logs to establish that each component reaches the intended database. Do not point unrelated servers at a shared schema merely to test visibility.
Give a test moderator the documented pv.networkvanish permission and use the release’s /networkvanish command. Keep ordinary observers on two participating backends.
Move the moderator through the public proxy between those backends. Check entity visibility, tab entries and join or switch messages from both observer accounts.
Reappear through the supported network control and repeat the movement. Confirm normal visibility returns across the same backend set before staff rely on the feature.

Check the result

The hidden state should follow the moderator across every backend included in the supported configuration. Record the tested proxy version and backend versions. A successful command on the proxy does not prove an omitted or disconnected backend received the state.

If the result is wrong

If one backend leaks the moderator, inspect that component’s version, shared storage and startup errors before changing permission levels. Avoid disabling backend connection protection to simplify testing. Restore the previous visibility state and use local vanish only within the verified scope until integration is corrected.

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