Guide

How to test a Minecraft plugin

Updated October 7, 2026

Never test a new plugin on the live server first. A plugin that fails on startup, conflicts with another one or has a wrong permission can break the server for everyone. Test it on a copy first, the same version and software as your real server.

An example to start from.

Generate this with Codexe

Step by step

  1. 1.Use the same server software and version

    A Paper 1.21.4 plugin is tested on Paper 1.21.4, with the same other plugins it depends on (Vault, LuckPerms, PlaceholderAPI).

  2. 2.Read the console on startup

    The plugin must load without errors. Exceptions on startup usually mean a wrong version or a missing dependency.

  3. 3.Try every command

    As an operator and as a normal player, with right and wrong arguments, to check permissions and error messages.

  4. 4.Restart and check the data

    Anything that must survive a restart (homes, balances) should still be there.

Testing with Codexe

Projects made with Codexe can be tested with Try it now: a private server of the right version starts with the plugin installed, and you join it from your own Minecraft (any version from 1.8 to 26.3). Test players join too, run every command as operator and as normal player, and check what you asked for. You can export the server log to read errors.

On the free plan you get 3 test servers a day, 10 minutes each, for up to 2 people.

Questions

Can I test a plugin I did not make with Codexe?

You can import a plugin project into Codexe and build and test it there, or run your own local test server.

Build and test a plugin in one place

This prompt opens ready to send:

“A Paper 1.21.4 plugin called StaffChat: /sc <message> sends a message only to players with staffchat.use, /sc toggle makes normal chat go to staff chat, messages also logged to a file.”

Generate this with Codexe
How to test a Minecraft plugin before installing it | Codexe