How to write a Minecraft/Bukkit Plugin for Spigot 1.11

The Minecraft community seems to have an obsession with doing everything on YouTube.  For some people that’s great, but as someone who is already a coder and I just need to know the environment-specific details for coding for Minecraft I have a really hard time sitting through an hour of tutorial videos just to get the four things I needed to know that I didn’t already know how to do.  This is where having a text and pictures version of a tutorial comes in handy, so you can skim through it looking for the parts you still need to know, and easily skip over the stuff you already know. Another friend of mine was also recently trying to get into writing a plugin for Spigot, and everything I could find to point him at which was text-based rather than a YouTube video was very outdated, had instructions that were no longer relevant because Bukkit and Spigot and Eclipse have all evolved since then, etc.  So I figured I’d write one, and here it is!

Update: since writing this up, I discovered a very nice page on the Spigot Wiki documenting much of this, which seems to be mysteriously absent from the search engine searches I did trying to find this information (or at least ranked low enough that all the YouTube videos and a bunch of forum posts that skirt this issue outrank it). How to create a Minecraft/Bukkit/Spigot plugin on the SpigotMC website. I’m posting this anyway because I do a few things differently. Pick your flavor. 🙂

Setting up your development environment

Install Java

You need the Java Development Kit, not the Runtime Environment.  Download the Java SE JDK from Oracle’s site.  Make sure you get the JDK, not the JRE, and make sure you have the correct one for your operating system. only has JREs, you have to go to Oracle’s site for the JDK.  Linux users can try installing the java-8-openjdk package.

Note for OS X users: OS X no longer ships Java by default. It will automatically install if you try to run something that needs Java, however, the version it installs is old (Java 6) and Bukkit/Spigot development requires at least Java 7, so you will need to download the newer Java even if you already have the system Java.

Download and Build Spigot

You need to link against Spigot in order to compile plugins, so you’ll need a local copy of Spigot to link to, even if you never actually run it.

Download BuildTools.jar from

Place it in an otherwise empty directory.  Open a command prompt (or a terminal window) and navigate to the directory you placed it it.  Run the following command to build it:

java -jar BuildTools.jar

This will probably take a while. If all goes well, you should get a file called Spigot-1.11.2.jar in the same directory with BuildTools.jar (the version number in the filename may be different if Spigot has been updated since I posted this). Remember where this directory is, you’ll need it later when creating the project in Eclipse.

Install Eclipse

Plugin development is done with a Java IDE.  If you already have a favorite Java IDE, I imagine you can make it work, but if you don’t, I recommend Eclipse, and that’s what my instructions will be based on.

You can get Eclipse here:

Most Linux distributions have Eclipse packaged already and you can probably use your package manager to install it.  Your mileage may vary in getting it to work.  Personally, I’ve had issues getting Eclipse plugins to work correctly because updating plugins sometimes breaks the way the packager packaged the main app, and sometimes plugins want a newer version of Eclipse (Ubuntu ships an older version), so I use a copy of Eclipse downloaded from rather than the one Ubuntu ships.

If you have more than one version of Java installed (OS X users, this is probably you), go into Eclipse’s preferences, click the triangle next to “Java”, and look for the “Installed JREs” section.  Make sure the one you just installed is listed in there, and checkmarked.  If it is not, click Add, then click on Directory to the right, navigate to where you installed the Java JDK, and find the “jre” directory inside it.  On OS X, Oracle’s installer will install inside /Library/Java/VirtualMachines/. Examples:

Mac OS X: /Library/Java/JavaVirtualMachines/jdk1.8.0_31.jdk/Contents/Home/jre
Linux: /usr/lib/jvm/java-8-openjdk-amd64/jre

Install the YEdit plugin to Eclipse

The file you create that tells Spigot how to interact with your plugin is in YAML format.  As shipped, Eclipse does not understand how to edit YAML files (even though it’s really just a text file).  There is a plugin that will teach it how, though.

Go to Help -> Eclipse Marketplace, and type “yedit” into the Find box.  The YEdit plugin should be the first hit.  Click Install and follow the prompts.

Creating your first project in Eclipse

Create the project itself

  1. Choose File -> New -> Java Project
  2. Enter the name of your plugin
  3. Choose Next (not Finish)
  4. Click the Libraries tab.
  5. Click Add External JARs…
  6. Choose the shaded version of the Spigot-API JAR file from the Spigot directory that you compiled above. Within the directory with BuildTools.jar the API file will be in Spigot/Spigot-API/target and will probably be named something like spigot-api-1.11.2-R0-SNAPSHOT-shaded.jar
  7. Toggle the triangle to the left of spigot-api
  8. Choose Javadoc Location
  9. Click Edit…
  10. In Javadoc location path, enter: . This will allow the autocomplete in Eclipse to autocomplete Spigot API objects and methods.
  11. Click OK
  12. Click Finish

