The public API for the Magic plugin.

This can be used in one of two ways:

If you wish to integrate with magic, you can easily add it to your project with Maven, or download and reference it directly.

Make sure to add Magic to your depends list if you intend to hard-depend on Magic.

Alternately, you can use the API as a soft-depends, if you are sure to use wrapper classes that don't load unless you know Magic is present.

You can easily import Magic's API into your project like this:

<dependencies>
  <dependency>
      <groupId>com.elmakers.mine.bukkit</groupId>
      <artifactId>MagicAPI</artifactId>
      <version>11.3-SNAPSHOT</version>
      <scope>provided</scope>
  </dependency>
</dependencies>
<repositories>
  <repository>
      <id>elMakers</id>
      <url>https://maven.elmakers.com/repository/</url>
  </repository>
</repositories>

Alternatively, you can import Magic's API with Gradle like this:

repositories {
    elmakers {
        url 'https://maven.elmakers.com/repository/'
    }
}

dependencies {
    compileOnly 'com.elmakers.mine.bukkit:MagicAPI:11.0'
}

      MagicAPI getMagicAPI() {
          Plugin magicPlugin = Bukkit.getPluginManager().getPlugin("Magic");
            if (magicPlugin == null || !(magicPlugin instanceof MagicAPI)) {
                return null;
            }
          return (MagicAPI)magicPlugin;
      }

Other plugins may deeply extend Magic, such as by adding new spell or effect classes.

To do so, you may directly link to Magic, or you can try to work within the confines of MagicAPI - think of it as MagicAPI:Magic :: Bukkit:Craftbukkit.

In either case, you will likely be making a hard dependency to Magic, in which case you can reference both MagicAPI and Magic as "provided" in your pom.xml (for Maven), since the classes will be provided by Magic at runtime.

Issues, feature requests, or suggestions for this API should be made at our issue tracker:

https://github.com/elBukkit/MagicPlugin/issues