Find a Minecraft plugin setup or troubleshooting guide

Find setup and troubleshooting instructions for Minecraft server plugins, grouped by what you want to do. These guides cover individual projects and their integrations; they are not a recommendation to install every plugin together. Start with the smallest set of features your community needs.

Before choosing a plugin

Check the plugin author's supported Minecraft release and server platform before downloading. Paper, a proxy such as Velocity, and a Fabric server require different builds. A guide does not guarantee compatibility with every future release. Some projects require a paid licence; obtain those files from the author through a legitimate account.

Read how to install plugins, keep a completed backup, and test substantial changes away from the only copy of your world. Plugins may keep player data in an external database, which needs its own matching backup. Use the commands and configuration for the exact installed release.

Maps, worlds and land protection

NPCs, menus, quests and progression

Voice chat, voting and community tools

Administration, compatibility and moderation

Shops, travel, economy and shared player data

Permissions, protection and performance essentials

Already have the basics installed? These existing guides explain common dependencies and the controls used by several plugins above. Check permissions with an ordinary player account as well as an administrator; operator access can conceal a missing permission or bypass a protection rule.

When a plugin does not work

Save the first useful startup error and record the server, Java and plugin versions. Check dependencies before changing permissions or replacing data. Restart normally after a supported file change; do not repeatedly reload the entire server to bypass a failed plugin. A missing command, an inactive dependency and a blocked network connection need different investigations.

If you need help, open a private support ticket with the relevant server ID, timestamp and redacted logs. Do not post database passwords, voting tokens, bot credentials or remote-storage keys. Keep the original files and last working backup while investigating.

Focused tasks by plugin

Choose a plugin below for individual configuration tasks, checks and recovery steps. These guides complement the setup articles above. Match the instructions to your installed release and keep a recovery copy before changing player data.

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