Create a package

  1. Choose File -> New -> Package
  2. Enter the name of your package.  This is usually structured like a domain name, but in reverse.  It should start with something that identifies you, and then have the name of the project at the end, and be all lower-case.  Minecraft itself is net.minecraft.server for example, Spigot is org.spigotmc, and the Bukkit plugin API is org.bukkit.plugin.  I’ll use tld.example.myplugin in the examples.
  3. Click Finish

Create the Main class

  1. Choose File -> New -> Class
  2. Enter the name of the class which will be loaded by Spigot when it loads the plugin.  You can really name this anything you want (we’ll deal with telling Spigot how to find it later), but for simplicity I’ll call it Main in the examples.
  3. Next to Superclass, click Browse…
  4. In the search box, type JavaPlugin, and choose what should be the only match (
  5. Click OK
  6. Click Finish

It should automatically open in the editor, and you should now be looking at code that looks like this:


  1. package tld.example.myplugin;
  3. import;
  5. public class Main extends JavaPlugin {
  7. }

There are two functions defined by the API which you are required to implement. Those are onEnable and onDisable, which get run when your plugin is enabled or disabled. They don’t need to do anything, but if you have any resources that need allocating or disposed of, those are the places to do it. Add those two functions to your file, so that it looks like this:


  1. package tld.example.myplugin;
  3. import;
  5. public class Main extends JavaPlugin {
  7.     @Override
  8.     public void onEnable() {
  10.     }
  12.     @Override
  13.     public void onDisable() {
  15.     }
  17. }

Create the plugin.yml file

  1. Choose File -> New -> File
  2. Select the top-level folder of your project (the project name)
  3. for the File name enter plugin.yml
  4. Click Finish

It should open in the editor. If it doesn’t, you likely forgot to install YEdit up at the top of this tutorial.

This file will be in YAML format, and describes to Spigot how to interact with the plugin. The top of the file leads off with some basic information about the plugin, and is then followed by a description of the commands which are made available by the plugin.


  1. main: tld.example.myplugin.Main
  2. name: MyPlugin
  3. version: 1.0
  4. author: me
  5. description: An Example plugin
  6. commands:
  7.   mycommand:
  8.     description: An example command
  9.     usage: /mycommand
  10.     permission: myplugin.mycommand
  11.     permission-message: You don't have the myplugin.mycommand permission.

The “main:” line needs to list the package and class name of the class which is loaded by Spigot when it loads the plugin’s jar file.  “version”, “author”, and “description” are human readable, and shown to the user by the /plugins and /help commands.

The “commands:” block should contain one line for each command you implement.  If it’s not listed here, Spigot won’t send the command to you when users use it.

Within each command’s block, the “description” and “usage” sections are shown to the user when they use the /help command.  The “permission” line describes which permission grants access to the command. “permission-message” is shown to users who don’t have permission to use it if they try to. The “permission” should start with the name of the plugin, a dot, and then an arbitrary permission name.  You can also borrow another plugin’s permission or a core permission.  For example, if your plugin adds additional features to MultiWorld you could require “mw.admin” permission or so forth.  You can leave out this line if you want it available to all users.

Create your build script

To be able to install the plugin into Spigot, you need to create a JAR file (Java ARchive).  You can use File -> Export -> Java -> Java JAR to create it, but then you end up having to specify which files to include every time.  In the long run, it’s easier on you to set up Eclipse to automatically build it.  So in this step we’ll be creating a build script that defines the contents of the JAR file so that Eclipse can do that.

  1. Go to File -> New -> File
  2. Choose the top-level folder (the name of your project)
  3. For File name enter build.xml
  4. Click Finish

It should open in the editor.

Paste in the following:


  1. < ?xml version="1.0" encoding="UTF-8"?>
  2. <project name="MyPlugin" default="makejar" basedir=".">
  3.     <target name="makejar" description="Create a jar for the project">
  4.         <mkdir dir="target"></mkdir>
  5.         <jar destfile="target/${}.jar">
  6.             <fileset dir="bin"></fileset>
  7.             <fileset file="plugin.yml"></fileset>
  8.         </jar>
  9.     </target>
  10. </project>

Where it says “MyPlugin” at the top, you’ll want to replace with your project name. Also, WordPress adds a space between the < and the ?xml in the first line because it looks too much like the syntax used to start a php code block. You’ll need to remove that space for the file to be valid.

Tell Eclipse to use your build script

  1. Right-click (control-click or two-finger-click on Mac) on the project name and choose Properties.
  2. Choose Builders on the left side.
  3. Click New…
  4. Choose Ant Builder and click OK
  5. Set the name to Make JAR
  6. For Buildfile, enter ${project_loc}/build.xml (literally, including the $ and the braces)
  7. Click the Refresh tab
  8. Checkmark Refresh resources upon completion
  9. Choose The project containing the selected resources
  10. Switch to the Targets tab.
  11. Click on Set Targets… next to each of “Auto Build” and “During a ‘clean'” and just click the OK button on the resulting dialog.
  12. Click OK to close out of the Edit Configuration window.
  13. Click OK to close out of the Properties window.

At this point you should have a working project, and any time you make changes to anything in your project, it will automatically rebuild the plugin’s jar file in the target directory. As long as you’ve been saving your changes, it should always be up-to-date with your code.

Start Coding

If you’ve followed the above instructions up to this point, you now have a working plugin file which does absolutely nothing, but has all of the necessary framework.

Oh, one more thing.

The plugin.yml file included a description of a command just to use an example of how to put that in the plugin.yml file. I would be remiss if I didn’t also give you the sample code for actually handling that command. That goes in by adding an onCommand() handler function. Your final would look like this:


  1. package tld.example.myplugin;
  3. import org.bukkit.command.Command;
  4. import org.bukkit.command.CommandSender;
  5. import;
  7. public class Main extends JavaPlugin {
  9.     @Override
  10.     public void onEnable() {
  12.     }
  14.     @Override
  15.     public void onDisable() {
  17.     }
  19.     @Override
  20.     public boolean onCommand(CommandSender sender,
  21.             Command command,
  22.             String label,
  23.             String[] args) {
  24.         if (command.getName().equalsIgnoreCase("mycommand")) {
  25.             sender.sendMessage("You ran /mycommand!");
  26.             return true;
  27.         }
  28.         return false;
  29.     }
  31. }

Additional Resources

Spigot Plugin Development Page
Spigot API Reference

UPDATED 2016/05/06: Still works in 1.9, so updated references accordingly. Fixed step 6 in creating the project to use the shaded version of the API file. Thanks to several people in the comments for pointing it out.

UPDATED 2017/02/21: I haven’t had a chance to try it myself recently, but multiple people have said in the comments that this still works in 1.11.x, so I’ve updated the references accordingly.

44 thoughts on “How to write a Minecraft/Bukkit Plugin for Spigot 1.11”

  1. So I have a problem, after I try to compile BuildTools.jar (I used git&bash here like it was advised in a youtube video StormCoreFilms) I get an error:

    Applying: Skeleton API Implementations
    Applying: Obfuscation Helpers
    fatal: sha1 information is lacking or useless (src/main/java/net/minecraft/server/
    Repository lacks necessary blobs to fall back on 3-way merge.
    Cannot fall back to three-way merge.
    Patch failed at 0004 Obfuscation Helpers
    The copy of the patch that failed is found in:
    When you have resolved this problem, run “git am –continue”.
    If you prefer to skip this patch, run “git am –skip” instead.
    To restore the original branch and stop patching, run “git am –abort”.
    Something did not apply cleanly to Spigot-Server.
    Please review above details and finish the apply then
    save the changes with
    Error compiling Spigot, are you running this jar via msysgit?
    java.lang.RuntimeException: Error running command, return status !=0: [bash,]
    at org.spigotmc.builder.Builder.runProcess(
    at org.spigotmc.builder.Builder.main(

    Do you maybe know what is wrong/what I can do to avoid this error? Thank you in advanced 🙂

    1. Hi, I don’t normally use git so idk, but you don’t need git to run the JAR. On Windows/Linux, open a terminal/cmd prompt and run “java -jar BuildTools.jar” which will compile it. 🙂

      1. I’m pretty sure if you don’t have git already, BuildTools.jar will automatically download and install it for you. It does use it as part of the build process.

  2. Thank you for your short but very helpfull introduction to Spigot-Plugin writing. As I’m a programmer too, I really aprecciate a well written tutorial.
    So thanks for writing this and giving each section the right header (So I was able to skip the unnecessary ones).

  3. Hello! Thank you for the very helpful tutorial. However I seem to be getting a weird error on my package. I named it “” and it gives me this error: “The type com.avaje.ebean.EbeanServer cannot be resolved. It is indirectly referenced from required .class files”. Thanks for any help you can provide!

    1. Use the shaded version of the API instead at this step :

      6.Choose the Spigot-API JAR file from the Spigot directory that you compiled above. Within the directory with BuildTools.jar the API file will be in Spigot/Spigot-API/target and will probably be named something like spigot-api-1.8.3-R0.1-SNAPSHOT.jar

  4. Eclipse gives me an error on the first line of code (package declaration). I have done everything like you said, so why am I getting this?
    “The type com.avaje.ebean.EbeanServer cannot be resolved. It is indirectly referenced from required .class files.”

  5. Epic work, this is a great concise and detailed guide.

    Worked like a treat and massively appreciated the focus on setting up the environment properly, been looking for something like this for a long long time.

  6. I follow your fantastic instructions, but i have only a problem: the package in the first line is underlined and it say: “Multiple markers at this line
    – The type com.avaje.ebean.EbeanServer cannot be resolved. It is
    indirectly referenced from required .class files
    – The type com.avaje.ebean.EbeanServer cannot be resolved. It is
    indirectly referenced from required .class files”
    can someone help me?

    1. You need to use the Spigot Shaded build.
      To find:
      Build Path -> Configure Build Path
      Go to Libraries
      Add the spigot-api-shaded.jar, using the add external JAR tab.

  7. To fix the “The type com.avaje.ebean.EbeanServer cannot be resolved. It is indirectly referenced from required .class files”
    error, you HAVE to import
    spigot-api-1.9-R0.1-SNAPSHOT-shaded.jar and NOT

  8. This tutorial worked great! With very detailed instructions I set up Eclipse and am developing plugins within the hour. I can’t believe I ran into only a few problems!

  9. If you get error, ““The type com.avaje.ebean.EbeanServer cannot be resolved. It is indirectly referenced from required .class files”

    use the server file in the Spigot-Server folder


    Hope this helps

  10. Thanks for this! I was fighting the same battles and trying to slog through the swamp of youtube to learn this particular skill. Because of you a new economy plugin is under way. Expect to be credited as a contributor, in essence if not in actual code.

  11. This was a very great tutorial for beginners such as myself. The question I have is where do I go from here? I want to be able to make complex and specific commands and other features. Where can I learn to do this?

  12. Hey Dave, thanks for writing this.

    In order to get Ant to auto-build, instead of using the recommended`${project_loc}/build.xml`, I had to click the Browse Workspace folder, navigate to build.xml, and use the location Eclipse provided.

    I *also* had to set Base Directory to my project root.

    Using Eclipse, Version: Neon Release (4.6.0), Build id: 20160613-1800

    1. Thanks for the above info on the auto-build, I had the same problem.

      Great tutorial – I completely agree with comments on the YouTube obsession. I’d much rather have things written out clearly by someone who knows what they’re talking about.

  13. This may sound strange, but you lost me at “Tell Eclipse to use your build script”. In the first step I can’t quite figure out where it is I’m supposed to right click…

    1. It likely hasn’t changed a whole lot, but I’ll get it updated as soon as I update one of my plugins for it. So far, mine seemed to work without recompiling, so I wasn’t in a rush, and I haven’t had time to work on it lately.

  14. A couple of issues I had, the terminal command that I had to use was: java -Xmx2G -jar (then drag/drop the file there for the directory bit) and then hit return.

    It created several directories and both a Craftbukkit and a Spigot jar.

    Also, the new Eclipse Neon version does not look like the Eclipse you are using. I had to find Eclipse Luna, and found it here which looks like what you’re describing in the tutorial. Happy to finally be able to move forward!

  15. 1.11.2 Works great. Teaching my 7 yr old how to code and he has been able to keep up with your very clear instructions. This is a better approach than videos.


  16. I tried unloading spigot, and it said

    “C:\Windows\Spigot>java -jar BuildTools.jar”
    “Loading BuildTools version: git-BuildTools-4bf25ea-55 (#55)”
    “You must run this jar through bash (msysgit)”

    I have no idea what that means, or how to fix it… Please elaborate…

    Running this on windows 7, not sure if that matters too much.

    1. You probably need to install one of the unix-like shells to use instead of using the Windows command prompt. I’m not all that familiar with Windows so I’m not sure if there’s something else better nowadays, but I used to hear about people running Cygwin for that purpose.

Leave a Reply

Your email address will not be published. Required fields are marked *