Recognize the PremiumVanish API jar before installing an integration

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

The public PremiumVanish API project is a development dependency, not a replacement for the licensed server plugin. Installing the wrong jar can produce a startup failure without providing vanish functionality.

Follow the procedure

Read the integration developer’s installation requirements and the PremiumVanish API repository notice. Determine which jar is the actual server plugin and which is only a compile-time API artifact.
Open the game panel Files view and list existing vanish-related jars. Record filenames, versions and their legitimate download sources before moving anything.
If an API-only jar was uploaded accidentally, stop the server for a controlled correction. Keep a copy outside the plugin load directory rather than deleting unrelated plugin data.
Install the supported actual plugin from the authorized source, together with the integration version it supports. Do not use an unverified third-party fork as a substitute for the licensed dependency.
Start the server and read the first plugin-loading messages. Confirm the vanish plugin and integration both enable without a stub-API warning or missing-class error.
Exercise one read-only integration feature with a test account, then confirm ordinary vanish still works. Preserve the previous working jar and configuration until the check is complete.

CloudExa game panel: server file manager — CloudExa game panel reference. This image shows the panel, not the PremiumVanish interface.

Check the result

The server should load the actual PremiumVanish plugin and the integration should find its runtime API. A jar named after an API does not establish that the feature is installed. Verify the startup result and one practical integration action before closing the maintenance task.

If the result is wrong

If class-loading errors persist, restore the matched previous plugin set and capture the first exception for the integration maintainer. Do not keep multiple versions of the same plugin in the load directory or remove configuration folders to force a clean startup.

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