Setting up your development environment

To use the CommandAPI in your plugins, there are a few methods of adding it to your development environment. First things first, if you're using the CommandAPI plugin, you need to add the CommandAPI as a dependent in your plugin.yml or paper-plugin.yml:

name: MyPlugin
version: 1.0
depend: [CommandAPI]
name: MyPlugin
version: 1.0
      load: BEFORE
      required: true
      join-classpath: true

Developer's Note:

If you've never used maven before, I highly recommend it! It makes it easier to keep your code updated with the latest dependency updates. For information on how to set up a plugin using maven, you can read Bukkit's plugin tutorial.

  • Add the dependency to your pom.xml:

  • Add the repositories to your build.gradle file (the second repository is required because the CommandAPI depends on the NBT-API):

    repositories {
        maven { url = "" }
  • Add the dependency to your list of dependencies in your build.gradle file:

    dependencies {
        compileOnly "dev.jorel:commandapi-bukkit-core:9.4.0-SNAPSHOT"

Manually using the .jar

  • Download the latest CommandAPI.jar from the download page here

  • Add the CommandAPI.jar file to your project/environment's build path:

    • Adding the external .jar file in Eclipse:

      An image of some context menu entries in Eclipse after right clicking a project. Displays the highlighted options "Build Path", followed by "Add External Archives..."

    • Adding the external .jar file in IntelliJ:

      • In your project, first click File -> Project Structure -> Libraries

      • Next, click the little + at the top:

        An image in IntelliJ showing the plus icon to add an external .jar.

      • After you clicked that, you need to select Java. A little pop-up will appear where you can choose the location of your external .jar file.