Providing and maintaining a separate API as its own dependency for each add-on is very tedious. For this reason, we have unified most official APIs into a single dependency.
This does not mean they are all bundled within MBedwars. The API classes corresponding to each add-on are bundled within the add-on itself. Meaning that you should check whether the given (add-on) plugin is loaded, or add it as a dependency to your plugin.yml.
Example of a plugin.yml:
name: MyPlugin
main: abc.def.Moo
depend: [ MBedwars, MBedwars-Cosmetics ]
softdepend:
- MBedwarsTweaks
- PrivateGamesAddon
| Name | Plugin name | Javadoc | Marketplace |
| Cosmetics & Coins | MBedwars-Cosmetics |
de.marcely.bedwars.api.cosmetics | MBedwars.com |
| Level Shop | MBedwars-LevelShop |
de.marcely.bedwars.api.levelshop | MBedwars.com |
| Private Games | PrivateGamesAddon |
me.harsh.privategamesaddon.api | MBedwars.com |
| MetallicGoat's ExtraSpecialItems | ExtraSpecialItems |
de.marcely.bedwars.api.specialitems | MBedwars.com |
| MetallicGoat's Tweaks | MBedwarsTweaks |
de.marcely.bedwars.api.tweaksaddon | MBedwars.com |
The dependency is being updated regularly and automatically. Its version coresponds to the version's build date and includes all the latest API changes of each supported add-on.
Insert these snippets into your pom.xml accordingly:
<repositories>
<repository>
<id>marcely-repo</id>
<url>https://repo.marcely.de/repository/maven-public/</url>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>de.marcely.bedwars</groupId>
<artifactId>Addons-API</artifactId>
<version>Build-261025</version>
<scope>provided</scope>
</dependency>
</dependencies>
Insert this to your build.gradle.kts accordingly:
repositories {
maven {
url = 'https://repo.marcely.de/repository/maven-public/'
}
}
dependencies {
compileOnly 'de.marcely.bedwars:Addons-API:Build-261025'
}