Guide

How to make a Minecraft plugin without coding

Updated October 7, 2026

You do not need to learn Java to get a working plugin. You need to describe clearly what it should do, and a tool that turns the description into real code, builds it and lets you test it in the game before you install it. This guide shows how, and what to write so the result is what you had in mind.

Start from this example and change it to what you need.

Generate this with Codexe

Step by step

  1. 1.Pick the server and version

    Plugins run on Spigot, Paper or Folia servers. Note the Minecraft version your server runs (for example Paper 1.21.4): the plugin must be built for it.

  2. 2.Describe the plugin in plain words

    Say the commands, who can use them (permissions), what happens in game and what should be configurable. Short lists work better than long paragraphs.

  3. 3.Let Codexe write and build it

    Codexe writes the Java classes, plugin.yml and the build files, compiles the project and fixes compile errors before calling it Ready.

  4. 4.Try it on a real server

    Press Try it now to join a private test server with the plugin installed, from your own Minecraft client. Test players run the commands and check the result.

  5. 5.Ask for changes in the chat

    If something is not right, say what you saw ("the cooldown resets when I log out") and Codexe edits the code and builds again.

  6. 6.Install the .jar

    Download the built .jar, put it in your server's plugins/ folder and restart the server.

What to write so the plugin comes out right

An AI writes what you ask for, so the description is the whole job. A good description answers these questions:

  • Commands: the exact names and arguments, like /home <name>.
  • Permissions: which commands are for everyone and which for staff (for example homes.admin).
  • Rules: limits, cooldowns, costs, what happens on death or logout.
  • Configuration: what server owners should be able to change in config.yml, and the messages.
  • Data: whether things must survive a restart (saved to a file or a database).

Example description

"A Paper 1.21.4 plugin called Homes. /sethome <name>, /home <name>, /delhome <name> and /homes. Up to 3 homes per player, 10 with the permission homes.vip. Teleport after a 3-second warmup that cancels if the player moves. Homes saved in a YAML file per player. All messages and limits in config.yml."

That is enough for a complete, configurable plugin. You can always add features later in the same chat.

What "without coding" does and does not mean

You do not write code, but the plugin is real code: a normal Java project you can open, read and change, or hand to a developer later. Codexe checks that it compiles and that it loads on a real server, which is where AI-written code most often fails when it only comes from a chat.

Generating, compiling and testing are free on the free plan (50,000 tokens refilled every 24 hours). Downloading the .jar for your own server needs a plan or a download pack.

Questions

Can I really make a plugin without knowing Java?

Yes. You describe it, Codexe writes and compiles the Java code, and you test it in the game. Knowing a little helps to describe edge cases, but it is not required.

Will it work on my server version?

Codexe asks which Minecraft version the plugin is for (1.8.8 to 26.3) and builds it for that version's API and Java level. The test server runs the same version.

Can I change the plugin later?

Yes, in the same project chat, or by editing the files yourself. Configuration files stay readable and editable.

Describe your plugin and try it in the game

This prompt opens ready to send:

“A Paper 1.21.4 plugin called Homes: /sethome, /home and /delhome with a name, up to 3 homes per player (10 with homes.vip), a 3-second warmup that cancels on movement, homes saved per player, every message and limit in config.yml.”

Generate this with Codexe
How to make a Minecraft plugin without coding | Codexe